Running a Pipeline Council That Stays Under 90 Minutes
A timed agenda for monthly pipeline councils—commit scrutiny, stage drift, and CRM hygiene without endless deal storytelling.
Pipeline councils fail when every deal gets a ten-minute monologue. Sellers perform; managers check email; RevOps wonders why fields stay empty.
We use a fixed clock for monthly councils chaired by Magnolia Path or internal leaders trained on the same format:
| Block | Time | Focus |
|---|---|---|
| Commit review | 35 min | Top commit deals only; evidence checklist on screen |
| Stage drift | 20 min | Deals that jumped stages without criteria |
| New pipeline | 15 min | Sourced deals entering stage 2+ this month |
| CRM hygiene | 10 min | Field completion rates by team |
| Actions | 10 min | Named owners for next steps |
Commit review rules: AE speaks two minutes maximum; manager adds one minute on risk; chair asks one clarifying question. No slides unless a technical validation diagram is essential.
For Taiwan teams with mixed Mandarin and English sellers, circulate the evidence checklist bilingual the day before. Councils that start with translation catch-up always run long.
Recording is optional. We prefer annotated deal briefs stored in CRM so absent executives can read asynchronously.
After three months, teams often internalize the chair role. We step back to quarterly prep or remain as external chair for governance retainers.