What software development actually costs
There is no honest single price for custom software, and any page that gives you one has made it up. What can be described honestly is what drives the number, which engagement models exist, and which costs proposals routinely omit — so you can read a quote and tell whether it is serious.
Why quotes for "the same" project differ by 5x
Send the same brief to five vendors and the range will be enormous. That is not usually dishonesty; it is that they have each imagined a different system.
One has quoted a WordPress theme with a form. One has quoted a single-tenant application with a shared admin login. One has quoted a multi-tenant platform with role-based access, audit logging, backups and a staging environment. These are wildly different pieces of software wearing the same one-paragraph description.
The way to compare quotes is to make them describe the same thing. Ask every vendor what happens when two users act at the same moment, who owns the code, what the deployment looks like, and what is excluded. The cheap quote usually becomes expensive at that point, or it stays cheap and you have learned what you were about to buy.
What genuinely drives the number
Data model complexity is first. The number of screens matters far less than the number of entities and the rules between them. A ten-screen application over four tables is small; a five-screen application over thirty tables with approval workflows is not.
Integrations are second and are consistently underestimated. Every third-party system — payment gateway, SMS provider, accounting package, government portal — has undocumented behaviour you will find at the worst time.
Concurrency and correctness requirements are third. Software where two people can act simultaneously on the same record costs meaningfully more than software where they cannot, because it has to be designed and tested for it.
Then compliance and audit needs, then the volume of admin tooling, which is invisible in mockups and is often a third of the build.
- Number of entities and the rules between them — not the number of screens
- Third-party integrations, each with its own failure modes
- Whether concurrent users can touch the same records
- Audit, history and amendment requirements
- Admin and back-office tooling — routinely a third of the work
- Data migration from whatever you use today
The costs proposals leave out
A build price is not a total cost of ownership, and the gap is where budgets break.
Hosting is ongoing. So are domains, TLS certificates where not free, email delivery, SMS and WhatsApp messaging, payment gateway fees, and any per-seat third-party service. AI features carry inference costs that scale with usage and are the line item that most often surprises people.
Then there is maintenance: dependency updates, security patches, the occasional platform migration. Software is not a capital purchase that sits still; it is closer to a vehicle than a building.
Which engagement model to choose
Fixed price suits genuinely known scope and punishes discovery. Time and materials suits evolving product work and requires trust. A phased engagement — firm price on a well-defined first slice, then re-scope with real information — is usually the honest middle, because the first phase is what teaches both sides the true cost of the second.
Whichever you pick, insist that payment milestones attach to working software rather than to calendar dates. A milestone you can log into is a milestone you can verify.
Frequently asked
How much does it cost to build an app in India?
There is no honest single figure, and price tables claiming otherwise are marketing. Cost is driven by the number of data entities and the rules between them, third-party integrations, concurrency requirements, audit needs and the volume of admin tooling. Get a written scope and a phased quote rather than a headline number.
Why is one quote so much cheaper than another?
Usually because the vendors have imagined different systems from the same brief — one a themed site with a form, another a multi-tenant platform with access control, backups and staging. Ask each to answer the same specific questions about concurrency, code ownership, deployment and exclusions, and the quotes become comparable.
What ongoing costs should we budget for after launch?
Hosting, domains, email and SMS delivery, payment gateway fees, any per-seat third-party services, and inference costs if the product uses AI. Plus maintenance: dependency updates, security patches and occasional platform migrations. Budget for the software continuing to need attention, because it will.
Should we pay fixed price or time and materials?
Fixed price when the scope is genuinely known and unlikely to move. Time and materials when the roadmap will evolve and you trust the team. For most first builds a phased approach works best: a firm price on a well-defined first slice, then re-scoping once both sides know more. Tie payments to working software, not dates.
Related
Want this built?
Tell us what you are trying to ship and we will tell you honestly whether we are the right team for it.