Category: Enterprise Sales Motion

“We’ve hit a snag in procurement” is one of the most common phrases a seller hears late in a deal cycle. By the time it’s said, the deal is usually already in trouble, and the trouble almost always has the same structural cause.

Most deals that die in procurement were dying earlier — sellers just didn’t recognize the signals, and procurement became the visible cause of a decision that had already been made upstream.

The Pattern

Procurement rarely kills deals on its own merits. What procurement does is surface the underlying weaknesses in the deal and force them into visibility at a time when the seller has the least leverage to address them.

If your champion hasn’t fully convinced the economic buyer, procurement will find the gap. If the ROI case hasn’t been made rigorously, procurement will push back on pricing. If the business urgency hasn’t been established, procurement will slow the timeline until the urgency evaporates.

In all of these scenarios, procurement is doing its job — protecting the company from bad vendor decisions. What looks like “procurement killing the deal” is really procurement revealing the deal was weaker than you thought.

The Signals You Missed

Several upstream signals predict procurement problems:

1. Your champion couldn’t articulate the cost of not buying.
If the champion can’t clearly explain what breaks if the company doesn’t make the purchase, procurement’s questions about ROI will expose the gap. The champion may be enthusiastic but unable to defend the investment when challenged. Procurement will find this out in month three and push back accordingly.

2. The economic buyer never engaged directly.
If you’ve been selling primarily to your champion, and the economic buyer has only been copied on emails, procurement often becomes the mechanism by which the economic buyer’s unspoken reservations surface. The economic buyer wasn’t going to say no directly, but they don’t need to — procurement will do it for them.

3. The timeline was optimistic.
If your deal timeline didn’t include adequate time for procurement, legal, and finance review, those functions will slow the deal to match their actual process. What looks like “procurement dragging their feet” is often procurement operating at their normal pace while your seller-driven timeline was unrealistic.

4. The pricing wasn’t defensible to an outsider.
If your pricing relied on your champion accepting it on faith, procurement will force a defense of the pricing with specifics. If the specifics don’t hold up, procurement will extract discounts — not because they’re aggressive, but because the pricing wasn’t grounded in defensible logic.

How to Prevent the Procurement Death Spiral

Three moves early in the cycle that prevent most procurement problems:

1. Engage procurement early.
Not at the end, when they’re surprised by the deal. Early, when you can shape their perception. Even a courtesy call in week two — “I know you’ll eventually need to review this, and I wanted to make sure you understood what we’re discussing and when it will likely come to you” — pays compound returns later.

2. Help your champion build the ROI case themselves.
Don’t write it for them. Walk through the logic together so they own it. A champion who built their own ROI case can defend it to procurement, the CFO, and the board. A champion who was handed the case can’t.

3. Price with defensible specifics.
Every pricing element should have a rationale your champion can explain. If the implementation is $X, it’s because Y specific work is required. If the annual is $Z, it’s because the ROI math supports that value. Pricing without defensible logic invites procurement to reduce it.

---

Procurement doesn’t kill healthy deals. It surfaces the weaknesses in unhealthy ones.

If you’re losing deals in procurement, the fix is rarely “better procurement engagement at the end.” The fix is stronger upstream selling — clearer ROI, earlier economic buyer engagement, realistic timelines, defensible pricing.

Fix the upstream. Procurement becomes a milestone, not a mortality event.

Most software and technology demos are designed to show off the product. The buyer’s perspective — what they actually need to understand, what decisions they’re trying to make, what risks they’re trying to assess — is usually an afterthought. The result is a demo that’s impressive to the product team and mostly useless to the buyer.

Better demos are constructed around three principles that most sales teams either miss or ignore.

Principle 1: The Demo Is Not the Selling

The demo is where the buyer confirms what they already believed. Selling happens in discovery, in the narrative you build, in the relationships. By the time you’re demoing, the buyer has usually made a preliminary decision based on what they understood about your company before the demo. The demo either confirms or disconfirms that preliminary decision.

This means the demo’s job is not to create desire. Desire was (or wasn’t) created earlier. The demo’s job is to remove doubt. Every minute of the demo should be serving a specific doubt the buyer has already surfaced — either in discovery or in their own head.

A demo that tries to create desire usually fails. The buyer sees features they don’t need, workflows they won’t use, dashboards that don’t address their actual problem. The pitch feels generic because it is. You’re showing them a tour of the product, not an answer to their question.

Principle 2: The Questions Drive the Demo, Not the Script

The best demos I’ve watched started with the seller asking, “Before I show you anything, what are the three things you specifically want to see today?” And then the demo was structured around those three things.

The worst demos I’ve watched were the ones where the product marketing script was executed beat-by-beat regardless of what the buyer cared about. The script covered the full product. The buyer wanted to see one workflow. The buyer spent 40 minutes waiting for the relevant part.

