Alliance QBR Readout
Prep the alliance QBR with a data-grounded readout — joint footprint growth, the co-sell pipeline's account quality, and the whitespace for next quarter.
Partner - Alliance QBR
An alliance QBR grounded in footprint, pipeline quality, and whitespace
$1.8M
Joint pipeline
34
Whitespace accounts
| Section | Read |
|---|---|
| Pipeline | 12 deals, 4 late-stage |
| Quality | 9 of 12 in-market (HG) |
| Whitespace | 34 untapped overlap |
Why it lands
A partner QBR usually reviews the same pipeline slide both teams already have. This adds whether those 12 accounts are actually in-market — and hands the partner 34 untapped overlap accounts as next quarter's joint target list.
Overview
Build an alliance QBR readout combining a pasted joint-pipeline summary with HG enrichment — characterizing the joint install-base trajectory, the quality of the co-sell pipeline accounts, and the untapped whitespace — so the partner QBR is grounded in data, not slideware.
Use cases
QBRs that plan, not just report
Reviewing the pipeline is table stakes. Bringing 34 data-qualified whitespace accounts turns the partner QBR into next quarter's joint plan.
Honest pipeline quality
Co-sell pipelines get padded. Checking which accounts are genuinely in-market gives both teams an honest read on what's real.
View workflow prompt
# Alliance QBR Readout
## Parameters
- `{{partner}}` *(required)* — The alliance partner. Example: `Microsoft`
- `{{joint_pipeline}}` *(required)* — Pasted joint-pipeline summary (accounts, deal stages, amounts). Example: `12 co-sell deals, $1.8M, 4 in late stage`
- `{{category}}` *(required)* — Category for whitespace + intent context. Example: `security analytics`
## Purpose
Build the {{partner}} alliance QBR readout from {{joint_pipeline}} plus HG data — the joint footprint trajectory, the quality of the co-sell accounts, and the {{category}} whitespace for next quarter — so the QBR is a data conversation, not a status slide.
## Process
1. **Pipeline snapshot** — summarize {{joint_pipeline}} (count, value, stage distribution).
2. **Account quality** — `company_technographic` + `company_intent` on the pipeline accounts to assess whether they're well-fit and in-market (quality, not just quantity).
3. **Joint footprint** — characterize the partner-overlap base relevant to the {{category}}.
4. **Whitespace** — `search_companies` + `intent_category` for accounts with partner footprint + {{category}} intent NOT yet in the joint pipeline — next quarter's targets.
5. **Readout** — exec-grade QBR narrative: what shipped, pipeline quality, whitespace, the joint ask for next quarter.
## Output Format
Markdown with:
- `# Alliance QBR — {{partner}}`
- `## Pipeline Snapshot` (from the input)
- `## Account Quality` (fit + in-market read, cited)
- `## Whitespace for Next Quarter` (untapped overlap accounts)
- `## Joint Ask`
- `## Citations`
## Quality Checklist
- Account-quality read cites `company_technographic`/`company_intent`
- Whitespace accounts have partner footprint + intent, are not already in pipeline
- Readout is exec-grade prose, not a data dump
- Pipeline numbers come from the input, not invented