Questions to Ask Before Hiring a Web Designer

Key Takeaways

• Asking the right questions before hiring a web designer protects you from vague promises, scope creep, and being left without support the moment your site goes live.
• According to Clutch's agency research, unclear project scope and poor communication are the two most common causes of client dissatisfaction with web design agencies.
• Most buyers focus entirely on portfolio and price — the questions about process, ownership, and post-launch support are where the real differences between agencies emerge.
• A good agency will welcome these questions. One that deflects, gives vague answers, or creates urgency pressure is telling you something important.
• Google's own guidance on hiring developers recommends asking about technical SEO practices from the start — not retrofitting them at the end.

Hiring a web designer is one of the most consequential decisions you'll make for your business online presence. A good agency will build you something that grows with you. A poor one will deliver a site you can't update, don't own, and have to rebuild in two years.

The problem is that most buyers evaluate agencies on the wrong things. They look at portfolio images, check whether the pricing feels about right, and maybe ask for a couple of references. But the questions that actually predict whether a project will go well are rarely asked.

I've been on both sides of this. At Brambla we've taken on projects from clients burned by previous agencies, and I've spoken to enough business owners post-disaster to know which questions would have saved them. These are them.

Portfolio and Experience Questions

1. Can I see examples of work similar to my project?

This is more specific than "can I see your portfolio." A portfolio page full of beautiful brochure sites is irrelevant if you need an e-commerce platform with custom checkout logic. Ask for examples that are comparable in scope, industry, or technical complexity to what you're commissioning.

Good answer: Specific examples with context — "this one was similar because..." — and ideally a link to the live site.

Red flag: A portfolio that doesn't include live URLs, or one that lists "confidential client work" for most entries. If you can't verify the work exists, you can't evaluate the quality.

2. Have you worked with businesses in my industry before?

Industry experience matters more than you might expect. An agency that's built sites for restaurants understands booking systems, menu management, and ambiance-driven design. One that's mostly done professional services sites might not. It doesn't mean they can't do it — but it's worth understanding the curve they'll face.

3. Who will actually work on my project?

Larger agencies often pitch senior team members and then hand the work to junior staff. Ask directly who will be your day-to-day contact and who will handle design, development, and copy. If those are different people, ask how handoffs work.

Process and Timeline Questions

4. What does your project process look like from brief to launch?

You want to understand the stages: discovery, wireframes, design, development, content, testing, launch. A well-structured agency should be able to walk you through this clearly. If the answer is vague — "we just get started and see how it goes" — that's not creative freedom, it's a lack of process.

Our web design process follows a defined sequence with clear client checkpoints. If you're not sure what a good process looks like, our post on the web design process gives a stage-by-stage breakdown of what to expect.

5. What do you need from me and when?

Projects stall because clients don't provide content, copy, or feedback on time. But sometimes they don't provide it because no one told them when it was needed. Ask for a clear list of what you'll need to supply and a timeline for when it's expected.

Good answer: A structured brief or onboarding document that lists content requirements with target dates.

Red flag: No mention of your responsibilities. If the agency talks only about what they'll do and never about what they need from you, the project will stall.

6. What happens if the project runs over schedule?

Delays happen. The question is how they're handled. Is there a buffer built into the timeline? Who is responsible if delays are on the agency's side? What's the communication protocol when something slips?

7. How do you handle changes to the scope during the project?

This is one of the most important questions you can ask. Most project disputes are about scope — the client thinks something was included; the agency thinks it wasn't. A professional agency will have a clear change request process with defined costs for additions outside the agreed scope.

Good answer: A written change request process with agreed day rates or a clear formula for pricing additions.

Red flag: "We'll cross that bridge if we come to it." That's not flexibility — it's deferred conflict.

Pricing and Contract Questions

8. What exactly is included in this quote?

Not what the quote covers in general — what's specifically included. How many pages? How many rounds of revisions? Is content writing included or separate? What about photography or stock images? Is hosting included for year one?

Our pricing page breaks out exactly what's in each package because we think ambiguity at the quoting stage creates problems later. Use that transparency as a benchmark for what you should expect from any agency.

9. What are the payment terms?

A typical project splits payment across milestones — deposit to begin, payment at design sign-off, final payment at launch. Be cautious of 100% upfront requests with no milestone structure. Be equally cautious of "pay at the end" arrangements, which give the agency no financial security and can create pressure to cut corners to close the project out.

10. What's the contract and what are the exit terms?

Any professional agency will have a contract. Read it. Specifically: what happens if the project doesn't proceed? What are the cancellation terms? What's the agency's obligation if they fail to deliver?

Technical Questions

11. Who will own the website and domain after launch?

This should be non-negotiable: you should own your domain and your website outright at the end of the project. Agencies that host sites on their own accounts and retain ownership as a way to prevent clients leaving are not acting in your interest.

