Category: Enterprise Sales Motion

“Send me a proposal.” Those four words kill more deals than any competitor ever will. They sound like progress — the customer is asking for something specific, something formal, something that looks like a buying step. Often they’re the opposite: they’re the polite exit ramp.

Knowing the difference is a craft.

What “Send Me a Proposal” Often Means

Before you race back to the office to draft a document, consider what the phrase often actually signals:

“I need to look busy.”
The customer is evaluating three vendors to satisfy an internal process. You’re one of them. A proposal from you becomes file material, not a decision input. The customer has already decided — probably for internal build, or for the vendor they worked with before.

“I want to end this meeting politely.”
The conversation wasn’t going anywhere useful. Asking for a proposal is a soft way to give you something to do without committing to next steps.

“I need to justify this upward.”
The customer likes what you’re offering but can’t justify it without documentation. The proposal is real, but the request came before the conversation fully surfaced the objections you’d need to handle in the document.

“I want to compare pricing.”
The customer is using your proposal to pressure an incumbent vendor or to benchmark another option. You’re the stalking horse.

All four of these are more common than “I want to evaluate your offering seriously and move to close.” Treating every proposal request as the last one is how sellers end up writing twelve proposals to get one close.

The Qualifying Move

Before accepting the request at face value, run a qualifying sequence:

1. “What specifically would you want to see in the proposal?”
If the customer says “standard stuff — pricing, timeline, scope,” you’re in a commoditized bake-off. If they say “specifically how you’d address X and how the implementation would go for Y team,” you have a real proposal request.

2. “Who else will be reviewing this document?”
If the customer names specific stakeholders (“my CFO, our ops lead, and procurement”), the proposal is real. If they say “just me” or “I’ll pass it around,” the proposal is probably not going to a real committee.

3. “What’s the decision timeline after you review it?”
A real proposal has a decision attached. “We’ll make a decision by [specific date]” is a good sign. “We’ll take some time to think about it” is a warning. “I’m not sure” often means the request was tactical rather than strategic.

The Counter-Move

When the qualifying sequence suggests the proposal request is a soft deflection, the right move is often not to write the proposal. Instead:

“Happy to put something together. Before I do, it would help me make the proposal more useful if we could do a 20-minute working session with [specific stakeholder] to walk through how it would actually fit their situation. Without that, the proposal ends up generic — and I don’t think a generic proposal serves either of us. Can we schedule that for next week?”

This move does three things: it qualifies the seriousness of the request, it engineers another stakeholder conversation, and it repositions you from “vendor sending paper” to “thoughtful partner who’s trying to help.” Customers who are serious will find the time. Customers who weren’t serious will reveal themselves.

When to Send the Proposal Anyway

Sometimes the proposal is the right move even when the signals are mixed:

• Strategic account where being in the consideration set is worth the cost
• Customer with a history of slow but real buying cycles
• Situation where your proposal itself can reframe the conversation

In those cases, write the proposal — but write it as a strategic document, not a commodity quote. Include discovery findings, the problem framing, a recommendation, a proposed structure, a pricing approach. Make it something the customer couldn’t get from a competitor, because it reflects specifically what was surfaced in your conversation.

The Cost of Getting This Wrong

Every generic proposal written for a soft-signal request is lost time. A typical enterprise proposal is 10 to 20 hours of work — legal, pricing, SE, rep time. If 70% of proposals go to deals that were never real, the cost compounds fast.

The seller who writes 30 proposals per year and closes six of them has the same result as the seller who writes 10 proposals per year and closes six — except the first seller spent 400 hours on paper that went nowhere.

---

The proposal is a tool, not an automatic response. Use it when it’s going to move a real deal forward. Qualify before writing. Sometimes the best response to “send me a proposal” is a working session that produces a real deal, instead of paper that produces silence.

“Send me a proposal” is the phrase sellers want to hear and should investigate before trusting. Most of the time, what sounds like the last step is actually the last-but-polite exit.

Most deals die in silence. Not in rejection — in silence. The customer stops responding, the rep stops reaching out, and the deal slides quietly off the forecast. This is the most common deal-death pattern in enterprise sales, and it’s also the most preventable.

The prevention is the follow-up. But most follow-ups are wrong.

The Typical Follow-Up

