B2B Demand Generation Brief to Protect Your Campaign Budget
V
Vinita S
October 14, 2026•5 min
B2B Demand Generation Brief to Protect Your Campaign Budget
A low cost per lead can hide expensive delivery. In the illustrative comparison below, two campaigns each cost $6,000 and deliver 100 contacts. One produces 40 accepted records; the other produces 80. The quoted price is identical, but the cost per accepted record doubles in the first campaign.
A B2B demand generation brief should make that difference visible before you approve a proposal. This guide shows what to define, which numbers to request and how to identify the work your budget actually covers.
Define the problem and audience
Choose whether the campaign must build awareness, generate content engagement or identify people ready for a sales conversation. These outcomes need different offers, evidence and reporting.
Ask for a recent comparable campaign baseline showing delivered records, accepted records, rejection reasons, total cost and follow-up completion. Keep market, audience, offer and reporting window visible so the comparison is meaningful. If one proposal reports registrations and another reports completed meetings, their conversion rates answer different questions. Request the underlying counts and definitions before using either rate to set a target. Where comparable data is unavailable, agree a limited pilot and use its results to establish the baseline.
Also define how the campaign builds awareness and captures interest before sales engagement. Content interactions and event registrations can be valuable outcomes. Agree which signals trigger nurture or a sales conversation, then measure each stage against the promised campaign objective.
Define industry, company size, geography, relevant roles and exclusions. For example, an illustrative security campaign might target US manufacturers with 200–1,000 employees and IT directors or above. Replace these sample boundaries with your actual audience.
The distinction between demand and leads helps clarify the outcome before setting volume targets.
Specify the work and the exclusions
Require a response against each deliverable:
Content: supplied asset, revisions or new creation.
Distribution: included channels, markets and audience checks.
Follow-up: nurture, qualification or delivery only.
Handoff: required fields, engagement evidence and destination.
Mark every item included, excluded or dependent on a client input. If the agency distributes content but your team must qualify respondents, the proposal buys contact acquisition and leaves qualification work with you. Price that internal work when comparing options.
Write lead acceptance rules
Test the delivery definition against sample records. An operations manager downloading the security guide fails an IT-only audience requirement. An IT director at a matching manufacturer passes the audience check, but the download alone does not establish a purchasing project.
Specify the qualifying action and its evidence: a content interaction, an agreed callback or a conversation documenting the prospect’s current challenge. Use the level the campaign actually promises.
Audience fit: verified account and role boundaries.
Record quality: complete, usable required fields.
Interaction: date, source and relevant evidence.
Duplicates: an agreed lookback window and exclusions.
Agree review deadlines, rejection reasons and replacement eligibility. Track initial acceptance separately from replacements so repeated delivery problems remain visible.
Assign the work on your side
Name the owners for approvals, exclusions, CRM preparation, delivery review and follow-up. Missing inputs delay launch; unworked accepted contacts make campaign performance harder to interpret.
HubSpot’s SLA guidance links shared goals and lead definitions with accountability. Put both delivery and sales responsibilities in the brief.
Request follow-up coverage: accepted records receiving the agreed follow-up divided by accepted records assigned to sales, multiplied by 100. Check this before assuming poor conversation results came from targeting.
Separate fees, spending and reporting
Split setup, content, distribution, media and tools. Include internal qualification costs when your team supplies that work. Use the same cost scope for every option.
Then calculate acceptance rate: accepted records divided by delivered records, multiplied by 100. Calculate cost per accepted record: campaign cost divided by accepted records.
The comparison below uses hypothetical figures and identical acceptance rules. It is an arithmetic example, not agency pricing, market research or DemandTech results.
📊 Data TableSwipe to view →
Measure
Campaign A
Campaign B
Campaign cost
$6,000
$6,000
Delivered contacts
100
100
Accepted records
40
80
Acceptance rate
40%
80%
Cost per accepted record
$150
$75
Both show $60 per delivered contact. Checking acceptance reveals the difference. Accepted records still do not guarantee meetings, opportunities or revenue; inspect conversation quality and later CRM outcomes separately. Apply only the agreed criteria: valid event registrations should not be rejected for lacking an immediate sales request when registration was the promised outcome.
Use rejected-record reasons to choose the next action:
Audience mismatch: review targeting and validation.
Duplicates: check suppression rules and timing.
Missing evidence: clarify the promised interaction.
Accepted records unworked: address sales capacity.
A brief you can adapt
For the illustrative manufacturing campaign, specify:
Audience and offer: agreed manufacturers, IT roles and security guide.
Scope: distribution plus defined follow-up; explicit exclusions.
Acceptance: audience fit, usable fields and documented interaction.
Ownership: named approvers, reviewer and sales owner.
Reporting: acceptance rate, rejection reasons, cost per accepted record and follow-up coverage.
Add your budget, launch dependencies, review dates and replacement process. Set targets from comparable historical campaigns where available; a different market or offer may require a pilot to establish a baseline.
Compare the answers before committing
Request a sample delivery record with sensitive details removed and a report showing the agreed calculations. Resolve unclear definitions before comparing prices.
A useful proposal should explain what reaches sales, what it costs and what happens when records fail the agreed checks.
What should a B2B demand generation brief include?+−
Include the business problem, priority audience, offer, campaign scope, exclusions, lead acceptance criteria, responsibilities, budget and reporting requirements. Identify which assets already exist and which must be created or revised. State the markets and roles you want to reach, along with accounts to exclude. Specify the evidence required with a delivered lead and the process for resolving rejected records. Add approval deadlines and the sales follow-up owner. The brief should make assumptions visible so providers can quote the same work. It does not need to prescribe every channel before an agency has assessed the audience and objective.
How is an agency brief different from a demand generation strategy?+−
A demand generation strategy sets the broader audience, positioning, objectives and approach to building interest over time. An agency brief translates a specific part of that strategy into work someone can propose and deliver. It defines what is included, what remains with your team, what evidence is expected and how the work will be reviewed. You can use a brief for a limited pilot or an ongoing engagement. If the strategy is still uncertain, say that explicitly and request discovery as a separate phase. Otherwise, agencies may price execution while you are expecting them to define the entire approach.
Should we request a guaranteed number of qualified leads?+−
You can ask a provider to propose a delivery target, but first agree what qualified means for this campaign. Audience fit, recorded engagement and readiness for a sales conversation are different checks. Specify which checks are required and what evidence confirms them. Ask how the target depends on audience availability, channel, offer and exclusions, and what happens if agreed records are rejected. A contact guarantee does not guarantee opportunities or revenue. Use your own historical data where comparable, and review a defined pilot before committing to larger volumes. Avoid accepting a large number attached to an unclear qualification definition.
What information should we share before requesting an agency proposal?+−
Share an audience definition, the offer or content asset, the campaign objective, your current process and any useful baseline. Explain existing customers, active opportunities and other exclusions that affect targeting. Outline your CRM handoff needs, available sales capacity and approval process. Include the budget range and intended launch window so the provider can propose a realistic scope. You do not need to provide unrestricted access to customer records during initial discussions. Describe the required checks first and agree the appropriate data exchange later. Ask each provider to identify missing inputs rather than assume your team can supply everything immediately.
How should we compare two demand generation proposals with different prices?+−
Compare the same scope, audience and acceptance criteria before comparing fees. Separate setup, content, distribution, media, tools and any qualification work your team must supply. Request delivered and accepted record counts, with rejection reasons. Calculate acceptance rate by dividing accepted records by delivered records, and cost per accepted record by dividing campaign cost by accepted records. Those calculations reveal differences a headline cost per lead can hide. Acceptance still measures the agreed delivery standard, not guaranteed revenue. For an event campaign, valid registrations can meet that standard; assess attendance, engagement and sales follow-up as separate stages with appropriate measures.
