Hiring a web design agency: the questions that actually tell you something

There are a lot of "questions to ask your web designer" lists online, and most of them are filler. "How long have you been in business?" "Do you have a portfolio?" These don't tell you anything useful, because every agency answers them the same way.

The questions worth asking are the ones where the answer reveals how an agency actually works, not how they describe themselves. Here are the ones we'd ask if we were on your side of the table.

What does your discovery process actually look like

This is the single most predictive question. The answer tells you whether the agency builds what you ask for, or whether they take the time to figure out what you actually need.

A good answer involves a structured process before any design happens. Workshops, stakeholder interviews, content audit, sitemap, sometimes user research. A weaker answer is "we have a kick-off call and then start designing".

You're listening for evidence that the agency thinks of discovery as work in its own right, with its own deliverables, rather than a quick chat before the real project begins.

How do you handle content

Content is the single biggest reason web projects run late. If the agency doesn't have a clear answer for how they handle it, the project will stall the moment they're waiting on copy from you.

Listen for whether they offer copywriting support, whether they'll write to a brief, whether they have a content production process for photo and video, and whether they build the timeline assuming content will be late (because it usually is). Agencies that have done this for a while bake content support into the process by default. Agencies that haven't will tell you "we'll need all the content from you upfront" and then act surprised when the project drifts.

If you don't have time to write your own copy, say so early. The right agency will have a plan for that.

Who actually does the work

A lot of agencies sell on the strength of their senior people and then deliver with juniors or subcontractors. That's not always a problem, but you want to know before you sign.

Ask who'll be designing your site, who'll be building it, and whether they're employees, contractors, or offshore. Ask whether the person you're meeting in the sales call will still be involved week to week. The answers don't have to be a particular shape, you just want them to be straight.

The follow-up worth asking: how many other live projects will those people be working on alongside yours? Capacity is usually a bigger predictor of timeline than skill.

What happens after launch

This question separates agencies that treat the website as a finished object from those who understand it as something that needs ongoing attention. Both can be valid, depending on what you need, but you want to know which one you're hiring.

A good answer covers the warranty period for fixes, how training is handled, what support looks like in the first few months, whether they offer ongoing maintenance, and how that's priced. A weaker answer is "we hand over the keys and you take it from there".

If they offer ongoing support, ask what's actually in it. Hosting and updates is the floor. Anything that calls itself a care plan should also include monitoring, security, backups, performance checks, and time for small improvements.

How do you measure whether the project worked

This one tends to surface the strategists from the order-takers. Most agencies measure success as "did we ship on time and on budget". The better answer involves what the site is meant to do for the business and how they'll know if it's doing it.

Listen for things like enquiry volume, conversion rate, time to first lead from a new page, organic traffic to specific service pages, or specific customer journeys completed. If the agency has thought about this, they'll have an opinion. If they haven't, they'll talk about page speed scores and how nice the design looks.

You don't need to hold them to specific numbers. You just want to know they think in those terms at all.

Can you walk me through a project that didn't go to plan

This is the question most people are too polite to ask, and it's one of the most useful. Every agency has had projects go sideways. The ones worth working with can talk about it without getting defensive, and have learned things from it that have changed how they work.

You're not looking for a horror story or a confession. You're looking for self-awareness, the ability to take responsibility, and evidence that they've actually changed their process in response to something that went wrong. Agencies that claim they've never had a difficult project either haven't done many, or aren't being straight.

What does the timeline actually look like, and what makes it slip

Most agencies will quote you a timeline. The useful follow-up is what they think is most likely to make it slip and how they handle it when it does.

A strong answer mentions content delays, sign-off bottlenecks, scope creep from new stakeholders being added late, and the agency's process for keeping the project moving when these things happen. A weaker answer is "as long as you give us what we need on time, we'll deliver on time", which is technically true and practically useless.

The point of asking is to find out whether they've built a process that's resilient to the things that always happen, or whether they're hoping this project will be the exception.

How do you handle disagreements about design or strategy

You will disagree with your agency at some point. How they handle it determines whether the project ends up better or worse for the disagreement.

The best answer is something like "we'll tell you what we recommend and why, we'll listen to your reasoning, and if we still disagree we'll show you the evidence we've got". The worst answer is "the client is always right". An agency that defaults to your preference on every call is not adding value, they're protecting the relationship at the expense of the work.

You're paying for expertise. You want an agency that will use it, even when it's uncomfortable.

What we'd do with the answers

Take these into a couple of agency conversations and notice the difference in how they respond. The ones who answer with confidence and specifics, and who occasionally disagree with you, are usually the ones to take seriously.

If you want to see how we approach all of this, our process page walks through how we run discovery, design and build, and our web design service page covers what's typically included. There's also a related read on project work versus growth partner retainers if you're trying to work out which shape of relationship fits.