Software project cost estimator
Work out an indicative budget and schedule range for a software build, with a breakdown by phase and an explanation of what drives the number.
Indicative budget range
—
| Phase | Share of budget |
|---|
A planning aid, not a quotation. Real quotes vary with scope detail, team seniority and contract type.
Runs entirely in your browser. Nothing is uploaded.
How the figures are produced
The estimator multiplies a base scope size for the product type by three factors: the number of platforms, a complexity multiplier, and a regional rate multiplier reflecting typical published agency day rates. Selected features add scope. The result is shown as a range because single-number estimates for software are almost always wrong.
North America is treated as the baseline. Western Europe typically quotes somewhat lower, Eastern Europe and Latin America lower again, and South Asia lowest of the five. These are broad market patterns, not quotes from specific firms, and the spread within any region is wide.
Why estimates vary so much
- Scope clarity. A written specification with screens and rules can be quoted tightly. "An app like Uber but for X" cannot.
- Design. Using an existing design system is far cheaper than bespoke design and research.
- Integrations. Each third-party system adds its own authentication, failure modes and edge cases. Legacy and enterprise systems add the most.
- Compliance. Healthcare, finance and anything handling children's data carry audit, documentation and testing costs that can exceed the build itself.
- Contract type. Fixed-price work carries a risk premium, usually 20–40%, because the supplier absorbs the uncertainty.
What the estimate leaves out
Budget for running costs after launch: hosting, third-party services, monitoring, and maintenance. A common planning figure is 15–25% of the original build cost per year for updates, dependency upgrades and small improvements. App store fees, payment processing, domain and certificate costs, and the time your own team spends reviewing work are all real and routinely forgotten.
Getting a sharper number
The fastest way to tighten a range is to write down the screens and the rules. A list of twelve screens with a sentence each about what the user can do, plus a note on which systems it must talk to, converts a guess into a quotable scope. A paid discovery phase — typically one to three weeks — is normal for larger projects and usually cheaper than the overrun it prevents.
Questions
Why is the range so wide?
Because scope is the dominant variable and it is rarely fully known at the start. The range narrows as the specification firms up.
Do these figures include design?
Basic interface work is included in the base scope. Tick the custom design option for bespoke visual design and user research.
Can I get a real quote?
Describe the project on the project enquiry page and it will be read by a person.
More tools
Browse all free developer tools or read the guides.