Pipeline reviews should show engaged seats, scaled to deal size

A stage and a close date can’t show who is engaged

A stage and a close date record only the seller’s view of a deal. Neither says who on the buyer’s side has spoken to you lately. So a €180k deal and a €30k deal look alike in the review, even when one rests on a single person. That matters because a B2B purchase is a group decision: the average one involves 13 people.^↗ At Palo Alto Networks, opportunities with multiple people attached were 8× more likely to advance in the pipeline than those with 1 person attached.^↗

We read the 5 pages AI answers cite for this question today.^↗ They cover the review itself well: a weekly agenda, a stakeholder checklist, a mutual action plan with owners and due dates. None sets how many seats a deal needs at a given size. None defines engaged as a two-way exchange within a set window. The only page that sets a number of engaged contacts uses the same one for every deal: 3 by stage 3.^↗

So the fix has 3 parts. Count seats against what the deal’s size needs, make the stage exits ask for them, and close each review on the next empty seat.

Count engaged seats against the seats a deal needs

Coverage is engaged seats divided by required seats, deal by deal.^↗ A seat is a buying role: the champion, the budget owner, IT or security, finance, the executive who signs. Engaged people from IT fill 1 seat, however many there are. A contact count can make a thin deal look busy. Google’s AI Overview for this question scores deals that way: 1 linked contact is a risk, 3 or more is healthy.^↗

Engaged needs a definition the CRM can check. We use a two-way exchange with the seat’s holder in the last 90 days.^↗ That means a call, a meeting or a written reply to a question you asked. Opened emails, accepted connection requests, webinar visits and the champion’s account of a meeting don’t count. None of them shows the seat’s own view.

The CRM needs 4 fields: each contact’s role on the deal, each contact’s last two-way date, the deal’s required seats and a coverage formula. In HubSpot, association labels on the contact-to-deal link can hold the role and filter reports.^↗ In Salesforce, contact roles on the opportunity do the same job. The review then reads coverage beside the amount, without asking the rep.

The same count works before a deal exists. Fewer than 1% of leads become closed deals.^↗ On a list of named accounts, engaged seats per account give marketing a better number to own than MQLs.

A €180k deal needs more seats than a €30k deal

The seats a deal needs grow with its size, because bigger deals involve more people. In 10,332 deals Gong analysed, won deals near $25k involved about 5 buyers and won deals near $200k about 25.^↗ Multi-threading lifted win rates by 130% on average in deals over $50k.^↗

Set the bands from your own deals rather than from a benchmark. Take the last 24 months of won and lost deals and group them by size.^↗ For each deal, list the roles that had a two-way exchange before each stage exit. A role engaged in most won deals of a band and missing from most lost ones is a required seat for that band.

Until that analysis is done, start small. Our starting point is 3 seats under €50k, 4 at €50–150k and 5 above €150k (Illustrative).^↗ Our build method starts with 3–5 required roles and lists 12 that nobody fills as a pitfall.^↗ Add a seat only when your deals ask for it.

Treat the bands as a starting point you will move. What matters is that the €180k deal is held to a higher bar than the €30k deal. ChatGPT’s answer today sketches a $180k deal with 5 stakeholders to engage and a $30k deal with 4: nearly the same bar for deals 6× apart in value.^↗

Stage exits should require engaged seats

A stage exit should name the seats that must be engaged, because seller activity can rise while the buyer stands still. Across 655,000 opportunities, win rates rose by 55% when decision makers were actively involved in the first 2 stages of the sales process.^↗ That puts the budget owner in the exit criteria for evaluation, well before the proposal.

A starting set for most long-cycle deals:

• Leave discovery when the champion is engaged and the budget owner is named
• Leave evaluation when the champion, the budget owner and IT or security are engaged
• Enter commit when every required seat for the deal’s size is engaged and the close date falls inside the quarter

Let the CRM check these at the stage change, as required fields or a prompt, so the review doesn’t argue about them.^↗ A deal that misses its stage’s seats doesn’t move on, and it stays out of commit until the next seat is engaged. Keep the checks light, though. Hard blocks on every field teach reps to type whatever passes.

Low forecast confidence starts in the stage definitions

We think low forecast confidence is mostly a data and stage-definition problem, not a rep problem. When a stage records what the seller did, a €180k deal can reach commit on a single relationship. Coaching the rep doesn’t change what the stage measures. When the stage records which seats are engaged, the forecast moves because its inputs do.

Only 45% of sales leaders and sellers have high confidence in their forecast accuracy.^↗ We read a number that low as a sign of how stages are built across teams, more than of who works them.

We also think deal size has to set the bar. A single playbook for a €30k and a €180k deal over-inspects the small deal and under-covers the large one. Below roughly €50k, a single seller can often reach the whole group; above it, the group grows and the cycle stretches.

And we think multi-threading happens reliably only when someone plans it: a named seat, an owner on your side and a date. Left to the champion, it happens when it suits the champion. We don’t say coaching never helps, or that clean stage data alone makes a forecast accurate. It makes the forecast honest about what each deal rests on.

End the review with the next empty seat, owner and date

The review should spend its time on the gaps, and every gap should leave with an owner and a date. It needs no new meeting. Add 3 columns to the weekly pipeline view: coverage, the next empty seat, and that seat’s owner and engage-by date. Then sort by the value of deals that miss their stage’s seats.

Here is how it reads for a fictional software vendor with 5 open deals worth €505k (Illustrative).^↗

The €180k deal sits in proposal with 1 of its 5 seats engaged.^↗ The €30k deal has 5 people across all 3 of its seats.^↗ The €95k deal looks busy, with 6 people engaged, yet they fill 2 of its 4 seats.^↗ A contact count would rate it the healthiest deal on the list.

The rep’s commit is €350k: the €180k, €140k and €30k deals.^↗ Counted by seats it is €170k, because the €180k deal hasn’t engaged its budget owner.^↗ That deal is 36% of the open pipeline and more than half of the rep’s commit.^↗ It leaves commit with a task: the budget owner engaged by 30 October 2026, owned by the vendor’s CEO and introduced by the champion. For the whole pipeline, report the share of open value in deals that meet their stage’s seats: 64% here.^↗

Give each seat an owner who can answer its first question: your executive for the budget owner, your solutions engineer for IT or security. The champion opens the door; your owner runs the conversation. A date that passes without the seat opens next week’s review, with a new date and a reason or a later close date.