What Custom Software Actually Costs in 2026 — A Line-by-Line Breakdown
Why identical briefs get wildly different quotes
Three things explain almost all of the spread: where the team sits, what the vendor assumed you meant, and how much risk they are pricing in. A brief that says 'user management' might mean email login or might mean SSO with SAML, role hierarchies, audit logging and SCIM provisioning — a difference of weeks. Vendors who ask a lot of questions before quoting tend to come in higher and change less later. Vendors who quote in two days from a one-page brief tend to come in lower and rebuild the number through change requests.
Blended rates by region, honestly stated
As of 2026, blended engineering rates run roughly $110–$220 an hour in the US and Western Europe for established agencies, $60–$110 in Eastern Europe, and $28–$60 in India for teams with strong English and delivery track records. Gulf-based delivery typically sits between European and offshore rates, often with a local account layer over an offshore build team. Rate is not cost, though — a cheaper team that needs 1.6x the hours and a rewrite in year two is not cheaper. Ask for velocity evidence, not just a rate card.
What a typical build actually contains
For a mid-sized business application — say a customer portal with role-based access, workflow, integrations to two existing systems, reporting and an admin back office — expect roughly 900 to 1,600 engineering hours. Design is usually 10–15% on top. QA is 20–25% if it is done properly rather than by the developers on Friday afternoon. Project management is 10–15%. DevOps and environment setup is a fixed 60 to 120 hours that everyone forgets. Applying regional rates to that gives you a realistic corridor rather than a number pulled from a calculator page.
The four things that reliably blow budgets
Integrations with systems nobody has documentation for. Data migration from a legacy database where the same customer exists four times with different spellings. Compliance requirements discovered in month three — accessibility, data residency, sector rules. And unbounded stakeholder review, where a new executive joins in month four with opinions. Every one of these can be de-risked cheaply upfront: a two-week discovery that inspects the actual legacy data and the actual APIs typically costs 3–5% of the project and prevents the 30% overrun.
Fixed price, time and materials, or capped
Fixed price makes sense only when the scope is genuinely fixed and well understood — a defined integration, a migration with known endpoints. For product development, it converts every conversation into a negotiation about whether something was in scope, which is a terrible way to build software. Time and materials with a capped budget per phase and a documented change process is what works for most engagements. Whatever the model, insist that you own the repository and the cloud accounts from day one.
Budget for after launch, because most people don't
Plan on 15–25% of the build cost per year for hosting, dependency upgrades, security patching, small enhancements and support. Software is not a capital purchase that sits still. Teams that skip this line for two years end up needing a modernisation project instead, which costs far more than the maintenance would have. If a proposal has no ongoing figure in it, that is a sign the vendor is thinking about the sale rather than the system.
How to get a comparable quote from three vendors
Write one brief with the same user stories, the same integration list, the same non-functional requirements and the same assumptions, and require each vendor to quote against it with an hours breakdown by workstream. Ask each to state what they excluded. The comparison then becomes meaningful, and the excluded lists will teach you more about the project than the prices do.
Have a project that needs this kind of thinking?
Let's talk through what you're building — free consultation, no commitment.
Get in Touch