Answer
How much does app development cost — and why nobody can answer without asking
There is no price for an app, only a price for a scope. This page does not invent a range; it teaches you to read a quote: what raises cost, what lowers it, and where the gap between two quotes actually hides.
We will not publish a price table here, and not out of evasion. Any number we print would be right for some cases and wrong for most, and if you decided on the strength of it you would pay for the error. What can be given is the variables that actually set the price, and that is what will genuinely help you in a conversation with a supplier.
Why can't anyone give a number?
Because "an app" describes six weeks of work and two years of work using the same word. An app that displays content and lets someone get in touch is not from the same world as one with payments, permissions, notifications and an admin panel — and the gap between them is not measured in percentages.
What actually raises the cost?
The surprise for most founders is that screen count is not the main driver. What raises cost is the number of states the system has to handle, and that grows faster than the number of screens.
| Factor | Impact | Why |
|---|---|---|
| User types | Very high | Each multiplies permissions, screens and testing |
| Payments | High | Refunds, failures, invoicing, regulatory fit |
| Two platforms | High | Separate development, testing and release for each |
| External integrations | Medium to high | Each adds failure states that must be handled |
| Screen count | Relatively low | Another screen in the same pattern is cheap repeat work |
That is why a request like "let's add an admin user too", which sounds small in a meeting, is usually more expensive than adding five screens for a user type that already exists.
How do you read a quote?
When two quotes arrive with a large gap, the difference is almost never margin. It is the scope each side understood, so the first question is not "why are you expensive" but "what exactly is included". Ask explicitly for four things.
- What is explicitly out of scope — that list reveals more than the list of what is in.
- Whether failure states, testing and store submission are included or priced separately.
- What happens after delivery: the warranty window, and what counts as a defect rather than a change.
- Exactly who will work on the project, and whether you will speak to them directly.
A quote materially cheaper than the others is usually a quote for a different scope rather than an opportunity. We set out the clauses that decide what happens when something goes wrong in what to check in the contract, and the variables that drive schedule in how long an MVP takes.
What can you actually do to lower it?
Three moves lower cost without lowering quality, and all of them happen before work starts. The first is narrowing to a single user type in version one. The second is dropping a second platform until there is evidence you need it. The third is using existing services for authentication and payments rather than building your own.
What almost never pays to economise on is testing and failure states. They look like a comfortable place to save because they cannot be shown in a demo, and they are what determines whether the product survives contact with real users. Saving there returns as work within weeks, usually at a higher price.
In short
- There is no price for an app, only for a defined scope.
- User types and payments raise cost more than screen count.
- A gap between quotes is nearly always a gap in the scope each understood.
From our own work
When a client sent us and another supplier the same written scope document with an explicit "not included" list, the gap between the quotes narrowed dramatically — which showed the original gap was in understanding rather than in price.
Recurring questions
Why are two quotes for the same project so far apart?
Almost always because they price different scopes, not because one is exploiting you. One supplier assumed the design exists, another priced it; one included testing and store submission, another did not. The only way to compare properly is to send both the same written scope document and ask for an explicit statement of what is excluded.
Is a fixed price better than hourly?
A fixed price suits a clear, closed scope and transfers estimation risk to the supplier, who will price it accordingly. Hourly suits a scope that will emerge as you go, and requires you to track it. In practice the combination that works is a fixed price for a short definition phase, and only then a closed quote for development.
What does it cost after launch?
There are two separate costs worth planning for: infrastructure and third-party services, which are monthly and grow with usage, and maintenance — fixes, operating system updates and small changes. Many founders budget the build and forget both, and both arrive in the first month.
Sources
- The top reasons startups fail — CB Insights (2026-08-10)
Keep reading
Answer
How to choose a software house — five questions that filter fast
A portfolio shows what came out, not how it was made. Five questions about decisions, people and the contract filter suppliers faster than any introductory meeting, and all fit in one call.
5 min read ·
Article
How to hand a project to another team without losing a month
What stalls a handover is almost never the code. It is the accounts nobody recorded ownership of, and the knowledge that lived in one person's head and was never written down.
8 min read ·
Answer
Why work with Israeli developers on a startup — and when not to
The clear advantage is early-stage product experience and a direct communication culture that shortens cycles. The clear disadvantage is a materially higher price than offshore, and that is a decision rather than a detail.
5 min read ·