The Last Meeting Is Where Adoption Dies
The deal that taught me this stalled for five months after a flawless demo. What killed it happened in a meeting I was never going to be invited to.
Most enterprise technology purchases get decided in an internal meeting the vendor never sees. Someone who liked your product has to re-explain it to people who care about risk, not features, and that retelling is where deals and adoption actually die. So the most useful work happens before that meeting: put the risks in the buyer’s own units, give your champion a one-page script in their own words, and say the ugly costs out loud before somebody else discovers them.
The deal was with a mid-sized manufacturer. Plant-floor analytics. A genuinely good fit, and I’d still say that now.
The demo went about as well as demos go. Their operations head asked hard questions and got real answers. Two of their engineers spent twenty minutes trying to break the thing live and couldn’t. Handshakes all round. I drove back that evening thinking it was done.
It stalled for five months.
Nothing in the demo was wrong. What went wrong happened in a room I wasn’t in: the operations head sat across from his CFO and managing director and had to explain the whole thing again, alone, in a language he only half spoke, fielding questions nobody had prepared him for. Months later I found out what he actually said in there.1
“It’s basically like the dashboard we already have, but newer.”
The decision meeting is a game of telephone with a budget attached
Here’s the thing I underestimated for years as an engineer, and that a lot of salespeople never really admit: the person who understands your product is almost never the person who signs for it. Between those two people there is at least one retelling. Sometimes two or three. Whatever can’t survive being retold — the caveats, the nuance, the honest shape of the risk — gets dropped, and the person doing the retelling improvises something to fill the gap. They have to. They’re standing in front of their boss.
And the audience in that final room isn’t scoring features. In my experience they are pricing exactly one question, in some phrasing or other: what breaks, and who owns it when it does? A CFO does not hear “99.9% uptime” as a strong number. She hears that there is downtime, and that nobody has told her what it costs.2
Translation is not simplification
The standard fix is “simplify it for the executives.” I hate this advice, and executives can smell it anyway. When you strip the detail out of a technical case you don’t make it clearer. You make it unverifiable, and unverifiable claims get priced as risk, which is the opposite of what you were trying to do.
What actually works is restating, not reducing. Same claim, different units. Latency becomes how long the queue gets at a counter. An integration estimate becomes this many people for this many weeks, with names attached. A migration risk becomes one specific bad Tuesday: which shift notices first, what they do about it, who they call. Nothing has been dumbed down. You’ve just changed the currency.
What actually works
One page, in their words, covering the three questions they will actually face: what does it cost all-in, what breaks, who owns it when it does. If they have to improvise those answers alone, you’ve already lost — you just won’t find out for a quarter.
Every deal has one honest, unattractive cost. Put a number on it and say it before anyone asks. Coming from you it reads as diligence. Discovered by them, it reads as a cover-up, and it quietly poisons everything you said before it.
Somewhere in that company is somebody whose actual daily work your product alters. They’re never in the demo and never in the final meeting, but their one-line verdict travels up the building faster than your deck does. Go meet them early.
A demo that dazzles with things nobody asked about plants questions your champion can’t answer later, alone. Show what maps to their stated problem and then stop.
You can’t attend the last meeting. That’s just the rule of the game, and no amount of relationship-building changes it. What you control is how well the truth travels without you. It can arrive in that room dressed for the audience, or it can show up in a t-shirt full of jargon and get sent home.
I’ve come to think that this preparation is the most understaffed job in enterprise technology, on both sides of the table. It’s also, more or less, the job I’ve given myself.