The typical follow-up sequence looks like this:

• Week 1: “Just following up on our conversation.”
• Week 2: “Circling back to see if you’ve had a chance to review.”
• Week 3: “Did you get a chance to look at the proposal?”
• Week 4: “Bumping this to the top of your inbox.”

None of these are follow-ups. They’re nudges. They add zero value, ask for an answer, and signal to the customer that you have nothing else to offer.

The customer interprets the pattern accurately: “This seller wants something from me and has nothing useful to give me. Each of their emails is a request for attention. I’ll respond when I have a reason — but the pattern of asking makes me respond less, not more.”

What a Real Follow-Up Does

A real follow-up delivers value, then asks. Sometimes it doesn’t ask at all.

Week 1 real follow-up:
“One thing that came up in our conversation that I wanted to think about more — you mentioned [specific challenge]. I looked at a couple of analogous situations from our work and wanted to share what we’ve seen. [Specific observation or insight]. Happy to discuss further if useful — no rush.”

Week 2 real follow-up:
“Saw the announcement from [their competitor or industry development]. That probably has implications for [specific thing they discussed]. Wanted to flag it. [Brief observation].”

Week 3 real follow-up:
“[Useful article or resource that’s relevant to their work]. Not directly related to our conversation but thought it might be interesting given what you’re focused on.”

Week 4 real follow-up:
“It’s been a few weeks since we connected. I know things shift — happy to re-start the conversation whenever it makes sense. No pressure. Here’s something I’ve been thinking about that touches on what we discussed: [short insight].”

Every touch delivers something. Every touch signals “I’m useful to stay connected with, not a distraction.” The customer responds because responding is valuable to them, not because they’re pressured.

Three Rules

1. Every follow-up should be able to stand on its own.
If the customer read only this one email and nothing else, would it be worth their time? If no, don’t send it. The “hey just checking in” email fails this test universally.

2. The cadence should be geometric, not arithmetic.
Not “every week for eight weeks.” Try: 3 days, 7 days, 14 days, 30 days, 60 days. The intervals lengthen. The customer doesn’t feel hunted. The touches are rare enough that each one is noticed.

3. After the fourth value-add follow-up, consider the long-game sequence.
If the customer hasn’t responded after four substantive touches, the situation has changed — or never was what you thought. Drop the frequency. Move to quarterly check-ins that maintain presence without feeling like pursuit. Many deals I’ve seen close on the eighth or ninth touch, but rarely on the fourth or fifth.

The Psychology

Customers stop responding for specific reasons: competing priorities, internal politics, a champion who’s lost steam, a budget that moved, a stakeholder who blocked. None of these reasons are visible to you. All of them are navigable.

The follow-up that breaks through the silence is rarely the pressure follow-up. It’s the follow-up that makes the customer remember that you’re the thoughtful seller they liked, and that reopens a door they’d let drift closed.

The Diagnostic

Pull the last ten follow-up emails you sent to deals that went cold. Ask yourself: if the customer read only this email, would they have responded? Or does the email require them to have remembered the earlier context, felt social pressure, and given you a charity reply?

If your follow-ups require all three to convert, that’s why your follow-ups don’t convert.

---

The art of the follow-up is the art of staying present without being pushy. Of continuing to add value when nobody has asked for it. Of being the person the customer thinks of when they’re ready — not the person they’re avoiding in their inbox.

Most follow-ups are the latter. The ones that convert are the former.

That’s the craft.

Everyone talks about qualifying out early in the cycle. Few talk about walking away from a deal that’s actively winnable — one where the customer is engaged, the economics look plausible, and the close is in sight. But sometimes that’s the right call, and the operators who make it consistently are the ones who build durable businesses.

Here’s when to walk.

The Poison Customer

Some deals close, and the customer proceeds to consume disproportionate support resources, complain about everything, demand scope they didn’t pay for, and ultimately become a reference against you rather than for you. These customers are net-negative on the P&L even though they paid.

The tells are visible during the sales cycle if you know what to look for:

• They negotiate every term aggressively, even minor ones, as if your every move is a threat
• They ask for significant scope concessions and then ask for more after you’ve conceded
• Their references treat their previous vendors poorly (the way they treated the last vendor is how they’ll treat you)
• They can’t articulate internal accountability — everything is someone else’s fault
• They demand unusual contract terms that would create precedent you don’t want to set

