25 questions that instantly reveal whether a web design agency is worth hiring

Choosing a web design agency can feel like fishing with a blindfold. You see portfolios and promises, but you rarely know how the team actually works, who owns outcomes, or what happens after launch. This guide gives you 25 direct questions and a clear scoring method that lets you expose capability, fit, and delivery risk in under 30 minutes. Use it to build an agency shortlist you can trust and to cut through polished proposals that hide gaps.

Why choosing a web design agency is harder than it looks

Buyers often judge agencies on look and narrative rather than evidence. That approach tends to favour glossy presentations and case studies crafted for marketing. The danger is that a nice pitch can mask weak discovery, fragile technical delivery, poor SEO thinking, and a lack of post-launch support. 

The right agency will share their work, explain trade-offs, demonstrate process, and show how they manage risk. The right questions will turn vague impressions into measurable signals. If you want a ready brief, start with this website brief template to get your goals and constraints in one place.

The 5 areas to score every agency against

Before you dive into case studies and timelines, score agencies against five concrete areas that reveal their capabilities and risks. These categories cover the decisions that determine whether a redesign succeeds or stalls.

Strategy, UX, technical delivery, SEO, support

Score agencies against five practical areas. Each area reveals a different type of risk.

• Strategy: Do they understand your business, metrics, and competitors?
• UX capability: Can they translate goals into usable, measurable journeys?
• Technical delivery: Do they own integration, performance, and deployment processes?
• SEO: Will they preserve and improve organic visibility through redesign and migration?
• Support: How do they plan for testing, QA, bug fixes, and long-term ownership?

These categories map to real tasks and timelines during a redesign and help you compare agencies consistently. 

25 questions to ask on every agency call

Ask these questions early. You should be able to get meaningful answers in a 20 to 30-minute call. Mark each response on a simple scale: strong, weak, red flag. See the scoring section below.

Strategy and discovery

1. How do you run discovery, and who participates? Look for structured workshops with stakeholders, analytics review, and a clear artefact list.
2. What are the key business metrics you will design to influence? Ask for specific KPIs, not vague outcomes.
3. Can you show a brief from a past project and explain how it shaped delivery? Request real examples, including constraints and trade-offs.
4. How do you handle scope changes and prioritisation? Strong teams use backlog and sprint planning.

UX capability

5. What UX research methods do you use, and when are they applied? Expect interviews, analytics-driven insights, and usability testing.
6. Can you walk through a recent UX solution and how you validated it? Look for evidence of iteration and measurable improvements.
7. How do you approach accessibility and inclusive design? Accessibility should be woven into the process, not an afterthought.
8. What is your approach to information architecture and navigation? Poor IA often kills findability and conversions.

Technical delivery

9. What is your typical technical stack and why? Ensure it matches your in-house skills or hosting strategy.
10. Who owns integrations with CRM, commerce, and third-party tools? Clarify responsibilities early.
11. How do you handle performance budgets and page speed? Ask for examples of measurable gains.
12. What is your QA process before launch? Expect automated tests, manual checks, and staging sign-off.
13. Who will manage deployment and rollback? You need a clear owner for launch-day activities.
14. How do you document code, APIs, and operational procedures? Good documentation reduces long-term risk.

SEO and migration

15. Have you handled SEO migration before, and can you share a plan outline? SEO migration should include redirects, content mapping, and crawl testing.
16. How do you measure organic impact during and after launch? Look for SERP tracking, traffic attribution, and technical crawls.
17. Who is responsible for content strategy and SEO-friendly templates? Design and templates must support on-page SEO. See our guide to website redesign and SEO migration for practical steps.
18. How do you test and validate structured data, metadata, and indexability? These are often missed and cause traffic loss.

Governance, ownership, and risk

19. What does success look like at project close? Ask for acceptance criteria and success metrics.
20. Who owns final assets and intellectual property? Confirm ownership rights and deployment artefacts.
21. How do you handle bugs and warranty periods post-launch? Clarify SLAs and response windows.
22. What is your escalation path for critical issues after launch? You need names and times, not generic promises.

