How to Brief a UX Agency: A B2B Template for London Teams

Why Most UX Agency Briefs Waste the First Meeting

The single biggest cause of a slow, unproductive start to a UX engagement is not a bad agency — it is a brief that describes a solution ("we need a redesign") instead of a problem ("our demo-to-trial conversion has dropped 15% over two quarters and we don't know why"). A vague brief forces the first meeting to become a discovery session, which is fine, but it also means the agency cannot give you an accurate scope, timeline, or price until a second or third conversation. A sharp brief compresses that cycle from weeks to days.

This guide gives London B2B teams a practical structure for briefing a UX agency — whether the engagement is UX research, a UX audit, or a full UX strategy programme — so the first call is a scoping conversation, not a fact-finding mission.

The Six Things Every UX Agency Brief Should Include

1. The Business Problem, Not the Design Symptom

State the metric that is underperforming and the timeframe over which it changed — "trial-to-paid conversion fell from 18% to 13% over Q2" is a brief an agency can act on immediately. "Our onboarding feels clunky" is not.

2. Who the Product Serves

Name the primary buyer persona and the primary user persona if they differ, which is common in B2B SaaS. An agency scoping research or an audit needs to know whether it is designing for a procurement-driven enterprise buyer or a self-serve solo evaluator — the two require different evidence and different fixes.

3. What Has Already Been Tried

List prior internal attempts, even failed ones. This single item saves the most wasted time in early engagements — agencies routinely re-propose ideas a team already tested and shelved, because the brief never mentioned it.

4. Available Data and Access

Specify what analytics platform is in use (GA4, Mixpanel, Amplitude), whether session-replay tooling exists, and what access level you can grant. An agency that knows it will have read-only GA4 access and no session replays scopes very differently than one expecting full instrumentation.

5. Internal Stakeholders and Decision-Makers

Name who signs off on the engagement, who the day-to-day point of contact is, and who else needs to be consulted (engineering lead, head of sales, compliance). Agencies waste real time discovering a hidden stakeholder three weeks into a project.

6. Constraints You Already Know About

Budget range, hard deadlines (a funding round, a conference launch, a regulatory deadline), and any technical constraints (a legacy design system, a platform migration in progress) should be stated upfront rather than surfaced mid-engagement.

A Worked Example: Briefing a UX Audit

Weak brief: "We think our dashboard is confusing and want a UX audit." Strong brief: "Our B2B SaaS dashboard has a 40% drop-off between login and first meaningful action, measured in GA4 over the last quarter. We serve two personas — solo founders and enterprise ops teams — and suspect the dashboard is over-indexed on the enterprise persona's needs. We have GA4 and Hotjar session replays available, no prior audit has been run, and our engineering lead can commit two hours a week to review findings. Budget is set at £8,000-£12,000, with a hard deadline of six weeks before our next board meeting." The second version lets an agency return an accurate quote and timeline within a day, because there is nothing left to discover before scoping.

What to Deliberately Leave Open

A good brief states the problem precisely but does not prescribe the solution. Avoid specifying "we need three new screens" or "add a progress bar" — that is solution-jumping, and it is exactly what a competent UX strategy or research engagement exists to validate or replace with something evidence-based. The brief's job is to define the destination and constraints; the agency's job is to define the route.

How This Differs for an Enterprise vs. a Scaling SaaS Brief

Enterprise briefs typically need to name compliance and accessibility constraints (WCAG, sector-specific regulation) and the internal governance process for sign-off, since more stakeholders are involved. Scaling B2B SaaS briefs typically benefit more from stating growth-stage context — current MRR band, primary acquisition channel, and whether the product is pre- or post-product-market-fit — since this materially changes whether the right engagement is research, an audit, or a full B2B UX design agency partnership.

Frequently Asked Questions

How long should a UX agency brief be?

One to two pages is usually enough. The goal is precision, not length — a focused half-page brief that names the metric, the persona, and the constraint beats a ten-page document that never states what's actually broken.

Should we get quotes from multiple agencies using the same brief?

Yes — sending an identical, well-structured brief to two or three shortlisted agencies is the fastest way to compare like-for-like scopes and pricing. See our guide to choosing a UX consultancy in London for how to run that comparison.

What if we don't know whether we need research, an audit, or strategy?

Say that explicitly in the brief. A competent agency will use the discovery call to recommend the right engagement type rather than assuming — naming the uncertainty upfront is more useful than guessing at agency jargon.

Ready to brief us on your project? Book a free 45-minute consultation and bring whatever version of the brief you have — we'll help you sharpen it into something scopeable in that same call.