Campaign Brief Generator
Turn a campaign theme into a full brief — target segment, message angle, channel mix, and the in-market account list — grounded in real intent data.
Demand Gen - Campaign brief
A launch-ready campaign brief — segment, in-market list, angle, channels
312
In-market accounts
Brief, not a blank doc
Segment + in-market list + message
angle + channel mix, all grounded.
Segment + in-market list + message
angle + channel mix, all grounded.
| Section | Output |
|---|---|
| Segment | US MM software, 200-2000 |
| In-market | 312 accounts (HG intent) |
| Angle | Legacy-tool consolidation pain |
Why it lands
A campaign brief usually starts as a blank doc and ends as a guess. This one starts with 312 accounts actively researching the category and a message angle drawn from the legacy stack they are trying to replace.
Overview
Generate a demand-gen campaign brief for a stated theme: define the target segment, identify the in-market accounts via HG intent, derive the message angle from the segment's technographic pain, and recommend a channel mix — so the campaign launches from a data-grounded brief, not a blank doc.
Use cases
Briefs that start from the data
Instead of a theme and a vibe, the brief opens with the actual in-market account list and a message angle grounded in the segment's installed-stack pain.
Align demand gen and sales on day one
The same in-market list the campaign targets is the list sales can work — so marketing and sales are pointed at the same accounts from launch.
View workflow prompt
# Campaign Brief Generator
## Parameters
- `{{campaign_theme}}` *(required)* — The campaign theme or offer. Example: `migrate off legacy observability to a unified platform`
- `{{target_segment}}` *(required)* — Who the campaign targets. Example: `US mid-market software, 200-2000 employees`
- `{{category}}` *(required)* — The category whose intent identifies in-market accounts. Example: `observability`
## Purpose
Build a launch-ready brief for the {{campaign_theme}} campaign targeting {{target_segment}} — defining the in-market account list from {{category}} intent, the message angle from the segment's installed-stack pain, and a channel mix grounded in how this segment buys.
## Process
1. **Segment definition** — restate {{target_segment}} as a crisp targeting definition (industry, size band, geo).
2. **In-market list** — `search_companies` + `intent_category` for {{category}} intent within the segment; `company_technographic` to confirm the legacy-stack signature the campaign theme targets.
3. **Message angle** — derive the angle from the segment's shared pain (e.g., the legacy tool the theme displaces), not generic benefits.
4. **Channel mix** — recommend channels matched to the segment and intent stage (in-market accounts -> ABM + outbound; researching -> content + paid).
5. **Success metrics** — define the campaign's leading and lagging metrics tied to the in-market list size.
## Output Format
Markdown with:
- `# Campaign Brief — {{campaign_theme}}`
- `## Target Segment` (targeting definition)
- `## In-Market Accounts` (count + sample, cited)
- `## Message Angle` (the pain-grounded angle)
- `## Channel Mix` (channels x intent stage)
- `## Success Metrics`
## Quality Checklist
- In-market list cites `company_intent`/`intent_category`
- Message angle derives from a real installed-stack pain, not generic benefits
- Channel mix matches the segment's buying behavior
- Account count is from search, not estimated