Ask specifically: will the domain be registered in my name? Will the website files and CMS access be transferred to me on completion?

12. What platform will the site be built on and why?

WordPress, Webflow, Umbraco, Squarespace, custom-built — each has trade-offs. Ask why the agency is recommending the platform they're proposing. "It's what we use" is a different answer from "it's the right fit for your requirements because..."

If you're going to be editing the site yourself, ask what the editing experience is like. Ask for a demo of the CMS if possible.

13. How will the site be optimised for search?

Basic technical SEO should be built in from the start — proper page titles, meta descriptions, heading structure, image alt text, page speed, and mobile responsiveness. These aren't extras. If an agency treats SEO as an optional add-on or doesn't mention it at all, it won't be a priority during the build.

Google recommends asking prospective developers about technical SEO practices upfront — not retrofitting them after launch.

14. How fast will the site load and how will you test it?

Page speed affects both rankings and conversions. Ask whether performance is tested during the build process and what tools are used (Lighthouse, Core Web Vitals, PageSpeed Insights). A target score isn't unreasonable to ask for.

Post-Launch Questions

15. What support is available after launch?

Launch day is not the end of the project — it's the start of the site's working life. What happens when something breaks at 9pm on a Friday? Is there a support contact? Is it included in the project fee or billed separately?

Our SiteCare plans exist precisely because this is where most agencies drop the ball. From £65/month, we cover hosting, security monitoring, software updates, and backups. It's worth understanding from any agency you hire what your post-launch situation looks like.

16. How will content updates be handled?

If you need to add a new service page, update your pricing, or publish a blog post, how does that work? Can you do it yourself via the CMS? Do you need to submit a support ticket? Is there a cost per change?

17. Will you provide training on the CMS?

If you're expected to manage the site yourself, you need to know how. Basic CMS training should be included in any project — a short session walking you through how to update pages, add images, and publish content.

The Questions Agencies Rarely Get Asked (But Should)

18. What's the worst project you've worked on, and what went wrong?

This is not a trick question. Experienced agencies have had difficult projects — scope creep, client-side delays, technical challenges. How an agency talks about those experiences tells you a lot about their honesty, self-awareness, and how they'd handle a similar situation with you.

Good answer: A candid account of what went wrong and what they changed as a result.

Red flag: "We've never had a bad project." That's not credibility — it's a script.

19. Do you have references I can contact directly?

Testimonials on a website are curated. A direct conversation with a previous client is not. Ask for references from projects similar in scope to yours, and actually call them.

20. What do you not do?

Every agency has limits. Knowing what they don't handle — copywriting, photography, complex integrations, ongoing marketing — helps you plan what you'll need to source elsewhere and prevents disappointment when those needs arise mid-project.

Putting It All Together

You won't get through all 20 of these in a single call. Prioritise the ones that matter most for your specific situation. If you're commissioning a simple brochure site, ownership and post-launch support questions matter most. If you're building something with complex functionality, the process and technical questions deserve more weight.

What you're looking for in the answers is consistency, specificity, and honesty. Vague reassurances, deflection, and sales pressure are all warning signs. A good agency will give you direct answers to direct questions — and if they're unsure about something, they'll say so.

If you're ready to talk through your project, start with our brief form and we'll come back to you with straight answers. Or if you'd rather have a conversation first, get in touch.

Frequently Asked Questions

How many agencies should I get quotes from?

Three is the standard recommendation — enough to give you meaningful comparison without overwhelming the process. Make sure all three are quoting against the same brief. A well-written brief produces comparable quotes; a vague one produces quotes that can't be compared. If you need help with the brief, our guide on how to write a web design brief covers exactly what to include. Clutch recommends reviewing at least three agencies before committing.

Is it reasonable to ask an agency for references?

Yes — and any professional agency should be able to provide them. References from comparable projects (similar size, industry, or technical complexity) are more valuable than generic endorsements. Ask the reference specifically about communication, how problems were handled mid-project, and whether they'd use the agency again. Those three questions tell you more than any portfolio image.

What should I do if an agency can't answer my technical questions?

It depends on which questions. An agency that can't explain why they're recommending a particular CMS, or can't tell you how post-launch support works, is either not experienced enough for your project or not used to working with informed clients. Either way, that's useful information. However, if you're asking deeply technical questions that require a full discovery process to answer accurately — architecture decisions, specific integrations — a good agency will say "we'll know more after discovery" rather than bluffing. The Google Search Central documentation is a useful reference for technical SEO questions specifically.

Related Reading

• How to Choose a Web Design Agency (Without Getting Burned)
• How to Write a Web Design Brief
• The Web Design Process: What to Expect When You Hire an Agency
• Web Design Pricing Models Explained

• **Complete Guide:** Custom Website Design: The Complete Buyer's Guide