CRO Pipeline State-of-the-Business
A CRO-grade state-of-the-business read — your pipeline and coverage numbers, framed against whether the market is helping or fighting you.
Executive - State of the business
Is coverage falling because of the market or your execution? Here's the evidence
2.4x
Coverage (your metric)
Market vs. execution
Coverage down. HG: category demand
still growing - so it's execution.
Coverage down. HG: category demand
still growing - so it's execution.
| Weak metric | Diagnosis |
|---|---|
| Coverage 2.4x | Execution (demand grew) |
| Conversion 18% | Competitor gaining |
| ASP flat | Mix shift |
Why it lands
When coverage drops, the easy excuse is 'the market's tough.' HG data showing category demand actually grew this period takes that excuse off the table — coverage fell on execution, and now the CRO knows where to push.
Overview
Produce a CRO state-of-the-business narrative: take supplied pipeline/coverage/conversion metrics and frame them against HG market signals (category demand trajectory, competitive pressure) — so the read separates 'we have a sales-execution problem' from 'the market is contracting' with evidence for each.
Use cases
Separate market from execution, with proof
Every down quarter blames the market. Pairing the metrics with HG demand data settles it: if demand grew while you shrank, it's execution — and the conversation gets honest.
Point the CRO at the real lever
Diagnosing whether each weak metric is market, competitive, or execution-driven tells the CRO which lever actually moves the number.
View workflow prompt
# CRO Pipeline State-of-the-Business
## Parameters
- `{{pipeline_metrics}}` *(required)* — Pasted pipeline/coverage/conversion metrics. Example: `Coverage 2.4x (down from 3.1x), conversion 18%, ASP flat`
- `{{category}}` *(required)* — Your category for market framing. Example: `observability`
- `{{competitive_set}}` *(optional)* — Key competitors to assess pressure from. Example: `Datadog, New Relic`
## Purpose
Produce a CRO state-of-the-business read that frames {{pipeline_metrics}} against the {{category}} market — is coverage falling because the market is contracting, or because of execution? Use HG demand + {{competitive_set}} pressure signals to separate the two, with evidence.
## Process
1. **State the metrics** — restate {{pipeline_metrics}} with trends (user-supplied; labeled).
2. **Market demand** — `intent_category` + `list_intent_topics` for whether {{category}} demand is expanding or contracting (the macro on coverage).
3. **Competitive pressure** — `company_technographic` + `company_intent` for whether {{competitive_set}} is gaining (the micro on win/conversion).
4. **Diagnose** — for each weak metric, assign the most likely cause (market contraction vs. competitive vs. execution) with the evidence.
5. **Narrative** — a CRO-grade read: where we are, what the market is doing, the diagnosis, and the lever to pull.
## Output Format
Markdown with:
- `# CRO State of the Business — {{category}}`
- `## The Numbers` (your metrics, labeled)
- `## Market Backdrop` (demand + competitive, cited)
- `## Diagnosis` (market vs. execution per metric)
- `## The Lever` (the highest-impact action)
- `## Citations`
## Quality Checklist
- Metrics labeled user-supplied; market signals cited
- Each diagnosis distinguishes market from execution with evidence
- The lever follows from the diagnosis
- Exec-grade prose, honest about uncertainty