What custom software actually costs in 2026

Nobody publishes software pricing, so every buyer starts from zero and concludes that quotes are arbitrary. They are not — they are mostly driven by five decisions, and you control four of them.

Rough bands

For a competent North American or nearshore team, delivered properly:

Scope	Typical range (USD)
Single-purpose internal tool	$9k – $25k
Line-of-business system, one department	$25k – $75k
Multi-role platform with integrations	$75k – $200k
Regulated or multi-tenant product	$200k+

Offshore-only shops quote below these. Large consultancies quote two to four times them. Both can be the right answer; neither range is evidence of quality by itself.

The five decisions that move the number

1. How many user roles. Each distinct role is a separate set of screens, permissions and test paths. Going from one role to three rarely triples cost, but it is closer to doubling than most people expect.

2. How many integrations, and whose. A documented REST API with a sandbox is a day. An undocumented SOAP endpoint at a vendor who answers email weekly is a month, and the risk is not yours to control.

3. Whether you need offline. Local-first data with conflict resolution is a genuine architectural commitment, not a feature flag. Worth it for field work, expensive everywhere else.

4. Who owns data migration. Importing fifteen years of spreadsheets where the same client is spelled four ways is frequently the single largest line item, and it is almost always underestimated because it looks clerical.

5. Compliance scope. HIPAA, SOC 2, PHIPA and PCI each add real engineering and documentation work. Decide early — retrofitting an audit trail is dramatically more expensive than designing one in.

Where budgets actually go wrong

Not in the build. In two places either side of it:

• Scope that was never written down. If the proposal says “reporting dashboard” without naming the reports, you have not agreed on anything and both sides know it.
• Nobody budgeted for year two. Software has a running cost: hosting, dependency updates, the small changes that keep it useful. Assume 15–20 per cent of build cost annually. A system nobody maintains becomes a system nobody trusts.

The question worth asking first

Before any of this: should this be custom at all? If an off-the-shelf tool covers 80 percent and the remaining 20 is not where you compete, buy the tool.

Custom software earns its cost where your process is the advantage — the quoting logic nobody else uses, the compliance trail your regulator expects, the three systems that have never spoken to each other. We will tell you which case you are in, including when the answer costs us the project.