How Do You Compare Website Design Proposals?
Website proposals become comparable when each supplier's scope, evidence, responsibilities and ongoing costs are set against the same requirements.
Part of our guide: How Much Does a Small Business Website Redesign Cost in the UK?
Compare website design proposals by translating each one into the same list of outcomes, deliverables, responsibilities, assumptions and ongoing costs. Do not begin with the total price. Two proposals can use similar language while promising very different amounts of strategy, content, migration, testing and support.
A simple comparison table can expose the differences, but the decision still needs judgment about approach, relevant experience and how well the team understands your business.
Confirm that everyone received the same brief
Comparisons are unreliable when suppliers answered different questions. Give each the same description of business goals, audiences, current problems, required functions, content volume, constraints and desired timing.
Record what remains uncertain. A responsible proposal may include discovery rather than pretend every unknown has already been priced.
Thinking about your own rebuild?
Tell us about your business, your current website and what you would like to improve. We will help you work out the next step.
Record each supplier against the same requirements in the quote-comparison worksheet. Keep unclear inclusions as questions until they are answered.
Compare the stated outcome
Read the opening diagnosis and intended outcome. Does the proposal address customer tasks and business problems, or mainly promise a modern appearance?
Look for evidence that the supplier listened. Generic claims that could apply to any business add little confidence.
The strongest proposal may challenge part of the brief and explain why.
Normalise the scope
Create rows for discovery, structure, design, content, development, integrations, migration, testing, launch and support. Mark each proposal included, limited, excluded or unclear.
Add quantities where possible: unique templates, migrated pages, written pages, forms, integrations and revision rounds.
Do not treat a five-page design system as a promise to migrate a hundred pages unless it says so.
Review discovery
Compare research and planning activities. Analytics review, content inventory, stakeholder work and customer evidence may be included, optional or absent.
Ask what decisions discovery will produce. Meetings without outputs do not necessarily reduce project risk.
If discovery is separate, understand whether later scope and price can change.
Compare content responsibilities
Clarify who supplies facts, writes copy, edits existing material, checks sources, creates images and manages approvals. Note page or word allowances only as part of the picture.
Original content requires research and editorial review. Important factual claims should cite authoritative sources rather than copy competitors.
Include migration and formatting, not only writing.
Compare information architecture
Look for a sitemap or method for creating one. The site structure should reflect customer tasks, services and useful existing content.
Ask whether navigation labels and internal links are designed as part of the work. Confirm who approves URLs.
A redesign can look excellent while preserving a confusing structure.
Compare design deliverables
List mood boards, wireframes, prototypes, page designs and component states. Confirm desktop and mobile treatment, interactions and error states.
Ask how real content enters the process. A homepage concept with placeholder text does not demonstrate how the full site will work.
Understand the feedback process and revision limits.
Compare technical solutions
Record platform, hosting model, dependencies and editing experience. Ask why each solution fits the requirements.
One proposal may customise an existing theme; another may create a tailored component system. Neither is automatically better, but the effort and constraints differ.
Include licence fees, updates and portability.
Compare functionality in journeys
Translate feature lists into tasks. A booking system should cover availability, confirmation, cancellation, notifications, payments and error handling where relevant.
Identify third-party products and charges. Confirm whether integration configuration and end-to-end testing are included.
Vague feature names conceal important differences in responsibility.
Compare migration plans
An existing site needs URL inventory, content decisions, redirects and launch protection. Check whether the proposal includes all four.
Ask how domains, DNS and email are handled. A website move should not casually disrupt business communication.
The website replacement guide describes this work in detail.
Compare SEO work precisely
Replace the label SEO with actions: keyword and intent research, URL preservation, metadata, internal linking, canonicals, structured data, sitemaps, redirects and post-launch monitoring.
Reject guaranteed rankings. Compare the controllable work and its evidence.
Ask which existing pages and search performance will be protected.
Compare accessibility
Check the target standard, design practices and test method. Keyboard use, focus, zoom, contrast, alternatives and form errors need human attention as well as automated tools.
The Web Content Accessibility Guidelines provide a common reference. Ask how third-party components and future editing are governed.
An unqualified claim of fully accessible needs clarification.
Compare performance commitments
Look for budgets, representative pages, mobile conditions and defined testing. Hosting alone does not determine speed.
Ask how images, fonts and external scripts will be controlled. Confirm whether fixes are included if the built site misses agreed criteria.
Avoid comparing a single projected score with a complete performance process.
Compare quality assurance
List browsers, devices, forms, content, links, redirects, accessibility and production configuration. Confirm who tests and records results.
Client acceptance is not a replacement for supplier testing. Both have roles.
Use the website pre-launch checklist to identify missing areas.
Compare hosting and operations
Record hosting, backups, monitoring, certificates, staging, deployment and incident support. Note normal renewal prices and traffic limits.
Ask who controls accounts and how the site can move. Separate infrastructure from supplier maintenance.
Include the value of management, not just the wholesale host price.
Compare ongoing support
Check launch warranty, response times, maintenance, content support and improvement services. Distinguish defects from new work.
Some proposals include several months of care; others finish at handover. Adjust total cost rather than treating those offers as equivalent.
Confirm cancellation and handover terms.
Compare ownership
Create rows for domain, code, content, data, design files, licences, analytics and third-party accounts. Mark who owns and administers each.
Ask what can be exported and in which format. Ownership on paper is weak if the business lacks access.
Identify proprietary dependencies and the cost of leaving.
Compare schedules realistically
Review phases, dependencies and approval windows. A shorter schedule may assume finished content or immediate feedback that the business cannot supply.
Ask which people are allocated and how delays are handled. Note whether the launch date is fixed or indicative.
Choose credible sequencing over an attractive unsupported promise.
Compare project management
Understand meeting rhythm, contact, issue tracking and decision records. Coordination is real work, especially with several stakeholders.
Check who consolidates client feedback and who can approve changes. A defined process can prevent expensive late disagreement.
More meetings are not automatically better; purposeful communication is.
Compare pricing structure
Separate fixed fees, time-based work, optional items, third-party charges and recurring costs. Check tax, payment milestones and expiry dates.
Read assumptions and exclusions. Ask how scope changes are estimated and authorised.
The guide to why redesign prices vary explains why total figures alone mislead.
Build a three-year ownership view
Add hosting, licences, support and expected content or maintenance over a meaningful period. Include internal staff time and migration risk.
A higher build price may reduce recurring cost, but only if the architecture and terms demonstrate it. A lower price may be right when it transfers manageable tasks to the business.
Compare like with like and document assumptions.
Evaluate relevant evidence
Review live projects with similar complexity. Look beyond screenshots to page quality, mobile use, speed and clarity.
Ask references about communication, handling of problems and post-launch support. Respect confidentiality.
Awards and visual polish can supplement, but not replace, evidence relevant to your project.
Assess the working relationship
Notice the quality of questions, clarity of explanations and response to uncertainty. Look for a supplier who can discuss difficult decisions candidly.
Choose a team that can explain tradeoffs at your level and record commitments. Avoid dependence on one charismatic presenter you will not work with.
Fit matters, but should accompany a sound proposal.
Use weighted criteria carefully
You can weight strategy, content, accessibility, technical quality, ownership, price and confidence according to the project’s risk.
Do not disguise judgment with false mathematical precision. Scores help structure discussion, while notes explain the actual decision.
Require evaluators to cite proposal evidence for each score.
Ask clarifying questions
Send a consolidated list and allow suppliers to amend their proposal. Record answers with the contract if they change scope.
Useful questions are listed in what to ask a website design agency.
Do not fill blank cells with assumptions favourable to one bidder.
Common comparison mistakes
Choosing the most pages, features or revision rounds can reward volume rather than value. Choosing the lowest number can ignore essential migration and content work.
Other mistakes include overlooking ongoing fees, accepting undefined SEO, ignoring ownership and comparing suppliers before the brief is stable.
Check that the proposal covers the work your business needs.
Frequently asked questions
Should price be weighted heavily?
Price matters, but compare it after confirming scope and risk. An unaffordable proposal is not suitable, and an incomplete one is not cheap.
What if every agency recommends different technology?
Ask each to connect its recommendation to requirements, editing, maintenance and ownership. Use those consequences to compare the proposed platforms.
Is a detailed proposal always better?
Detail reduces ambiguity, but relevance and judgment matter more than length. Important assumptions must still be explicit.
Can proposals be negotiated?
Yes. Negotiate scope and priorities openly rather than demanding the same work for an arbitrary discount.
Who should evaluate proposals?
Include people responsible for business outcomes, content and technical risk. Keep the decision group small enough to act.
Choose the clearest credible route
Before choosing, check that the proposal explains what will change, how the supplier will test it and what you will own afterwards. Resolve unclear scope and responsibilities, then compare the total price.
Afterworks makes this comparison easier through a visible speculative redesign approach that demonstrates meaningful proposed improvement before full commitment.
