Why web design in Brussels is a governance problem first
The client base here is not shaped like a normal city market. Alongside the usual mix of retailers, clinics and software firms, Brussels concentrates federations, member associations, representative offices, institutes and non-profits, and those organisations commission websites in a particular way. The brief arrives with a committee attached. Someone must represent the members, someone the legal side, someone the communications team, and the visual direction has to survive all three.
That changes what you are buying. In a straightforward commercial project the hard part is taste. In a Brussels project the hard part is agreement, and the studio you hire is partly being hired to run that agreement process. Ask candidates how they have handled a multi-stakeholder sign-off before, what artefact they use to close a decision, and whether they charge for workshops separately. A team that answers with a portfolio rather than a process is answering a different question.
Three languages, one web design system
Most sites produced here ship in French, Dutch and English, sometimes with German added for legal completeness. Treating this as translation work is the classic mistake. Language affects composition: label lengths differ, compound words break navigation, and a tagline that reads crisply in one language becomes two lines in another. If the design is composed in a single language and translated afterwards, the other versions inherit compromises nobody signed off.
Put the language question into the brief explicitly. Decide whether every version must be visually identical or whether each may adapt, decide which version is authoritative when they conflict, and decide who supplies terminology for interface labels. Ask a candidate to walk you through a trilingual site they built and show the language switcher behaviour on a deep page, not just the homepage. Language switching that dumps the visitor back at the start is a design failure, and it is extremely common.
Accessibility is a contractual obligation, not a feature
Public bodies, publicly funded organisations and many of the institutions based here are bound by accessibility requirements, and suppliers to them increasingly inherit those requirements through the contract. This has direct consequences for the visual work. Colour palettes drawn from a brand manual often fail contrast thresholds. Focus indicators get removed because they were considered unattractive. Text set over photography fails at small sizes. All three are decided during the design phase and are expensive to fix afterwards.
Ask whether the studio designs against WCAG 2.1 AA from the first concept, who on the team checks it, and whether they deliver an accessibility statement. Ask to see a colour system with contrast values documented. A web design team that treats accessibility as a development task will hand you a beautiful set of screens that your build partner cannot implement compliantly.
How the Brussels web design market divides
Broadly there are three groups, and their pricing logic differs more than their portfolios suggest. Independent studios of a handful of people work closely with the client and produce distinctive work, but they have limited capacity when several stakeholders need parallel attention. Mid-sized agencies combine strategy, design and content, and are the natural fit for organisations that need a governance process as much as a visual one. Network agencies and consultancies handle large institutional programmes with formal reporting, and charge for that overhead whether or not you need it.
Matching the supplier to the decision structure matters more than matching them to the sector. A small association with one decisive director is badly served by a formal programme structure, and a federation with a board is badly served by a two-person studio that expects a single client contact.
Writing a brief that produces comparable proposals
Ask every web design bidder for the same breakdown: discovery and stakeholder alignment, creative concept, screen production, design system documentation, and handoff. Require them to state how many concept directions they will present, how many revision rounds each phase includes, and the price of one additional round. Require a named designer and a named project lead.
State your own constraints honestly. If a brand manual is binding, say so, because a studio that assumed freedom will price creative work you cannot use. If translation is handled internally, say so. If your approval window closes for a month during the summer recess, say that too; institutional calendars derail more Brussels timelines than any technical issue.
Pricing models and what each protects
Fixed-price work protects your budget and punishes late changes, which suits a project with a settled brand and a defined page inventory. Time-based billing protects the studio and suits exploratory work, but it needs a written cap and regular reporting. A retainer makes sense once the site is live and the real work is continuous: campaign pages, report microsites, annual updates to a design system. Avoid outcome-linked arrangements for pure web design engagements, since the studio controls neither your traffic nor your membership growth.
What matters more than the model is the change-request mechanism. Ask how a change is estimated, who approves it, and whether small adjustments are absorbed. That single clause determines whether the relationship feels collaborative or adversarial in month four.
Ownership and the files you walk away with
Confirm that copyright in the delivered web design work is assigned to your organisation on final payment. Under civil-law systems the author retains certain moral rights that cannot be signed away, so ask specifically what the studio may still do with the work: publish it as a case study, enter it for awards, or reuse components. None of that is unreasonable, but you should know it in advance rather than discover it.
Then confirm the deliverables list: editable source files with organised layers, a documented component library, exported assets in the formats your build partner needs, and written licence terms for every typeface, photograph and icon set. Fonts are the usual trap, because commercial licences are tied to traffic volume and often sit in the studio's account.
When the brief is ready, look at how studios position themselves in the wider web design directory, compare related suppliers such as SEO specialists in Brussels, local digital marketing agencies and communications and PR teams, and then request proposals so the same scope reaches several candidates at once.