By Ryan Richardson · 14 November 2026
Read a software quote one part at a time, in the order it is printed, and ask the builder what each part assumes and what it leaves out. Do it on a half-hour call before you sign anything, because a price only makes sense once you know what it was worked out from.
The scope is the list of screens and features, and every number after it is priced on it.
Look for money and weeks next to each line, rather than one total at the bottom. Then find the assumptions, the things the builder took as given, such as who writes the words on the screens. Each one can move the price.
With two quotes, put both splits side by side and see which line holds the gap.
Look for a section headed exclusions or not included. If there is none, ask for one in writing.
Check whether monthly hosting fees, app store fees, moving your old records across and writing the words on the screens are inside the price or outside it. For anything outside, ask who pays and roughly how much a month.
Find the clause on changes. Look for a written rate and a rule that nothing extra is billed until you have agreed to it in writing.
Look for names in the quote, not job titles.
Ask, "Who's doing the work, which parts does each person own, and will they be on the call?" A fair answer gives names, parts and rough hours a week. Get the names in writing before you sign, not in week nine when the person you trusted has moved to another account.
Look for a sentence saying the code belongs to you once it is paid for. Check that the hosting, the web address and any app store accounts will sit in your business's name.
Ask for access to the code from the first week, so another builder could pick it up if you ever needed one.
Look for each payment tied to something you can see working, rather than to a date on a calendar.
Ask for two dates, the day a real person first uses a rough version and the day it is finished. On a six month quote with one date, nobody learns anything until launch. A rough version in front of ten people at week eight is where the learning starts. If the two dates are the same, ask why before you sign.
Look for how long the builder fixes faults for free after handover, who keeps the app running after that, and the monthly cost.
Ask who you call on the day something breaks, and how quickly they answer.
Ask, "What would you need to ask me, to be sure this is the right thing to build?"
Good builders ask back, about who uses it and what happens on the day it works. If they have nothing to ask and can start Monday, they will build your written description exactly as written.
An operations lead needed a tool built. He wrote everything down, with examples and ideas for how it might work, as context for the team. The team read it as the thing to build and built all of it. What he wanted, and never said because it felt too obvious, was a light tool he could update every few weeks as site processes changed.
The conversation that would have caught it took thirty minutes. Someone laid out what could come out to make it simpler, and he said yes without hesitation. What had to be built dropped by ninety percent, and the solution that had been six months in progress was rebuilt in a day.
Any builder who priced his document would have got the sum right, for six months of the wrong thing, since a quote can only price the description it is handed.
The full story, and the reasoning behind most of the builder questions above, is in my $5 book, Turn Your Expertise Into a Product. All my prices are in US dollars.
Paste these three sentences into an email to the builder.
Before I sign, I'd like a half-hour call on how the price was put together. Please bring the people who will do the work. I'd also like two dates, the day a real user first touches a rough version and the day it is finished.
Send it today, before you sign anything.
Not on price alone. A cheap quote can be cheap because someone quietly trimmed the part that is yours, the one piece nobody else can supply. Look at the size of that line before you look at the total.
No. You are not scoring the builder's technical design, and you could not if you tried. You are checking whether the number came from a conversation about your business or from a written description you put together before that conversation.
You won't always get a clean read. Ask the same questions in a second meeting and see whether the answers hold their shape.
That needs a different first step, a written list of what is left. I cover it in what to do when a software build is stuck at 80 percent.