The same brief, quoted ten times apart
A ten times spread is not evidence that somebody is lying. It is evidence that each firm is quoting a different project, because the brief did not say enough to pin one down. The cheap quote is usually narrower, excludes integration, or prices a demonstration.
Cheapest to most expensive quote for the same requirement, market average marked. Log scale.
Source: ivector, Custom software costs in 2026
The number you are quoted is not the number you pay
A build quote covers building it. Most of what the software costs you arrives after it works, and it arrives every year. Annual maintenance commonly runs 15 to 25 percent of the original build cost: five independent publishers land in the same band.
As a percentage of initial development cost.
Source: VendorBenchmark, Pharos Production, Monterail, Trawlii, Mobisoft
Published figures put the 24 month total for AI deployments at 1.6 to 2.2 times the build cost once inference and retraining are counted. Inference is charged by use, so the bill grows when the thing succeeds.
What AI integration costs →Build projects run about 38% over on cost and 42% over on timeline.
One thing reliably predicts whether it lands on budget
Not the firm you pick, and not the technology. Whether the requirement was worked out before anyone committed to building it. Worth saying plainly: this figure is published by a firm that sells discovery, and we would do the same work. Treat the direction as sound and the exact numbers as indicative.
Source: Mobisoft Infotech, from its own project data
Five questions to ask before you sign anything
These work on us as well as on anyone else, and they are the fastest way to tell a scoped project from a hopeful one.
- 1
What is the three year total, split into build, running and change?
A quote that covers only the build is not a cost, it is a deposit. A firm that cannot produce the three year figure has scoped a demonstration rather than a project.
- 2
What is excluded, in writing?
Testing, monitoring, integration and post launch support are where a low number hides its real cost. Get the exclusions listed rather than described.
- 3
Who maintains this in year two, and have they been told?
The answer is revealing more often than it should be. A system nobody has been assigned to is a system that degrades quietly.
- 4
What happens to the number if the requirement changes?
Requirements always change. What matters is whether the contract treats that as a costed change with an agreed rate, or as an argument.
- 5
What would make you tell me not to build this?
If a firm has no answer, they have no criteria, and you are the one carrying the risk of a project that should not have started.
Most published cost data in this category is produced by firms that sell the work, so it is not disinterested. Where several independent publishers agree, that is noted. Ranges are quoted as ranges because that is how they were published.
Because the brief is usually underspecified, so each firm is quoting a different project. A low quote often assumes a narrower scope, excludes integration, testing, monitoring and post launch support, or prices a demonstration rather than a production system.
Want the number for your case?
Describe what you are trying to build and we will tell you what it would take, what it would cost, and whether it is worth doing at all.