How to Choose a Web Design Agency: Criteria That Separate the Right Partner

Knowing how to choose a web design agency protects you from a costly mistake, because you are not buying a one-off product. You are starting a working relationship that lasts months and a digital asset you will use for years. I have been in digital marketing since 2012. I have advised companies picking an agency, and I have sat on the other side of the table as the one being picked.
This guide covers the criteria that separate a good agency from a risky one, and a scoring table you can use today. Comparing price quotes line by line is a separate job. Here the focus is on judging the agency itself before you ever look at a quote. If you want to see how I work, my web design service page lays it out.
How to choose a web design agency: what is the short answer?
Choosing a web design agency means scoring each candidate on portfolio, working process, verified references, ownership of code and domain, and post launch support, then picking the one with the highest weighted total. Price comes last, because a cheap quote from the wrong agency usually ends up as the most expensive option.
In practice I suggest three stages. First, run a quick shortlist and drop anyone whose portfolio or sector fit is too weak. Second, hold an introductory call with the three or four agencies that remain. Finally, call their references, read the draft contract and fill in the scoring table.
The benefit of this method is simple. It moves the decision away from gut feeling and onto shared ground. That matters most when several managers have a say. In addition, six months later you will have a written answer to the question "why did we pick this agency?"
What should you define before you contact any agency?
Before you judge agencies, write down what you need. Otherwise every agency will sell you the solution it is best at, and you will end up comparing different things. So prepare a one page brief.
- Business goal: Should the site collect quote requests, find dealers or support hiring?
- Measurable conversion: Name the action that counts as success. My guide on setting website conversion goals helps here.
- Languages and markets: One language, or a multilingual site for export?
- Content ownership: Who will write the copy and supply the photos?
- Internal team: Who will update the site after launch?
- Timeline and budget range: Not an exact figure, but a realistic range.
Send the same brief to every agency. That way you read every answer as a reply to the same question. If your audience is still vague, start with a target audience analysis first.
Which criteria matter most when you choose a web design agency?
In my experience five core criteria decide the outcome when you choose a web design agency. Each one closes a different risk. As a result, an agency that is weak on one of them can cause trouble later, however strong it looks on the others.
- Portfolio: Has the agency delivered work at your level of complexity?
- Process: Are the steps from discovery to launch written down and repeatable?
- References: Would past clients hire the agency again?
- Ownership: Whose name is on the domain, the code, the design files and the accounts?
- Support: Who handles bugs, security and updates after launch?
I also use two supporting criteria: communication quality and technical competence. You can observe communication from the very first email. Technical competence shows up in how the agency answers your questions on SEO, speed and accessibility. The sections below explain how to test each one.
How should you read an agency portfolio?
A portfolio is a shop window, and a window does not always reflect the shop. So look at live sites, not screenshots. Open every project in a browser, try it on your phone and test the contact form. Projects that are offline or now run by another agency also tell you something.
In practice, here is what I check:
- Are the projects close to your sector or your level of complexity?
- Do the sites look like copies of each other, or does each brand feel distinct?
- Is the mobile experience as careful as the desktop one?
- Do pages load fast, and do the menu and forms work?
- Does the agency state its exact role, or does it simply add its logo?
The last point matters. For example, some agencies present a project as entirely theirs when they only did the visual design. So ask about each project: "What exactly did you build here?" You can also run a quick Lighthouse performance test. The same weak result across several portfolio sites says a lot about the agency's standard quality.
How can you check technical quality in a portfolio quickly?
You do not need to be a developer for this. With a few free tools you can build a useful picture in half an hour. For instance, Google's web.dev guidance sets the Core Web Vitals thresholds for a good experience at 2.5 seconds for LCP, 200 milliseconds for INP and 0.1 for CLS. Check how close the portfolio sites come to those numbers.
I also recommend these quick checks:
- Does every page have its own title and description? The SERP preview tool shows how they look in search.
- Do old URLs redirect to the right new pages? A redirect checker answers that in seconds.
- Can you read the text on mobile and tap buttons easily?
- Are images a sensible size, or does each page pull down several megabytes?
These tests are not a final verdict. The client may have broken the site after launch. Still, if the same problem appears on several projects, it gives you a good reason to raise it in the call.
Why does the working process matter more than the portfolio?
The portfolio shows the past. The process shows what will happen on your project. A good agency can describe discovery, information architecture, design, development, testing and launch in writing. It can also name the output and the sign off point for each step.
So ask these questions in the call:
- What do you ask in discovery, and what do you deliver at the end of it?
- Which tool do you design in, and how do you present designs to us?
- How many revision rounds are there, and what does a revision cover?
- Which devices and browsers do you test on?
- What happens on launch day and during the first week after it?
An agency that answers clearly has done this many times. On the other hand, "every project is different, we will see" sounds flexible, but it usually means there is no plan. To set expectations about design tools, see my Figma web design process guide.
What should you expect from the discovery phase?
Discovery is where a good agency and an average one differ most clearly. The average agency jumps straight into design. The good one first tries to understand your business, your competitors and your users. So the number of questions they ask you in the first meeting is an important signal.
Typical outputs of this phase include a sitemap, a content plan per page, the key user journeys and a measurement plan. The measurement plan lists which forms and buttons you will track. If you already have a site, the list of pages that bring traffic and a redirect plan also belong here.
Teams often skip the redirect plan, and that mistake is expensive. I explain what it takes to keep search traffic in my guide on protecting SEO during a redesign. If an agency cannot describe a concrete plan for this, write it down as a serious minus.
How do you verify agency references?
Testimonials on an agency website are hand picked, so they do not count as verification. Real verification happens when you speak to a past client yourself. Ask for contact details of at least two clients from the last two years. Ideally, one of them had a difficult project.
In short reference calls I ask:
- Did the project finish on schedule, and if not, why?
- Did the budget stay within the range you agreed at the start?
- How did the agency behave when a problem came up?
- How fast did they respond to support requests after launch?
- If you had a new project today, would you hire them again?
The last question is the most valuable. A hesitant "yes, overall we were happy" is not the same as a clear "absolutely". It also helps to contact a company from the portfolio directly, without going through the agency. That gives you an unfiltered view.
What ownership questions should you ask before signing?
Ownership gets the least attention and causes the most trouble. You need to know from day one whether you can take your site, domain and data with you if the relationship ends. So ask in writing, before the contract, whose name each of these assets will sit under.
| Asset | What you want | Warning sign |
|---|---|---|
| Domain name | Registered to your company, you hold the login | Registered to the agency, password stays with them |
| Hosting account | In your company's name or transferable | Agency shared server, moving costs extra |
| Source code and theme | Full copy handed over at delivery | Closed, licensed platform you cannot move |
| Design files | Editable source files handed over | Only exported images shared |
| Analytics and Search Console | Owner rights stay with your company | Agency account, you only have view access |
| Business email | Account your company controls | Inside the agency panel, limited access |
A warning sign in this table does not always mean bad intent. Sometimes it is just convenience. Still, put the handover terms into the contract. I cover the email side in more detail in my business email guide.
What does a closed platform mean compared with an open one?
Some agencies use a content management system they built themselves, and it only runs on their servers. At first glance this looks simple and safe. However, if you want to leave, you may not be able to move the site at all. In practice you would then pay for a brand new build.
An open platform means a widely used CMS or a documented framework. Another developer can take it over. I do not treat a closed system as an automatic reason to reject an agency. Still, I always ask two questions: "If we part ways, do we get a full copy of the site and the database?" and "Could another team understand this code?"
In short, the platform decides how dependent you will be on the agency. Dependence is not always bad; with a good agency you want a long relationship. That said, choosing that dependence knowingly is very different from discovering it later.
How do you judge post launch support and maintenance?
A website is not finished on launch day. In fact, that is when the real work starts. Security updates, backups, small content changes and bugs never stop. So treat the support model as seriously as the design when you choose a web design agency.
Specifically, ask these questions:
- Is there a free bug fix period after launch, and how many days does it last?
- What does the monthly maintenance plan include, and what does it exclude?
- Who do I contact in an emergency, and through which channel?
- Are first response time and resolution time written down?
- Where do you keep backups, and have you ever tested a restore?
A written response time is worth far more than a verbal "we will get back to you right away". I also explain how fresh content affects search visibility in my guide on content freshness and SEO. An agency that is vague about support may leave you alone after launch.
How can you judge communication in the first meeting?
You do not need a contract to judge communication. How fast they reply to your first email tells you a lot. So does whether they come prepared and whether they summarise your notes correctly. A team that is careless during sales will not become careful during delivery.
Also ask who your day to day contact will be. A senior manager often leads the sales call, and then someone you have never met runs the project. That happens a lot. So it is reasonable to ask to meet the project manager at least once before you sign.
Also ask about their project tool. Where do they track tasks, approvals and files? Do they send a weekly status update? On my own projects I get every approval in writing. Three months later, only a written record settles the "but we discussed this" argument.
How do you test SEO, speed and accessibility skills?
Many agencies say "SEO friendly", but the phrase alone says nothing. So ask concrete questions: who writes the page titles, who adds structured data, and how will old URLs redirect? Google's own page on hiring an SEO also advises asking for examples of previous work. It adds that no one can guarantee a number one ranking on Google.
You can ask a similar question about accessibility. For example, the W3C WCAG 2.2 guidelines require a contrast ratio of at least 4.5:1 for normal text at level AA. When you ask "how do you check contrast in your designs?", the agency should describe a clear method.
If you want to go deeper, my article on SEO and UX is a good start. Put simply, an agency that gives technical answers to technical questions really knows the work.
How much does sector experience matter?
Sector experience helps; however, it is not decisive on its own. An agency that has worked in your industry grasps the buying process and common customer questions faster. That shortens discovery and makes the first design round more accurate.
On the other hand, an agency with many projects in one sector may offer every client a similar solution. A site that looks like your competitor's makes it harder to stand out. So when you ask about sector experience, also ask how two of their projects in that sector differ from each other.
Manufacturers have extra needs, such as product catalogues, technical data and dealer networks. I collected those standards in my guide to manufacturing website design. In short, count sector experience as a bonus, but never let it replace portfolio and process.
Who should own content production?
Many business website projects stall because of content, not design. The agency finishes the template, then waits weeks for copy and photos. Therefore, settle content responsibility in the very first conversation.
There are three common models. In the first, you write the copy and the agency places it. Second, the agency interviews you and writes the copy itself. Finally, the agency supplies a skeleton, you fill it in and the agency edits the final version. Whichever you pick, the contract should say so clearly.
Also ask whether they plan content around search intent. A beautiful design full of headings nobody searches for brings no traffic. The steps in my guide on writing SEO friendly content give you a shared language for that talk. So give extra points to an agency with a clear answer here.
What signals should you look for in the first design presentation?
The first design presentation is the first hard evidence of how well the agency listened. In a good presentation, the agency links each design decision to something it learned in discovery. For example, you hear: "We kept the quote button here because your buyers check the technical sheet first."
In a weak presentation, decisions rest on taste alone, such as "this colour feels more modern". That is not always bad, but design without reasons turns the first revision round into a debate. Also check whether they show mobile views. An agency that only presents desktop mockups may treat mobile as an afterthought.
Finally, check the conversion focus. Does the design put the target action from your brief front and centre? I explain this approach in my article on conversion focused web design.
How do you build a scoring table to choose a web design agency?
A scoring table turns the choice into measurement instead of debate. Give each criterion a weight, score each agency from 1 to 5 and calculate the weighted total. The weights below are my starting point, based on field experience. Treat them as a baseline, not a universal truth.
| Criterion | Weight | What a 5 looks like | What a 1 looks like |
|---|---|---|---|
| Portfolio fit | 20% | Live, fast sites of similar complexity | Repeated templates, broken or offline sites |
| Process clarity | 20% | Written steps, outputs and sign off points | "We will see" level vagueness |
| Reference check | 20% | Both references would hire them again | No references, or reluctant ones |
| Ownership and handover | 15% | All assets in your name, handover in writing | Domain and code with the agency, no exit terms |
| Support model | 15% | Written response times, tested backups | Verbal promises, undefined scope |
| Communication | 10% | Fast, prepared, written summaries | Slow replies, repeated misunderstandings |
Example calculation: an agency scores 4 on portfolio, 5 on process, 4 on references, 3 on ownership, 4 on support and 5 on communication. Its weighted score is 0.8 + 1.0 + 0.8 + 0.45 + 0.6 + 0.5 = 4.15. I suggest that at least two people fill in the table separately. Where their scores differ, you have found the point to discuss.
When should you look at price?
Look at price last. That does not mean price is unimportant. The reason is simple: the price of an agency that fails the criteria only muddies the comparison. First, identify the two or three candidates that clear the bar in your scoring table. Then put only their quotes side by side.
This order also protects you from a mental trap. If you see a cheap quote early, you tend to forgive that agency's weak spots without noticing. Likewise, an early expensive quote makes you score a strong agency too harshly. So scoring before you see prices gives a fairer result.
Comparing quotes line by line is a separate exercise, covering scope, hidden costs and maintenance fees. I will only add one point here: comparing two quotes that describe different scopes is misleading. Ask every agency to write scope in the same format, listing pages, languages, features and support period. You can see finished work of mine on the references page.
Which red flags should end the conversation right away?
Some signs make scoring unnecessary. When I see them, I advise walking away, however impressive the agency looks otherwise. These signs usually grow into bigger problems halfway through a project.
- Guaranteeing a specific ranking in search results.
- Insisting on registering the domain in the agency's name.
- Offering a fixed price and design in the first call, without any discovery.
- Avoiding requests for reference contacts.
- Wanting to start on a price quote alone, without a contract.
- Gossiping in detail about previous clients.
The ranking guarantee matters most, and Google's own guidance warns against it. For a wider list of questions to ask any consultant, see my consulting checklist.
Which clauses must the contract include?
You have picked the right agency; now you need to put that choice on paper. A contract is not a sign of distrust. Instead, it protects both sides. I recommend reviewing it with your legal adviser, but on content I check for these clauses:
- Scope: which pages, languages, features and integrations are included.
- Timeline: phase dates and what happens if there is a delay.
- Revision limit and how you will price out of scope requests.
- Intellectual property: design and code transfer to you on payment.
- Asset ownership: who holds the domain, hosting and accounts.
- Support: duration, scope, response time and cost.
- Personal data: where form data lives and who can access it.
- Exit: how files and access transfer if the relationship ends.
Most contracts miss the last clause. Yet writing exit terms while things go well is far easier than writing them when things go badly.
Big agency or small team: how do you decide on size?
Agency size alone does not signal quality. A large agency may have more specialists, but your project may rank low on their list. A small team may give you more attention, but its capacity may be limited. So instead of asking "who is bigger?", ask "how important is my project to them?"
I use a practical rule. If your budget sits far below the agency's typical project, you will probably get its least experienced team. If it sits far above, you will stretch its capacity. Somewhere in the middle is healthiest. This is an observation from field experience, not a guarantee.
Working directly with one specialist or with a full team is a separate decision with its own trade offs. If you are curious about how I work, my about page summarises the process.
What is the final checklist before you decide?
Then scoring is done and one agency stands out. Before you sign, run one last round. It catches small but important details the table can miss.
- Does every item in your brief appear in the proposal?
- Did you speak to the references yourself?
- Does every row of the ownership table favour your company?
- Are the support period and response time written into the contract?
- Have you met your project manager?
- Does someone on your side own this project internally?
Every "no" on this list is a gap to close before you sign. Also, remember your own team's role. Even the best agency cannot keep to schedule with a client who takes weeks to approve.
Conclusion: how do you recognise the right agency?
To sum up, the right agency is not the one with the prettiest pitch. It is the most transparent one. It shows its portfolio openly, describes its process in writing, lets you talk to its clients, puts ownership in your name and defines support clearly. Once you score those five criteria in a table, the decision largely makes itself.
The first step you can take today is writing your one page brief. Then talk to three agencies and fill in the table. If you want a second opinion on your own project, write to me through the contact page. I will listen to your needs first, then tell you honestly whether I am a good fit.




