How to read a software development quote
By the YAVI Solutions team · Published
What a good software quote contains, the vague phrases to question, and how to compare two quotes for the same project.
Key points
- Scope and acceptance in plain words.
- Exclusions should be written down.
- Confirm code ownership.
Scope
A list of what the software will do, written so a non-developer can check it. If you cannot tell whether a feature is in, ask.
Acceptance
How both sides will agree something is finished. Without this, "done" is a matter of opinion.
Assumptions and exclusions
Good quotes state them. Typical exclusions are data migration, third-party fees, content and training.
Phrases to question
"Standard functionality", "as required", "etc." and "reasonable changes". Ask for each to be replaced with a list or a number.
After delivery
Warranty period for defects, who hosts it, what maintenance costs, and who owns the code.
Comparing two quotes
Put their scope lists side by side. The cheaper quote is often the one that has left something out.
Related
Start the software questionnaire
Want to talk it through? Call 0422 222 267 or request a callback.