Operations
Part of B2B demand generation operations explained for UK agencies and in-house teams
Why B2B demand generation service standards need a written owner
Service standards for B2B demand generation only hold when one named person owns each promise. Here is how to write, test and review them in England.
What to take away
- Standards fail without a named owner. The IAB UK creative best practice guidance treats creative approval as a defined step rather than a matter of taste, and the same logic applies to response times, data handling and reporting.
- Write each standard as a number, a period and an owner. A promise such as "we reply within one working day" needs a name beside it.
- Test standards against real work before signing them, not after a client complains.
- Review the list every quarter, because scope, tools and team roles change.
- Keep the list short. Eight to twelve standards is workable; thirty is decoration.
The B2B demand generation operations and delivery guide covers the wider workflow these standards sit inside, so read it before you draft anything.
Why standards need an owner, not a promise
The difference between a standard and an aspiration
An aspiration sounds reasonable in a pitch. A standard can be checked. "We keep clients informed" is an aspiration. "A written pipeline update by 4pm each Friday, owned by the account lead" is a standard.
Aspiration vs Standard
Aspiration
- Wording
- Vague
- Owner
- None
- Timing
- Unclear
- Evidence
- None
- Miss detection
- Hard
Standard
- Wording
- Checkable
- Owner
- One named person
- Timing
- 4pm each Friday
- Evidence
- Written update
- Miss detection
- Clear
Buyers increasingly ask for evidence. HubSpot's guidance on finding and reaching customers frames outreach as a repeatable process with defined targeting, which needs agreed internal rules.
A useful test is to hand the list to someone outside the account team. If they cannot say how a miss would be spotted, the wording is vague.
Who signs off each promise
Every standard needs one accountable person, not a team. In a small agency that may be the founder; in a larger one it sits with a delivery lead or operations manager. The B2B demand generation team roles in England article maps typical ownership splits, so two people do not believe they own the same promise.
Record sign-off. A short line in the statement of work is enough.
Where two people share a promise, name a deputy rather than leaving ownership open. The deputy covers holidays and sickness, so the standard still holds.
What a workable standards list covers
Response, reporting and quality
Cover four areas: how quickly you respond to a client query, when reporting lands, which quality checks happen before work leaves the building, and how data is handled. Keep each measurable.
Standards list coverage
- Response time by channel
- Reporting dates fixed
- Quality checks before launch
- Data storage and access
- Retention period set
- Escalation route clear
Split response times by channel. A shared inbox and a named account manager carry different expectations, and a single figure hides that.
Quality checks deserve attention in creative work. The IAB UK introduction to creative best practice sets out principles to adopt as a pre-launch checkpoint, not an afterthought.
Data, security and compliance
If you handle lead data or run outreach at scale, write down where it is stored, who can access it and how long you keep it. GOV.UK's business innovation, protection and cyber security section covers the security and protection context, especially for B2B technology clients.
For example, a team paying £400 a month for a data enrichment tool should still know which fields it stores and for how long.
Retention is the standard most often missed. Pick a period for enquiry records, then delete on schedule.
A checklist you can run this quarter
Use this as a working list, ticking each item only when evidence exists.
- Each standard names one owner and one deputy.
- Each standard has a number and a period attached.
- Response times are split by channel, for example email and shared inbox.
- Reporting dates are fixed and visible in the client calendar.
- Quality checks happen before launch, not after a complaint.
- Data storage, access and retention are written down.
- Escalation route is clear when a standard is missed.
- Misses are logged and reviewed, not quietly absorbed.
- Standards appear in the statement of work or contract schedule.
- A quarterly review date is booked with the client.
Common questions
How many service standards should an agency publish?
Eight to twelve is a practical range. Fewer than six leaves gaps clients notice; more than fifteen becomes hard to monitor and easy to ignore.
Do standards need to be in the contract?
They do not have to be, but putting them in a schedule or statement of work removes ambiguity when a promise is missed. A short appendix is usually enough.
Who should own the standards list overall?
One person should own the list itself, even where individual standards sit with different team members. In most agencies that is an operations lead or the founder.
How often should standards be reviewed?
Quarterly works for most teams. Review sooner if you change tools, add a service line or see repeated misses against the same standard.
