How to compare website quotes before choosing a development partner
Two website proposals can look similar while covering very different work. A total price does not tell you who writes the copy, transfers existing data or runs the site after launch. Our comparison template helps you evaluate the same assignment and resolve open questions in writing before selecting a partner.
Give every supplier the same starting assignment
Write a short, shared scope first. An illustrative example is a company website with five page types, two languages and an enquiry form; this is not a pricing recommendation. Describe the visitor action you want, available content and necessary connections. If a supplier proposes a different solution, ask for that departure and its reasoning to be listed separately.
- Audience and the main visitor action.
- Page types, functions and languages.
- Existing copy, images, data and access.
- Required connections and known constraints.
- Target date and internal approval owner.
Use a matrix with four possible answers
Our matrix gives each task four answers: included, optional, client responsibility or unresolved. For included work, record the actual scope too. Five pages could mean five custom designs or five pages populated from one template. An empty cell is a question to ask, not evidence that a supplier is poor.
- Planning and information structure.
- Design, page templates and mobile presentation.
- Copy, images, translations and content entry.
- Forms, integrations and data transfer.
- SEO foundations, redirects and measurement.
- Testing, launch, training and handover.
Make content and approvals explicit
Clarify who supplies the text, who reviews it and who enters it into the website. Do the same for photographs and translations. Agree what a revision round applies to: one design concept, one page or the whole project. Name an approval owner so contradictory feedback does not leave the delivery team waiting for a decision.
Compare running costs and handover separately
Separate one-off work from ongoing services. Ask about hosting, domain management, paid extensions, updates and support after launch. Request a clear handover list covering accounts, access, source files, documentation and owners. Rights and supplied services should be explicitly agreed; this checklist does not replace reviewing a particular agreement.
Define acceptance through real visitor journeys
Write checkable outcomes rather than looks good to us. Our example is finding a service on a phone, submitting the form and locating the accepted enquiry in the intended system. For a redesign, also check important old addresses and their new destinations. Agree who tests, which failures prevent launch and how outstanding items are recorded.
Record the decision and its assumptions
Compare price and scope after the questions have been answered. A cheaper proposal can be suitable if it deliberately covers less and your team can do the remaining work. Record the decision, assumptions and unresolved risks on one page. This reduces expectations about work that was never included and gives the selected supplier a clear starting point.
Frequently asked questions
- Should I choose the cheapest quote?
- First compare the same assignment and the work left to your team. A cheaper proposal can make sense when its scope and responsibilities fit your resources.
- How many quotes do I need?
- A fixed number does not solve comparability. A shared brief and answered questions matter more. Additional proposals without a clear scope remain difficult to compare.
- Is SEO automatically included?
- Ask for the actual tasks. A general label does not say whether metadata, redirects, indexability and ongoing work are included.
- What if a supplier leaves important questions unanswered?
- Record them as unresolved and assess their effect on your project. Do not award work on the basis of your own assumptions about included services.
Send us your project scope. We can prepare a proposal with named deliverables, responsibilities and acceptance checks so you can compare it clearly.
Discuss a website project