A pipeline council exists so marketing, sales, ops, and CS stop arguing about different versions of the same pipeline number. One meeting, one dataset, one shared truth that every leader quotes back to the exec team for the next thirty days.
A pipeline council is a monthly cross-functional governance meeting that pulls sales, marketing, revenue operations, and customer success into one room to align on the same pipeline math. Rev ops runs the agenda. The council reviews coverage ratio, stuck deals, source performance, and segmentation drift, and leaves with a single pipeline number every department will quote for the rest of the month. It is governance, not forecasting, and it is not a deal review.
The six rules that define what a pipeline council actually is, who sits in it, and what it is supposed to produce in a single ninety-minute slot once a month.
A pipeline council exists to produce a single pipeline figure that marketing, sales, rev ops, and CS will all quote back to the exec team for the next thirty days. If finance hears one number from the CRO and a different number from the CMO on the same Tuesday, the company does not have governance. The council is where those numbers get reconciled, in public, with the dataset on screen.
A pipeline council runs once a month on a fixed calendar slot. Ninety minutes is enough to walk coverage, stuck deals, source performance, and segmentation drift without turning into a deal review. The cadence matters as much as the agenda. Ad hoc pipeline meetings get captured by the loudest crisis of the week, which is exactly what the council exists to prevent.
Rev ops chairs the council because rev ops owns the pipeline dataset. The CRO and CMO are participants, not chairs. That separation keeps the meeting about math instead of politics. Rev ops presents one dataset, every leader challenges it with their own questions, and the chair rules on which definition the company will use for the next month when there is a conflict.
The required seats are the CRO, the CMO, the head of rev ops, and the head of CS. Finance is a strong optional attendee because the pipeline number feeds the forecast. Sales managers and SDR leaders join when their segment is on the agenda. The council is deliberately smaller than a board meeting and deliberately bigger than a sales standup, which is how it stays useful.
The council leaves with three artifacts: the agreed pipeline number for the next thirty days, a short list of actions the group signed off on, and a dated owner for each one. No deliverable, no council. The chair posts the artifacts to the shared rev ops channel inside two hours of the meeting ending, so the number is in writing before anyone can relitigate it over Slack.
A pipeline council is not where individual deals get worked. That is what one on ones and deal reviews are for. It is also not a forecast call, which commits to a quarterly number and lives weekly. The council sits above both: it governs the dataset those meetings run on, so when the forecast slips, the council has already caught the shape of the slip before it hits the quarter.
The pipeline council agenda is the same every month on purpose. Repetition is the point. The same four blocks, in the same order, with the same rev ops dashboard on screen, so every leader learns to read the chart the same way and no one gets to argue about the format instead of the math. Coverage ratio first, stuck deals second, source performance third, segmentation drift fourth. Everything else is out of scope.
The council opens with coverage ratio: open pipeline divided by remaining quota, by segment, for the current and next quarter. The target multiple is set at the start of the year and does not move inside the meeting. If SMB coverage is three times and the target is four, that gap is the first conversation of the day, and marketing owns the response unless pipeline velocity is the root cause.
Block two is the stuck deals report: every opportunity open longer than the segment median cycle, grouped by stage. The council is not working the deals here. It is deciding whether the stuck pile is a sales execution problem, a product gap pattern, or a pricing signal. The owner of the response changes based on that decision, and the meeting records it.
Block three walks pipeline created in the last thirty days by source: inbound, outbound, partner, customer expansion. The council is looking for drift against the plan, not making channel strategy. If outbound created forty percent of SMB pipeline this month against a plan of fifteen, the council asks why and who is paying for the shift, and books the follow-up in rev ops.
Block four checks segmentation drift: the actual segment mix of pipeline created against the plan. If mid-market is forty-five percent of pipeline when the plan said sixty, that is a signal before it is a problem. Rev ops presents the mix, the CMO and CRO reconcile campaign targeting and territory loading, and the council commits to one adjustment, not six.
The last fifteen minutes of the slot are reserved for decisions and owners. Rev ops reads back every proposed action from the four blocks, the group approves or defers each one, and a dated owner is assigned. Nothing in the meeting counts until it has an owner and a date. The chair enforces that rule even when the CRO wants to leave early.
Individual deal strategy, forecast commits, headcount decisions, and tool procurement are out of scope and the chair rules them so on the fly. Those conversations happen in the forecast call, the one on one, the staffing meeting, or the ops roadmap review. The council stays narrow so the output stays trustworthy. Scope creep is the fastest way to kill the meeting.
A pipeline council runs off one dataset. Rev ops presents it, every leader challenges it, and no one brings a parallel spreadsheet. The dashboard below is the default surface the chair owns, refreshed inside the hour before the meeting starts. If a leader wants a cut that is not on screen, they request it before the next council, not during the current one. The constraint keeps the ninety-minute slot honest.
The first chart is open pipeline by segment for the current and next quarter, each segment compared against its coverage target. Every other block in the agenda refers back to this chart, so it has to be stable, versioned, and dated. The chair confirms the as-of timestamp out loud at the start of the meeting so no one argues the number is stale three slides later.
The second chart is pipeline created in the last thirty days by source and segment, compared to the same window a quarter ago. Open pipeline is inventory, created pipeline is flow, and the council has to look at both. A healthy inventory with falling flow is a cliff six weeks away. Rev ops annotates the chart with any one-off campaigns or events that would skew the comparison.
The third chart shows stage-to-stage conversion by segment for the trailing ninety days. The council uses it to catch quiet leaks: a stage that used to convert at sixty percent now converting at forty, inside a segment where volume looks fine. These are the leaks that do not show up in a weekly forecast call because the top-of-funnel number masks them.
The fourth chart is median sales cycle by segment, trailing ninety days. This is how the council defines stuck in block two. Any open deal older than the median plus one standard deviation lands on the stuck report. The chart has to be refreshed each month because cycle creep is one of the earliest signs of a buying slowdown and rev ops owns catching it.
The fifth chart overlays actual source mix on planned source mix for pipeline created in the last thirty days. The council is not approving channel strategy, it is catching drift. If partner pipeline is suddenly twenty percent of the mix when the plan said five, the council asks why and whether the economics still work at that share before the next council locks it in by inertia.
The sixth chart is segment mix of pipeline created versus plan. This is the chart finance quotes back to the exec team when the quarterly number lands differently than expected, so the council has to agree what it says each month. If the mix is drifting from the plan, the council either changes the plan or changes the targeting, but it does not leave the mix drifting silently for another quarter.
The fastest way to kill a pipeline council is to let it swallow other meetings. Within three months, the council becomes a forecast call, a deal review, and a vendor roadmap meeting at the same time, and nobody trusts the output. The failure modes below are predictable, which is why the chair enforces scope hard. Each of these conversations has its own forum. The council is the one place where none of them happen.
A forecast call runs weekly and commits to the quarterly closed-won number. A pipeline council runs monthly and governs the pipeline dataset the forecast depends on. The council spots cycle creep and coverage gaps that the forecast will feel six weeks later. If the council becomes a forecast call, the exec team loses the early-warning system and starts missing quarters without seeing it coming.
The council is not where the top ten deals get worked. That is what deal reviews and one on ones are for. When a leader starts pitching strategy on a specific account, the chair interrupts and books the follow-up in the right forum. The pattern that matters at council is deal shape, not deal content. Stuck deals is a bucket count, not a per-logo discussion.
The council looks at source performance as a drift signal, not as a campaign review. Campaign-level performance belongs in the marketing operations review the CMO runs separately. If the council keeps diving into open rates and ad spend, marketing stops bringing honest data because the forum became a performance review instead of a governance meeting.
A pipeline council spots data gaps, but it does not resolve them inside the ninety minutes. If a cut is missing from the dashboard, rev ops takes it as an action item and ships it before the next council. If a vendor demo is relevant, it goes on the rev ops roadmap review. The council treats the tooling as given for the slot, so the conversation stays on the business.
The council will surface capacity gaps: too few AEs for the pipeline a segment is producing, too few CSMs for the renewals a quarter is loading. It flags the gap and books the headcount conversation with the CRO, CMO, and finance offline. Opening headcount inside the council collapses the agenda, because every unresolved number turns into a request for more people within fifteen minutes.
Pipeline council attendance is non-negotiable for the CRO, CMO, head of rev ops, and head of CS. Delegates are allowed once per leader per year, not as a standing rule. The moment attendance becomes optional, the output stops being authoritative, and every other meeting goes back to running on its own pipeline math. Protect the slot like a board meeting.
Strkr unifies the CRM, calling, calendar, and forecast on one tenant, so rev ops can walk coverage ratio, stuck deals, source mix, and segmentation drift from the same dashboard every month. One login, one pipeline number, one shared truth for every leader in the room.
A pipeline council is a monthly cross-functional governance meeting that pulls sales, marketing, revenue operations, and customer success into one room to agree on the same pipeline math. Rev ops chairs the meeting and runs through coverage ratio, stuck deals, source performance, and segmentation drift. The council produces a single pipeline number every leader will quote to the exec team for the next thirty days, plus a short action list with dated owners.
A pipeline review usually means a sales manager working individual deals with their reps. A pipeline council is cross-functional, run by rev ops, and never touches individual deal strategy. The council governs the dataset that pipeline reviews and forecast calls both run on, so when the forecast slips the council has already caught the shape of the slip through coverage drift, stuck-deal patterns, or segmentation drift a month earlier.
Revenue operations runs the council because rev ops owns the pipeline dataset. The head of rev ops chairs the meeting, presents one dashboard, and rules on definitions when leaders disagree. The CRO and CMO are participants, not chairs. That separation keeps the meeting about math instead of territory. If rev ops does not yet exist as a function, the sales ops lead chairs with the CRO explicitly delegating authority on definitions.
The required attendees are the CRO, the CMO, the head of rev ops, and the head of customer success. Finance is a strong optional attendee because the pipeline number feeds the quarterly forecast. Sales managers and SDR leaders join when their segment is on the agenda. The room is deliberately smaller than a board meeting and bigger than a sales standup, which is how it stays useful. Delegates are allowed once per leader per year, not as a standing rule.
The agenda has four fixed blocks and is the same every month. Coverage ratio by segment first, stuck deals grouped by stage second, source performance by channel third, segmentation drift against plan fourth. The last fifteen minutes are reserved for decisions and dated owners. Rev ops reads back every proposed action, the group approves or defers, and nothing in the meeting counts until it has an owner and a date. Scope creep is ruled out of order by the chair.
Once a month, ninety minutes, on a fixed calendar slot. The cadence matters as much as the agenda. Weekly makes it a forecast call. Quarterly misses the drift signals the council exists to catch. Monthly gives enough time for coverage, stuck-deal patterns, and source mix to move meaningfully between meetings, and keeps the output fresh enough that finance and the exec team can quote the pipeline number for the following thirty days with confidence.
Three artifacts, written up inside two hours of the meeting ending. The agreed pipeline number for the next thirty days, a short list of approved actions, and a dated owner for each one. Rev ops posts the artifacts to the shared revenue channel so the number is in writing before anyone can relitigate it over Slack. If a council leaves without those three artifacts, the chair treats the meeting as unresolved and books a thirty-minute follow-up to close it out.
Once a company has at least three revenue-touching functions, sales plus marketing plus a dedicated ops or CS leader, and the pipeline number is already being quoted differently in different meetings. For earlier-stage teams, a weekly founder-led pipeline standup is enough. The council becomes necessary when nobody can tell the exec team which pipeline number is the right one, which usually happens somewhere between series A and series B scale.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