Scripted demos signal that the seller isn’t listening. Listening demos signal that the seller is there to help the buyer evaluate, not to perform.

Principle 3: Show the Ugly Parts

Most demos show only the smooth happy path. “Here’s how it works.” Click. Click. Click. Perfect.

The buyer knows no software is that smooth. What they’re actually trying to understand is: where does it struggle? What happens when I try something complicated? How does it handle my weird edge case?

Demos that show the ugly parts — “here’s where it gets tricky, and here’s how we handle it” — build trust faster than demos that don’t. The ugly parts aren’t embarrassing; they’re what makes the rest of the demo credible.

When I’m buying, the vendor that walked me through the hard cases was the vendor I trusted. The vendor that showed me only the clean version was the vendor I mentally discounted, because I knew they were hiding something and I didn’t know what.

The Structural Move

Before your next demo, call the buyer. Fifteen minutes. Ask: “What do you specifically want to understand from this demo? What are the questions that, if I answer them well today, make this an easy decision? What would someone on your team push back on, and what do you need to see to address that pushback?”

Structure the demo around those answers. Skip the rest.

---

The demos that close are the ones that answer the buyer’s questions. The demos that don’t close are the ones that perform the product tour.

Stop running tour demos. Start running question-answering demos. Your close rate will tell you which one was the problem.

Looking back: April 2026

There was a specific board meeting, years ago, that changed how I thought about forecasting. I hadn’t realized until that meeting how deeply I’d absorbed a culture where forecast commitment was treated as a display of confidence rather than as a probabilistic estimate. The board conversation that surfaced this was uncomfortable, instructive, and one of the more useful feedback moments of my career.

The Setup

I was walking the board through the current quarter’s forecast. Coverage looked reasonable. Pipeline quality was mixed. I’d committed to a number that was toward the optimistic end of the range because — as I told myself — that’s what you did. Boards wanted confidence. Leaders delivered confidence. The forecast was aspirational because aspiration was the expected register.

I walked through the slides. Numbers matched expectations. I was ready to move to the next topic.

An experienced board member interrupted. “I want to push on this. You’ve told us the commit number. I want to understand what you think the actual number is going to be.”

The Question That Reframed Everything

The question was simple but cracked something open. The commit number and the expected number had quietly become different things in my head — and I hadn’t been articulating the difference. The commit was aspirational. The expected was what I actually thought would happen. Those numbers differed by about 15%. I’d been showing the first and privately carrying the second.

I said something like: “The commit is X. My personal expectation is closer to Y.”

The board member nodded. “Thank you. That’s the number I want. I need to make decisions based on what you actually think, not on what you think you’re supposed to say.”

The meeting shifted. We spent the next 40 minutes talking about the honest forecast — the one I actually believed — and the uncertainty around it. Where were the biggest risks? What were the leading indicators? What would I see in the next 30 days that would update my estimate?

The conversation was more useful than any previous board conversation I’d had about revenue. Not because the number was better. Because the number was honest.

What I Realized Afterward

The lesson that took a few weeks to fully land: forecast commitment and forecast honesty are different things, and treating them as the same thing produces worse decisions.

I’d been trained — through years of watching leaders perform confidence, through cultural messaging about “missing your number” being unforgivable, through my own discomfort with presenting uncertainty — to converge on a single commit number that was optimistic by design. The optimism served a signaling function (look how confident the leader is) but undermined the real function of forecasting (help decision-makers plan).

The board member’s question forced a separation I hadn’t been making consciously: the commit is a promise to the team and the market; the expected is an analytical estimate. Different purposes, different numbers, different conversations.

How I Forecast Now

After that meeting, I shifted my forecasting practice in specific ways:

1. I present ranges, not point estimates.
The honest forecast has a low, mid, and high. The commit is usually somewhere between low and mid. The expected is around mid. The upside — what happens if things go unusually well — is the high. Three numbers, not one, force a real conversation about uncertainty.

2. I explicitly state what would move the forecast.
“If these three deals close on current timelines, we hit the upside. If any two slip, we hit the midpoint. If all three slip, we’re at the low end.” This gives the board (or any audience) the ability to track the forecast themselves, which builds trust faster than presenting a clean number ever did.

3. I separate commit from expectation deliberately.
The commit is what I’m willing to publicly stand behind and be measured on. The expectation is what I analytically believe. I present both, name them differently, and explain the gap. Some audiences find this jarring at first. They end up appreciating it.

4. I review my forecast accuracy quarterly, honestly.
The single most important forecasting discipline is looking back. Was my forecast within 5%? 10%? 20%? The pattern over four quarters tells me whether I’m a reliable forecaster, a systematically optimistic one, or a sandbagger. Every forecaster has a personal bias. Knowing yours is a precondition for adjusting.

