5 things to check in a software quote

Most software quotes are written in good faith. Still, a few points come up again and again where a little clarity upfront saves both sides trouble later. Here are five to check before you sign.

1. Features described in one line

"User management" or "admin panel" can mean a day of work or a month. If a feature is described in a single line with a large number of hours next to it, ask the vendor to break it down into the screens and actions it includes.

2. A large "miscellaneous" or "contingency" line

Some buffer is reasonable and often sensible. If the line is large, it helps to understand it. Ask what it covers, and whether unused contingency is returned.

3. Nothing about hosting, maintenance or support

If the quote stops at launch day, the running costs will arrive later as separate bills. Ask for a yearly figure for hosting, maintenance and support, in writing.

4. No mention of who owns the code

You should own the source code, designs and all accounts (domain, hosting, app stores) once you have paid. If the quote is silent on this, ask for it to be added to the contract.

5. Hours that ignore today's tools

AI-assisted development has made many routine tasks much faster. If a quote prices standard features, such as login, forms or basic dashboards, as if every line were written by hand, it is fair to ask how the estimate was made.

What to do next

None of these mean the vendor is acting in bad faith. They are simply the questions to ask before you commit. If you would like an experienced reviewer to go through your quote line by line, send it to us.