On this page
Asking what custom software costs is like asking what a building costs. The useful version of the question is: what is the smallest thing we can build, in what order, and what does each stage cost on its own?
What actually drives the price
- The number of distinct user roles and what each is allowed to do.
- Whether money moves through the system, and how it is reconciled.
- How many external systems must be integrated, and how good their APIs are.
- Whether existing data must be migrated, and how dirty it is.
- The amount of offline, real-time or compliance-sensitive behaviour.
- How much design work precedes the build.
What barely matters: the number of pages, the colour palette, and whether the logo is animated. Small interfaces over complicated rules are cheap; simple interfaces over complicated rules are not — the complexity moves, it does not disappear.
Why quotes for the same brief differ so much
Three quotes for the same description often price three different products. One includes testing on real devices, deployment, documentation and a warranty; another stops at “it works on my machine”. Ask what is included, and ask what happens in the first month after launch. That comparison is usually more revealing than the number.
Cheapest to build and cheapest to own are rarely the same quote.
Structure the engagement in stages
A sensible structure looks like this. First, a short discovery with a written scope and a fixed price for each milestone — not an hourly estimate that can drift. Second, a prototype or first vertical slice that proves the riskiest assumption. Third, the remaining milestones, approved as the earlier ones demonstrate the value.
- Discovery: days, not weeks, ending in a written scope and data model.
- Stage one: the core workflow, usable by real people.
- Stage two: integrations, reporting and the screens that support them.
- Ongoing: a defined support window, then an optional monthly plan.
Questions that protect your budget
- Who owns the repository, domains and cloud accounts on day one?
- What is out of scope, written explicitly?
- How do change requests get priced, and by whom?
- What is the post-launch warranty, and what does support cost after it?
- Can we export our data at any point, in a usable format?
A team that answers all five without hesitation is a team that has done this before. If any answer is vague, treat that as the price you are actually being quoted.
