Skip to main content
    SEYMOURDIGITAL
    Web Design
    22 July 2025
    8 min read

    How to Choose a Web Design Agency in the UK: 7 Questions to Ask

    The questions most businesses forget to ask before signing a web design contract — and the answers that should concern you.

    James Seymour

    Founder, Seymour Digital

    The UK web design market contains extraordinary talent and extraordinary risk in roughly equal measure. An experienced client can identify the difference quickly. An inexperienced one — making their first significant web investment — often cannot, until the project has overrun by three months and the delivered result does not match what was discussed. These seven questions, asked before any contract is signed, substantially reduce that risk. They also tend to differentiate the agencies worth working with from those worth avoiding.

    1. Can We See the Last Five Projects You Completed?

    Most agencies maintain a curated portfolio showing their strongest work from any point in their history. Ask to see the last five completed projects regardless of how they look. This tells you two things: the consistency of their output, and whether their portfolio reflects current capability or work from three years ago when the team was different.

    When you review those sites, open them on your mobile phone. Run them through PageSpeed Insights. Load them on a slower connection. A visually impressive desktop screenshot does not tell you whether the site works commercially. The performance data does — and it is publicly available for any live URL.

    2. Who Specifically Will Work on This Project?

    Many agencies pitch with senior designers and experienced developers in the room and deliver with junior staff or offshore contractors. Ask directly: who will be the lead developer, who will be the lead designer, and is it possible to speak with them before signing? A credible agency introduces you to the actual team. An agency that deflects this question is telling you something important about its delivery model.

    Also ask about current capacity. An agency that is significantly overcommitted will deprioritise your project when another client's deadline conflicts. Understanding their current workload gives you a realistic view of the attention your project will actually receive.

    3. How Do You Handle Scope Changes?

    Scope creep is the most common cause of web project overruns and relationship breakdowns. Every project encounters requests for changes during build. A credible agency has a documented process: a change request form, a time or cost estimate for the change, and written sign-off before additional work begins. This protects both parties and prevents ambiguity.

    An agency that responds vaguely — 'we're flexible, we'll sort it out' — is setting up a situation where the client expects changes to be included and the agency plans to invoice for them. The conflict this creates is entirely avoidable with a clear process documented upfront.

    4. Who Owns the Code and Domain After Launch?

    You should own your domain outright, registered in your name or company name, in an account you control. You should have access to your hosting environment or the code repository that allows you to deploy elsewhere if you choose to. You should receive the complete source code of your website on completion.

    Some agencies retain control of these assets as a lock-in mechanism. If you want to change agencies, you effectively need to rebuild from scratch because you do not own the underlying infrastructure. This practice should be explicitly addressed and excluded in any contract before signing.

    5. What Does Your Handover Process Include?

    A professional agency delivers more than a live website. The handover should include documentation of the architecture and technology stack, access credentials for all relevant platforms (hosting, domain registrar, analytics, CMS), a walkthrough of the CMS if applicable, and a defined warranty period for post-launch bug resolution.

    Ask specifically: 'If we found a bug three weeks after launch, what happens?' The answer reveals how the agency views its relationship with clients after payment has been received — and whether they consider their obligation to end at launch or to extend through the site performing as promised.

    6. How Do You Measure Whether the Project Succeeded?

    Design agencies often measure success aesthetically. Engineering agencies measure it technically. Commercial agencies measure it by results: did organic traffic improve? Did conversion rate improve? Did the site achieve its stated commercial objective?

    Ask what metrics they propose tracking, and whether they have case studies demonstrating measurable commercial outcomes. An agency that can only point to screenshots rather than results may deliver a visually impressive site that does not move the business forward. The distinction matters.

    7. What Happens After Launch?

    A website is infrastructure, not a project. It requires ongoing maintenance, security updates, performance monitoring, and periodic content and strategy review. Ask what their post-launch support offering looks like and what the commercial model is.

    An agency with no structured post-launch offering is signalling that the relationship ends at launch. For a business where the website is a significant commercial asset, that is an unacceptable risk position. The best agencies view the launch as the beginning of a long-term partnership, not the conclusion of a transaction.

    The process of choosing a web design agency is itself a signal. An agency that answers these questions with specificity, confidence, and transparency has a mature process and is not afraid of scrutiny. An agency that deflects, generalises, or becomes defensive is showing you how they will manage challenges during the project. Choose the one that welcomes the scrutiny.

    Related Service

    Custom Web Design

    View Service