Nine months. Seven people. One shot. This is not the sales process you read about.
Almost everything published about B2B selling assumes a short cycle, one decision-maker and a big enough market to make mistakes in. If you sell equipment, systems or technical services, none of those hold. Here’s how complex, low-volume, high-value deals are actually won — and the specific ways they’re lost.
Why standard sales advice actively hurts you
The playbooks aren’t wrong — they’re written for a different game. Applied to a long technical sale, most of them do damage. Volume tactics burn a finite market. Urgency tactics read as desperation to an engineer. “Always be closing” gets you removed from the tender list.
Who actually decides — and it isn’t who signs
The single most expensive mistake in technical B2B is mapping the deal by job title. Formal authority and real influence come apart badly in engineering-led purchases. The person who can kill your deal outright usually has no budget authority at all.
Formal authority vs actual influence
Genuine alignment. Your primary relationship.
The one who has to live with it. Can kill it in a sentence.
Shapes terms and timing, rarely picks the winner.
Almost never chooses. Frequently delays.
If it disrupts the shift, it doesn’t happen.
Absolute veto, usually exercised at week 30.
The silent period
Every long-cycle deal goes quiet, usually for six to twelve weeks somewhere in the middle. This is normal, it is not a signal, and it is where most inexperienced BDMs destroy deals they had already won.
What it feels like
Your champion stops replying. Calls go to voicemail. The proposal you sent six weeks ago has vanished into an internal process you cannot see. Every instinct tells you the deal is dead or that you have done something wrong.
So you start chasing. Then you follow up on the follow-up. Then you send the “just circling back” email, then the one that mentions a discount, then the one that hints the price may go up.
By the time they resurface — and they usually do — you have repositioned yourself from technical partner to anxious vendor. That costs you leverage in a negotiation you haven’t even started.
What’s actually happening
Nothing about you. Capital approval is queued behind two other projects. The plant had an unplanned shutdown. The engineer who championed it is on leave. The budget cycle moved. A parent company put a freeze on capex for a quarter.
The correct response is a cadence, not a chase. Agree the next contact point before the silence starts — “I’ll check in on the 14th, and if there’s nothing to report, just tell me that.” A scheduled non-update is a normal business interaction. An unscheduled chase is a request for reassurance.
Between contact points, send things with independent value: a relevant case, a spec clarification they’ll need later, a heads-up on a lead time change. You stay present without ever asking “any update?”
Score a real deal, right now
Pick your biggest open opportunity and answer honestly. Each item is something that separates deals that close from deals that quietly disappear. Tick only what is actually true — not what you intend to do this week.
Long-cycle deal health check
Ten checks. Nothing is stored or sent anywhere.
Qualifying out is the highest-value thing you do
In a nine-month cycle, a bad deal doesn’t cost you a bad deal — it costs you nine months you could have spent on a real one. With a handful of serious opportunities a year, that arithmetic is brutal. These are the signals worth acting on early.
They won’t introduce you to anyone
Your contact is friendly, engaged, takes every meeting — and has quietly declined three requests to meet the engineer or walk the floor. That isn’t a scheduling problem.
Do this: ask directly what’s making the introduction difficult. The answer tells you whether you have a deal or a pen pal.
The driver is yours, not theirs
You can explain the ROI beautifully. They can’t explain it at all. If nobody internally can articulate why this matters, nobody will fight for it when the capex list gets cut.
Do this: ask your champion to explain the business case back to you. If they can’t, you don’t have one.
You’re the third quote
Called late, spec already written, incumbent already chosen. You are there to make the process look competitive. It happens constantly and almost nobody says it out loud.
Do this: ask who wrote the specification. If it wasn’t them and it isn’t you, you’re validating someone else’s price.
Every date has slipped twice
Not the close date — every date. The site visit, the technical review, the internal meeting. Chronic slippage reflects an organisation that cannot execute a decision.
Do this: park it. Set a reminder for a quarter out. Don’t carry it in the forecast.
Price comes up first, and constantly
In technical B2B, early and repeated price focus usually means they haven’t understood the technical difference — or they have, and they’ve decided it doesn’t matter.
Do this: one attempt to reframe around risk and total cost. If it doesn’t land, you’re in a commodity sale — price it that way or leave.
Nobody will own a next step
Every meeting ends with “we’ll be in touch.” Six weeks pass. Another meeting, same ending. A deal that can’t produce a committed next action isn’t progressing — it’s being politely stalled.
Do this: propose a specific next step with a date. Watch what happens to it. That’s your answer.
Get the B2B Sales Stack Cheat Sheet
The tooling behind the scorecard above — one page, no fluff. Sent straight to your inbox.
None of this survives a broken pipeline
Stakeholder maps, cadences and qualification only work if they’re recorded somewhere that outlives the conversation. In most businesses that’s exactly what’s missing — and it’s why good deals still disappear.
This page links to tools we use and may earn a commission from. The frameworks above are tool-agnostic — the stakeholder map and the scorecard work on paper.