<knowledge_base_/>

How to read a software quote (and the red flags)

Choosing and buying 9 min read published

A good software quote describes what will be built, what is not included, who ends up owning the code, and what happens if it overruns. If one of those four is missing, that is not sloppiness — it is a choice.

What belongs in it

  • A description per component, not one line saying "build webshop".
  • What explicitly falls outside the scope.
  • Who ends up owning the source code, the domain and the data.
  • What happens with extra work, and whether you get a price for it up front.
  • A schedule with the moments at which you have to supply something.
  • What applies after delivery: warranty, maintenance, and whether it is compulsory.

The red flags

A quote with no breakdown. If there is one amount under one sentence, you cannot compare anything and cannot check anything.

"From" in the price. That is not a price, that is an opening bid.

Not a word about ownership of the code. That usually means the answer will not please you.

Compulsory maintenance as a condition of delivery. Maintenance is fine; making it compulsory is a lock on the door.

What to ask before you sign

Ask for an example of an earlier quote for a comparable project, with the client name removed. Anyone who cannot or will not show one usually has a reason.

Ask who will actually work on it and whether those are the same people as in the meeting. Finally, ask what happens if you jointly decide halfway that it is not working.

<next_step/>

QUESTIONS AFTER READING_

Question not covered? Just call. You will get an honest assessment — even if the answer is that you should do something else.