Choosing a website design agency is unusually hard because almost every proposal looks the same on the surface. The decks use the same words, the portfolios show the same kind of screenshots, and the prices vary by a factor of ten for what appears to be the same deliverable. Buyers end up choosing on gut feel or on price, which is how most disappointing website projects begin.
The difference between agencies is rarely visual taste. It is whether they treat the website as a business system that has to produce enquiries, or as a design artefact that has to be approved. Those two definitions produce very different projects from the same brief, and you can tell them apart before signing anything if you know what to examine.
This guide sets out how we would evaluate a full-service website design agency if we were the ones buying: what full-service should mean, how to read a portfolio properly, the questions that reveal how an agency really works, how the common pricing models behave once a project is underway, and the warning signs that should end a conversation early.
What full-service should actually mean
The phrase is used loosely, so pin it down early. In practice there are three tiers dressed in similar language. A design studio produces visuals and hands them to somebody else to build. A build shop takes a template, drops in your logo and copy, and ships it. A genuinely full-service agency owns the chain from positioning and content structure through design and build to launch, measurement and iteration.
The distinction matters because the gaps between tiers are where projects fail. Beautiful designs get built badly. Well-built sites launch with placeholder copy because nobody was responsible for content. Sites go live with no analytics, so six months later nobody can say whether the investment worked. When one party owns the whole chain, those gaps become their problem instead of yours.
Ask directly which of those three the agency is, and ask them to list in the proposal who writes the copy, who sources images, who configures analytics, who handles hosting and domains, and who is responsible if the site is slow on mobile. An agency comfortable with that list is describing work they routinely do. One that deflects is quietly telling you those pieces will land on your desk mid-project.
How to read a portfolio properly
Portfolios are curated, so read them like a sceptic. The first move is simple: stop looking at the case study images and visit the live sites. Plenty of portfolio pieces no longer exist, have been rebuilt by someone else, or were never launched at all. If a site is live, you can evaluate the real thing rather than a flattering render.
On each live site, check the things a client cannot see in a screenshot. Open it on a phone over mobile data and see how long the first meaningful content takes to appear. Try the contact form. See whether the navigation makes sense to someone who has never heard of the business. Look at whether every page has a clear next action, or whether the site simply ends. These are the mechanics of whether a site generates enquiries, and they are largely independent of visual style.
Then look for relevance rather than volume. Twenty restaurant sites tell you very little about how an agency handles a professional services firm with a long sales cycle. What you want is evidence they have solved a problem structurally similar to yours: similar buying process, similar need to explain a service, similar integration with a CRM or booking system.
Finally, look for outcomes. A case study that says the client loved the new look is decoration. One that says enquiries rose from eleven to thirty-four a month, or that the quote request form completion rate doubled after restructuring, is evidence of an agency that measures. If no case study contains a number, assume nobody measured anything, and expect the same on your project.
The questions that reveal the most
A short list of unglamorous questions separates partners from vendors faster than any brief. Ask who owns the code, the domain, the hosting account and the analytics property when the project ends. The correct answer is that you do, on your own accounts, with the agency holding access rather than ownership. Anything else means leaving is expensive by design.
Ask what happens after launch, in specifics. How long is the defect window? What does a small content change cost, and how long does it take? Can your team edit pages without a developer? Sites rot when routine updates require raising a ticket, and the cost of small edits over two years frequently exceeds the original build fee.
Ask how many revision rounds are included and what counts as a revision. This single clause causes more project friction than any other. Two structured rounds with consolidated feedback works well. Unlimited revisions sounds generous and usually signals either a padded price or a process with no decision points.
Ask what they need from you and when. A credible agency answers immediately, because content, approvals and access are the usual causes of delay, and they have learned to schedule them. Vague answers here reliably predict a project that stalls and is then described as waiting on the client.
Then ask the most useful question of all: tell me about a recent project that went badly and what you changed afterwards. Every agency has one. The ones worth hiring answer plainly and describe a process change. The ones to avoid claim it has never happened, which means either inexperience or a habit of blaming clients.
Understanding the pricing models
Three models dominate, and each behaves differently once work begins. Fixed-price is predictable and suits well-defined projects, but it makes agencies defensive about scope, so anything not written down becomes a change request. Time and materials is honest about uncertainty and suits projects that involve discovery, but it requires trust and disciplined reporting to avoid drift. Retainers work best after launch, when the site is treated as something that improves monthly rather than a thing that gets finished.
Whichever model you choose, the comparison you should be making is not price against price. It is total cost of ownership across two years: build fee, hosting, licences for any premium plugins or platforms, the monthly support arrangement, and the realistic cost of the content edits you will want. A cheaper build with expensive edits and locked-in hosting is routinely the more expensive option by month eighteen.
Be equally wary of both ends of the range. A quote far below the others usually means a template, offshore assembly with minimal oversight, or a scope that omits content and integrations. A quote far above should come with a clear explanation of what the extra buys: original photography, custom functionality, research, or a team doing work the others left out.
Red flags worth walking away from
Guaranteed first-page rankings are the clearest one. Nobody controls Google's results, and an agency willing to promise it is either uninformed or comfortable misleading you. Neither is a good basis for a working relationship.
A proposal that arrives without a single question is another. If an agency can quote your project after one email, they are pricing a template, not designing a solution to your problem. Serious agencies ask about your customers, your sales process, your current traffic and what happens after someone submits a form.
Watch for proprietary platform lock-in, where the site can only exist on the agency's own system and cannot be exported. Watch for refusal to name the people doing the work. Watch for pressure tactics around discounts expiring. And treat slow, vague communication during the sales process as a preview: it is the most attentive an agency will ever be, and it only gets slower once the deposit clears.
What a good process looks like
A well-run project starts with discovery rather than design: who the site is for, what those visitors need to believe before they enquire, what currently stops them, and what the site must do that the old one did not. That conversation shapes the page structure, which is settled before anyone opens a design tool.
Content comes next, or at least in parallel. Designing around real copy produces a site that works when it is populated; designing around placeholder text produces layouts that break the moment your actual paragraphs arrive. If an agency wants your content at the end, they have the sequence backwards.
Design then moves from one or two key templates to the rest, with feedback consolidated into scheduled rounds rather than trickling in. Build follows, with staging links you can review on your own devices. Launch includes analytics, search console verification, redirects from old URLs, and a check that forms actually deliver to a monitored inbox. That last item is missed surprisingly often and quietly costs more than any design decision.
What happens after launch
The launch is the start of the useful part. A site that is never touched again is a brochure; one that is reviewed monthly against real behaviour becomes a channel. Ask what reporting looks like after go-live and what the agency does with it. Traffic numbers alone are not a report. Enquiries, form completion rates, which pages precede a conversion, and where visitors abandon are what justify further spend.
Ask, too, how the site connects to the rest of your operation. An enquiry that lands in an inbox and waits until someone notices is a lead with a decaying value. Routed automatically into a CRM, acknowledged instantly and assigned to an owner, the same enquiry converts at a materially higher rate. Full-service agencies that also build automation tend to design for that from the start, because they know the form submission is the middle of the process, not the end of it.
Frequently asked questions
Making the decision
Shortlist three agencies, give them the same brief, and compare how they respond rather than what they charge. Note who asked the sharpest questions, who described a process you could follow, who was specific about what they need from you, and who was honest about a project that went wrong. Then check one reference each and ask a single question: what was frustrating about working with them?
You are not buying a design. You are buying two years of a working relationship with the system your customers use to decide whether to contact you. Pick the partner who understands that, put the scope, ownership, revisions and post-launch terms in writing, and start with a clear number you expect the site to move.