The Broader Lesson

The board meeting taught me something beyond forecasting specifically. It taught me that performing confidence — in any domain — often costs more than it provides. Audiences (boards, teams, customers) are usually more sophisticated than the performance assumes. They can tell when the presentation is calibrated for signaling rather than for honesty. The leaders who consistently present honestly — with appropriate uncertainty, with explicit reasoning, with acknowledged risks — build trust that the performative leaders can’t match.

This is hard in cultures that reward confidence. It’s the right bet anyway, because the alternative is a long career of building trust on unstable ground. One honest forecast compounds into permission to be honest about everything else. One performative forecast forces the next one to also be performative.

What I’d Tell a First-Time CEO

If you’re a first-time CEO or a first-time revenue leader, resist the temptation to converge to a single commit number that performs confidence. Present the range. Explain the uncertainty. Separate commit from expectation. Your board will be more helpful, your team will trust you more, and your own decision-making will be cleaner.

The board meeting that taught me this was uncomfortable for me at the time. It’s also the meeting I most often refer back to when I think about what kind of operator I want to be.

---

Honesty about uncertainty is a professional muscle. Most leaders aren’t taught it. Many cultures actively punish it. The leaders who develop it anyway build something more durable than the confident-performer alternative.

It’s a quieter way to lead. Over time, it’s also more effective. I’m grateful for the board member who asked the question that forced me to see the difference.

Looking back: April 2026

The first time I formally ended a customer relationship was harder than I expected and more important than I realized. It’s one of those small professional moments that shaped everything that came after, though I couldn’t have said so at the time.

The Setup

The customer in question was well-known. They paid. They weren’t particularly difficult in obvious ways. But over the course of the engagement, a pattern had emerged: they consumed disproportionate resources, they negotiated every small item as though it were existential, and their team treated my team as adversarial rather than collaborative.

The math on the account had slowly shifted from profitable to marginal to negative. Support hours escalated. The delivery team dreaded every call. Morale around the customer had soured.

I’d been told by every mentor and business book I’d ever consumed that firing a customer was legitimate. That some customers cost more than they produced. That walking away was sometimes the right call. Intellectually, I agreed.

In practice, actually doing it was something else entirely.

Why It Was Hard

Three reasons, in order of intensity:

1. The revenue was real.
Losing the account meant losing revenue. Revenue is always tangible. The cost of keeping the account was distributed across the team and the quarter — less tangible, harder to sum. The instinctive math always favored keeping them.

2. The story I’d tell myself about losing a customer felt worse than the reality of keeping them.
I’d spent years building a book of business. Every customer was a win. Losing one felt like a loss, regardless of the circumstances. I realized, in thinking about it, that I had an irrational attachment to the customer count as a measure of my professional standing — and that the attachment was making it hard to make the economically rational decision.

3. The conversation itself required specific skills I hadn’t developed.
“We’re choosing not to continue our relationship” is a sentence I’d never had to say before. Saying it well, without drama, without burned bridges, required a poise I didn’t naturally have. I rehearsed the conversation more than any meeting I can remember preparing for.

How It Went

The conversation itself went better than I’d feared. The customer was surprised, then defensive, then — once they realized I wasn’t going to be negotiated out of the decision — gracious. They appreciated the directness. They wished us well. The meeting ended in about 40 minutes.

A week later, the lead stakeholder sent me a note thanking me for the professionalism. He said — and I remember this exactly — that he’d had vendors walk away from his business before, and none of them had done it with the clarity I had. It was the first time I’d heard that feedback, and it changed how I thought about what “firing a customer” even meant.

It wasn’t a failure. It wasn’t even a loss. It was a specific professional action, done well, that left both sides better off than if I’d tried to limp through another six months of a dying relationship.

What Shifted

Several things changed for me permanently after that experience:

The customer count stopped being my benchmark.
I started paying attention to customer quality in ways I hadn’t before. The question became not “how many customers do we have?” but “how many of our customers are ones we’re proud to work with?” The first question has a ceiling. The second one has a floor.

I got better at the pre-signing conversation.
Having actually walked away from a customer, I became more willing to surface fit concerns before a contract was signed. The customers I’m most reluctant to bring on now are the ones I know would be hard to walk away from later. Better to have the hard conversation up front than to manage through months of difficulty.

My team changed.
The delivery team, specifically, noticed that I’d chosen their morale over the revenue. That one decision did more for team trust than any of my leadership intentions had. They knew, after that, that I wasn’t going to trade their well-being for my numbers. Every retention and recruiting conversation we had afterward built on that foundation.

