The deal is closing. Your champion is thrilled. The forecast looks clean. Legal has the redlines. Your VP of Sales has already mentally booked the number.
Then it doesn’t close.
Every time I’ve seen this pattern — and I’ve seen it across medtech, telecom, construction, and consulting — the culprit was the same. A stakeholder who was invisible during discovery became decisive at close.
I call them the silent second stakeholder.
They’re not the economic buyer. They’re not the champion. They’re the person with veto power your champion didn’t think to mention, because your champion genuinely didn’t think about them.
The Pattern, By Industry
In medtech, it’s hospital IT. Your clinical champion is ready to sign. Then IT asks how your device talks to their EMR over HL7, and suddenly the deal slides two quarters while integration questions get answered.
In telecom, it’s the facilities team at the customer site. The CIO signed. The rack isn’t ready. The install slips. The renewal conversation starts from behind.
In construction, it’s the bonding company, insurance carrier, or owner’s rep. The GC wants to move. The bonding company hasn’t reviewed the terms. The close date becomes aspirational.
In consulting, it’s procurement. Always. You thought you were selling to the COO. Procurement is now telling you your rate card is “non-standard” and asking for a 15% discount you weren’t planning to give.
The pattern is identical in every industry: there is a stakeholder whose job is to say no, and they weren’t in your discovery calls.
The Fix Is In Discovery, Not At Close
The fix is not more diligence at close. By close, it’s too late — you’re already in reactive mode, your champion is frustrated, and the discount clock has started. The fix is mapping them in discovery.
Three questions to ask your champion in the first 30 minutes of the first real call:
1. “When this goes to procurement, what’s the first thing they’ll flag?”
If your champion says “I don’t know,” that’s the answer — and that’s your homework. The question itself is also a gift to your champion; you’re teaching them how to defend the deal internally.
2. “Who else on the technical, legal, or financial side needs to bless this before it moves?”
Ask them to name names. Not titles. Names. If they can only give titles, they haven’t talked to those people yet — and that’s a leading indicator your deal has more fragility than the pipeline stage implies.
3. “When was the last deal like this one stopped, and who stopped it?”
This is the best question on the list. It surfaces institutional memory your champion might not volunteer. Every organization has a stopper — a person or a team that has killed deals like yours before. Finding out who, early, is worth three months of discovery.
Get Them In the Room Early
Beyond the questions, there’s a structural move: get the silent stakeholder in the room before you need them.
In medtech, that means a technical call with IT in week two, not week ten.
In telecom, a site walkthrough with facilities before contracts go to legal.
In construction, a procurement or bonding courtesy call early enough that you’re not being introduced at the moment of pricing friction.
In consulting, a procurement conversation that treats their standard questions as a checklist to clear, not an obstacle to work around.
The best sellers I’ve worked with treat silent stakeholders as primary characters in the deal, not obstacles at the end. They build multi-threaded relationships that include the technical reviewer, the procurement liaison, and the operational sponsor — not just the decision-maker and the champion.
Put silent-stakeholder mapping into your deal reviews. Ask it on every deal above your forecast threshold. The cost is 15 minutes of conversation. The savings are entire quarters of slipped revenue.
Most lost deals aren’t lost to competitors. They’re lost to invisible people nobody thought to invite.
The irony: silent stakeholders almost always will bless your deal if they’re engaged early. They only become deal-killers when they’re surprised. The surprise is the failure — not the stakeholder.