Before you ask: what to have clear
- The problem, in one sentence. What is costing you hours or money today, and what you would like to happen instead.
- How it is done now. Who is involved, with which programs and which spreadsheets.
- What must not change. The ERP, the invoicing program or the way the warehouse works.
- Who will use it. Three people in the office, the whole sales team, or your customers too.
- The data you already have. Where it is, how many years of it, and whether anyone trusts it.
- Whether a date is driving it. A campaign, a change in regulation or an old program that will stop working.
You don’t need a requirements document. With this, in a half-hour conversation a supplier can already tell you whether it is clear to them or whether they need to look at it more carefully first.
What a quote should include
- The scope, by feature. What the software will do, piece by piece, written so that the people who will use it can understand it.
- The price of each piece and the total. And if it is by the hour, how many hours there are and what happens when they run out.
- What is left out. This is the part that saves the most arguments: if it isn’t there, everyone imagines something different.
- The timeline and the deliveries. When you will see the first thing working and how often there will be a new one.
- What you have to provide. Access, data, content and one person who tests each delivery.
- How it is paid. How much up front, how much at each delivery, and how long the quote is valid.
- The day after. Hosting, maintenance and changes: what they cost each month and whether there is a minimum term.
- Who owns it. The code, the domain and the accounts, and where the data will be kept.
If the accepted quote is going to act as the contract, read it as a contract. We are not lawyers: if you have a legal question, have it reviewed.
How to compare two quotes that look nothing alike
- Put them side by side by feature, not by total. Make a list of everything that appears in either one and mark who includes it.
- Look at what each one leaves out. Bringing over the old data, the connections to other programs and the training are what is missing most often.
- Look at who carries the risk. With a fixed price, if the work runs long that is the supplier’s problem; with estimated hours, it is yours.
- Add what is paid every month. Compare what you will have paid after a few years, not just on delivery day.
- Ask what happens if you walk away one day. If the code is yours, you can carry on with another supplier; if not, you start again.
If after all this one of the two is still much cheaper, ask why. Sometimes there is a good reason; other times, the work simply hasn’t been understood.
When a quote can’t be given straight away
Some work can’t be quoted properly after a single conversation: when more than one system is involved, when nobody knows for certain how the process is done today, or when what is being asked for is to put things in order rather than one specific tool.
In those cases, a serious supplier will suggest a step first: a prototype to check that they have understood the problem, or a study that ends in a phased roadmap, with a price for each phase. A fixed price given blind ends badly for someone: either the supplier gets burned and cuts corners, or they set it high enough to cover themselves.
Warning signs in a quote
- A single line with a total, without saying what it covers.
- Estimated hours with no cap.
- Not a word about what is paid after handover.
- It doesn’t say who owns the code.
- It arrives the same day, without anyone having asked how you work.