higher win rates when decision makers were actively involved in the first 2 stages
Ebsta x Pavilion, 2025of sales leaders and sellers have high confidence in their forecast accuracy
Gartner press release, 2020Why does a close slip after a verbal yes?
A close slips after a verbal yes because the stage let the deal advance on one engaged seat. The sponsor, usually your champion, says yes and the forecast counts the deal. Only then do the seats whose reviews the signature waits on start their own work. Each review has its own queue, so the close moves by however long the late reviews take.
Slipping is common. In Ebsta and Pavilion’s 2025 benchmarks, 36% of deals slipped past their close date, down from 44% the year before.↗ A buying group runs to 5–16 people across up to 4 functions, so the sponsor is one voice among many.↗ Buying groups that reach consensus are 2.5 times more likely to report a high-quality deal.↗ That consensus has to form before the decision, while each seat can still shape it.
Timing matters as much as headcount. Across 655,000 opportunities, win rates rose 55% when decision makers were actively involved in the first 2 stages of the sales process.↗ Discovery is where the late seats belong.
We read the 2 AI answers to this question and the 3 pages our weekly AI-answer tracker found cited for it.↗ The answers offer scripts, workshops and checklists; the pages come from one ETRM vendor and are written for the buying firm. None defines what counts as an engaged seat. None gives a rule the CRM checks before a deal changes stage, and none cites a figure on early involvement.↗ Google’s AI Overview even tells the seller to ask for the introductions at the verbal yes, the moment the slip starts.↗
Slipped closes are a stage-definition problem, not a rep problem
We think a close that slips after a verbal yes is usually the stage definition at work. The stage rewarded the sponsor’s yes, so reps chased the sponsor’s yes. Coach them harder and next quarter’s forecast is still built from the same definitions.
Only 45% of sales leaders and sellers report high confidence in their forecast accuracy.↗ When so few trust the number, we think the cause sits in the system that produces it rather than in a few weak reps. Change what a stage requires and you change what the forecast is built from.
Multi-threading works the same way. We think it happens reliably only when the plan names who talks to whom and by when. Left to the sponsor, it depends on how comfortable the sponsor feels opening doors. The reward is large: multi-threading lifts win rates by 130% on average in deals over $50k.↗
We don’t say coaching never helps, or that every contact in the buying group must be engaged. Only the seats the signature waits on have to be in before discovery ends. A cleaner stage won’t make a forecast accurate on its own either. It gives the forecast a definition that holds.
Find the late seats in your own slipped deals
The seats to move forward are already in your history: the ones that first met you after a verbal yes on deals that slipped. A slip review finds them in the deals of the last 24 months.↗
- 01Step 1
Pull every deal that got a yes
Each deal of the last 24 months that reached a verbal yes, whether won, lost or still open, with its close date on the day of the yes.
- 02Step 2
Mark the slips
A close that moved a quarter or more after the yes is a slip. Note how many days it moved.
- 03Step 3
Name the first seat after the yes
From the deal’s contact roles and meeting history: the first seat to meet you after the yes, and what it asked for.
- 04Step 4
Make the late seats required
A seat that arrived after the yes in half or more of the slips becomes required at discovery exit. Its median days of slip is your baseline.
The threshold in step 4 is a starting rule: a seat that arrived after the yes in half or more of the slips becomes required at discovery exit.↗ A required seat is any seat the signature waits for, with or without a veto. Risk may hold no formal veto and still keep a close open for weeks while it tests valuations on its own book.
Record the median days of slip for each late seat. That is what its lateness costs, and it is your baseline. Run the review again each quarter and compare 3 numbers with the first one.↗
- The share of deals that leave discovery with every required seat engaged
- The median days from verbal yes to signature
- Close-date moves, by the seat named in the reason
Leave discovery only when every required seat is engaged
A deal should leave discovery only when every required seat is named and engaged, and its test is written down. Engaged means a two-way exchange with the seat’s holder in the last 90 days: a call, a meeting or a written reply to a question you asked.↗ Opened emails, webinar visits and the sponsor’s account of a meeting don’t count.
The written test turns each seat’s yes into something you can check. Ask each seat, in its own words, what has to be true before it can agree. For risk that may be a report on its own positions; for operations, its exceptions run end to end; for IT, the interfaces and hosting it will sign off. Those tests then decide what the demo or proof of concept has to prove. Any review with its own queue, such as a security questionnaire, vendor risk or supplier onboarding, gets a start date before discovery ends.
- Every required seat has a named person in it
- Each of those people has had a two-way exchange with you in the last 90 days
- Each seat’s test is written down in its own words
- Each seat has an owner on your team and an engage-by date
- Every review with its own queue (security, vendor risk, supplier onboarding) has a start date
- The sponsor’s yes, if given, is a dated field and moves no stage
Then change what the verbal yes does. Record the sponsor’s yes as a dated field on the deal. The stage your forecast counts as commit needs each required seat to confirm, in a two-way exchange, that its test was met. A review still running needs an end date, confirmed by its owner, before the close date.↗
Put it in the CRM, or it won’t hold. Give each required seat a field with its status (named, engaged, test agreed, test met), its owner and its engage-by date. Check those fields at the stage change, and make every close-date move carry a reason that names the seat. Block only where a field proves something, because hard blocks on every stage teach reps to type whatever passes. Go live at the start of a quarter so the forecast comparison stays clean.
Our general starting rule for seat coverage leaves discovery with the champion engaged and the budget owner named.↗ Your slip review tells you which seats to move forward from there.
Give each seat an owner and an engage-by date
Each required seat needs one person on your team who owns it, a first meeting with a purpose and a date by which it is engaged. Match by peer. Your solution architect takes IT and security, and a product specialist takes risk. Your implementation lead takes operations. The account executive keeps the sponsor, finance and procurement.
Set each engage-by date from the buyer’s calendar, before the evaluation is designed. Once the demo scripts or the proof of concept are fixed, a seat that joins later can only test what someone else chose to prove.
Team selling shows up in win rates. Across 10,332 deals, Gong Labs found a 15% win rate with no team selling and 50% with 3 or more seller personas involved.↗ Gong sells revenue software and the data shows a correlation, so read it as a pattern in won deals rather than proof that headcount wins.
Win rates rose from 15% with no team selling to 50% with 3 or more seller personas.
Data behind this chart
| Item | Value |
|---|---|
| No team selling | 15% |
| 3 or more seller personas | 50% |
The sponsor’s job is to open doors early. In the first or second meeting, ask: “Which review would start only after you said yes?” The answer names the seat, its queue and often its owner. If the sponsor won’t open that door, the deal stays in discovery with one task: the next seat’s introduction, with a date.
What does the rule change in an ETRM deal?
In an ETRM deal (software for energy trading and risk management), the rule moves risk, middle office and IT into discovery. It also takes deals out of commit that only the head of trading has agreed. By our estimate, an ETRM buying group at a mid-size trading firm has 6–12 people, and a mid-market sale takes 3–18 months, about 9.↗ On our map of that group, risk and middle office hold no veto, unlike the head of trading, IT, security, finance and procurement.↗ Both still run tests the signature waits on.
Take a fictional cloud ETRM vendor selling at about €200k a year (Illustrative).↗ Its slip review finds 12 deals with a verbal yes from the head of trading in 24 months.↗ Of those, 8 slipped a quarter or more, by a median of 5 months.↗ IT and security first met the vendor after the yes in 6 of the 8, risk in 5 and middle office in 4.↗ All 3 become required at discovery exit.↗
The seats and what each one tests come from our ETRM page; the owners and dates are the example’s.↗
| Seat | Its test, written at discovery | Owner on your side | Engage by |
|---|---|---|---|
| Head of trading (sponsor) | A daily P&L and position view without spreadsheets | Account executive | First meeting |
| Risk and market compliance | Its own positions, exposure and limits in one view, with trade reporting complete | Risk product specialist | Before the demo scripts are set |
| Middle office and trading operations | Its own confirmation and settlement exceptions, run in the scripted demo | Solution consultant | Before the demo scripts are set |
| IT, architecture and security | Interfaces to its exchanges and market data, the hosting model and a clean security questionnaire | Solution architect | Before discovery exits, with the questionnaire started |
| Finance and procurement | Total cost over the term with implementation counted, and a selection it can defend | Account executive | Before the proposal |
Its commit list holds 5 deals, €1M in all.↗ Under the new rule 2 qualify.↗ Of the other 3, 1 has no engaged risk seat and 2 have security questionnaires that haven’t started, against a review of 1–3 months by our estimate.↗↗ Commit falls to €400k.↗ The other €600k goes back to evaluation, each deal with one task and a close date that leaves room for its slowest review.↗
The same test applies if you hire an agency for account-based marketing to trading firms. Ask for a plan that names the head of trading, risk, middle office and IT at each target firm, with an owner and a date for each seat. Then ask for a weekly count of engaged seats per account.
In practice
How we do it at Panelhop
In a Panel Check (GTM audit · 2–3 weeks) we read the last 24 months of your deals, won and lost, with your forecast snapshots where they exist.↗ We score whether your stages have exit criteria the CRM enforces, how many contacts are engaged on each open deal, how often close dates move and how far the forecast misses. The same exports can show which seats first met you after a verbal yes.
A Leak Fix (we build the fixes) then puts the seat fields, the discovery exit and a required reason for every close-date move into your HubSpot or Salesforce. Panel Ops (we run it monthly) reports seat coverage and forecast accuracy against the baseline the Panel Check set. For trading-software vendors we start from the seats on our ETRM page.
Questions buyers ask about this
Is there an agency that does account-based marketing for ETRM software, reaching the head of trading, risk, middle office and IT at the same firm?
Yes. Panelhop builds and runs account-based GTM for vendors selling deals of €25k or more, and ETRM and CTRM software for energy traders is one of the vendor types we map in depth: the head of trading, risk, middle office, IT and security at each target firm, as seats. Whoever you hire, ask to see engaged seats per account each week, with an owner and a date for every empty seat.
What counts as an engaged seat?
A two-way exchange with the person in that seat in the last 90 days: a call, a meeting or a written reply to a question you asked. Opened emails, webinar visits and the sponsor’s account of a meeting don’t count, and 10 people from IT still fill 1 seat.
What if the sponsor won’t introduce risk, operations or IT?
Keep the deal in discovery with one task: the next seat’s introduction, with a date. Ask which review would start only after they said yes. A sponsor who won’t open that door leaves you with one engaged seat, and the forecast should say so.
Won’t stricter discovery exits shrink our forecast?
At first, yes: deals that advanced on the sponsor’s yes alone move back a stage, so commit drops. We think most of that value would have slipped anyway. Compare forecast snapshots with what closed after a full quarter to see whether the smaller number holds.
Do deals under €50k need the same discovery exit?
They need the same rule with fewer seats. Our starting point, Illustrative until your own won and lost deals replace it, is 3 required seats under €50k (the champion, the budget owner and IT or security), 4 at €50–150k and 5 above €150k.