One or two of these is noise. Four or more is a pattern. The customer who shows three of these signals during the sales cycle will absorb 3 to 5x the support cost of a normal customer and still be dissatisfied.

Walking away from these deals is a P&L decision, not an ego decision. You’re not losing revenue — you’re preventing negative revenue.

The Unhealthy Economics

Sometimes the deal closes but at terms that are permanently bad for you. The discount is 40%. The payment terms are 90 days net. The SLA guarantees penalties that exceed margin. The implementation is committed to be done in a timeline that will require overtime and rework.

When a deal structure requires your delivery team to operate at a loss, or creates contractual risk that dwarfs the contract value, the deal is not a win. It’s a paid learning experience — and usually the learning is that the customer will never be profitable.

The senior operators I’ve watched walk away from these deals do it calmly and without apology: “We can’t do this at these terms. If the terms change, let’s reconnect. If they don’t, we wish you well with your other option.”

Sometimes the customer comes back. Often they don’t. Either outcome is better than taking the deal at bad economics.

The Strategic Misalignment

Occasionally a deal is winnable but doesn’t fit your strategy. The customer wants something your roadmap is moving away from. They want custom work you’ve decided not to offer. They’re in a market segment you’ve deprioritized.

Taking the deal means distorting your execution to serve a customer you’d rather not have. The product team builds features they don’t want to build. The services team runs engagements that don’t scale. The marketing team writes case studies for segments they’re trying to exit.

These deals usually close because the rep doesn’t have visibility into the strategic implications. They see revenue. The broader cost is paid by teams outside sales, which is why it rarely enters the deal review.

The Honest Diagnostic

Before closing a deal, run three questions:

1. Will this customer be a reference worth having?
Not just “will they sign a reference agreement.” Will their account be one you want competitors to look at? Will their public statements about you improve your market position?

2. Will the economics look the same a year from now?
Discounts given at close don’t disappear at renewal. SLA commitments don’t soften. Scope promises accumulate. What looks acceptable on closing day often becomes unacceptable as costs compound.

3. Does this deal pull my company in a direction I want to go?
Or does it reinforce what we’re trying to move away from? Every closed deal is a vote for the future version of your company. Vote with intention.

---

Walking away from a winnable deal is expensive in the short term and valuable in the long term. The companies that build durable businesses have a concept of customer fit that is ruthless — they’re willing to lose revenue to avoid the wrong customer.

Most companies don’t have this discipline. They take every deal that closes. Then they spend disproportionate resources on the customers that should have been turned away, and they wonder why their margins are compressed and their team is burned out.

The ability to say no to a sale is the difference between a business that scales and a business that grinds.

Most sales forecasts are fiction, and everyone senior enough to have seen three or four forecast cycles knows it. The question isn’t whether the forecast is accurate — it’s which kind of inaccurate, and what to do about it.

Forecasts fail in predictable ways. Understanding the failure modes is the first step to building a forecasting process that is actually useful — as a planning tool, as a diagnostic, and as a conversation between sales leadership and the rest of the organization.

The Four Ways Forecasts Lie

1. The optimistic lie.
Reps have incentive to include aspirational deals in the forecast because pipeline coverage ratios are watched. Sales managers have incentive to protect their reps and not challenge optimistic calls too hard — too much skepticism looks like lack of confidence in the team. The forecast ends up systematically 15 to 30% over reality.

2. The sandbag lie.
Occasionally the opposite happens. Reps who fear missing their number strip the forecast to near-certainties. The forecast looks conservative. Sales leadership ties the forecast to a smaller commit. Then deals actually close, the forecast looks great, and the seller has earned room to sandbag again next quarter.

3. The stage-mislabel lie.
The rep has the deal in “verbal” or “commit” stage because they had a positive call, even though nothing specific has been committed. The stage labels feel rigorous but the gating criteria behind them are soft. Stage mislabeling is the most common forecast failure and the hardest to detect in aggregate.

4. The close-date lie.
The deal has a specific close date because the forecast requires one. The close date is based on nothing except the quarter-end the rep needs to book. Deals with unrealistic close dates slip, and the forecast for the following quarter gets fatter in a predictable pattern.

Why the Lies Persist

