Skip to content
Udyat Technologies
Cost guide7 min read

What custom software actually costs to build

The build is the deposit. The running cost is the mortgage, and it is rarely quoted.

Amit Kumar
Founder, Udyat Technologies
The short answer

Compare the second year, not the build. A cheap version one with no handover, no tests, and no documentation is the most expensive option available.

Software quotes vary enormously for what sounds like the same brief, and the variation is usually not margin. It is scope that was never made explicit — whether testing is included, whether the thing will be documented, whether anyone will still understand it in two years.

Rather than a number that would be meaningless without your requirements, here is what moves it and what to interrogate in any proposal you receive.

What drives the number

How many user roles

Each distinct role means its own screens, permissions, and edge cases. A single-role internal tool and a four-role system with a customer portal are different orders of work regardless of how similar the description sounds.

Integrations

Every external system adds work, and integrations to legacy software with no proper interface add a great deal. This is the most common source of overrun because it is the least specified up front.

Data migration

Rarely in the first quote and frequently the longest task, particularly where existing data is inconsistent.

How decided the process is

Building against a settled process is efficient. Building while the business argues about how it should work means building twice, and the second time is billed.

Ask about every one of these

The answers are what make two quotes comparable.

  • Who owns the code and the repository? The answer should be you, in writing.
  • Are automated tests included, or is testing manual and therefore skipped under pressure?
  • Is documentation in scope, or delivered as a handover call?
  • Who hosts it, and is that cost in the quote or arriving separately?
  • What does support cost after go-live, and what response time does it buy?
  • What happens if we want a different partner in year two?

The second year is the real comparison

A build quote is a one-off. Software is a commitment: dependencies need updating, browsers and platforms move, security patches arrive, and the business changes. That cost exists whoever built it and it is almost never in the proposal.

The cheapest version one is frequently the most expensive three-year total, because the savings come from exactly the things that make year two affordable — tests, documentation, a mainstream stack, a reproducible deployment. Ask any bidder what they expect year two to cost. A serious partner has an answer.

You are not buying software. You are taking on an asset that needs maintaining, and the quote covers the acquisition only.

FAQ

Custom software cost — questions we get asked

Why do quotes differ by several times for the same brief?

Almost always because the briefs are being read differently. One includes migration, testing, documentation and support; another covers building the screens described. Both are honest; only one is complete.

Is offshore or local cheaper?

Rate is the least interesting variable. Communication overhead, rework, and the cost of misunderstanding a process dominate — a cheaper rate that needs three clarification cycles is not cheaper.

Should we pay fixed price?

Fixed price is safer once scope is genuinely understood, which usually means after a paid discovery phase. Fixed price on a vague scope gets recovered through change requests, and everyone ends up unhappy.

Next step

Still weighing it up?

Most of these questions are quicker to settle in a conversation than in an article — particularly the ones where the answer depends on your numbers.