How to choose a web design agency — what to do before you talk to anyone

Most people start the agency search in the wrong place. They browse portfolios of top web design agencies, ask for recommendations, sit through sales calls, and then try to figure out which pitch was most convincing. The problem with this sequence is that without a clear picture of what you actually need, every agency sounds plausible and no comparison means anything.

The preparation you do before contacting anyone is the most important part of the process. Here’s how to do it properly.

Get clear on what you’re actually trying to achieve

Before you write a brief, before you send an email, answer three questions as specifically as you can.

First: what is the business goal? “A better website” is not a goal. “Increase demo requests from enterprise buyers by reducing friction in the first thirty seconds of the visit” is a goal. The specificity of your answer determines what kind of agency you need — and whether a given agency is actually equipped to help you. A team that specialises in brand storytelling for creative businesses is a different thing from one that builds conversion-optimised platforms for SaaS companies. Without a clear goal, you can’t tell the difference.

Second: what does success look like six months after launch? Pick one or two metrics that would tell you the project worked. Traffic, conversion rate, lead quality, time on site, bounce rate — whatever is most relevant to your situation. Write it down. Any agency worth hiring will ask you this question early. Having a clear answer signals that you’re a serious client, and it gives you a meaningful benchmark for evaluating proposals.

Third: what are your actual constraints? Budget range, timeline, whether you need post-launch support, whether the agency needs to handle content or just design and development. Be honest about what’s fixed and what’s flexible. This prevents a lot of wasted time on both sides.

Write a brief before you talk to anyone

A brief does one thing: it gives every agency you contact the same starting point, so you can compare responses on equal terms rather than on how well each agency’s salesperson performed.

It doesn’t need to be long. One page covering your business goal, target audience, the features you know you need, your rough timeline, and your budget range is enough. The act of writing it forces clarity you probably don’t have yet — and the gaps you can’t fill are useful information about where you need to do more thinking.

For more complex projects involving multiple stakeholders or significant budget, a formal request for proposal is worth the effort. It specifies deliverables, evaluation criteria, and submission requirements, and it signals to agencies that you’re an organised, serious buyer. The proposals you receive in response will be more detailed and more comparable than what you’d get from a round of informal conversations.

How to read a portfolio properly

A portfolio tells you how an agency thinks. Most people look at them the wrong way.

Relevance matters more than aesthetics. A portfolio full of restaurant websites and brand campaigns tells you very little if you’re building a complex product platform. Look for agencies that have handled projects at a similar level of complexity to yours — similar audience, similar functional requirements, similar stakes.

Outcomes matter more than screenshots. The strongest portfolios describe what happened after the site launched — not just how it looked. Conversion improvements, engagement changes, user behaviour shifts. If a portfolio shows only the visual result with no reference to business impact, that’s a meaningful gap. It may mean the agency doesn’t track outcomes, or it may mean the outcomes weren’t worth highlighting.

Look at the actual live sites, not just the case study images. Click through to the URLs. Test the load speed. Navigate on your phone. Check whether the UX holds up under real use conditions. Portfolio presentations show the best-case version; live sites show what was actually delivered.

Ask about projects that aren’t in the portfolio. A good agency won’t hesitate to tell you about work that was difficult or didn’t go as planned. How they talk about those experiences — what they learned, what they’d do differently — reveals more about their character than any highlight reel does.

Look for a consistent point of view. Does the work feel like it came from a team with a perspective, or does every project look like it was designed by a different studio? Consistency signals craft and strategic thinking. Random variation often means the agency takes direction without adding value.

The questions that actually filter for quality

Most discovery calls are spent listening to agencies describe themselves. Flip that. The questions you ask are more informative than anything they volunteer.

Ask what their discovery process looks like. An agency that skips straight to design is guessing about your users and your goals. Discovery should involve research before a wireframe is drawn. If their answer is vague or they treat it as optional, that’s a meaningful signal.

Ask who will specifically work on the project. Many agencies win business with senior talent and deliver it with junior staff. Ask for names, and ask to see individual portfolios. You have every right to know exactly who is doing the work.

Ask how they handle scope changes. Scope creep is one of the most reliable ways a project goes over budget. A clear process for documenting, estimating, and pricing changes protects you. An agency that’s vague about this is one where disputes are more likely.

Ask what you receive at handoff. At project end, you should own everything: design files, source code, CMS access, and documentation. If an agency is unclear about this, get it resolved before signing anything.

Ask how they measure success. If the answer amounts to “the client was happy,” that’s not enough. You want to hear about performance baselines, metrics tracked, and a plan for iteration after launch.

Ask whether you can speak to a past client. Every credible agency has references. If they hesitate or can’t produce one, that tells you something. A fifteen-minute reference call is worth more than three sales meetings.

The pricing model conversation

Most web design projects are priced on a fixed-scope basis: a defined deliverable set, a capped fee, a clear end date. This works well for launches and redesigns where the scope is relatively predictable.

Some ongoing relationships work better as retainers — a monthly fee for continuous design and development work. Retainers suit companies that need design as a constant function rather than a periodic project. The two models carry different risk and flexibility profiles, and the right choice depends on your situation.

Ask the agency which model they’d recommend for your specific situation and why. Their answer reveals whether they’re thinking about what’s best for you or what’s easiest to bill.

One thing most clients underestimate: budget separately for discovery, content production, and post-launch iteration. These three items are consistently underfunded and consistently critical. They’re not optional extras — they’re what makes the difference between a site that looks good and one that actually performs.

What to look for before you sign anything

The contract is where intentions meet accountability. Read it carefully, not as a formality.

The most important clause is IP ownership. You must own all final work — code, design files, creative assets — once payment is complete. If ownership is conditional or unclear, resolve it in writing before signing.

Deliverables should be specific. “Website design” is not a deliverable. The contract should list exactly what gets built, in how many revision rounds, and in what formats at delivery.

There should be a clear process for early termination. If the project needs to stop, both parties need protection. A fair structure reflects the work completed at the time of stopping.

Watch for automatic renewal clauses in maintenance or hosting contracts. These can lock you in annually with short cancellation windows. Understand what you’re agreeing to over the long term, not just for the initial project.

Understand the liability provisions. If the work has serious quality problems or there’s a launch failure, what recourse do you have? This matters more often than people expect.