None of this is intentional deceit by individual reps or managers. It’s the emergent behavior of a system that rewards pipeline optimism and punishes pipeline pessimism. The lies are structural. Changing them requires changing the incentives, not the people.

I’ve watched sales organizations run quarterly forecast accuracy analyses, identify patterns, launch training, and fail to change the underlying metrics by more than a point or two. The reason is always the same: the incentive structure still rewards the lies. As long as reps and managers are evaluated on coverage ratios and forecast commit, they’ll optimize the number to protect themselves.

What to Do About It

Three structural moves that actually move forecast accuracy:

1. Replace stage gates with commitment gates.
Instead of “Discovery / Evaluation / Commit / Close” stages — which are largely self-reported by reps — define each stage by specific buyer actions. “Customer has agreed to a technical review call with their CIO” is a commitment gate. “The rep thinks the customer is evaluating” is not. Commitment gates are harder to fake and easier to verify.

2. Track forecast-to-close variance by rep over time.
Every rep has a personal forecast style — optimistic, conservative, accurate. Over four quarters, the pattern becomes visible. Adjust each rep’s forecast by their historical variance. This is basic math that few organizations actually do, but it immediately improves aggregate accuracy.

3. Run the forecast conversation with blind calibration.
The VP of Sales independently estimates each deal’s probability without looking at the rep’s call. The manager does the same. The three numbers are compared. Systematic divergence between rep and manager calls is the diagnostic — it identifies where the lie is happening and who’s participating in it.

The Cultural Move

The deeper fix is cultural: forecast accuracy has to be valued more than forecast size. In most organizations, hitting your forecast is celebrated; missing it is punished. Few organizations celebrate accurate forecasts that were smaller than hoped — even though that accuracy is more useful to the business than an inflated commit that missed.

Sales leaders who want better forecasts have to start rewarding accuracy over optimism. That’s a cultural shift that takes 18 to 24 months to implement, and most leaders don’t stay in role long enough to complete it.

---

The forecast isn’t broken because reps are dishonest. It’s broken because the system produces the outcome it’s designed to produce.

If you want a different outcome, change the system. Commitment gates, variance adjustment, blind calibration, accuracy-weighted incentives. None of these are exotic. All of them work. Few organizations implement all four.

The ones that do forecast at quality levels their competitors can’t touch.

The pilot sounds like progress. You’ve got signed paper. Users are in the system. The customer is engaged. Then the pilot ends, and the expansion to full deployment just… doesn’t happen.

If you’ve sold enterprise anything, you’ve lived this. It’s not failure — it’s a specific, recognizable failure mode, and the reasons are almost always predictable in advance.

Here’s the pattern I’ve watched across medtech, telecom, and consulting: the pilot that looked like a win was actually a slow-motion loss, because the conditions for conversion were never built into the pilot design.

Why Pilots Don’t Convert

1. The success criteria were never agreed.
The pilot started with everyone excited. Nobody wrote down what “successful” meant in specific, measurable terms. At the end of the pilot, the champion says “it went well.” The economic buyer says “I’m not seeing the ROI.” Both are right, because “success” was never defined.

2. The pilot was run with different people than the full deployment would be.
In medtech, the pilot runs in a single department with clinical early adopters. The full rollout would hit the whole hospital, including physicians who didn’t volunteer. The pilot users love it. The broader population was never consulted. Conversion requires convincing a new group from scratch.

3. The economic model wasn’t agreed up front.
“Let’s pilot it and see” usually means “let’s defer the hard budget conversation.” The hard conversation now has to happen after the pilot, at a time when organizational energy has already shifted to whatever’s next.

4. The pilot outlasted the champion’s attention.
You started with executive sponsorship. The pilot ran 90 days. Somewhere in week six, your sponsor got pulled into a reorg, a new initiative, or a different priority. By end of pilot, nobody on the customer side is actively driving conversion.

5. The pilot became the solution.
The customer got enough value from the limited scope that they didn’t feel urgency to expand. This is the most insidious one — the pilot was useful, just not useful enough to fund expansion. You accidentally built a free version that the customer never pays to upgrade.

How to Design a Pilot That Actually Converts