The remaining customer base got better.
It wasn’t immediate, but over the following year, the quality of our customer base noticeably rose. Partly because we’d freed up resources to serve the good customers better. Partly because word travels in any industry, and the customers we wanted more of could tell we were the kind of vendor who wouldn’t tolerate bad-fit relationships — which is exactly the kind of vendor the best customers want to work with.

The Principle That Generalized

The first time I fired a customer, I was operating on the assumption that every customer is valuable and that ending a relationship is a failure mode. What I learned is the opposite: the willingness to end a customer relationship is a marker of operational maturity, and companies that can’t do it have a ceiling they can’t see.

This generalizes beyond the specific action of customer termination. The same underlying skill — ending what isn’t working with clarity and grace — applies to underperforming hires, failed partnerships, unprofitable products, strategic dead ends. The founders and operators I’ve watched scale successfully all share this skill. The ones who struggle often can’t bring themselves to exercise it.

---

If you’ve never fired a customer, it might be a skill worth developing before you need it. Not because you should fire any specific customer today — just because the capacity to do it changes how you think about every other decision downstream.

The first time is hard. Every time after is easier. By the third or fourth time, it’s just one tool among others in the operator’s kit, used sparingly, but present.

That’s where you want to be. It took me one specific customer to get there. I’m grateful for the lesson.

Looking back: April 2026

When enterprise selling moved remote in 2020, a lot of what had worked in the pre-2020 era had to be rebuilt. Some of the rebuilding produced better motions than existed before. Some of it produced worse ones. Understanding which is which has been clarifying in retrospect.

What Got Harder

Reading the room.
In-person meetings transmitted dozens of small signals — how the champion was reacting to the skeptic, who was checking their phone, whether the energy in the room was with you or against you. On video, most of those signals disappeared. Sellers who relied heavily on reading the room had to rebuild their craft around the narrower bandwidth of video meetings.

The best sellers found ways to compensate — asking more direct questions, checking in explicitly with specific stakeholders, structuring the meeting to draw out reactions that would have been spontaneous in person. The lesser sellers kept expecting the signals to come through and missed them.

The hallway conversation.
In-person meetings had a structure where the formal meeting was 70% of the value and the 30% that happened in hallways, over coffee, walking to the parking lot was often where the real progress happened. Those informal moments disappeared almost entirely in remote selling.

The adaptation was to engineer equivalents: specific one-on-one video calls, separate calendar time for off-record conversations, use of messaging platforms for between-meeting dialogue. These worked, partially. The equivalents never fully matched the spontaneous-hallway version.

Building trust with people you haven’t met in person.
Some of this wasn’t obvious until later. Trust can be built on video — but the depth and durability of that trust, in retrospect, seems shallower than the in-person equivalent. Relationships formed entirely remote during 2020-2022 often proved less resilient to difficulty than relationships with equivalent touch count that included some in-person contact.

The lesson: the high-bandwidth modalities build relationships faster than the low-bandwidth ones. When everything was low-bandwidth, the relationships still formed, but with shallower foundations.

What Got Easier

Access.
Getting a meeting with a senior executive became dramatically easier in 2020. The logistics overhead of in-person meetings — flights, parking, calendar blocks — had constrained how many meetings senior people could take. When all meetings became 30-minute video calls, senior executives could take 6 to 10 meetings a day where they previously took 3 to 5.

This meaningfully expanded the pool of possible conversations for many sellers. Cold outreach to executives became more productive because the calendar constraint had eased. Existing relationships became easier to maintain because a quick video check-in was lower-friction than scheduling a lunch.

Geographic reach.
Regional sellers who could previously only cover their geography could now work across regions. Enterprise deals in cities the rep had never visited became viable. This expanded the effective market for many sellers and compressed the advantage of locally-based competitors.

Parallel engagement across buying committees.
In-person selling was almost always sequential — you had meetings with specific stakeholders in specific sequence, and the timeline was governed by travel logistics. Remote selling let sellers run parallel engagement across multiple stakeholders simultaneously. The CTO call could happen Tuesday, the CFO call Wednesday, the operations call Thursday — with all three feeding into a unified internal pipeline of the deal.

This actually compressed some deal cycles, especially for deals where multi-threading was the primary constraint.

What Became a Permanent Mixed Bag

Discovery.
Discovery calls got more efficient (no travel time, tighter agendas) and less rich (fewer side conversations, less whiteboard collaboration). The net effect varied by industry and deal type. Complex, multi-stakeholder discovery still benefited from in-person intensity. Simpler, single-stakeholder discovery was often better on video.

Closing.
Closing a significant deal via video remained awkward for years. Something about the final steps — the handshake equivalent, the moment of commitment — didn’t transmit cleanly over the video medium. Many sellers found that they could do 80% of a deal remotely but wanted the final stages in person.

What I’d Tell Anyone Rebuilding

