Choosing a Web Design Agency

Choosing a web design agency is something most organisations do rarely, so the people running the process are often out of practice and working from a shortlist built on portfolios alone. Portfolios show what an agency can make look good, but they say little about how the project will be run, who will own the finished website or what happens when something breaks a year after launch. The tests below separate a capable partner from a polished pitch. They apply to a small brochure website as much as to bespoke WordPress web design for B2B organisations.

Each section covers one test, starting with the decisions to make before contacting anyone and finishing with the questions that matter after launch. Working through them in order tends to narrow the shortlist on its own, because weaker proposals stop holding up once they are compared on the same terms.

Decide What the Website Has to Achieve Before You Shortlist

Before shortlisting anyone, write down what the website has to achieve, who it has to serve and how success will be judged. A brief that only asks for something modern and easy to update gives every agency the same blank space, so each proposal fills it with different assumptions and none of them can be compared fairly.

The useful version of that document is short. It sets out the commercial job the website does, the audiences it serves in order of importance and the decisions that are already fixed, such as the deadline or the systems the website has to connect to.

• The enquiries, sales or applications the website has to produce and how they are counted today
• The audiences it serves, ranked, with the one task each group most needs to complete
• The content that already exists, the content that needs writing and who will write it
• The systems it must connect to, such as a CRM, a booking tool or a finance platform
• The people who approve the design and the person who accepts the finished build

Sending the same document to every agency on the shortlist turns the proposals into answers to one question rather than several different pitches. Our guide to briefing a web design agency covers what to include in more detail.

Know Which Kind of Supplier You Are Buying From

Web design suppliers fall into a handful of types and the right one depends on how much of the project you want handled for you. A freelancer, a design studio, a full service agency and a development company can all produce a good website, but they carry different risks once the launch is over.

None of these is the wrong choice in itself. Problems start when the supplier type does not match the project, such as a design studio quietly subcontracting a complex integration or a development company producing layouts nobody on its team has tested with real users.

Whichever type you shortlist, ask who will do the work day to day. The people in the pitch meeting are not always the people who design and build the website, so ask to meet the designer and developer who will be assigned and check whether any part of the project is passed to another company.

Read Portfolios for Results, Not Just Looks

A portfolio is evidence of what an agency can make look good, so read it for results rather than style. Ask which projects in it are live, open them on a phone and check how quickly they load, how easy the navigation is and whether the forms still work.

Case studies are more useful than galleries when they explain the problem, the approach and what changed afterwards. A case study that only shows screenshots tells you about taste, while one that describes the enquiries, the search visibility or the accessibility standard the website reached tells you about delivery.

Sector experience matters most where the audience or the rules are unusual. Public sector bodies have legal accessibility duties, healthcare organisations handle sensitive enquiries and technical B2B buyers expect a level of detail a consumer brand would never publish, so an agency that has already worked in your sector knows where the difficult conversations will be.

Judge the Process Rather Than the Pitch

A capable agency can describe its process in detail before you sign, so ask for it and judge the answer on its order and its checkpoints. The order matters because each stage fixes decisions the next one relies on, with the structure agreed before design, the design approved before the build and testing finished before launch.

Weak answers usually skip a stage or blur two of them together. An agency that moves straight from the deposit to a homepage design has not mapped the content yet. One that starts building before the design is approved will spend part of the budget on rework.

Priority Pixels works in the same order, with development starting only once the full design has been approved. The web design process from brief to launch sets out what should happen at each of these stages and the questions to ask at each one.

Check the Technical Standards Before You Sign

Technical standards are the part of a proposal most buyers skim, yet they decide whether the website stays usable, findable and lawful. Ask each agency which standards it builds to and how it tests them, then check the answers against the published guidance below.

An agency that answers these points vaguely is likely to treat them as extras later in the project. Accessibility is the clearest example, since fixing it after launch usually means reworking templates that were approved months earlier. The accessibility requirements for public sector websites show how much has to be designed in from the start.

Priority Pixels builds every website bespoke without themes or page builders, with accessibility requirements identified at the planning stage. Whoever you choose, ask to see a recent project tested against each of the four areas above.

Settle Ownership, Platform and Hosting Before Work Starts

Ownership should be settled in the contract, because the default position may not be the one you expect. GOV.UK guidance on the ownership of copyright works explains that when you commission a work, the first owner of the copyright is the person or organisation that created it unless you agree otherwise in writing.

That can cover the design files, the custom code and any photography or illustration produced for the project. Ask for a clause that assigns the copyright in the finished website to your organisation on final payment, along with the source files.

The platform decides how free you are to move later. WordPress itself is released under the GPLv2 licence, so a WordPress website can be taken to another provider. Page builders work differently, because the content and layouts are often tied to a tool that only the original supplier knows how to maintain.

Hosting deserves the same attention as ownership. Ask where the website will be hosted, who applies updates and security patches, how often backups run and how quickly the agency responds when something goes wrong. Managed WordPress hosting run by the agency keeps all of that with one supplier, while a separate host needs a clear agreement about who does what.

Compare Quotes on Scope Rather Than Price

Quotes for the same brief can vary a long way because each agency has assumed a different scope. Before comparing totals, line the proposals up against the same list of items and note what each one includes, leaves out or leaves vague.

The items that cause most disagreements later are the number of page templates, who writes and loads the content, how many rounds of design changes are included, which integrations are covered and what training the team receives at handover. Support after launch is the other common gap, since some quotes include a period of fixes and others charge for every change from the day the website goes live.

A lower quote that leaves out content loading or redirects is rarely cheaper by the end of the project. The work still has to be done, so it usually reappears later as a change request with less time available to do it properly.

Judge the Relationship That Follows Launch

Launch is the start of the relationship rather than the end of the project, so judge the agency on how it will look after the website once it is live. Ask who handles support requests, how quickly they respond and whether the people who built the website will still be involved a year later.

References are the most reliable test of this. Ask for two clients whose websites the agency has supported for several years, then ask those clients how problems were handled rather than only whether the launch went smoothly.

Training matters as well, because the team that edits the website every week will judge the project on how easy that is. Ask to see the editing screens of a recent build before you sign, so you know what your colleagues will be working with long after the agency has handed over.

The right partner will be comfortable with every test here, because a well run project has nothing to hide at the shortlist stage. An agency that resists written ownership terms, avoids naming its standards or cannot describe its process in order is already telling you how the project is likely to go.