1. Write the conversion terms into the pilot agreement.
Before the pilot starts, write down: if X outcomes are achieved, the customer agrees to expand to Y scope at Z price within W timeframe. This is not pushy — it’s just explicit. Customers who refuse to write this down are customers who are not actually planning to convert.

2. Define success with the economic buyer, not just the champion.
The clinical champion’s definition of success is different from the CFO’s definition of success. Get both in the room. Get both agreements in writing. In medtech, the clinical “does this work” answer has to match the financial “is this worth the cost” answer — and those are rarely the same conversation.

3. Design the pilot to test the full deployment, not just the happy path.
If the full deployment would involve users who aren’t clinical early adopters, the pilot should include some of them. If the full deployment would cross two departments, the pilot should cross at least two. A pilot that only validates the easy part tells you nothing about the hard part.

4. Name the conversion owner on the customer side.
At pilot start, the customer identifies the person responsible for driving conversion if the pilot succeeds. Not the champion — the conversion owner. Often this is the procurement or operations lead. Naming them forces the buying committee conversation earlier.

5. Define the decision date.
The pilot ends on a specific date. By that date, a specific decision must be made: expand, extend, or end. “Let’s keep going and see” is the failure state. Kill criteria or conversion — no middle path.

---

The pilots that convert at the highest rates are the ones that look least like “try it and see” at the start. They look like clearly scoped experiments with written conversion terms, dual sign-off on success criteria, and a named date for the decision.

A pilot without those elements isn’t a pilot. It’s a paid demo that lets the customer feel productive while not actually committing.

If you’re running pilots that don’t convert, the problem is almost never the product. It’s the structure.

Design the structure for conversion before the pilot starts, or accept that you’re designing for learning — and price the learning accordingly.

Most deals that slip in the final stages don’t slip because of product or price. They slip because the seller and the customer never aligned on what “closing” actually requires.

The fix is a mutual close plan — a shared document, written between you and your primary buyer, that sequences every step required from both sides to get the deal signed, installed, and adopted.

Done well, it’s the single highest-leverage artifact in enterprise sales.

Done poorly (or skipped), it’s the reason your forecast looks clean at week six and then slides through the final three weeks.

What a Mutual Close Plan Actually Contains

1. The end-state definition.
Not “signed contract.” A specific outcome: “Solution deployed to X users by Y date, integrated with Z system, with defined success metrics agreed by Q stakeholder.” If you don’t know what the customer is actually trying to accomplish, the close plan is premature.

2. The decision path.
Who specifically needs to sign off, in what order, and with what approval authority. Not titles — names. If your champion can’t give you names, that’s a diagnostic result: the deal is less advanced than the pipeline stage implies.

3. The gating artifacts.
What documents, meetings, approvals, or reviews are required at each step. Security review. Architecture review. Procurement review. Legal redlines. Pricing approval. Each of these has its own timeline, and they are almost never sequential — many can run in parallel if surfaced early.

4. The dates.
Specific, with joint accountability. “Security review by March 15, owned by customer-side CIO.” If the customer won’t commit to dates, the deal isn’t closing on your forecast timeline. The close plan forces this conversation while you still have time to react.

5. The risks and mitigations.
What could delay each step. What the contingency is. In construction, I saw close plans that specifically named bonding review as a risk with a mitigation plan. In telecom, security approvals were always the named risk. Naming the risk up front is how you prevent being surprised by it at week ten.

The Structural Move: Make It Mutual

The unlock is that this document is not your document. It’s theirs too.

You draft it. You send it. You ask your primary buyer to review and amend. They own half the rows. The act of reviewing and owning commitments is itself a qualifying step — a customer who will not engage with a close plan is a customer who is not going to close. A customer who engages, amends, and adds rows is a customer whose deal is real.

I’ve watched sellers resist this because it felt too formal or too aggressive. The customers I’ve watched respond to well-built close plans don’t find them aggressive — they find them useful. Enterprise buyers have their own internal processes they’re trying to navigate. A seller who helps them organize the process is a partner, not a pusher.

The Diagnostic Value

Here’s what a mutual close plan reveals that nothing else does:

• Whether your champion actually has authority (if they can’t commit dates on behalf of their org, they don’t)
• Whether the buying committee actually knows about your deal (if dates slip because named stakeholders weren’t aware, you’re single-threaded)
• Whether the timeline your champion gave you matches reality (it rarely does, in the first draft)
• Whether the deal is real (real deals absorb the close plan; unreal deals reject the close plan)

