The hardest part of most web design projects is not the visual language. It is that the organisation cannot say clearly what it does. Service lists grow by accretion, departments name the same thing three different ways, and the site ends up as an honest map of an internal structure nobody outside the building understands. No amount of art direction fixes that, and a good studio will say so in the first meeting.
Bristol studios are small, opinionated and frequently booked
The independent web design scene here is unusually strong and unusually busy. Most practices are small, most are led by the people who do the work, and the better ones are booked several months out. That changes the buying process in two practical ways.
First, approach earlier than feels necessary and ask about availability before you fall in love with a portfolio. Second, expect to be assessed in return. Small studios choose their projects, and a brief that arrives with a clear problem, a named decision maker and a realistic timeline will get a better response than one that opens with a request for a quotation. This is not precious behaviour; a studio taking two or three projects a quarter cannot afford a bad fit.
A complicated service list is a web design problem
If your organisation offers overlapping services to several audiences, the structure of the site is the project. Decisions about what sits at the top level, what is a page and what is a section, which audience gets its own route, and what to call everything will absorb more time than the visual work and will determine whether the site is usable.
Insist that this happens before anything is drawn, and that you see it as a structure rather than a picture: a list of templates, a route for each audience, and the wording of the main navigation agreed in writing. Test it on somebody who does not work with you. The most common web design failure in complex organisations is that navigation labels use internal vocabulary, and everybody inside the building nods because to them it reads perfectly.
Write the structure before you buy the visuals
Content is the single most common cause of a stalled project, and the reason is almost always that the client agreed to write it. Sitting down to write forty pages while doing a full time job is not a plan, and the studio cannot proceed without it.
Decide explicitly who writes. If it is you, agree a schedule with dates per template and accept that the design will be reviewed against real text rather than filler. If it is the studio, price it separately so you can see what it costs. If it is a third party, make sure they are in the kickoff rather than receiving a brief second hand. A web design phase reviewed with placeholder text produces layouts that look balanced and break the day genuine copy arrives.
Constrained budgets do not have to mean a template
Charities, social enterprises, cooperatives and small professional practices make up a large part of the local client base, and most of them are working to a figure that will not stretch to a fully bespoke build across a large site. The usual response is to buy a theme and adapt it, which is a reasonable web design answer and not the only one.
The alternative is to narrow the scope rather than the quality: bespoke work on the handful of templates that carry the organisation, a simpler treatment everywhere else, and a second phase later if it earns its place. That produces something specific where it matters and modest where it does not, which is almost always better than something uniformly average. Say the number you have out loud at the start. Studios can shape a proposal around a real constraint and cannot shape one around a figure they are asked to guess.
Accessibility and plain language, decided early
Organisations serving the public here are frequently expected to meet a stated conformance level, and even where nobody demands it, a large share of the audience benefits. Contrast, focus states, heading order, target sizes and form error handling are all settled when the visual language is settled, so raise them in the brief rather than commissioning an audit at the end. WCAG 2.1 is the usual reference.
Plain language belongs in the same conversation. Reading age, sentence length and the naming of things are design decisions in everything but job title, and they affect the layout directly: a page written in short, direct sentences needs a different typographic rhythm from one written in institutional prose.
What happens in the year after launch
Launch is the point at which most attention stops and most cost begins. Decide in advance who owns the site, what they are allowed to change, and where they go when something breaks. A site with no named owner degrades predictably: the campaign banner outlives its season, pages get published without images, and the careful structure fills with documents.
Ask what an editor sees when they add a page, whether every component tolerates the content you will realistically have, and what the support arrangement covers, priced separately from the build so that you can decline it without losing the site. Ask for a short recorded walkthrough for whoever inherits the work. It is the cheapest line in any proposal and the first one cut.
Comparing three different shapes of proposal
You will receive quotes structured in incompatible ways unless you impose a shape. Ask each studio for a template inventory rather than a page count, named stages with exit criteria, the revision policy and what counts as a new round, who writes the copy, the platform named in writing, and what arrives at handover: editable source files, the component library, font licences in your name, administrative access to every account.
Running that exchange three times is a fair amount of work, and you can instead set out the requirement once and collect structured proposals written to the same brief. If the project turns out to be an application with logic behind it rather than a set of pages, the shortlist belongs with firms that build and maintain web applications. If the naming and positioning are the real problem, that work sits with brand and identity specialists and should be settled before any web design begins. For the wider view of this category, start from the overview of website design agencies.