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.
Is coverage falling because of the market or your execution? Here's the evidence
Coverage down. HG: category demand
still strong - so it's execution.
| Weak metric | Diagnosis |
|---|---|
| Coverage 2.4x | Execution (demand strong) |
| Conversion 18% | Competitor gaining |
| ASP flat | Mix shift |
Overview
Produce a CRO state-of-the-business narrative: take supplied pipeline/coverage/conversion metrics and frame them against HG market signals (current in-market category demand, competitive pressure) — so the read separates 'we have a sales-execution problem' from 'current market demand is thin' 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 is strong 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 current {{category}} demand is thin, or because of execution? Use HG current-demand + {{competitive_set}} standing signals to separate the two, with evidence.
## Process
1. **State the metrics** — restate {{pipeline_metrics}} with trends (user-supplied; labeled).
2. **Market demand** — `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 how many accounts are in-market now and the high-signal share (the macro on coverage). This is a current-level snapshot: say demand expanded or contracted only if the user supplied a prior-period figure.
3. **Competitive pressure** — `company_technographic` for {{competitive_set}} current install footprint, plus `company_intent` on a few representative in-market accounts (`topic_ids` from step 2, `fields: ["topics"]`, `granularity: "global"`, `context_type_names: ["Displacement"]`). Count a Displacement row toward a competitor only when its `vendor_names` includes that {{competitive_set}} vendor, and name the matched vendor per row; rows naming no {{competitive_set}} vendor are general category displacement, not pressure from the set. This is current standing (the micro on win/conversion): call a competitor gaining or slipping only against a prior-period figure the user supplied.
4. **Diagnose** — for each weak metric, assign the most likely cause (thin current demand vs. competitive vs. execution) with the evidence; call it market contraction only against a user-supplied prior-period figure.
5. **Narrative** — a CRO-grade read: where we are, where the market stands now, the diagnosis, and the lever to pull.
## Output Format
Markdown with:
- `# CRO State of the Business — {{category}}`
- `## The Numbers` (your metrics, labeled)
- `## Market Backdrop` (current demand level + competitor standing, Displacement rows matched to {{competitive_set}} by `vendor_names`, 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
- Competitor reads are current standing, scoped to {{competitive_set}} via `vendor_names`; no gaining/slipping claim without a user-supplied prior figure
- The lever follows from the diagnosis
- Exec-grade prose, honest about uncertainty