One founder, one brief, two software development quotes: SAR 95,000 and SAR 39,000. He has no way to know which number is real — and no way to know he's about to pick wrong.
Most founders respond the only way available to them. Collect a few quotes, drop the highest, keep the lowest in play, settle somewhere that feels safe. It looks like diligence. It only works if the numbers measure the same thing, and they almost never do. At least one of those numbers was never about his project.
Why comparing quotes feels rational
If you can't read code and haven't built software before, price is the one part of a proposal that looks comparable across agencies. Scope documents vary in format, portfolios are curated, and timelines are always estimates anyway — but two numbers sit on the same axis, and weighing them requires no technical background at all.
So the comparison itself is rational. When price is the only dimension you can read, of course you use it. The problem sits inside the tool's assumption: that both agencies priced the same project.
What a software development quote actually is
A quote is the agency's understanding of your project, expressed as a number. The price is just the format.
Everything the agency understood about your brief flows into that figure, and so does everything they missed. The edge cases they thought about. The integrations they noticed. The parts of your operation that sound simple in a sentence and take weeks to build correctly — a brief that says "employees order lunch" can hide a concurrent stock reservation problem that most teams never see until it breaks in production.
Read the SAR 95,000 and the SAR 39,000 again with that in mind. What you are looking at is two readings of one brief. A low reading is rarely a discount. Usually it means a smaller project got priced — one that happens to share a name with yours.
Where the missing SAR 56,000 goes
Follow the cheap quote after signing, and I've watched this pattern repeat often enough to describe it before it happens, not after.
The project starts without three things, because producing them was never part of the price:
A scope document stating what will exist when the work is finished
A definition of "done" for any individual stage
Any boundary on change requests — no count, no process, no limit
From there, the structure of the engagement does the rest. Most of these contracts in the Gulf start the same way: a deposit up front, milestones described in a sentence or two, no written definition of what closes a stage. The client works stage by stage, reasonably: he cannot specify the next step until the current one is finished and in front of him. Except the current one is never finished, because
"Done" was never defined. Anywhere. By anyone. For anything.
Nothing in the project has an edge, so every stage bleeds into the next. The developer is convinced the client keeps growing the work. The client is convinced the developer never finishes anything. Both are right. Both are stuck inside a build that now feels endless from either side.
I've sat across the table from founders on both sides of this — the ones who underpriced and the ones who got underpriced. It tends to end the same way: no delivery, a dispute over what was owed, and months gone on both sides while the product still does not exist. The SAR 56,000 saved at signing was repaid in full. It just never appeared as a line item anyone could point to.
What to compare instead
Nothing in a proposal is less informative than the number at the bottom of it. Three things carry more signal:
Scope clarity in writing. Does the proposal state specifically what will exist at the end — down to the exact features, the exact flows, the exact third-party services it needs to talk to? An agency that prices a vague scope is pricing its own way out.
Delivery track record. Finished projects you can verify, with clients you can actually reach. A portfolio page is not that; the signals worth checking are visible before you sign anything.
Contractual accountability. What the contract commits to on deliverables, ownership, and change requests. Structured change handling is real; it can be built into how a project runs from day one, and an agency that has it will show you. An agency that quoted low tends to go quiet here, because boundaries are exactly what the low number cannot afford.
An agency that gives you all three alongside a higher number has priced your actual project. One that hands you a lower number without them has quoted a vaguer, smaller project — one that grows back to full size after the deposit clears.
The cheapest quote is rarely the lowest number
None of this means the highest bid wins. An expensive proposal wrapped around a vague scope carries the same risk with a larger deposit. A software development quote is worth exactly what the scope behind it is worth, and no more.
The founder holding the SAR 39,000 quote was not being offered a bargain. He was being offered a project one-third understood, with the other two-thirds left to be negotiated later — from a weaker position, with money already spent.
Comparing the two numbers side by side was never going to answer his real question. Scope in writing, a track record he could verify, and a contract that named its own boundaries would have.