If you’re optimizing a sales motion in 2026, the remote-selling lessons are still live:

• Don’t fight the hybrid equilibrium. Engineer it.
• High-bandwidth modalities (in-person, long-form video, workshops) build deeper relationships faster. Use them strategically.
• Low-bandwidth modalities (email, chat, short video) scale broader but shallower. Use them for volume.
• Sequence deliberately. Use remote for early, in-person for inflection points, remote for execution.

The sellers doing the best work now are the ones who’ve internalized this layering. Not remote-first. Not in-person-first. Deliberate-sequencing.

---

The remote shift didn’t kill in-person selling and it didn’t replace it. It reshaped the hierarchy of which modalities do which work. Five years in, the sellers who’ve digested that reshaping have better motions than existed before. The ones who haven’t are still nostalgic for 2019 or still overcommitted to 2020.

Neither nostalgia nor overcommitment serves. The hybrid reality is the stable one now. Work from there.

Looking back: April 2026

I’ve told versions of this story to a lot of people I’ve mentored. It’s one of the cleanest lessons I’ve ever learned in enterprise selling, and it cost enough that I remember the details more than a decade later.

The Setup

The deal was with a large telecommunications carrier. The champion was the CIO — not just my champion, my lead champion. The kind of executive sponsor every enterprise seller hopes for. She understood the technology, had authority over the decision, and had personally advocated for our solution against internal skepticism.

We were nine months into a 12-month cycle. The deal was worth low seven figures. Legal was engaged. Procurement had the redlines. I’d forecasted the close for the following quarter, and the number was good enough that it was going to earn my team president’s club.

Then the CIO got promoted.

Not to a better role at the same carrier — to a different business unit. A different market segment, a different portfolio, a different buying authority. She wasn’t leaving the company. She was moving to a role that had no visibility into, or authority over, the deal she’d been championing.

What Happened Next

Her replacement walked in on a Monday. The handover was less than a week. Her new boss introduced her to the vendors she was inheriting as part of the buying portfolio — including us.

She was professional. She took the meeting. She asked good questions. And then she made clear that she wanted to take the next 60 days to evaluate all the open vendor relationships and make her own assessment before moving forward on any of them.

Sixty days became ninety. Ninety became one hundred and twenty. By the time she was ready to move, the internal budget timing had shifted, the original business case had to be rebuilt with her name on it, and the organizational momentum we’d built over nine months was effectively reset to zero.

The deal didn’t die. It closed — nine months later, at 60% of the original scope, because by the time the new CIO was comfortable, the business conditions had shifted.

What I Got Wrong

I had multi-threaded the deal somewhat. I’d built relationships with the CIO’s direct reports, with procurement, with the architecture team. What I had not done — and this is the specific failure that cost me a year — is build a relationship with the CIO’s peer executives or her boss.

My champion was strong. But she was single-threaded on her own authority. When she moved, her authority moved with her, and nobody above her had a personal investment in the deal.

If I’d invested in one relationship at her boss’s level — a casual but consistent relationship over the nine-month cycle — the transition would have played out differently. The boss would have vouched for the deal to the new CIO. The new CIO would have inherited a semi-endorsed relationship instead of a blank-slate evaluation.

I didn’t build that relationship because I didn’t see the need. The deal was moving. The CIO was on board. Why burn political capital to get time with her boss when everything was going well?

The reason why is exactly the scenario that played out. Deals don’t die when they’re going well. They die when the conditions change. And the conditions always change.

The Principle I Now Apply

In every enterprise deal I’m in now — or that I coach someone through — I try to make sure there’s one relationship above the level of the primary champion. Not deep. Not intrusive. Just enough of a personal connection that if the champion moves, promotes, or leaves, there’s someone else in the organization who remembers the deal, thinks favorably of us, and would advocate at the executive level.

This relationship often takes a while to build. Executives above the buying authority don’t have time for vendors who aren’t specifically relevant. So the relationship has to be built on something other than the current deal — shared industry interests, introductions to other executives, a perspective you can bring to their strategic questions.

It’s slow and inefficient in the short term. It pays the moment your champion moves, which is more often than most sellers expect.

---

I don’t often tell this story at scale because it’s specific and personal. But I think about it every time I look at a pipeline. Every single-threaded deal is one job change away from dead. I learned it in telecom. The lesson never stops being relevant.

Looking back: April 2026

When I first started selling into the construction industry, I thought I understood enterprise deals. I’d sold into medtech. I’d worked in consulting. I knew about champions, buying committees, and slow procurement cycles. Construction taught me something different: the industry where the non-obvious stakeholder has the most power over whether your deal closes.

In construction, that stakeholder is the bonding company. And if you don’t know the bonding company, you don’t know the deal.

Who the Bonding Company Is