Team, communication, and costs

23. Who will be on the delivery team, and what is their availability? Check team structure and depth; a single point of failure is a risk.
24. How do you run project management and progress reporting? Expect a regular cadence and clear dashboards.
25. Can you provide case studies that match our sector and challenge? Look for measurable outcomes and honest context; review their case studies for depth and relevance.

How to score the answers properly

Don’t overthink scoring. Use a three-level rubric and a simple tally. Assign 2 points for a strong answer, 1 point for a weak answer, and 0 points for a red flag. Add up scores across the five areas to compare agencies quickly.

Strong answer, weak answer, red flag

• Strong answer (2 points): Provides concrete examples, numbers, named processes, and references to past work. They offer documentation or a logical plan you can verify. They proactively raise risks and mitigation steps.
• Weak answer (1 point): Gives generic statements, refers to “we usually” without evidence, or cannot explain the mechanics of delivery. They may promise outcomes without methods.
• Red flag (0 points): Avoids the question, blames others, or offers contradictory information. Examples include no QA process, no ownership of integrations, or no plan for SEO migration.

A quick benchmark: 35 to 50 points indicates a high-confidence fit. 20 to 34 points suggests capability but requires further diligence. Below 20 points calls for caution.

What a polished pitch can hide

A slick presentation often highlights design polish and selective wins while hiding the messy parts that determine a project’s success. Visuals can impress stakeholders, but they do not prove how an agency runs the discovery process, tracks metrics, or handles unexpected integration issues. 

During a proposal review, push past the showreel. Ask for the internal brief and the project timeline so you can see how they translate goals into milestones. Request a written case summary that spells out constraints, stakeholder friction, the trade-offs they made, and the concrete outcomes they achieved.

Look into their team structure and who actually did the work on the showcased projects. An agency that assigns a senior lead to a pitch but delivers with juniors creates delivery risk. Ask how they handled the QA process and performance testing, and who owned deployment and rollback. Confirm ownership rights for code, assets, and content so you do not discover limitations after launch. Good agencies will openly discuss where things went wrong and what they learned. They will share failed experiments and the changes those failures prompted in their workflows.

Finally, check for repeatable results rather than one-off creative sparks. Look for case studies that include baseline metrics and post-launch tracking. A genuine partner will show how they protect organic traffic through migration planning, how they hand over operational documentation, and how they support you after launch with clear SLAs and escalation paths.

How to compare agencies without defaulting to price

Price matters, but it should not be the default filter. Compare expected outcomes against the total cost of ownership. A cheap build that loses organic traffic or needs heavy rework is more expensive in the long run. Use these lenses:

• Time to value: How fast will you see measurable improvement?
• Risk transfer: Who assumes risk for integrations and migration?
• Scalability: Can the solution grow with your needs?
• Support burden: How much internal maintenance will fall back on your team?

When you review proposals, look at assumptions and exclusions. A fair proposal will list not only what is included but also what is explicitly out of scope. Use proposal review sessions to clarify hidden costs and to align expectations.

The shortlist template marketing teams can use

Use this simple shortlist template during calls and reviews. Create a spreadsheet with agency names across the top and the five scoring areas down the side. Add the 25 questions as checklist items. For each question record: answer summary, score, and a confidence note. Add columns for price, timeline, and red flags. Share the spreadsheet internally to gather input from stakeholders.

Work with London’s leading web design agency

Yellowball blends strategic discovery, human-centred UX, robust technical delivery, and careful SEO migration to deliver high-performing websites, backed by over 250 successful projects and a 92% client retention rate. 

We run focused discovery workshops, create measurable UX solutions, manage integrations and QA, and protect organic traffic through proven SEO migration plans. After launch, we provide clear ownership, SLAs, and ongoing support so your site keeps delivering value.

If you need a partner that reduces risk and accelerates outcomes, contact our team and let’s get the ball rolling!