What does custom software cost? What actually drives the price
Why quotes for the same project differ by a factor of five, which six factors really determine the price, and how to buy custom software without an open-ended budget.
Ask five providers for a quote on the same idea and you will get numbers that differ by a factor of five. That is not dishonesty — it is that nobody has defined what is being built.
This article explains what drives the price and how to buy so the budget cannot run away.
- Integrations and edge cases drive cost far more than screens do.
- An undefined scope is the single biggest cause of overruns.
- Buy in stages: scope, quote, release, then decide on the next stage.
- Cheap builds are usually rebuilt within 18 months.
The six real cost drivers
- Number and age of systems to integrate. One modern API is easy; three legacy systems are not.
- How many exceptions the process has. The happy path is cheap; the twelve special cases are not.
- Data quality and volume at the start.
- How many roles and permission levels the system needs.
- Regulatory requirements — audit trails, retention, approvals.
- How precisely the process is described before the build starts.
Only the last one is fully in your control — and it is the one with the largest effect on the final invoice.
Why an audit before a quote saves money
A quote written from a two-hour conversation is a guess, and guesses are padded. A quote written after a structured process audit is based on documented workflows, a listed set of integrations and a known set of exceptions.
That is why we quote the audit first as a fixed price, and everything after it on findings. The audit output — the process map, the automation inventory, the costed architecture — belongs to you whether or not we build anything.
Pricing models, and what they cost you
We work with the third model: each stage scoped, quoted, approved, released to production. If a stage does not deliver, you stop after it rather than after two years.
| Model | What it means for you |
|---|---|
| Time and materials | Flexible, but the risk of scope creep sits with you. |
| Fixed price, whole project | Predictable, but heavily padded and rigid to change. |
| Fixed price per stage | Predictable per step, scope revisited between stages. |
| Monthly retainer | Fine for evolution, dangerous as a way to build the first system. |
The cost of building it cheaply
The lowest bid usually wins by leaving things out: tests, documentation, error handling, permissions, the exceptions. Everything works in the demo and falls apart in month four with real data.
The rebuild then costs more than the correct build would have, plus the months lost. This is the most common story we hear from companies coming to us with a system somebody else built.
What to ask before you sign
- What exactly is in this stage, and what is explicitly not?
- Who owns the source code, the data and the documentation?
- What happens if we want to work with someone else in a year?
- What does year three cost — hosting, support, changes?
- Can we see the system running in production, not just in a demo?
Frequently asked
- What is a realistic budget for a first operational system?
- For a mid-sized company, the first production module is typically a five-figure euro investment, staged. Full operational systems with several agents grow from there, one funded stage at a time.
- Are cheaper offshore rates worth it?
- The hourly rate is only one factor. What decides total cost is how well the process was understood before coding started — which is where distance, time zones and language usually cost more than the rate saves.
- Can we build in phases to spread cost?
- Yes, and it is how we work by default. Each stage produces something usable in production before the next one is quoted.
What this actually means for your company
Imagine the recurring work — quotes, invoices, documents, follow-ups, reporting — simply being done. Not by a bigger team, not by another subscription, but by a system that knows how your business works. Your people stop feeding software and go back to the work you hired them for. That is the whole point.
How this went for me
I ran operations where every day started with the same twenty small tasks. We hired more people, bought more tools, and the admin load still grew faster than the revenue.
The turning point was not a smarter tool. It was writing down how the business actually runs and building one system around it — then letting AI agents work inside that system. Within a few months the daily paperwork was no longer a leadership problem, and we could finally think three months ahead instead of three hours.
That is the only reason DND Systems exists: to do the same thing, properly engineered, for companies that recognise this situation.
Tell us how your business runs today
Write one email describing your day-to-day operation. You get an honest answer on what can be automated, what should stay human, and what a realistic first step would cost. No call centre, no sales sequence.
We reply within one business day, in English, Spanish, French, Portuguese or Russian.
