Answer in brief
Compare quotes for a digital service by scope, not by total. Ask each supplier to state deliverables, assumptions and exclusions, check that discovery, testing, revision rounds and handover are either included or priced, and put the answers into one table. The quote with the fewest unstated lines is usually the cheapest by the end of the project.
Why the lowest quote is often the most expensive one
Two quotes for the same website can differ by a factor of three and both be honest. The difference is rarely the hourly rate. It is what each supplier decided to leave out: research, copy, testing, the second round of changes, the handover. A quote is a description of work, and a short description is cheap to write and cheap to read.
The trap closes later. The missing work does not disappear. It comes back as a change request, as a second contractor hired to finish the job, or as a month of your own evenings. By then the first invoice has been paid and the comparison you made at the start no longer describes anything real.
The way out is not to choose the highest price instead. It is to make every supplier describe the same job, so that the totals can be compared at all. The rest of this guide is a method for doing that with one page of questions and one table.
Three things a quote must name before its total means anything
The first is the deliverable: what you will hold at the end and in what form. “A landing page” is a wish. “One responsive page, copy edited from your draft, the enquiry form connected to your CRM, source files and account access handed over” is a deliverable. The second version costs more on paper because it contains more work, not because the supplier is greedy.
The second is the list of assumptions. Every estimate assumes something about you: that texts and photographs arrive on time, that one person approves the work, that access to the domain exists. Each assumption is a place where the price can move. A supplier who writes them down is showing you where the risk sits before you pay for it.
The third is the list of exclusions. A quote with no exclusions is not generous, it is unfinished. Hosting, licensed fonts and images, translation, data migration and legal texts are the usual candidates. When they are named, you can decide who does them. When they are not, you will discover them one invoice at a time.
Discovery is a line in the budget, not a favour
The GOV.UK Service Manual opens its description of the discovery phase with a plain rule: before you commit to building a service, you need to understand the problem that needs to be solved, and you should not start building during discovery. For public services it calls four to eight weeks typical. A small commercial project needs days rather than weeks, but the order of the steps is the same.
The U.S. Digital Services Playbook says the same thing in budget language. Its checklist for structuring contracts asks that the budget includes research, discovery and prototyping, and that the contract requests frequent deliverables rather than milestones months apart. Both documents were written for government teams. The logic applies to a ten-page website as well as to a tax service.
So when discovery is absent from a quote, ask which of two things is true. Either the supplier does that thinking unpaid and recovers the cost elsewhere, or does not do it and builds from a guess. Neither is a saving. A short paid discovery with a written result is the cheapest stage of any project to get wrong, and the most expensive one to skip.
Revision rounds need a number and a definition
“Unlimited revisions” sounds like protection. Nobody prices unlimited work, so the limit exists anyway and you will meet it in the middle of the project, usually as a slower reply. A term you can rely on states how many rounds are included at each stage and what happens after the last one.
It also says what a round is. A workable definition: one consolidated list of comments, from one named person, sent within an agreed number of working days. Without that, five messages from three colleagues count as one round for you and as five for the supplier, and both readings are reasonable.
Finally, separate corrections from changes. A correction restores what was agreed and should cost nothing. A change adds something that was not in the scope and should have a price. If the quote does not draw that line, it will be drawn later in an argument, with the deadline as the hostage.
Testing, launch and handover are where low quotes go quiet
The visible part of a digital job is design and build. The part that makes it usable is less photogenic: checking forms and payments on real phones, setting up analytics, redirecting old addresses, testing with a keyboard and a screen reader, making a backup before launch. These hours rarely appear in a low quote, and they are the first to be cut when a fixed price starts to hurt.
Handover deserves its own line. Ask who will own the domain, the hosting account, the code repository, the design files and the licences for fonts and images. The Playbook's contract checklist includes a requirement that software and data produced by a third party remain under the client's control. A small business needs the same sentence in its agreement.
The same checklist asks for a warranty period in which defects found after launch are fixed at no additional cost. Agree the number of days in advance. Even a short warranty changes the supplier's incentive: it becomes cheaper to test before launch than to repair afterwards.
Put every quote into the same comparison table
Draw one table. The rows are the stages of the job: discovery, content, design, build, integrations, testing, launch, handover, revision rounds, warranty, payment schedule. The columns are the suppliers. In each cell write one of three things: included, excluded or not stated.
“Not stated” is the most useful cell on the page. Send every supplier the same short list of questions and ask them to fill the gaps in writing. The answers often bring the totals closer together than the first numbers suggested, and they show you how each supplier communicates when something is unclear, which is how they will communicate during the project.
Only now compare the totals. An illustration with invented round numbers: quote A is 1,800 and excludes copywriting and testing; quote B is 2,600 and includes both. If supplier A prices the two missing items at 900 when asked, the cheap quote is 2,700 and the expensive one is cheaper. The figures are an example of the arithmetic, not market prices.
Payment terms that keep both sides honest
Tie payments to accepted deliverables rather than to calendar dates. A stage is paid when its result has been shown and approved: the agreed structure, the approved design, the working build on a test address, the launched site with access handed over. This is the commercial version of the Playbook's advice to hold suppliers accountable to deliverables.
A deposit before work starts is normal and fair, because the supplier reserves time for you. Full prepayment for work that has not been defined is a different matter: it removes the only lever the client has. Keeping a final part of the price until after handover gives both sides a reason to finish properly.
Add one sentence about changes. Any addition to the scope receives a written price and a stated effect on the deadline before the work begins, and is approved by the person who signs the invoices. That sentence prevents most disputes, because it turns every “could you also” into a decision instead of a favour.
When a low price really is the right choice
A low quote is not always a trap. If the job is small, if you write the texts and test the result yourself, or if a ready template genuinely fits, a lower price is the correct price. The condition is that the reduced scope is stated and that you have accepted the work that moved to your side of the table.
There are signs that a low price is honest. The exclusions are listed without being asked for. The supplier asked questions before naming a figure. Something you requested was declined or postponed with a reason. A quote that agrees to everything immediately has usually not been thought through.
The decision rule is short. Choose the offer in which you can point to every piece of work and name who does it and when it is accepted. If two offers pass that test, the lower total is a real saving. If only one passes, it is the cheaper one whatever the first page says.
Practical checklist
- Ask every supplier to list deliverables, assumptions and exclusions in writing before you compare any totals.
- Check that discovery, testing, launch and handover each appear either as a line in the quote or as a stated exclusion.
- Fix the number of revision rounds, write down what one round means and what an additional round costs.
- Tie each payment to an accepted deliverable and keep a final part of the price until after handover.
- Confirm in writing that the domain, accounts, source files and licences will be in your name when the project ends.
Questions and answers
Why do quotes for the same digital project differ so much?
Mostly because they describe different amounts of work. One supplier includes discovery, copy, testing and handover; another prices only design and build and assumes the rest is yours. Hourly rates differ too, but less than the scope does. Until the quotes list the same deliverables, assumptions and exclusions, their totals are not comparable.
Should discovery be paid for as a separate stage?
Yes, when the project is not trivial. A short paid discovery ends with a written result: the problem, the scope, the risks and a firmer estimate. You can take that document to another supplier if you wish. Unpaid discovery is either skipped or hidden in a later line, and in both cases you cannot see what you bought.
How many revision rounds should a quote include?
There is no standard number, and the number matters less than the definition. A quote should say how many rounds each stage includes, what counts as one round, how quickly comments are expected and what an extra round costs. Two clearly defined rounds protect you better than an undefined promise of unlimited changes.
What should be in the client’s own name when a project is handed over?
Everything needed to run and change the result without the original supplier: ownership of the domain and hosting account, access to the code repository and the content system, editable design files, licences for fonts and images, and a short written description of how updates and backups work. Ask for the list in the quote, not at the end.
Is a fixed price safer than an hourly rate?
A fixed price is safer only when the scope is fixed too. With a vague scope, a fixed price pushes the supplier to cut the invisible work first, usually testing. An hourly rate with a written estimate, a cap and frequent accepted deliverables can be the more predictable arrangement. Judge the definition of the work before the pricing model.