"How much does an app cost?" is a fair question with an unhelpful answer: it depends. A booking app for one small business and a booking platform for a hotel chain share a name and very little else. Any price quoted before understanding the scope is a guess, and guesses turn into arguments later. So we estimate from your real requirements, and we explain how.
How an estimate is built
- Discovery. A call and, for larger projects, a short workshop. We learn what you need, who will use it and what already exists.
- Written scope. We list the features, user roles, integrations and assumptions, plus what is out of scope.
- Breakdown. Each part is estimated by the people who will build it, with AI speed-ups applied where they are real, not everywhere.
- Milestones. The work is grouped into milestones that each deliver something usable, each with a fixed scope, price and timeline.
- Risks. We call out the parts that are uncertain, such as unknown APIs or unclear data, and how we handle them.
What drives cost
Most of the difference between a small and a large budget comes from a handful of factors. Knowing them helps you decide where to spend.
-
Number of features and screens
The biggest single factor. Each workflow needs design, build and testing.
-
User roles
Each role with its own screens and permissions multiplies the work.
-
Integrations
Every outside system brings its own API, limits and failure cases.
-
Data work
Migrating, cleaning or connecting large or messy data takes real time.
-
Security and compliance
Payments, health, finance and personal data add review and controls.
-
Platforms
Web, iOS and Android each add effort, even with shared code.
-
AI features
Model testing, review workflows and usage costs need planning.
-
Deadlines
Very tight deadlines can require more people working in parallel.
Why fixed-scope milestones
A single fixed price for a large project forces everyone to pretend they know everything up front. Open-ended billing leaves you guessing. Milestones sit in between. Each one is small enough to define clearly and price firmly. You see working software at the end of each one and decide whether to continue, adjust or stop. For evolving products, we also offer ongoing development.
How AI changes the numbers
AI reduces the time spent on repetitive work such as standard screens, integrations, tests and documentation. That lowers the cost of most projects compared with a traditional build of the same scope. It does not reduce the time needed for discovery, design decisions, unusual logic or waiting on outside parties. Our estimates show where AI helps on your project so you can see the reasoning. Read how AI changes development cost for more.
Running costs after launch
Estimates also list expected running costs: hosting, third-party services, AI model usage and app store fees. These are paid directly by you to the providers, in your own accounts, so there are no hidden margins. We help you choose plans that fit your size.
Ways to lower the cost
- Start with a smaller first release, such as an MVP, and add features after real users try it.
- Use proven off-the-shelf services for commodity features like payments, email and login.
- Prepare content, data samples and access to systems before work starts.
- Have one decision-maker available to answer questions quickly.
What you will not see
No hourly rate hidden inside a fixed price, no charge for small clarifications within scope, and no surprise invoices. If something outside the scope comes up, you get a written change request with its cost before any work starts. For typical ranges and examples, read our guide on what a web app costs and how long an app takes.