A demand-generation team is not a list of channels. It is an ownership system for turning a defined audience problem into evidence that the business can act on. A small team may have one person carrying several roles; a larger team may split them across specialists. The operating model is sound when the handoffs and decisions remain visible either way.
Start with the route, not the org chart: audience definition, offer, distribution, capture, qualification, sales acceptance, pipeline evidence, and review. Then assign the smallest set of roles needed to keep that route reliable.
Define the team’s commercial contract
Write what demand generation owns and what it does not. A useful contract can include:
- creating and testing demand hypotheses for named audiences;
- delivering source-known responses or qualified conversations under a shared definition;
- preserving campaign, content, and offer context;
- reporting evidence and uncertainty to sales and leadership;
- stopping or repairing work when the quality or capacity boundary is breached.
It should exclude guarantees of revenue, automatic acceptance of every lead, unlimited content production, and platform-reported conversions treated as commercial outcomes.
Use five capabilities, not five mandatory hires
Organize work around capabilities:
| Capability | Core question | Possible owner | |—|—|—| | Audience and offer | who has the problem and why now? | growth lead or founder | | Distribution | where can the hypothesis be tested? | channel owner | | Content and proof | what evidence helps the buyer decide? | editor or subject expert | | Measurement | can the path be reconstructed? | analytics or RevOps owner | | Handoff and learning | what happens after response? | sales or lifecycle owner |
One person can hold all five capabilities in a small company. That is acceptable if the accountability is explicit and conflicts are reviewed. Adding a title without a handoff does not add capacity.
Build a RACI around decisions
Use a RACI for the decisions that can create loss or ambiguity:
| Decision | Responsible | Accountable | Consulted | Informed | |—|—|—|—|—| | audience rule | growth owner | commercial owner | sales, expert | delivery | | offer and claim | content owner | commercial owner | legal/policy as needed | channel owner | | launch QA | channel owner | growth owner | analytics | sales | | lead acceptance rule | sales owner | revenue owner | RevOps | growth | | budget change | growth owner | owner/founder | sales, delivery | team | | post-test verdict | analytics/RevOps | commercial owner | all owners | leadership |
One decision should have one accountable role. “Marketing and sales” is a collaboration, not an accountable owner.
Define handoffs as evidence contracts
A handoff is complete when the receiver has enough context to act without rebuilding the entire history. Define the minimum fields:
- source, campaign, content, and offer;
- requested service or problem;
- geography, role, and urgency where relevant;
- consent and contactability state;
- owner and due time;
- acceptance, rejection, or unknown reason;
- next action and timestamp.
The sender owns completeness at the handoff boundary. The receiver owns the response and the outcome state. If a field is not available, mark it unknown; do not silently infer it from a channel or page.
Choose KPIs by decision layer
Avoid one blended “demand-gen KPI.” Use layers:
Reach layer: eligible audience exposure and delivery health.
Response layer: source-known visits, registrations, replies, or forms.
Quality layer: accepted responses, fit, urgency, and contactability.
Pipeline layer: opportunity entry, progression, and mature outcomes.
Capacity layer: response time, queue load, expert review, and delivery constraints.
Each KPI needs a definition, owner, maturity rule, and decision it can change. If a metric has no decision attached, keep it as context rather than a target.
Design the weekly operating rhythm
The team needs a short loop:
- Signal review: what changed in audience, source, quality, or capacity?
- Exception review: which records cannot be reconstructed?
- Decision review: what will continue, change, pause, or remain unknown?
- Owner review: who will repair the first break and by when?
Keep platform views and commercial views separate. A paid platform may show a conversion while sales has no accepted record. The discrepancy is a handoff or definition question, not a reason to choose the more flattering number.
Protect small-team capacity
For a small team, start with a single audience, one offer, one primary channel, and one quality contract. Assign secondary work to a hold queue. Do not ask the same person to launch, respond, analyze, and rewrite the offer in the same hour without a stop rule.
For a larger team, specialization should reduce bottlenecks rather than create queues. Set service levels for analytics QA, creative review, sales acceptance, and content evidence review. Escalate when a queue breaches the level; do not hide the breach by changing the denominator.
Use a decision-ready dashboard
The dashboard should show a small set of views:
| View | Required fields | Decision | |—|—|—| | audience | segment rule, exclusions, evidence coverage | continue or redefine | | channel | source, spend/workload, response, quality | test or repair | | handoff | owner, due time, acceptance, reason | fix process or capacity | | pipeline | stage, maturity, value scope | maintain or change investment | | risks | claims, consent, data gaps, capacity | pause or escalate |
Do not build a dashboard before the definitions and owners exist. A polished view of contradictory data increases confidence without increasing truth. Where campaign parameters are used, keep naming governed; Google Analytics’ campaign URL guidance explains why inconsistent values can fragment reporting.
Team verdicts
Operating: one accountable path, stable handoff fields, and a review rhythm produce interpretable decisions.
Role conflict: two teams can change the same rule, or nobody owns a material transition.
Capacity-limited: the process is clear, but response, review, or delivery capacity is already at the boundary.
Evidence-limited: source, acceptance, or maturity evidence cannot support the KPI being used.
The Demand-Generation RACI is complete when it names the commercial contract, capabilities, accountable decisions, handoff fields, KPI definitions, weekly rhythm, capacity limits, and escalation path. A team is structured when work can move and be challenged by evidence—not when every channel has its own owner and dashboard.
How did this article land?
Choose one reaction. You can change it anytime.
