B2B lead capture London Manchester: planning briefs

What to take away

What a B2B lead-capture brief actually contains in each city

A B2B lead-capture brief is a short document that names the buyer, the offer, the page and form requirements (including relevant software), the lawful basis and the handover to sales. Briefs for Greater London and North West England need the same core information. The emphasis should follow the client's sales process and existing stack.

The five parts every brief carries

London briefs arrive from in-house growth teams, often with a CRM already chosen. The brief spends more words on routing rules, lead scoring and the service-level agreement between marketing and sales. The client expects the agency to work inside an existing stack and to match its naming conventions.

Manchester briefs more often arrive from a managing director or a practice manager at a professional services firm. The brief spends more words on what the offer is and who is allowed to receive it. The stack is usually chosen during the project, which adds a scoping call.

A London B2B brief template typically opens with a one-paragraph commercial case, then a table of buyer roles and named accounts. A Manchester brief opens with the service, the fee earner who will take the enquiry, and the response time promised to the prospect.

Both cities now ask the brief to fix the organisation rule and screening fields before the build starts, so a company address is treated differently from a personal one. That rule belongs in the brief, not in a developer's judgement call.

Name the capture software in the brief where the client has a clear requirement. HubSpot Forms can send enquiries into HubSpot CRM; Unbounce is a landing-page builder; Typeform provides online forms. These serve different roles, so do not treat them as like-for-like alternatives. If the client already uses HubSpot CRM, state whether submissions must enter it; if the brief calls for a landing-page builder, specify the build and integration requirements; if it calls for an online form, specify its fields and handover. These are options, not city-specific defaults.

Worked example: a ten-person Manchester accountancy practice

For this Manchester example, a lean form could ask for the business name, contact name and role, work email or phone, service needed and turnover band. Use the four-option turnover question as one field, not a substitute for the rest of the form. Mark which fields are required and why; keep the fee earner, response promises, lawful basis and suppression process in the brief.

For a London version, candidate fields could include company name, named contact, job role, work email or phone, target-account match, service need and buying timeframe. Include only what sales needs for account matching, routing or scoring. State the scoring inputs, routing owner and service-level agreement; test the assumption that buyers need a longer nurture sequence rather than building it in by default.

Sector mix: London financial and professional services versus Manchester manufacturing

The London cluster is financial services, legal, insurance, property and recruitment. Lead-capture work here supports high-value, low-volume pipelines. A single enquiry can carry a five-figure fee, so the brief tolerates more form fields and a longer qualification path.

The Manchester cluster is manufacturing, engineering, logistics, construction and the professional services that supply them. Lead-capture work here supports medium-value, higher-volume pipelines. The brief favours fewer fields and a faster route to a booked call.

The two clusters also differ in list quality. London clients often hold large opted-in databases built over years, and they want the new funnel to feed those. Manchester clients often start with a spreadsheet of trade contacts and need a lawful route to contact them.

Manchester professional services leads behave differently from London ones in one practical way. The buyer is often the owner of the business, and the owner answers the phone. London buyers are more often gatekept, so the brief must plan a longer nurture sequence, and the audience research has to name a real person rather than a job title.

Sector mix also decides the offer. A London accountancy firm selling audit readiness competes on credentials and sector experience. A Manchester engineering supplier selling a site survey competes on response speed, because the buyer often has other quotes by the end of the week.

That changes the channel choice. London briefs lean on paid search, LinkedIn and partner referrals from other advisers. Manchester briefs lean on trade associations, exhibitions, regional press and referrals from banks and accountants.

Neither mix is better. The mistake is to reuse a London brief in Manchester without cutting the field count and the scoring model. The second mistake is to reuse a Manchester brief in London without adding the routing rules the sales team will demand.

ICO business-to-business marketing rules that shape both briefs

The Information Commissioner's Office publishes guidance covering company-to-company contact. It sits alongside UK GDPR, the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations. The ICO business-to-business marketing guidance is the first document to read before writing a brief for a client in Greater London and North West England.

Three points from that guidance change what goes in the brief. A corporate subscriber is treated differently from a sole trader or a partnership in some channels. The lawful basis for contacting a named individual at a company still needs recording. Every campaign needs a suppression route that works when someone asks to stop.

The compliance block in a brief

Manchester suppliers are more likely to be small firms without a data protection officer. The ICO step-by-step guide to direct marketing for your small business is written for that reader, and it is a sensible attachment to a Manchester brief.

London briefs may sit inside a larger legal review run by in-house counsel or an outside firm. The compliance block still matters: record the applicable channel rules, approval and suppression process rather than relying on company size.

Neither brief should leave the acquisition route undefined, because cold email, paid social and purchased trade lists carry different lawful bases and different evidence requirements.

Both briefs should record the rule as a written instruction, so the developer builds the form the client actually approved.

Scope agency and software work in a brief

Do not treat location as a rate card. Ask each agency to quote the same named roles, seniority, specialism, scope and deliverables, separating agency fees from media spend and third-party items. Without comparable role-based quotes, the brief cannot establish whether either city is cheaper.

Treat any location comparison in the table as a prompt for questions, not as a rate benchmark. Ask each studio to separate strategy, data protection, build and design work in its proposal. This makes it easier to check whether quotes cover the same tasks and whether the brief needs a landing-page build, a form change or an integration.

The brief should specify whether the agency is pricing a project or estimating days, and what happens when the scope changes. Ask suppliers in either city for the same deliverables, role breakdown and assumptions so proposals can be compared.

What to request in a quote

Agency scope and test budget together shape the commercial opportunities in a brief. Set the number of test variants against the agreed build, software and media budget rather than assuming the city alone determines how much testing is affordable.

When the budget is fixed, the honest move is to cut scope rather than squeeze days. Drop the scoring model, keep the form and the follow-up sequence, and say what was dropped in writing.

Record the quote date, role, scope and whether software licences, media and data costs are included. This makes proposals easier to compare without treating an individual quote as a regional market benchmark.

ONS regional accounts and business data as context, not proof

ONS regional accounts can provide context on output, income and sector weight across UK regions. The ONS regional accounts can help a brief choose relevant market indicators. Record the geography, indicator and reference period alongside any figures used; naming the source alone is not evidence that a channel will work for a specific client.

Do not state that Greater London and North West England sit in different bands for output per head, or differ in employment share, unless the brief records the published values, geography and reference period. If those figures are not available, leave the comparison out.

For a sector comparison, quote the relevant ONS measure and reference period rather than asserting that one region carries more weight in a particular sector. Without verified figures, present the sectors as client-specific hypotheses to test, not as regional statistics.

ONS business data can provide enterprise counts by size and sector for UK market context. Before using a count to set a target, record the table, geography, size band, sector and reference period in the brief; do not imply that a target is supported by a count you have not checked.

Use regional and business data only after recording the figures and their context. Then set the target from the client's own pipeline history, not from a regional average.

A common failure is to quote a regional growth figure as a reason the campaign will succeed. Regional data describes the past. The brief needs a hypothesis about the buyer and a test that can fail.

A second failure is to treat a regional average as a benchmark for one firm. A ten-person Manchester practice is not a scaled-down version of the North West England economy.

A third use is gap analysis. If the client's pipeline sits heavily in one sector and the regional data shows the neighbouring sector is larger, that is a reason to test a second offer, not a reason to rebuild the form.

A comparison table for B2B lead capture London Manchester briefs

Use the table as a draft for each client, not as a fixed regional template. Replace generic entries with the named buyer, offer, field list, organisation rule, software, routing, owner and response commitment; check compliance against the ICO guidance and the client's own list history.

Common questions