For anyone outside construction: bonding companies underwrite the surety bonds that general contractors need to bid on projects. The bond guarantees performance — if the GC fails to complete the project, the bonding company has to make the project whole. Because of that risk, bonding companies have enormous informal authority over which GCs can bid which projects, which vendors they can use, and what terms they can accept.

If a GC takes on obligations the bonding company doesn’t like, the GC may find themselves unable to get bonding for their next project. That’s career-altering for the GC — and it means the bonding company’s preferences often shape decisions the GC makes without ever formally being in the conversation.

The Deal That Taught Me

A GC I was working with was excited about a project I was supplying into. The clinical champion equivalent — the project manager — was enthusiastic. The owner was on board. The sign-off felt imminent.

Then the bonding company asked to review the terms.

The terms I’d agreed to included performance guarantees the bonding company considered atypical. Not catastrophic — just unusual enough that they wanted the GC to push back on them. The GC couldn’t push back without embarrassing themselves, so they asked me to soften the terms, which I did. Cost me about 8% of the margin and added 30 days to the close.

What I learned from that experience: the bonding company was effectively a silent partner in every construction deal. They didn’t show up in meetings. They didn’t appear on my stakeholder map. But their preferences were absorbed into every decision the GC made — and when those preferences conflicted with my contract, I was the one who had to adjust.

The Pattern That Generalized

Once I understood the bonding company dynamic in construction, I started seeing equivalents everywhere:

• In medtech, it was medical device reprocessing companies, whose terms affected whether certain devices could be used profitably at the hospital.
• In telecom, it was the managed service providers, whose existing relationships and service agreements constrained what customers could adopt.
• In consulting, it was the audit firm, whose opinions about engagement scope and conflict of interest affected which projects the client could take on.

The pattern is always: there’s a third-party stakeholder with informal authority over whether your deal can close — and they’re not in any of your meetings, but they’re shaping the decisions of the people who are.

How to Find Your Bonding Company

In any enterprise deal, ask this question: “Who else has to be comfortable with this decision, even if they’re not in the room?”

The question almost always surfaces a silent stakeholder. Sometimes it’s internal — procurement, legal, risk. Sometimes it’s external — an auditor, a regulator, a bonding company, a reinsurance provider, a channel partner with contractual preemption rights.

Once you know the silent third party, you can structure the deal around their constraints. Not always in ways that satisfy them perfectly, but in ways that don’t trigger their objection after the champion has already agreed.

The construction lesson was: if you wait until the bonding company weighs in, you’re already behind. Your champion has committed. Your pricing is set. Any friction introduced by the silent stakeholder comes out of your margin or your timeline, because the GC won’t take the hit.

The same dynamic operates in every industry. The silent third party always wins — either by being satisfied up front or by extracting a price at close.

The Practical Move

On every enterprise deal I’m in now, I try to explicitly map the silent third parties. Not just internal stakeholders — external ones too. Who’s backstopping the buyer’s ability to say yes? Whose permission do they need in a form they’d never describe as “permission”?

Sometimes the answer is nobody. That’s useful to know. More often, the answer is a party I hadn’t previously considered, and their preferences start shaping how I structure the deal.

This has saved me more slipped quarters than almost any other habit I picked up across my BD career. Construction taught me the principle. Every industry reinforced it.

---

Find your bonding company before the close. Structure around their preferences. Save yourself the margin, the timeline, and the surprise.

Looking back: April 2026

Consulting teaches you pricing in a way that’s painful but permanent. Every hour of yours was sold at a specific rate, and every hour that didn’t get captured on a timesheet was revenue the firm never recognized. The discipline that system imposed taught me more about scope than any other experience in my career.

The Core Lesson

In most businesses, scope is abstract. “What did we commit to?” is answered with some hand-waving about “the deliverables” and “what the customer wanted.” The real answer is usually negotiated in the moment, often at the expense of the delivery team.

In consulting, scope was literal. Every conversation, every document, every meeting had a billable-hour cost attached. If scope was ambiguous, someone was either eating the hours or charging them anyway — and both outcomes had consequences. Eat too many hours, and the engagement’s margin collapsed. Charge hours that weren’t clearly in scope, and the client got angry.

The discipline this forced: learn to scope precisely, or pay a specific, visible cost for not scoping precisely.

Three Patterns That Stuck

1. Every “yes” has a silent “no” attached.
When a client asked for something that was out of scope, the temptation was to say yes. It’s friendlier. It’s easier. It builds the relationship. But every yes to unscoped work was a no to something else — either the margin of the engagement, the delivery team’s ability to finish the in-scope work on time, or the next client’s priority on your team’s time.

Learning to say “yes — and here’s what would need to change to accommodate it” was the discipline that separated consultants who delivered profitable engagements from those who delivered loss-making ones. Saying yes without that clarifier was how engagements quietly went underwater.

