How much does an app cost in 2026?
There is no single number, but there is a method. Here is how we turn a rough idea into a range you can plan around, and what makes that range move.
“How much will it cost?” is the first question every client asks, and the honest answer before scoping is a range. That is not evasion. A price quoted before anyone understands the problem is either padded to be safe or optimistic to win the work, and both are worse for you than a range.
We price hours, not features
Everything we size starts as engineering hours, because hours are the thing we can reason about from experience. We know roughly what payments, offline sync or a document pipeline has cost us before. Money comes last: hours multiplied by our rate, which on our estimator is $20 an hour. Keeping the rate separate means you can argue with the scope and the rate independently, instead of staring at one opaque figure.
What a small, medium and large build actually mean
Small: one platform, one core journey, a handful of screens and no external systems to integrate. Typically a few hundred hours.
Medium: accounts, payments or a second user role, some real business logic, and one or two integrations you do not control.
Large: several roles, an admin surface, live data, and compliance or reporting obligations that shape the architecture rather than sit on top of it.
Most enquiries that arrive describing a “simple app” are medium, and the reason is almost always the same: the app is simple, but the business behind it is not.
The things that move a price
Integrations with systems we do not control. Their timelines, sandboxes and outages become yours.
Compliance discovered late. Rules that arrive after the architecture is fixed are the single most expensive kind of change.
A second platform, which costs less than the first because the domain model, API and design system already exist — but is never free.
Unclear decision-making on your side. In our experience this causes more overrun than any technical problem.
What the estimate does not include
Third-party costs you pay directly: hosting, app store fees, payment processing, paid APIs and licensed assets. We size these with you during scoping so they are not a surprise in month two.
Use the range, then narrow it
Our estimator gives you an indicative range in a couple of minutes, built from the hours similar projects actually took. After a scoping call the number should get more precise rather than larger. If an estimate only ever moves upward once work starts, that tells you something about how it was produced.
Keep reading
Native or cross-platform: how we actually choose
We default to Flutter for cross-platform work and go native when the project earns it. The decision comes from constraints, not fashion.
What an MVP should actually contain
Most MVPs fail because they are either too small to prove anything or too large to ship. Here is how we decide what goes in.