Every one of those signals is worth more than the close plan itself. The plan’s real value is as a diagnostic instrument, not as a project management tool.

When to Introduce It

Mid-funnel, usually — after the solution is validated but before legal redlines start. Too early and it feels premature; too late and you’ve lost the opportunity to shape the process.

For most enterprise cycles, that’s around the 40 to 60% complete mark in your pipeline stages.

---

Write one this week for your highest-priority open deal. Send it to your primary buyer with a note: “I drafted this to keep us aligned on what’s needed from both sides — take a look and mark anything you’d change or add.”

Their response — the speed, the thoroughness, the willingness to engage — will tell you more about the deal than any other single signal available to you.

Most deals that slip in the last month did not look like they were going to slip until the last week. The close plan is how you see the slip coming at week three instead of week eleven.

That’s the game.

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.

Every single-threaded deal is one job change away from dead.

That’s not hyperbole. That’s attrition math. The average senior B2B buyer stays in a specific role for 2-4 years. If your enterprise deal cycle is 6-12 months, and your champion is late in their tenure, the probability they’re promoted, poached, or reorg’d out of their seat before the deal closes is non-trivial. Add another six months post-close for expansion and renewal — now the probability is high.

Single-threading is the most common pipeline hygiene failure I see across every industry I’ve sold into.

The Pattern

In telecom, I’ve watched a 9-month deal die in week 34 because the CIO got promoted and moved to a different business unit. His replacement had different priorities. The deal didn’t get killed — it just stopped getting prioritized, which is the same thing.

In construction, I’ve seen a deal slip two quarters because the project manager at the GC left for a competitor, and the incoming PM had a preferred vendor relationship. No drama, no objection — just quietly deprioritized into a no-decision.

In consulting, the pattern shows up at the partnership level. The senior exec who sponsored the engagement retires or moves. The new exec doesn’t owe you anything, and the engagement gets reviewed on its merits — at which point, if you haven’t multi-threaded, you’re defending to a stranger.

Medtech might be the worst of the four, because clinical sponsors frequently rotate departments. A 12-month implementation can easily outlast the tenure of the physician who championed it.

The Five Threads

On every deal above your forecast threshold — and I’d argue, every deal, period — you need three to five relationships at the customer, distributed across:

1. Peer-to-peer. Rep-to-operator conversations, daily/weekly contact. The relationship that makes the deal feel real day-to-day.

2. Executive sponsor. Your CEO/VP to their CEO/VP, relationship-level. The insurance policy for when something goes sideways and you need an adult conversation at altitude.

3. Operational. IT, procurement, legal, or whoever runs the backend. The relationship that keeps your deal from dying on a technicality.

4. Technical validator. The subject-matter expert who will sanity-check the solution. The relationship that gives the buying committee confidence.

5. Future expander. Someone adjacent to the buying center who could use your product next. The relationship that turns a single landing into an account strategy.

You don’t need all five on every deal. You do need at least three on every deal that matters.

The Test

The simplest test I know: pull every open deal in your pipeline. For each, list every person at the customer you’ve had a substantive conversation with in the last 60 days.

If the list has fewer than three names, you don’t have a deal. You have a relationship.

Single-threaded deals forecast aggressively and close softly. Multi-threaded deals forecast conservatively and close reliably. I have never in my career seen that pattern break.

Two Habits That Compound

Pre-deal multi-threading. In your first or second call, ask your champion “who else should I be talking to?” Ask it in a way that’s about serving the deal, not extracting contacts. Good champions will volunteer three names. Great champions will make the introductions.

Deal-review multi-thread test. In every deal review, name every stakeholder. If the same name comes up for every role — decision, technical, financial, operational — you’re single-threaded. The deal review is where this gets caught while there’s still time.

---

Most deals are not lost to competitors. They’re lost to reorgs, role changes, and silent re-prioritization. Multi-threading is the cheapest insurance in enterprise sales, and it pays every time.

The deals you don’t multi-thread don’t die in week one. They die in week thirty. By then you’ve built them into the forecast, told your board the number, and emotionally closed the deal in your own head. The miss is louder because of the build-up.

Thread the deal, or forecast the miss. Those are the options.