2. The hardest scoping conversation is the one that happens after the SOW is signed.
The easy scoping conversations happen at the front end, when everyone is excited, the relationship is fresh, and both sides are being cooperative. The hard ones happen in month three, when the client wants something that’s slightly outside the original scope and assumes it will be handled.

The way I learned to handle this: treat the mid-engagement scope conversation as a craft of its own. Not a confrontation. A graceful, explicit re-negotiation: “Here’s what was in scope. Here’s what you’re asking for. Here are the three ways we could accommodate it — change order, trade-off within current scope, or we phase it into the next engagement.”

Delivered cleanly, that conversation usually strengthens the client relationship rather than weakening it. Clients respect professionals who know their scope. They quietly disrespect ones who don’t.

3. Unscoped work accumulates interest.
A single unscoped task absorbed here and there doesn’t look like much. Five of them compound into a margin problem. Ten of them produce a client who assumes the unscoped behavior is baseline — and then gets upset when the next engagement is scoped properly.

Unscoped work accumulates interest in the same way debt does. The engagement manager who let it accumulate without comment was preserving short-term relationship warmth while creating a medium-term expectation problem. I watched this lesson play out in multiple engagements. The warmth always faded. The expectation always stuck.

How This Applies in Other Industries

Every industry has a scope problem. Software implementation. Construction. Marketing agencies. Product development. Medtech installations. The pattern is always the same: a customer asks for something slightly more than what was committed, the vendor accommodates, and six months later there’s a margin or timeline problem that nobody can quite trace.

The fix is always the same, too: treat scope as explicit. Name it. Document it. When it changes, renegotiate. Don’t let it drift.

The vendors I’ve watched do this well come across as more professional, not less friendly. The ones who let scope drift come across as accommodating in the short term, and chaotic in the medium term.

---

If you’re in any commercial relationship and you can’t cleanly answer “what’s in scope right now,” you probably have scope drift. The fix is cheap: an explicit conversation. The cost of not having it is a relationship that slowly becomes dysfunctional without anyone being able to explain why.

Billable hours taught me this the expensive way. I’m grateful for the lesson. I’ve since applied it in every industry I’ve worked in, and it’s been one of the most durable, generalizable things I learned in consulting.

Looking back: April 2026

Early in my career selling into medical technology, I lost a deal I thought I’d won. Not a deal slipped — a deal lost, definitively. The lesson has shaped how I think about enterprise selling ever since.

The deal was with a regional hospital system. The clinical champion was enthusiastic. The department head had quietly approved. The CMO had met with me twice and was leaning in. Everything looked right. Legal had the redlines. I was forecasting it to close that quarter.

Then IT got involved.

What Happened

The hospital ran an electronic medical records system I’d assumed would interoperate cleanly with our device. It didn’t. Specifically, the HL7 messaging format my clinical data needed to export into was implemented slightly differently in their EMR than in the two reference hospitals I’d cited. The integration wasn’t impossible — it was non-trivial, required their IT team’s involvement, and would add two to three months to the implementation timeline.

None of this had come up in discovery. Not because I hadn’t asked — because I’d asked the wrong people. I’d asked the clinical champion about integration and she’d answered based on her general understanding, which was “our IT team handles that kind of thing.” That answer was technically true and functionally useless.

The deal didn’t die. It slipped two quarters while the integration questions got worked through. But the damage was done: my CMO champion got frustrated with the timeline, my clinical champion started getting pressure from her department to explore alternatives, and by the time we got to a workable integration plan, a competitor had re-entered the conversation with a solution that had already been proven in that EMR environment.

We got the deal back, eventually. But it closed six months late at a 20% discount I wouldn’t have had to give if I’d identified the HL7 issue in discovery.

What I Learned

Three things, which I now teach anyone I mentor in enterprise selling:

1. Every enterprise deal has a silent second stakeholder.
It’s never the champion. It’s not the economic buyer. It’s the person whose job is to say “hold on” at some technical, legal, or operational layer. In medtech, it was IT. In telecom, it’s facilities or network ops. In construction, it’s the bonding company. In consulting, it’s procurement. The pattern is universal.

2. The silent stakeholder must be surfaced in discovery, not at close.
The cost of finding them early is 15 minutes of conversation with your champion, asking “when this goes to [X], what’s the first question they’ll have?” The cost of finding them late is a slipped quarter, a discount, and sometimes a lost deal.

3. Your champion’s answers about the silent stakeholder are almost always wrong.
Not because your champion is wrong about their own job. Because they’re answering based on how they’d want the process to go, not how it actually goes. “Our IT team will handle that” is directional truth. It is not actionable intelligence. You have to get to the IT team yourself — not through the champion’s interpretation of what IT will need.

