
How to Choose a Web Design Agency: 12 Questions Before You Hire
Choosing a web design agency is not mainly a design decision. It is a business decision about positioning, lead generation, ownership, technology and the team you may rely on after launch.
A beautiful portfolio can tell you whether an agency has taste. It cannot tell you who will do the work, whether the site will be easy to update, what the final bill includes or what happens when a form stops working six months later. The questions below are designed to expose those details before you sign.
If you are comparing agencies for a small-business project, start by reviewing what a professional web design agency should connect: clear messaging, responsive design, technical foundations and a conversion path that gives visitors a sensible next step.
Before You Contact an Agency, Write a One-Page Brief
Agencies cannot quote the same job if every conversation describes a different job. A short brief makes the comparison fair and reduces vague estimates.
Your business, audience and main service or product.
The primary action you want a visitor to take: call, enquire, book, buy or visit.
The pages and features you believe you need.
Examples of websites you like, with reasons rather than only links.
Who will supply copy, photography, product data and approvals.
Your target launch window and an honest budget range.
What is not working on the current website, if you have one.
Treat this as version one, not a fixed specification. A good agency should challenge weak assumptions. If every agency simply agrees with everything in the brief, you are collecting quotes rather than expertise.
12 Questions to Ask a Web Design Agency
1. What business problem would you solve first?
A credible answer starts with your customer, offer and conversion path. It may identify unclear positioning, weak trust signals, poor mobile usability or a confusing enquiry journey. Be cautious if the first answer is a colour palette, animation style or platform.
2. Can you show relevant live websites—and explain the decisions?
Do not stop at screenshots. Open the sites, use the navigation, test the mobile layout and inspect the calls to action. Ask what the original problem was, what the agency changed and which parts of the project it actually handled.
A good answer sounds like: “The old site attracted traffic but buried the consultation form. We simplified the service pages, moved proof closer to the call to action and rebuilt the mobile flow.” A weak answer sounds like: “The client wanted something modern.”
3. Who will work on my project?
Ask who handles strategy, copy, design, development, SEO, project management and quality assurance. You do not need a large team, but you do need clarity. If specialists or subcontractors are involved, ask how their work is reviewed and who remains accountable.
4. Which platform would you recommend, and why?
The platform should follow the operating reality of your business. WordPress, Wix and Shopify can all be good choices in the right context. The useful question is not “Which platform is best?” but “Which platform is best for these features, this editing team, this budget and this growth plan?”
A recommendation made before discovery is a red flag. The agency should explain trade-offs such as app costs, maintenance, content editing, checkout needs, integrations and portability.
5. What exactly is included in the price?
Request an itemised scope. Confirm the number of page templates, content migration, copywriting, photography, forms, ecommerce setup, integrations, redirects, analytics, training, revisions and launch support.
Also separate one-time costs from recurring expenses. Hosting, premium apps, domains, stock assets, maintenance and ongoing SEO may sit outside the build price. A low proposal can become expensive when essential work is hidden in exclusions.
6. What is your process from discovery to launch?
A professional process usually includes discovery, information architecture, content, wireframes or direction, visual design, development, testing, approvals and launch. The labels can differ; the decision points should not.
Ask what you receive at each stage, who approves it and how changes are handled. Clear review gates prevent the painful situation where everyone sees the full website for the first time just before launch.
7. How many revisions are included?
“Unlimited revisions” sounds generous but often hides an undefined process. A healthier agreement states how many review rounds are included, how feedback should be consolidated and what counts as a scope change.
The goal is not to limit collaboration. It is to prevent contradictory comments, endless micro-edits and surprise invoices.
8. What technical SEO work is included?
A website build should not promise rankings, but it should avoid creating basic SEO problems. Ask about page titles and descriptions, heading structure, indexability, canonical URLs, sitemap handling, redirects, image alt text, structured data where appropriate, analytics and Google Search Console.
If an existing site is being replaced, redirects deserve special attention. Changing valuable URLs without a map can break links and discard search equity.
9. How will you handle mobile performance and Core Web Vitals?
Ask how the team controls image weight, font loading, third-party scripts, layout shifts and interaction delays. Google’s Core Web Vitals use LCP, INP and CLS to describe loading performance, responsiveness and visual stability; the agency should understand the user experience behind those abbreviations, not only chase a screenshot score.
Request examples from live work and ask which constraints were under the agency’s control. Performance can be affected later by apps, ads, analytics tools and unoptimised content, so a responsible answer will include both build practices and ongoing governance.
10. Who owns the domain, content, accounts and website?
Your business should control the domain, primary website account, analytics, Search Console and advertising accounts. Ownership of custom code, design source files, fonts, stock images and copy should be stated in the contract.
An agency may manage accounts for convenience, but management is not ownership. Ask how access is transferred if the relationship ends.
11. How will we measure whether the website works?
“More traffic” is not always the right goal. For a local service business, qualified calls, form submissions, bookings and direction requests may matter more. For ecommerce, product discovery, add-to-cart behaviour, checkout completion and revenue are more useful.
A strong agency will distinguish what it can measure from what it can guarantee. It should agree on events and reporting before launch so success is not defined retrospectively.
12. What happens after launch?
Launch is the start of live evidence, not the end of the project. Confirm the warranty period, bug-fix process, maintenance options, backups, software updates, security monitoring, response times and the cost of future changes.
Ask for training and a handover checklist. You should know how to update common content, where credentials are stored and whom to contact when something breaks.
Use a Simple Agency Scorecard
After each call, score the agency while the details are fresh. Use the same criteria for every candidate and weight the factors that matter most to your project.
Understanding of your business and audience — 20 points.
Relevant live work and evidence — 15 points.
Strategy, content and conversion thinking — 15 points.
Scope and pricing clarity — 15 points.
Technical SEO and performance approach — 10 points.
Communication and project process — 10 points.
Ownership and handover terms — 10 points.
Post-launch support — 5 points.
The highest score is not automatically the right choice. Use the scorecard to expose trade-offs and then decide whether the remaining gap is acceptable. A slightly higher price can be rational when the scope is clearer and the risk is lower.
Red Flags That Should Slow You Down
Guaranteed first-page rankings or a guaranteed traffic number.
A fixed quote before the agency understands the scope.
No questions about customers, competitors, content or goals.
Portfolio images without links to live work.
Unclear ownership of the domain, accounts or final deliverables.
A recommendation based only on the agency’s favourite platform.
Missing exclusions, recurring costs or change-request terms.
Pressure to pay before the proposal and contract are clear.
No plan for redirects, testing, analytics or post-launch support.
Agency, Freelancer or In-House Hire?
An agency is useful when the project needs coordinated strategy, copy, design, development and SEO. A specialist freelancer can be a better fit for a focused build with a clear scope. An in-house hire makes sense when the website and digital product need continuous daily work.
Do not choose by label alone. Some small agencies are deeply hands-on; some large agencies outsource most delivery. Some freelancers have a stronger process than teams ten times their size. Evaluate the people, scope and accountability you will actually get.
A Practical Final Check Before You Sign
The proposal reflects the same brief you gave every candidate.
Deliverables, exclusions and recurring costs are written down.
The timeline names client dependencies and approval stages.
Ownership and account access are explicit.
SEO, redirects, mobile testing and analytics are included where relevant.
Support and handover responsibilities are defined.
The contract explains payment milestones, cancellation and scope changes.
If you want to compare this checklist with a team that builds WordPress, Wix and Shopify websites, review Webcurry’s web design agency services or discuss your brief through the contact page. The useful first conversation is not about selling you a page count; it is about deciding what the website needs to accomplish.
Frequently Asked Questions
What should I look for in a web design agency?
Look for relevant live work, a clear discovery process, named deliverables, transparent ownership terms, realistic timelines, mobile performance, basic SEO foundations and defined post-launch support. A polished portfolio is useful, but the agency’s reasoning and process matter more than visual style alone.
How many web design agencies should I compare?
For most small-business projects, compare three serious candidates using the same brief and questions. That is usually enough to understand the market without turning the selection process into a second full-time job.
Should I choose a local web design agency?
Local knowledge can help when your business depends on a specific city or service area, but proximity is not the only factor. Choose the team that understands your customers, communicates clearly and can show relevant results. Video calls, shared project tools and documented approvals make remote work practical.
How much does a web design agency cost?
Cost depends on page count, content, custom features, integrations, platform, migration work and post-launch support. Ask each agency to separate one-time build costs from recurring expenses such as hosting, apps, maintenance and content updates so proposals can be compared fairly.
What should a web design proposal include?
A useful proposal should define goals, sitemap or page scope, content responsibilities, design and development stages, platform, integrations, revision rounds, timeline, payment schedule, testing, launch tasks, ownership, exclusions and support after launch.
Who should own the domain and website?
Your business should control the domain registration, analytics, Search Console, advertising accounts and primary website access. The contract should also explain ownership of custom design files, code, copy, licensed assets and third-party subscriptions.
Should SEO be included in a website project?
At minimum, a new website should include crawlable page structure, sensible URLs, title and description fields, heading hierarchy, image alt text, redirects where needed, sitemap handling, analytics and Search Console setup. Ongoing keyword research, link building and content production may be separate services.
Which platform should a web design agency recommend?
The recommendation should follow your needs. WordPress may suit content-heavy or flexible builds, Wix can be efficient for owner-managed service sites, and Shopify is purpose-built for ecommerce. Be cautious if an agency recommends the same platform before discussing editing needs, integrations, budget and growth plans.
How long does a business website take to build?
Timelines vary with scope and how quickly content and approvals arrive. Ask for stages, dependencies and review deadlines rather than accepting a single launch date. A realistic schedule identifies what the agency needs from you and what happens when feedback is delayed.
How can I check an agency’s portfolio properly?
Open the live websites rather than relying on screenshots. Test them on a phone, check key pages and forms, review clarity of calls to action and sample important URLs in PageSpeed Insights. Ask what problem each project solved and which parts the agency actually delivered.
What are red flags when hiring a web design agency?
Major red flags include guaranteed rankings, vague scope, no discovery questions, unclear ownership, hidden recurring fees, unlimited revisions with no process, copied designs, inaccessible accounts and pressure to sign before requirements are documented.
What support should I expect after launch?
Confirm who handles backups, software updates, security, uptime issues, small edits, form testing, analytics checks and bug fixes. Ask for response times, included hours, monthly costs and a handover plan if you later move to another provider.
The Bottom Line
Choose a web design agency for the quality of its questions, not the confidence of its sales pitch. The right partner should make the scope clearer, explain trade-offs, protect your ownership and connect design decisions to measurable business outcomes.
Use one brief, ask every candidate the same questions and compare written answers. That small amount of discipline can prevent months of expensive ambiguity—and it gives a good agency the information it needs to do better work.


Comments