12 Questions to Ask a Web Design Agency Before Comparing Quotes

Send every agency the same starting brief

Before comparing quotes, give each supplier a common description of the business, intended audience, required customer action and essential features. Mention your existing website and any fixed launch dependency. A proposal for five informational pages cannot be compared fairly with one that includes copywriting, booking integration and an ongoing support arrangement.

Our small business website checklist helps you prepare that brief. This guide covers the next step: evaluating the agency’s response. Keep an evidence column alongside each answer, so a reassuring statement becomes something you can review.

Use the questions to find a suitable working relationship. A specialist freelancer, a small studio and a larger agency can each fit different projects. Team size, impressive visuals or a long technology list should not decide the project on their own.

1–3: Check fit, experience and responsibility

1. What would you investigate before proposing a solution?

Ask the agency to identify assumptions about your audience, content and customer journey. A useful response explains what it needs to learn and what discovery will produce. Request a sample output with confidential material removed, such as a page inventory or an annotated wireframe.

2. Can you show a relevant live project and explain your role?

Open the example on a phone and ask what the team actually delivered. A template adaptation, visual design project and complete build represent different responsibilities. If performance results are discussed, ask for the baseline, measurement period and limits of attribution. Treat an unmeasured example as design evidence.

3. Who will make decisions and communicate with us?

Identify the person managing the project, who creates the content and who handles development. Ask how feedback is collected, which milestones need your approval and what happens when either side is unavailable. Record one approval owner on your side to avoid conflicting instructions.

4–6: Turn the quote into a usable scope

4. Which pages, templates and features are included?

Request a list. Clarify whether ten product pages use one shared template or require ten separate designs. Describe each integration through the task it supports: an appointment request form is different from a calendar with live availability, payment and reminders.

5. Who supplies copy, images and policy information?

Agree who drafts, reviews and enters content, including whether image sourcing and licensing are included. Ask which missing materials would delay a milestone. If AI-assisted material is used, identify who checks accuracy, permissions and whether it represents the business truthfully.

6. What triggers an extra charge or a revised deadline?

Ask for the revision process, definition of a defect and procedure for new requests. Request approval before additional paid work begins. A scope document should explain payment milestones and exclusions clearly enough that both parties can identify when the project changes.

7–8: Understand the operating arrangement

7. What access and rights will our business receive?

Ask about the domain, platform, hosting, source files, content and design assets separately. A hosted platform can be a sensible choice even when every component is not exportable; the important question is whether the arrangement and its limits suit your business. Confirm licences, export options and any transfer work in writing.

8. Can our team make the updates we expect?

Request a demonstration of a realistic edit, such as changing opening hours, adding a service or publishing an article. Ask which tasks need a developer and how those requests are billed. Clarify renewal costs and what would stop working if a subscription or maintenance arrangement ended.

Use the website handover checklist to record the final deliverables. Give collaborators individual access where available, and store credentials securely rather than placing them inside an ordinary project worksheet.

9–10: Ask what will be verified

9. What customer tasks and accessibility checks will you test?

Ask for an acceptance list covering navigation, readable mobile content, keyboard use, form labels, error feedback and the agreed booking or enquiry journey. Identify the browsers and devices included. W3C’s Easy Checks gives examples of an initial accessibility review and explains that these checks alone do not establish complete accessibility.

10. What does SEO setup and measurement include?

Ask for concrete outputs: page titles, crawlability checks, canonical URLs, internal links, sitemap updates and any redirect work. For a redesign, request a plan for existing useful URLs. Ask who receives Search Console and analytics access and which events will be measured.

A click on an email link is different from a delivered enquiry, and a delivered enquiry is different from a qualified opportunity. Agree the definitions before reporting starts. Read our redesign SEO checklist when evaluating a migration scope.

11–12: Plan launch and the months after it

11. What must be ready for launch, and how do we recover?

Ask who approves the release, confirms enquiry delivery and checks the live domain. Identify a suitable backup or rollback process and who can use it. A shop with changing orders needs a different recovery plan from a static brochure site. Make the plan specific to your setup.

12. What support continues after the launch?

Separate correction of launch defects, routine updates, monitoring and new features. Ask about response windows, urgent issues, included time and recurring charges. Confirm how the relationship can be reviewed or ended and what access or export work would follow.

Request a schedule that names dependencies. Content approval, external integrations and timely feedback can affect delivery. A proposed date is more useful when the assumptions behind it are visible.

Use this proposal comparison worksheet

Mark each answer as documented, needs clarification or outside the scope. Resolve business-critical unknowns before comparing the final totals. If two proposals include different features, ask for a common core scope and price the optional work separately.

A low quote can be appropriate for a small, well-defined project. A higher quote may include useful work or unnecessary extras. Judge the actual deliverables and evidence rather than treating either price as a quality signal.

An example of a useful acceptance requirement

Hypothetical example: a repair business wants visitors to request an appointment. An acceptance requirement could be: “On an agreed phone browser, a visitor can choose a service, enter contact details, correct an invalid field and submit a request. The visitor sees confirmation and the request reaches the agreed inbox. Staff can identify which service was requested.”

This gives the team a testable outcome. The example does not imply a live scheduling system: confirmed appointments, reminders and deposits would each need their own scope. Ask the agency to explain that distinction before you approve a feature called “booking”.

Keep private customer information out of demonstrations. Use suitable test data and check that a successful form submission is recorded accurately, rather than counting a button click as completed work.

Final questions before signing off the proposal

Should we insist on results from our exact industry?

Relevant experience helps you evaluate fit, but a supplier can also explain a credible research process. Ask it to demonstrate understanding of your customer’s task and show how that changes the proposed solution.

Can an agency guarantee leads or search rankings?

A supplier can commit to specified deliverables and agreed checks. Future commercial outcomes depend on the offer, demand, competition, traffic and follow-up as well as the website. Ask for a measurement plan and qualified claims.

What if the proposal leaves important details open?

Request a revised scope or a defined discovery stage with its own output before committing to the full build. Keep a written record of the assumptions that remain.

Bring your brief and open questions to ReachX’s website development service. If you already have a site, our refresh versus redesign guide can help you decide the size of the project first.