What drives the cost of custom software: reading the quote
How to read a software quote line by line, which lines predict the real total, and the questions that expose a price built on hope.
The short answer
A software quote is a set of assumptions with a number attached, and reading it well means finding the assumptions before looking at the number. What scope is included and what is written out. How integrations with your other systems are priced. Whether data migration from the current system appears at all. How much testing, documentation and launch support are in. What the hosting and maintenance cost each month afterwards. What depends on you, and by when. The lines that predict the real total are discovery, integrations, data migration and testing; a quote that shows them small or absent will grow, usually as change requests. Compare quotes on what they include, not on their totals. The cheapest one is cheapest because it left the most out.
Reading the quote line by line
| Line | What to look for | Warning sign |
|---|---|---|
| Discovery | A defined phase producing scope, risks and spikes before the build price is fixed | ”Included” with no description, or absent |
| Scope | Features named specifically, grouped by stage | A list of headings that could mean anything |
| Not included | Content, migration, integrations, training, hosting, support, listed explicitly | Missing |
| Integrations | Each named system, with mapping, error handling and testing | One line: “integrations” |
| Data migration | Profiling, mapping, rehearsal, reconciliation | Absent, or “import of existing data” |
| Design | Prototype and testing with users before build | Screens delivered with the code |
| Testing | Automated tests, review, acceptance criteria | ”Thorough QA” with no mechanism |
| Launch and documentation | Setup, runbook, hand-over documents | Absent |
| Hosting and running | Monthly, in your accounts, at provider prices | Bundled into a fee with no breakdown |
| Maintenance | Scope, cadence, response times, monthly cost | Absent, or hourly on request |
| Client dependencies | Decisions, content, access, with dates | Not mentioned |
| Change process | How changes are priced and traded | Not mentioned |
The questions that expose a price built on hope
- “What is not included?” The answer should be a list; a blank is the largest risk in the quote.
- “How did you price the integrations, and have you connected to these systems before?” Specific systems, specific experience.
- “What happens to our existing data, and what does that cost?” Migration is a line or it is a surprise.
- “What do you need from us, and by when?” Client dependencies with dates.
- “What does it cost per month after launch, and in whose accounts?” The running and maintenance lines.
- “How are changes handled?” A process, not goodwill.
- “Can you break the price down by stage so we can phase it?” A builder who can has planned it.
Comparing honestly
Rewrite each quote under the same headings from the table. Fill each cell with what the quote actually says, and mark empties. Ask each builder about their empties. Then compare totals for equivalent scope, plus twelve months of running and maintenance. Put fit, ownership terms and the quality of the answers next to the numbers. The decision is usually clear at that point, and it is rarely the lowest original number.
What this means for you
Read software quotes for their assumptions: what is in, what is out, how integrations and data are priced, what testing and documentation exist, what it costs monthly afterwards, what depends on you, how changes work. Compare under the same headings, not by total. Ask the seven questions. The quote worth accepting is the one whose author has already thought about the things that make projects overrun, and it shows in the lines they wrote rather than the ones they left blank.
Frequently asked questions
Why do two quotes for the same software differ so much?
Because they are for different amounts of work under different assumptions: one includes discovery, integrations, testing, documentation and a maintenance plan; the other assumes all of that happens somewhere else or not at all. The number is the last thing to compare. Rewrite both under the same headings first and the difference usually explains itself.
What is the most reliable sign of an underpriced quote?
Integrations and data migration shown as a single small line or not at all, and no not-included list. Those are the parts of software projects that overrun most, and a builder who has done them prices them visibly. A quote that treats them as trivial has either never done them or plans to charge for them later.
Should we ask for a breakdown?
Yes, by stage and by area: discovery, design, build per feature group, integrations, data, testing, launch, documentation, maintenance. A builder who can produce it has thought through the project; one who resists is asking you to trust a number. The breakdown is also what lets you phase the project when the total is too high.