Why This Pattern Matters So Much

Looking back, the HL7 problem was probably the single most expensive lesson of my medtech career. But the principle it taught — silent stakeholders exist in every enterprise deal, they must be surfaced early, and your champion can’t fully characterize them — is something I now apply in every deal review, in every deal I’m in directly, and in every coaching conversation I have with someone earlier in their career.

I’ve watched sellers in construction learn this lesson with bonding companies. In consulting, with procurement. In telecom, with network operations. The industry changes; the pattern doesn’t.

The irony is that the fix is cheap. A seller who asks two or three specific questions in discovery about the silent stakeholders will catch most of these issues before they compound. But most sellers don’t ask, because the questions feel awkward, and because the champion is giving them warm signals that make the deal feel safe.

Warm signals from the champion are not the same as visibility into the full buying process. I learned that once. I don’t forget it.

---

If you’re selling enterprise anything and you haven’t identified your silent stakeholders in discovery, you don’t have a deal yet. You have a relationship that might become a deal, pending surprise.

Don’t be surprised. Ask early. Ask specifically. Get past the champion’s version of the process to the actual one.

That’s the HL7 lesson. It cost me a quarter. It’s saved me many more.

Looking back: April 2026

One of the most durable lessons I took from selling into medical technology was this: your clinical champion will change roles before your deal closes. Not sometimes. Usually.

This is true in every industry — champions get promoted, move sites, leave. But medtech has a particularly high rate of internal rotation. Clinicians shift sub-specialties. Hospital systems reorganize. Academic physicians move between institutions. The cadence is faster than in most B2B contexts, which made medtech a reliable teacher about multi-threading.

The Pattern

A typical medtech enterprise cycle runs 6 to 18 months. A clinical champion’s seat in a specific role at a specific institution is often 18 to 36 months. Do the math on overlap and you realize: in a non-trivial percentage of deals, the person who championed you at month one is in a different role by the time your deal is operational.

I saw this go sideways on specific deals. A surgical champion who was thrilled in the discovery phase got recruited to a different hospital system at month five. His replacement had a different preferred vendor. The deal didn’t die — it just stopped moving, and nobody could tell me why for three months.

Another deal — an internal medicine champion got pulled into an administrative role mid-cycle. She wasn’t moving institutions. She was just moving offices, and the new role didn’t include authority over clinical purchasing. The deal required a new champion, whom we had never met.

What I Learned About Building Deals

The first obvious lesson: multi-thread everything. In medtech, this meant cultivating at least three clinical relationships on a given deal, plus administrative, plus materials management. No single-threaded deal survived contact with institutional reality.

The less obvious lesson, the one that took me longer: build relationships with people who will outlast any specific role. The senior clinicians who remained in an institution for decades were worth more than a junior champion in the current buying center. A dean, a department chair, a longtime nursing director — their presence was stable across reorganizations.

I started building relationships at those levels even when they weren’t directly involved in my deals. Two years later, I’d find that one of them had become the sponsor I needed on a deal I hadn’t even started yet.

Why This Applies Everywhere

Medtech taught me the pattern, but I’ve since watched it play out in every industry:

• In telecom, CIOs rotate between business units every 3 to 4 years. The relationships with their VPs — who often stay longer — outlast them.
• In construction, project managers change but the owner’s representative often stays for years. Build that relationship and you have durable access.
• In consulting, the engagement manager on any specific project will rotate. The senior partner sponsoring the client relationship rarely does.

The common pattern: in any enterprise selling motion, there are transient relationships and durable ones. The transient ones drive individual deals. The durable ones drive careers.

The operators I’ve watched build the strongest enterprise selling records were the ones who invested in durable relationships even when they didn’t need them for the current deal. The ones who invested only in transient relationships had bursty results — strong when the specific person was in place, invisible when they moved.

The Principle I Now Apply

In every account I work, I try to answer one question explicitly: who, at this account, will still be there in five years?

The answer is sometimes the obvious senior executive. Often it’s someone adjacent to the buying center — a longtime operations director, an influential technical lead, a specialist who’s built a career at the institution. These people are often not the deal decision-maker in the current cycle. They are the decision-makers across decades.

Medtech made this legible because the rotation was so frequent that the lesson arrived early. Every industry has the same pattern. It just compresses or expands the timeline on which the lesson becomes obvious.

---

Looking back, the reason I still emphasize multi-threading so heavily — in content, in coaching, in deal reviews — is that medtech taught me, early, how expensive single-threading is in an industry where people move. The insight generalized. The urgency came from the compressed laboratory of clinical sales.

If you’re selling into any industry with high role rotation — and most B2B industries qualify — the multi-threading lesson is the same lesson medtech teaches. Learn it early or pay for it later.