CMO Marketing-Impact Narrative
A CMO-grade impact narrative — your marketing-sourced metrics, framed against the market demand that marketing is supposed to be capturing.
How much of the in-market demand is marketing actually capturing?
+18% sourced pipeline. HG: 117K accounts
in-market, 35% high-signal. Room to capture more.
| Metric | Read |
|---|---|
| Sourced pipeline +18% | vs. 117K in-market accounts |
| Verdict | Small share of active demand |
| Next bet | Mine the high-signal pool |
Overview
Build a CMO marketing-impact narrative: take supplied marketing metrics (MQLs, sourced pipeline, influenced revenue) and frame them against HG's current in-market category demand — so the board sees marketing's results against the scale of the active buying pool, with honest labeling of supplied vs. HG-sourced data.
Use cases
Marketing impact in market context
Raw marketing growth is ambiguous. Framing it against HG category demand shows marketing's reach against the scale of the active in-market pool — the context the board actually wants.
A defensible board story for marketing
When the CMO can show marketing's reach against independent in-market demand data, the impact narrative survives the CFO's scrutiny.
View workflow prompt
# CMO Marketing-Impact Narrative
## Parameters
- `{{marketing_metrics}}` *(required)* — Pasted marketing metrics (MQLs, sourced pipeline, influenced revenue, CAC). Example: `Sourced pipeline $24M (+18%), MQLs 1,200, influenced revenue $9M`
- `{{category}}` *(required)* — Your category for demand framing. Example: `observability`
## Purpose
Build a CMO impact narrative that frames {{marketing_metrics}} against {{category}} market demand from HG — so leadership sees how marketing's results compare to the size and strength of the current in-market pool. Label supplied vs. HG-sourced data.
## Process
1. **State the metrics** — restate {{marketing_metrics}} (user-supplied; labeled).
2. **Market demand backdrop** — `list_intent_topics` to resolve the {{category}} topic hex ids, then `search_companies` with `intent.topics: { ids, inclusion_method: "ANY_PRESENT" }` (and again with `intent.signal_score: "HIGH"`) for the current in-market account count and high-signal share (the market marketing is fishing in). This is a point-in-time level, not a growth rate.
3. **Relative read** — set sourced pipeline and MQL volume beside the number of in-market and high-signal accounts as a qualitative scale comparison: does marketing's output look large or small against active demand? MQLs, pipeline dollars and account counts are different units, so do not compute a capture rate or share of demand unless you match marketing's accounts to the in-market cohort at the account level (e.g. a user-supplied account list passed to `search_companies` as `company_identifiers.domains: { ids: [<account domains>], inclusion_method: "ANY_PRESENT" }` with the same intent filter). Compare growth rates only if the user supplied a prior-period demand figure.
4. **Sentiment** — `get_product_reviews` for whether buyer priorities are shifting in ways marketing should address.
5. **Narrative** — a CMO-grade impact story: results, market context, the relative read, and the next bet.
## Output Format
Markdown with:
- `# CMO Marketing Impact — {{category}}`
- `## Results` (your metrics, labeled)
- `## Market Demand` (HG, cited)
- `## Relative Read` (marketing output against the scale of in-market demand; a capture share only from account-level overlap)
- `## Next Bet`
- `## Citations`
## Quality Checklist
- Marketing metrics labeled user-supplied; demand signals cited
- The relative read compares marketing results to the current in-market pool qualitatively; any share or rate comes from account-level overlap, never from dividing MQLs or dollars by an account count
- Next bet follows from the relative read
- Exec-grade, honest framing