How to compare web design proposals fairly
Web design proposals become comparable when every candidate answers the same brief and makes deliverables, assumptions and costs clear.
Compare web design proposals against one written brief and one set of criteria. A total price is meaningful only when you know what it includes, who will do the work and what happens when assumptions change. Make the scope comparable before choosing a supplier.
Put every proposal on the same footing
Send each candidate the same description of audiences, goals, content, required features and timescale. Ask them to list assumptions and exclusions. If one assumes that you will supply finished copy while another includes copywriting, the prices are not directly comparable.
Create a simple comparison sheet with discovery, content, design, build, testing, launch, training and support as rows. Mark each item as included, excluded or unclear. The exercise often reveals missing work before it becomes a change request.
Read the method as carefully as the mock-ups
Look for a process that explains how the team will learn about your users and test decisions. Ask what you will review at each stage, how many feedback rounds are included and who has authority to approve. A persuasive visual concept is not a substitute for a plan to make the site usable, accessible and maintainable.
Consider the evidence behind proposed features. If a candidate recommends a complex animation or new tool, ask which visitor need it serves and what it will cost to maintain. Similarly, a very simple proposal should explain how it will meet the brief rather than relying on low price alone.
Compare ownership and ongoing costs
Check who will control the domain, content, design files and CMS accounts. Ask about training, security updates, licences and support after launch. Separate one-off project costs from recurring charges, and note any services that you could change later.
Clarify how additional pages or changes are priced. A useful proposal defines the boundary of the agreed work and a process for approving changes. This protects both sides from misunderstandings.
Score what matters to your organisation
Choose criteria before reading final prices. For example, you might weigh understanding of the audience, quality of process, relevant experience, accessibility, clarity of deliverables, support and cost. Record why you gave each score. The purpose is not to turn judgement into a perfect number, but to make trade-offs visible.
Invite candidates to explain one difficult part of your brief. Their answer can reveal how they handle uncertainty and whether they ask useful questions. If you are still unsure about the current site's problems, a structured website review can help you set priorities before awarding work.
Frequently asked questions
Should I choose the lowest web design quote?
Only if it covers the work you need and the approach is credible. Compare scope and ongoing costs before treating the difference as a saving.
What if proposals recommend different solutions?
Ask each candidate to explain the problem their approach solves, what evidence supports it and which assumptions need testing. You can then compare outcomes rather than identical features.
Is a fixed price always preferable?
It can help with budget control when scope is clear. Where significant discovery is needed, a phased scope may be more honest. Agree how decisions and extra costs will be approved.
HELP US IMPROVE
Was this article useful?
Your feedback helps shape future coverage.