Multi-Threading in Sales: The Practical Playbook for Enterprise Deals

Disclaimer: This article is written in partnership with GetAccept, the digital sales room platform I regard as the most robust on the market. Having spent 2+ years at GetAccept, I’ve seen its strengths firsthand and how it stacks up against the competition. The article includes affiliate links, meaning I may earn a commission if you book a demo or make a purchase through these links, at no additional cost to you. These partnerships support the blog and help me keep sharing free, practical resources. All views are my own, based on independent analysis to serve the enablement and revenue community.

Introduction

Every complex B2B deal is a group effort, even if some sellers still wish it weren’t. 

Today, enterprise buying groups average six to ten decision-makers, each reviewing independently and armed with peer feedback, benchmarks, and third-party insights.

Many times, your champion is in the dark. Not because they don’t believe in your solution, but because they’re navigating priorities you can’t see.

And it gets worse: Gartner research shows buyers spend just 17% of their time interacting with sales reps, usually divided among multiple vendors, with the rest spent in self-directed research.

Meanwhile, inside those accounts, many decisions get filtered in “meetings” or hallway debates that happen when you’re not in the room.

I’ve lost count of deals where the product was compelling, the champion was committed, but weak multi-threading meant a sudden org change, a budget reallocation, or a quiet shift in procurement killed everything.

Total radio silence. 

Poof. 

Pipeline goes up in smoke.

The data is crystal clear: deals with multiple engaged contacts close at materially higher rates. Gong data, for example, shows that closed-won deals involve 3x the number of people than lost deals.

And by 2026, Gartner expects that organisations that unify commercial strategies and leverage multi-threaded commercial engagements will realise revenue growth that outperforms their competition by 50%.  

In this guide, I’m tearing down generic “add more contacts” advice. 

You’ll get a field-tested playbook packed with strong foundational principles and the very tactics top-performing sales teams use to map influence, expand coverage, and turn scattered contacts into a unified buying group. 

I’ll include: 

• A clear multi-threading definition
• Key factors to consider when deciding whether to multi-thread
• Practical plays and talk tracks for effective multi-threading
• Enablement’s role in making multi-threading stick (skills, process, and assets)
• Key multi-threading metrics to track

If you’ve suffered from last-minute blockers, hidden vetoes, or resistance that’s hard to pin down – take heart. You’re not alone.

And if you’re an enablement practitioner or sales manager, you’ve probably seen your team lose winnable deals for the same reasons – despite strong champions and solid business cases.

This is where it stops happening.

Let’s dig into the mechanics, the mindset, and the plays that actually shift outcomes.

What is multi-threading in sales?

Simply put, multi-threading in sales means building relationships with multiple people across your buyer’s organisation – not relying on just one contact.

Picture this: instead of putting all your energy into a single champion or sponsor, you’re engaging with a range of stakeholders such as budget owners, end users, technical leads, procurement, legal, and beyond. 

Each brings a unique perspective, influence, and potential veto power.

Single-threading, on the other hand, puts all your eggs firmly in one basket. It might feel streamlined or even efficient, but it’s fragile.

Lose your key contact, and the deal often loses momentum or is lost entirely. 

In complex enterprise sales, that’s not just a risk, it’s the most common trap.

However, it’s important to understand one thing about multi-threading. 

It should never involve simply haphazardly copying the entire company on your next email. The goal isn’t “more outreach for the sake of it.” 

Instead, it’s about building a coalition: identifying who matters, why they matter, why your solution might matter to them, and engaging each thoughtfully with relevant insights and points of view.  

When you do this well, you’re helping every stakeholder see how your solution ties into a shared outcome. 

There’s a real satisfaction in watching consensus build across an account, knowing you’re helping people connect the dots. 

That’s the real power of multi-threading – creating an environment where the deal is carried forward by a network of advocates, not just one voice. 

When to multi-thread (and when not to)

Of course, not every deal demands the same level of threading. The more value, risk, and organisational change involved, the earlier you need to broaden your reach.

Think about large, high-value deals with long cycles. They almost always draw in multiple voices: executives setting direction, managers driving process, IT and security validating integrations, and legal reviewing terms. In those environments, multi-threading isn’t optional. It’s the only way to keep momentum and avoid last-minute surprises.

The same applies when your solution touches several departments at once. 

If Finance, Sales, and Operations will all feel the impact, you need to bring them in early.

Regulated industries, complex implementations, and formal buying committees like those in RFPs or the public sector only reinforce this point; consensus has to be built up front, not at the eleventh hour.

On the other hand, not every situation calls for a wide web of connections. 

Smaller, transactional deals often move quickly with a single decision-maker. In SMB environments where one person owns the budget and the outcome, threading too soon can actually slow things down or risk alienating your champion. 

The same is true in early discovery: before a clear problem and champion emerge, expanding sideways can feel like you’re going around your contact instead of with them.

The principle is simple: scale your threading to match the deal. 

In complex, high-stakes sales, widen the net early. In smaller, contained motions, keep it lighter and more focused. Knowing the difference is what separates thoughtful multi-threading from unnecessary noise.

As Nate Nasralla, founder of Fluint, puts it, the goal is to identify the “minimum viable buying committee” – the smallest group of stakeholders who can validate, fund, and implement the deal. Anything less, and you risk a shaky, single-threaded opportunity. Anything more, and you add friction without value. 

5 high-level practices for effective sales multi-threading

As we’ve already hinted at, performing multi-threading in sales means more than just reaching out to more people. 

It’s the art of building influence, alignment, and trust across the broader buying group – so decisions are informed, objections are addressed early, and momentum isn’t tied to a single person.

The five core practices I’m about to share form the foundation of effective multi-threading.

They give you the why and how at a strategic level, drawn from my own experience as both a seller and an enabler, and shaped by the insights of top-performing sales practitioners.

Later, we will translate these practices into practical plays that you’ll be able to tailor to your specific context. 

Let’s dive in.

1. Map influence, not just hierarchy 

A neat org chart rarely reflects how decisions are really made.

True multi-threading starts with uncovering the people – named and unnamed – who shape the outcome.

Yes, you’ll map formal roles: 

• Economic buyers
• Technical leads
• End users
• Legal, procurement, IT, finance
• Executive sponsors and project owners

But the real advantage comes from creating a “political map”: 

• Who sways opinion behind closed doors?
• Who holds quiet veto power?
• Who’s everyone looking to for reassurance?

Go further and capture what each person values most: certainty, recognition, speed, and control.

A simple influence/engagement/motivation matrix keeps this visible and lets you adapt your approach (a basic example is offered below). 

Account mapping tools and LinkedIn can help, but remember that the insights from your champion are irreplaceable. 

To keep everyone moving in the same direction, make sure the next steps, owners, and timelines are visible in a shared mutual action plan or buyer hub. This way, all parties can see progress, dependencies, and priorities without relying on back-and-forth updates.

2. Expand engagement with permission and purpose 

Once you’ve mapped the right people, the next move is to widen your engagement with genuine care.

You should always start by partnering closely with your champion; they’re central to progress. 

But let’s be honest, champions can only introduce you to the contacts they know. To build a complete, effective buying team, you’ll need to reach a little further – without eroding trust.

How to do it respectfully?

Treat introductions as a regular, value-driven part of the journey. Most sellers hesitate, worried about disrupting rapport. 

The best way to do this is to make stakeholder expansion a normal, value-driven step in the process. In my experience, asking “Is there anyone whose input might be missed here?” is never off-putting. It signals respect for the process and the diverse voices needed for consensus.

Permission-based outreach works because it frames your request as solving a problem, not creating one. Instead of dropping cold introductions into inboxes, ask questions like:

“Would it be helpful to involve the finance lead now so we can avoid approval delays later?” or

“I want to ensure legal has visibility on the timeline, who would be the right person to loop in?”

Whenever possible, connect new stakeholders through shared outcomes. If procurement and IT both care about speed, anchor your outreach in that common goal.

The aim isn’t to meet everyone in the organisation; it’s to involve the right people at the right time. That way, concerns are addressed early, blind spots are removed, and the buying group moves forward with clarity and confidence.

3. Strengthen personal relationships across the group 

Multi-threading only works when it’s personal. People support decisions made by those they trust – and trust is built one conversation at a time.

Before meeting someone new, ask your existing contacts for insights into their style, priorities, and communication preferences. This extra context helps you approach each interaction with empathy and relevance, rather than treating it like another box to tick.

Use names, not job titles – “Emma” sticks far better than “Head of Sales Ops.” After group calls, follow up with short, personalised one-to-ones via email, LinkedIn, or another channel they use often.

As top AE at Gong, Brian Lamanna often advises, the real relationship-building happens in those one-to-one moments between the big meetings.

Once you’ve built rapport, switch to warmer, more human touchpoints: LinkedIn voice notes, quick 15-minute virtual coffees, or informal “pulse checks.” Short and casual by design, these moments often surface concerns or opportunities you’ll never hear in a formal meeting.

Between calls, stay visible in ways that feel natural. Engage with stakeholders’ posts. Share a resource you know they’ll find useful. Celebrate a promotion, a big project win, or even a work anniversary.

These small acknowledgements tend to compound over time.

Keep track of them. A simple contact log – just names, key dates, and personal notes – ensures these details aren’t lost and can be referenced naturally later.

In the end, the goal is to create a network of genuine goodwill – one that keeps momentum going when priorities shift, objections arise, or champions move on. In complex sales, those human bonds are often the difference between progress and stall.

4. Keep everyone in the loop – with value

Consensus stalls when people are left out of the loop, or buried under noise.

You want to tailor updates to the person in front of you: 

• Executives: business outcomes, risks, strategic fit.
• Managers: progress against plan, KPIs, dependencies.
• End users: workflow impact, ease of adoption, support.
• Finance / Legal / Procurement: commercials, terms, compliance status.
• IT / Security: architecture, data handling, integrations, controls.

Avoid blanket emails. Make every message about them.

A good idea is to use a digital sales room or buyer hub as the single source of truth.

Keep next steps, owners, and timelines visible, alongside role-specific materials. 

Late-stage decision-makers can then drop in, see the state of play, and move things forward without chasing anyone.

5. Orchestrate your internal team with intent 

Multi-threading is as much an internal mindset as it is a customer-facing strategy.

Your organisation has to move in sync to match the complexity and pace of the buyer’s world.

Start with executive alignment. Early VP-to-VP or C-suite conversations clarify priorities, risk appetite, and budget guardrails. They also signal seriousness and shorten the path to yes.

Practice deliberate resource orchestration. Complex deals rarely move without the right people at the right moments. Bring in solution engineers, IT, legal, and customer success early enough to prevent last-minute surprises. Brief them well so they engage on outcomes, not just tasks.

Create role clarity and a single thread of ownership. Define who leads the deal, who owns product fit and demos, who handles commercials and contracts, and who prepares the onboarding path. When responsibilities are explicit, nothing slips between the cracks.

Keep a tight cadence. Short, regular deal huddles can help you align messaging, surface blockers, and adjust priorities quickly. Maintain one source of truth for notes, next steps, and dependencies, so the internal story matches what buyers hear.

Finally, plan for turbulence together. Run a short pre-mortem with your internal team to anticipate where the deal could stall on the buyer’s side; for example, procurement reviews, shifting priorities, or competing initiatives. Maintain a living risk register so everyone can see potential blockers and the agreed mitigations.

Map the buyer’s approval path clearly: who signs off, in what order, and by when. This way, you can mobilise the right internal people at the right time to keep things moving.

When your team moves as one, you mirror the buyer’s complexity with coordinated depth and agility – and you show, unmistakably, that you’re set up to make the project succeed.

Multi-threading plays & talk tracks

Now that we’ve covered the overarching practices that should guide your multi-threading efforts, it is time to get tactical. 

The plays below are intentionally short and flexible. You can lift them straight into your outreach or conversations without heavy rework.

Each one comes with a clear purpose, guidance on when it’s most effective, and a note on common pitfalls to avoid.

For ease of use, I’ve grouped the plays into categories.

Think of these as lenses that help you scan quickly for the type of move that fits your situation.

They’re not tied to a strict stage in the sales cycle, and you should think of them as a toolkit you can draw from whenever the situation calls for it – whether you’re an AE opening a new line of communication, a CSM trying to manage risk, or a solutions consultant working to build consensus.

Note: These plays are drawn from my own experience as both a seller and an enabler, observations of what has worked effectively in the field, and insights I’ve picked up from experts over the years.

Map the room, set the path 

Before you can influence a buying decision, you need to know who’s in the room – and who’s just outside of it. 

Mapping the decision network early gives you clarity on roles, responsibilities, and hidden influencers. It also sets the stage for structured execution: a mutual plan everyone can see, alignment on milestones, and a clear view of where risk might surface. 

These plays are about creating that shared map with your champion, surfacing the voices that matter, and setting a path the deal can follow without last-minute surprises.

1. Stakeholder co-mapping with your champion

Purpose: Build a complete, role-based view of the buying committee early, so you can plan targeted engagement and avoid late-stage surprises.

Primary stakeholder(s): Champion / primary sponsor.

Talk track:

“To make sure this project runs smoothly for you and avoids any last-minute roadblocks, it helps if I understand the wider picture of who might be involved.

That way, we can plan the right conversations together and save time later.

• Who owns budget approval for a decision like this?

• Who’s responsible for rollout and long-term adoption?

• Who might review for risk or compliance?

• And are there any decision-makers who won’t be directly involved but whose opinion carries weight internally?”

When to use it:  

• Early in the opportunity, when you and your champion are shaping the plan.
• Revisit mid-deal to check for changes as priorities shift or new functions get pulled in.

What to do (after talk track): Document the map in your CRM or any other relevant tool, and confirm it with the champion; create a light engagement plan per role.

Desired outcome: A shared, role-based map of the buying committee that both you and the champion agree on. 

Potential risks: Asking too soon or without context can make it feel like an interrogation. Use clear “why” framing: you’re helping them de-risk the project and avoid delays, not just filling CRM fields.

2. Mutual action plan kick-off 

Purpose: Establishes a single, visible source of truth from day one. Prevents confusion around tasks, timelines, and owners, while signalling that you’re a disciplined partner.

Primary stakeholder(s): Champion; project lead (sometimes an ops or PMO function).

Talk track:

“To keep us both moving smoothly, shall we stand up a simple plan with owners, dates, and milestones? Just a one-pager, visible to everyone, so nothing slips through the cracks.

We can keep it light, but it’ll help us stay aligned and reduce back-and-forth.”

When to use it: 

• Very early: after first serious discovery, once the problem and intent are clear
• Refresh at each milestone or major update

What to do (after talk track): 

• Draft a lean MAP with key milestones, owners, and dates (no more than 6–8 items). 
• Share in a collaborative doc/workspace (e.g., digital sales room) so all stakeholders can view
• Confirm update cadence (e.g., weekly check-ins, milestone-based updates)
• Refresh promptly when milestones shift or new dependencies appear

Desired outcome: One shared, lightweight plan that reduces “who’s doing what” churn, signals professionalism and rigour, and gives the champion a tool to align internally.

Potential risks: 

• Too much detail kills adoption. Keep it simple (milestones, owners, dates).
• If you don’t secure agreement on who owns what, the MAP becomes shelfware.
• In smaller orgs, pitch it as a clarity tool, not process overhead.

3. Silent stakeholder surfacing

Purpose: Anticipate hidden influencers or quiet blockers who may not appear on the org chart or project team but can heavily shape the outcome. Surfacing them early helps you plan engagement and avoid last-minute surprises.

Primary stakeholder(s):

• Champion / primary sponsor (guides you on who matters behind the scenes).
• Occasionally, a trusted peer of the champion who knows the organisational dynamics well.

Talk track:

“In your experience, who tends to weigh in on decisions like this, even if they’re not formally part of the process? Sometimes it’s someone who’s seen similar projects before or has strong views on risk, spend, or adoption.

It would help me understand their perspective early, so we don’t hit unexpected resistance later.”

When to use it:

• Early to mid-stage, ideally during stakeholder mapping with your champion.
• When you sense there may be an informal influence that hasn’t surfaced.
• After identifying formal decision-makers, but before consensus-building begins.

What to do (after talk track):

• Note names, roles, and influence level shared by your champion.
• Ask if/when it makes sense to involve them directly, or if your champion prefers to manage them initially.
• Prepare tailored enablement material (case study, FAQ, ROI snippet) for when they’re surfaced.

Desired outcome:

• You uncover potential silent influencers before they become late-stage blockers.
• Your champion feels you’re helping them de-risk the project, not just gathering political gossip.
• A plan emerges for how/when to address these voices.

Potential risks:

• If framed poorly, it may feel like you’re fishing for gossip or bypassing your champion’s control.
• Acting on this intel without alignment from your champion can backfire politically.

Expand the circle with consent 

Once you’ve built trust with your champion, the next step is carefully widening the circle. 

New voices can strengthen the case and smooth approvals, but only if you bring them in with care. 

These plays help you expand reach without undermining your champion – either by approaching peers directly with alignment, or by equipping your champion to make the introductions themselves. 

The goal is a broader base of support, built at the right pace, with your champion always in the driver’s seat.

1. Parallel outreach

Purpose: Extend the conversation to other functions or departments while protecting and reinforcing the trust of your champion.

Primary stakeholder(s): Departmental peers of your champion (e.g., IT, Finance, Ops, Marketing), or adjacent influencers who can validate or strengthen the business case.

Talk track:

“We’re working with [Champion] on [Project]. I’ve put together a 3-slide view on potential impact to [Function]. If helpful, I’d be glad to walk you through it and fold your input into the plan.”

(Alternative framing if you want to emphasise alignment with champion)

“[Champion] and I have been mapping the impact of this project, and your perspective on [Function] would be invaluable.

I pulled together a short summary, would you be open to reviewing it with me so we can make sure your priorities are reflected?”

When to use it:

• Mid-stage, once you’ve built trust with your champion.
• When expanding to other departments whose input will strengthen the case or smooth approvals.
• When you want to validate assumptions about functional impact before finalising the business case.

What to do (after talk track): Share the summary deck, incorporate stakeholder feedback, and loop back with your champion to show how it supports their plan.

Desired outcome: Secure input and buy-in from additional functions, while signalling to your champion that you’re strengthening their internal position, not undermining it.

Potential risks: 

• Could be seen as going around your champion if you don’t have their consent.
• If framed poorly, may make other stakeholders feel like an afterthought rather than a valued voice.
• Sending too much material upfront can overwhelm; keep it lightweight and tailored.

2. Champion-mediated expansion

Purpose: Leverage your champion’s credibility and relationships to introduce additional stakeholders in a way that feels natural, relevant, and non-threatening. This expands influence while keeping your champion in control.

Primary stakeholder(s): 

• Your champion (initiates the intro, retains ownership).
• Secondary: the adjacent role you want to bring in (Finance, IT, Security, Procurement, etc.).

Talk track:

“Since you mentioned [priority] is the top focus for this initiative, I think it could help to bring in [Role]. In similar projects, [Role] has often raised valuable points around [topic], and it might help to surface those early.

Would you be open to inviting them for a quick sync so we can make sure we’re addressing this properly and avoiding delays down the line?”

When to use it:  

• Early to mid-stage, once a clear problem and initial champion are established.
• When the conversation begins to extend beyond one department or functional perspective.
• As soon as you anticipate a potential blocker or approver who should be in the loop.

What to do (after talk track): Share the one-pager, then set a short follow-up call to walk through it together. Update your account map to reflect the new ownership and re-confirm next milestones.

Desired outcome: 

• Champion feels empowered, not bypassed.
• New stakeholder enters the conversation with a clear context and purpose.
• You strengthen the coalition early without slowing the process.

Potential risks: 

• Overloading your champion with too many intro requests in quick succession.
• Asking without a clear “why,” which can make it feel like busywork.
• Inviting new stakeholders before your champion is confident in the solution (can create resistance).

Keep alignment tight across the group

As more voices join, clarity often slips. Small misalignments compound into big delays if they’re not caught early. 

This set of plays helps you keep everyone on the same page without drowning them in detail. 

The aim is simple: create shared visibility, surface differences before they harden, and make sure your champion has the tools to drive a consistent story internally.

1. TL;DR recap for wider alignment

Purpose: Ensure clarity and keep stakeholders (including those who weren’t in the room) aligned without overwhelming them with lengthy recordings or detailed notes.

Primary stakeholder(s):

• Your champion (validates accuracy).
• Secondary stakeholders who didn’t attend but need awareness (executives, peers, adjacent functions).

Talk track:

“Here’s a three-line summary of our last discussion – decisions, risks, and next steps.

Could you confirm this reflects your view?

Once you’re happy with it, I can share the full recap with the rest of the team to keep everyone aligned.”

When to use it:

• After key meetings where multiple stakeholders are involved, but not all decision-makers could attend.
• Any stage where clarity across functions is important and misalignment could slow progress.

What to do (after talk track):

• Send the TL;DR to your champion first, validating accuracy.
• Once approved, circulate to relevant stakeholders who weren’t in the meeting but need visibility.
• Use the approved TL;DR as the opener when you send the longer recording/notes.

Desired outcome:

• Everyone, including non-attendees, has a clear and consistent view of progress.
• Reduces risk of misalignment or competing narratives.
• Signals professionalism and helps new stakeholders get up to speed quickly.

Potential risks:

• Getting facts wrong erodes credibility fast. Always double-check with champion before sharing broadly.
• Over-summarising and leaving out a critical nuance.
• Sending too long of a recap, which defeats the “TL;DR” purpose.

2. Visible progress check-in

Purpose: Show the buyer a simple visual of how far the project has come (decisions made, stakeholders engaged, next steps), and invite them to confirm or expand the group. It builds shared ownership without looking like you’re exposing gaps.

Primary stakeholder(s):

• Champion (validates and decides who else should see it).
• Secondary: functional leaders already engaged (to confirm progress and alignment).
• Potential new stakeholders (surfaced via champion’s input).

Talk track:

“To keep things clear, I put together a quick visual of where we are – what’s been decided, who’s involved, and the steps left.

Would it be useful to share this with your team, so everyone’s aligned and we can spot if anyone else should be looped in?”

When to use it:

• Mid-to-late stage, once momentum is established.
• Ahead of multi-stakeholder meetings or before final consensus.

What to do (after talk track):

• Share a concise slide or visual with decisions, roles, and next steps.
• Ask your champion which additional stakeholders should see it.
• Capture feedback and fold it into the mutual action plan.

Desired outcome:

• Champion feels you’re driving clarity and alignment.
• Broader group sees tangible progress and feels involved.
• You reduce risk of late surprises by surfacing missing voices early.

Potential risks:

• If too detailed, can overwhelm or trigger “why wasn’t I looped in earlier?” reactions.
• If progress is weak, visibility can backfire; use only when you have a solid story to show.

3. Post-meeting triangulation

Purpose: Maintain consistency across stakeholders by gently reconciling different perspectives after separate conversations. It prevents misalignment from derailing progress later.

Primary stakeholder(s):

• Champion or project lead (keeps them in the loop).
• Adjacent decision-makers or influencers you’ve met separately (Finance, IT, Legal, Ops, etc.).

Talk track:

“I’ve summarised the key points from my conversations with both you and [Other Stakeholder]. There’s strong alignment on [X, Y], and I noticed some different views on [Z].

Would you be open to a short sync so we can make sure everyone’s on the same page before we move forward?”

When to use it:

• Mid to late stage, after meeting multiple stakeholders separately.
• When preparing for consensus meetings or business case finalisation.
• If you sense differing perspectives that could create friction later.

What to do (after talk track):

• Share a neutral recap highlighting alignment first, then gently flagging differences.
• Propose a joint discussion (with you as facilitator) to close the gap.
• Always keep tone constructive: “resolve for progress” not “expose conflict.”

Desired outcome:

• Stakeholders appreciate your role in keeping things coordinated.
• Small differences are addressed early, preventing bigger clashes later.
• Champion sees you as a trusted facilitator, not a source of friction.

Potential risks:

• Poor framing may make differences sound like conflict rather than normal variance.
• If you overstep, you may look like you’re managing politics instead of enabling decisions.

4. Co-authoring a shared point of view

Purpose: Create a unified, stakeholder-approved message that prevents misalignment when the project is discussed internally.

Primary stakeholder(s):

• Champion / primary sponsor (leads the narrative).
• Secondary: functional peers (e.g., Finance, IT, Legal, Ops) who will later receive or validate the narrative.

Talk track:

“To make sure your priorities are represented clearly, could we draft a short summary together – 2–3 sentences that reflect how your team sees this initiative and the value it brings?

That way, when it’s shared with finance, IT, or other groups, it’s your voice leading the story, not mine.”

When to use it:

• Mid-stage, when the project is likely to circulate beyond the champion’s team.
• Before steering committees, review boards, or budget discussions.

What to do (after talk track):

• Draft a concise summary reflecting your champion’s words.
• Share it back for approval and confirm alignment.
• Offer to adapt it for other audiences (finance, IT, execs) while keeping their core narrative intact.

Desired outcome:

• A consistent narrative that champions can share internally with confidence.
• Other stakeholders see the initiative framed in their peers’ voice, not “sales-speak.”

Potential risks:

• If the language feels too vendor-driven, stakeholders may distrust it.
• If co-creation drags on, it can feel like extra work for the champion; keep it light and simple.

5. Pre-wiring the committee

Purpose: Align pivotal voices before the formal review, so the meeting can decide instead of debate.

Primary stakeholder(s): Champion / sponsor; 2–3 key influencers or decision-shapers (budget owner, IT, finance, operations lead, etc.).

Talk track (to champion):

“Ahead of the steering review, I’d like to make sure the discussion lands smoothly.

Could we share a short 2-slide pre-read and check in quickly with [Stakeholder A / B]?

That way, any questions or risks surface early, and the big meeting can focus on decisions instead of first reactions.”

When to use it:

• Mid to late stage, roughly a week before the steering or final review.
• Especially when multiple functions will be in the room and alignment risk is high.

What to do (after talk track):

• Draft a tight 1–2 slide pre-read (e.g., Slide 1: Decision at hand + 2–3 bullets on value delivered/expected. Slide 2: Top risks with owners + 1 clear proposed next step). 
• Send to the champion for approval, then circulate selectively.
• Hold short 1:1s with pivotal voices; capture red flags or objections.
• Adjust the deck or narrative before the main review.

Desired outcome:

• Committee enters the room with context and fewer surprises.
• Meeting energy is in deciding, not debating.

Potential risks:

• Over-circulating can trigger counter-lobbying or stall momentum.
• Keep the pre-wire circle intentionally small and endorsed by the champion.

6. Champion enablement pack

Purpose: Arm your champion with ready-to-use materials to build internal alignment, while keeping the message authentic and in their voice.

Primary stakeholder(s): Champion.

Talk track:

“I’ve pulled together a short kit you can adapt – a 2-slide value summary, a 90-second Loom, an FAQ, and a draft email.

Take, edit, or ignore as you wish; it’s just to make it easier for you to share internally.”

When to use it: Mid-stage, just before the champion needs to loop in other functions.

What to do (after talk track): Deliver the pack in one place; tailor slides/emails for each persona; keep total consumption < 5 minutes.

Desired outcome: Champion drives a consistent narrative inside their org without over-relying on you.

Potential risks: Too much “vendor-speak” erodes trust; mirror their language, not your marketing deck.

De-risk approvals early

Often, deals don’t stall because the value isn’t there, but because approvals get messy. Budget owners, reviewers, or new stakeholders often enter late, and unresolved risks can derail momentum.

This set of plays helps you surface friction points early, align on success before criteria diverge, and involve the right voices at the right time. 

The goal is to make approvals a formality, not a firefight.

1. Risk reset when a champion leaves

Purpose: Stabilise the opportunity after the departure of your main contact by quickly re-establishing clarity and credibility with their replacement. The goal is to preserve momentum, reassure the new stakeholder, and avoid the deal stalling or restarting from scratch.

Primary stakeholder(s): 

• The new contact taking over responsibility.
• Secondary: your champion’s manager or peer who can validate continuity.

Talk track:

“I understand you’ve stepped in to support [Project].

To make this transition easier, I pulled together a one-page summary of where things stand, including agreed goals, success metrics, and any open risks.

My aim is to save you time and show you exactly what’s been discussed so far.

From your perspective, are there any adjustments or priorities you’d like me to reflect?”

When to use it: 

• Immediately after your champion or main contact leaves their role.
• When organisational change creates uncertainty about ownership, priorities, or next steps.
• At any stage of the deal, since turnover can happen early, mid, or even late cycle.

What to do (after talk track): Share the one-pager, then set a short follow-up call to walk through it together. Update your account map to reflect the new ownership and re-confirm next milestones.

Desired outcome: 

• The new stakeholder feels supported rather than burdened.
• You secure alignment on what (if anything) has changed in goals or priorities.
• You avoid the need to restart the entire evaluation process.

Potential risks: 

• Overloading the new contact with too much detail too quickly.
• Assuming continuity instead of explicitly confirming it; what mattered to the old champion may not matter to the new one.
• Failing to adjust tone: what worked with the former champion might not land with their replacement.

2. Co-owned risk mitigation 

Purpose: Bring potential risks into the open early enough to address them, while positioning yourself as a partner in solving them.

Primary stakeholder(s):

• Champion and project sponsor.
• Occasionally a functional owner (IT, Finance, Legal) if risk sits in their lane.

Talk track:

“To make sure this initiative doesn’t lose momentum, it helps to get risks on the table now rather than later. From your side, what feels like the biggest factor that could slow things down or block it altogether?

I can share a couple of ways we’ve seen others handle similar challenges, and then we can agree together on the best approach, including who should own which part so nothing slips through the cracks.”

When to use it?

• Mid-to-late stage, once you have trust and a clear value case.
• Ahead of approvals, procurement, or exec review (common choke points).

What to do (after talk track):

• Listen actively and note risks in the buyer’s own words.
• Offer 1–2 proven mitigation strategies that have worked in similar deals.
• Co-assign ownership: clarify what you will take on (e.g., revised materials, security answers) vs. what they will own (e.g., securing budget sign-off).
• Summarise the agreement in writing as part of your mutual action plan.

Desired outcome:

• Risks surface early while you still have influence.
• Buyer feels supported and sees you as a partner in problem-solving.
• Clear ownership is established, reducing the chance of last-minute surprises.

Potential risks:

• Don’t open a risk discussion unless you’re prepared with at least one viable mitigation option; otherwise, you may amplify concerns without resolving them.
• Be selective with timing: too early and it might introduce objections that would never have been raised, too late and you lose the chance to influence resolution.
• Being vague about ownership can leave risks unresolved. 

3. Success criteria alignment 

Purpose: Bring stakeholders with differing priorities into one conversation to co-define shared metrics of success. It prevents conflicting definitions from derailing approval later.

Primary stakeholder(s):

• Champion (who benefits from having a unified story).
• Key decision-makers with diverging criteria (e.g., Finance vs. Ops, IT vs. Sales, Risk vs. Growth).

Talk track:

“I’d like to host a short working session with you and [Other Stakeholder] to align on a single definition of success.

Right now, I hear [A] emphasising [metric X] and [B] prioritising [metric Y].

If we can land on one or two metrics you both back, it’ll make the decision faster and smoother.

Would you be open to that?”

When to use it:

• Mid to late stage, when decision criteria start diverging.
• Before final approval cycles, to avoid conflicting expectations.

What to do (after talk track):

• Facilitate a structured session (timeboxed, ~30 min).
• Start with areas of overlap, then move to bridging gaps.
• Capture and circulate the agreed definition of success.

Desired outcome:

• Stakeholders converge on a shared success metric.
• Champion gains a stronger position internally.
• Evaluation becomes smoother, with less back-and-forth.

Potential risks:

• If facilitation is poor, positions may harden.
• If you push too strongly, you risk being seen as favouring one side.

4. Budget owner bridge

Purpose: Involve budget authority at the right time, with a focus on strategic value and ROI rather than just cost.

Primary stakeholder(s):

• Champion / sponsor (gatekeeper).
• Budget owner (CFO, VP, or equivalent).

Talk track:

“Since [Strategic Goal] is the focus here, I imagine [Budget Owner] will want visibility before long.

Would you be open to bringing them in now, so we can frame this around outcomes and ROI instead of it being just a line item later?”

When to use it:

• Mid-stage, after value case is defined with your champion.
• Before budget discussions risk becoming a blocker late in cycle.

What to do (after talk track):

• Secure explicit consent from your champion before any outreach.
• Position the meeting as a value/outcomes review, not a pricing discussion.
• Keep it short and executive-friendly (headline goals, ROI, risks).

Desired outcome:

• Budget owner is engaged early, seeing project as aligned to strategy.
• Champion feels supported, not undermined.
• Deal avoids late-stage finance pushback.

Potential risks:

• Moving too early can look like bypassing.
• Over-indexing on cost savings (if that’s not realistic) can trap you later.
• Without the champion’s consent, trust can be eroded.

5. Multi-person review nudge

Purpose: Ensure functional reviewers (IT, Legal, Finance, etc.) weigh in early, so approvals don’t stall later. It positions you as proactive in helping the buyer avoid last-minute bottlenecks.

Primary stakeholder(s):

• Champion / project sponsor.
• Secondary: functional reviewers (IT, Finance, Legal, Procurement).

Talk track:

“To keep things smooth and avoid late surprises, I put together a one-pager covering ROI, integration, and compliance.

From your side, who would make the most sense to review this now – Finance, IT, or Legal?

That way, we can surface any questions early and make sure you don’t get slowed down during approvals.”

When to use it:

• Mid-stage, once the business case is defined and functional input will soon be required.
• As you prepare to advance toward approvals or formal procurement.

What to do (after talk track):

• Send a short, role-specific summary (max 1–2 pages) tailored to each function’s lens.
• Offer to join the review call, or let the champion share on their own if that’s easier.
• Capture any concerns raised and add them into the mutual action plan with owners/dates.

Desired outcome:

• Key reviewers are engaged before final sign-off stages.
• Issues (integration, compliance, budget format) are addressed while momentum is high.
• Champion sees you as making their life easier by preventing delays.

Potential risks:

• Involving too many reviewers too early can create noise and slow progress.
• If the summary is too detailed, it can overwhelm; keep it short and role-specific.
• If you push without context, the champion may feel you’re complicating their process.

Secure executive air cover

Even the strongest champion can only take you so far. At some point, budget owners and senior leaders will weigh in, and if they’re caught off guard, deals can stall or even collapse. 

These plays help you create the right level of executive awareness and alignment without undermining your champion. 

Whether it’s a light-touch visibility email, a sponsor-to-sponsor sync, or a concise nudge to the right exec, the aim is to build top-down support that accelerates approvals and protects momentum.

1. Executive nudge

Purpose: Open a direct, time-efficient line to senior leaders once there’s already momentum at the working level. This isn’t for starting a deal; it’s for when progress is happening but senior oversight, budget, or approval could become a bottleneck.

Primary stakeholder(s):

• Budget owner (CFO, COO, etc.).
• Senior functional leader (CIO, CHRO, CRO, etc.
• Executive sponsor who will ultimately sign off.

Background / context: 

By this point, you should already have:

• A champion or manager-level contact engaged.
• A clear business problem and value case mapped out.
• Signs that executive alignment or approval will soon be required.

This play is about giving senior leaders an easy way to engage without undermining your champion – a concise “opt-in or redirect” moment.

Talk track:

“We’ve been working with [Champion] on [Project], and early discussions show [Problem] is costing roughly [X].

We’ve outlined a plan that could deliver [Impact] within [Timeline].

I’d love to give you a concise view so you can confirm we’re aligned at the executive level, or point me to the right person to make sure this lands where it needs to.”

When to use it: 

• Mid to late stage, after the value case is validated with your champion.
• When you anticipate executive approval will be a next step.
• When deals are stuck in sign-off cycles or committee reviews.

What to do (after talk track): If exec opts in, schedule a short alignment call with them and your champion present. If redirected, update your map and reframe your champion’s strategy with the correct exec.

Desired outcome: 

• The executive is aware, engaged, and possibly advocates for the project.
• If not relevant, you’re redirected quickly to the right decision-maker.
• Champion retains credibility, since you’re showing alignment rather than bypassing.

Potential risks: 

• Reaching out before enough groundwork is laid can irritate your champion.
• Too much detail can overwhelm an exec; keep it short, high-level, and business-focused.

2. Executive sponsor match 

Purpose: Pair your exec with theirs to align intent, unblock risk, and add weight.

Primary stakeholder(s): 

• Your champion or primary contact.
• Your executive leadership team sponsor.
• Their budget owner / senior exec.

Talk track (to champion):

“To keep this aligned at your level, would it make sense to set up a short sponsor-to-sponsor conversation?

That way, your [CRO/CFO/etc.] and our [Exec Title] can align on the strategic goal, surface any risks early, and confirm the path to decision.

We’ll keep it focused and make sure it supports what you’re driving.”

When to use it:

• Mid-stage: once the business value is clear.
• Before approvals, when executive buy-in will accelerate the deal.

What to do (after talk track):

• Secure the champion’s blessing.
• Prep both execs with a one-pager (goal, value, risks, immediate ask).
• Debrief with your exec and feed back into the deal plan.

Desired outcome: Top-down air cover, faster escalation paths, and sponsorship that reinforces your champion’s work.

Potential risks: Too early can look like bypassing. Without the champion’s support, you risk undermining them.

3. Executive visibility email 

Purpose: Creates early awareness at the executive level, signalling progress and de-risking surprises.

Primary stakeholder(s):

• Champion / primary sponsor (for awareness and alignment).
• Your ELT sponsor (sender of the email).
• Their executive / EB (recipient).

Talk track (to champion):

“I’d like to make sure [Their Exec] is aware of the progress we’re making, so there are no surprises later.

Would you be comfortable if [Our Exec] sends a short note introducing themselves, just to share that we’re working together on [Project/Initiative]?”

When to use it:

• Early to mid-stage, once there’s initial traction but before approvals.
• Especially useful if you expect the EB will be involved later.

What to do (after talk track):

• Draft a short, respectful email for your exec to send.
• Position it as an FYI, not a meeting request. Example: “I wanted to briefly introduce myself and let you know we’re partnering with [Champion] on [Initiative]. Early signs are strong, and we’re excited about the potential outcomes. No action needed on your side, but I’d be happy to connect later if it’s helpful.”
• Share the draft with the champion before sending.

Desired outcome:

• The executive is lightly engaged and aware of the project.
• Smooths the path for deeper exec ↔ exec engagement later.

Potential risks:

• If framed as a meeting too soon, it may feel like a bypass.
• If the email is too “salesy,” it could erode trust; keep it brief and factual.

Prove value and shape evaluation

Even the best discovery and positioning won’t matter if the buyer’s evaluation drifts in the wrong direction. 

This set of plays helps you show proof early, shape how success is defined, and make sure pilots or comparisons lean toward your strengths. 

The goal is to create clarity and momentum – proving value in ways that feel collaborative, not pushy – so the evaluation works for both sides and avoids endless cycles of uncertainty.

1. Influencing the evaluation process 

Purpose: Position yourself as a trusted advisor in the buyer’s independent discovery process, reinforcing credibility while influencing evaluation criteria.

Primary stakeholder(s):

• Champion / primary evaluator (drives research).
• Secondary: procurement, risk/compliance, functional specialists who may initiate comparisons.

Talk track:

“I realise you may already be looking at peers or alternative approaches – that’s completely expected for a decision like this.

To make that process easier for you, I’d be glad to help: for example, connecting you with a peer reference, sharing evaluation checklists from other customers, or surfacing common blind spots we’ve seen teams run into.

That way, you’ll have a fuller view as you compare options.”

When to use it:

• Early to mid-stage, once discovery shows they’re validating more than one option.
• When you sense information is being gathered independently (through peers, analysts, or online research).
• Before procurement formalises an RFP or vendor scorecard.

What to do (after talk track):

• Offer 1–2 tangible resources: a customer reference, benchmark data, or criteria framework.
• Encourage the champion to share what matters most in their internal comparisons.
• Use the insights to subtly influence weighting (e.g., ROI vs. feature count).

Desired outcome:

• You’re seen as supportive, not defensive – enabling transparency.
• Buyer criteria tilt towards your strengths, while still respecting their process.
• Relationship strengthened by positioning yourself as a facilitator. 

Potential risks:

• Surfacing competition too early if the buyer hadn’t planned to explore it.
• If you offer support but can’t back it up (no references, weak benchmarks), you may lose credibility.
• Mishandling peer comparisons can create unnecessary scrutiny.

2. POC / pilot success contract

Purpose: Avoid “pilot purgatory” by locking in outcomes, owners, and exit criteria before kickoff.

Primary stakeholder(s): Champion; delivery/project owner; CS/Solution engineering leads.

Talk track:

“To make this pilot decisive, could we align on three things upfront – the success metrics, the data/resources needed, and the path forward?

For example: if we see [X outcome] by [Y date], then we move to [Z decision].

That way, the pilot drives clarity instead of drift.”

When to use it: Before any trial or pilot begins.

What to do (after talk track): Draft a simple one-pager covering scope, 2–3 success metrics, timeline, resourcing, and the decision gate. Share it for sign-off.

Desired outcome: A clear go/no-go decision tied to measurable outcomes, not opinions.

Potential risks: If metrics are vague or open-ended, the pilot can drag into endless extensions without commitment.

3. Land-and-expand intro

Purpose: Leverage early wins to naturally expand into other functions or departments, positioning your champion as the one sharing value across the organisation.

Primary stakeholder(s):

• Champion (initiates the intro, benefits from being seen as a value-spreader).
• New department leader / stakeholder (potential future user).

Talk track:

“Now that [Department] has achieved [Result/Outcome], similar teams often look to apply those learnings elsewhere.

In your view, is there another department that might benefit from this?

If so, I’d be glad to put together a tailored view so you can decide if it’s worth sharing with them.”

When to use it:

• Late-stage, once tangible outcomes or success stories exist.
• Post-sale, after you can point to clear proof of value.

What to do (after talk track):

• Provide the champion with a short, tailored proof-point deck they can forward internally.
• Make it easy for them to look good when introducing you (position it as them bringing value, not you asking for a favour).
• Frame the expansion as solving adjacent problems; it’s not about replicating the same pitch.

Desired outcome:

• Champion feels they are sharing success, not being asked to sell for you.
• New department engages with openness, seeing proof from peers.
• Expansion conversations start naturally, anchored in real outcomes.

Potential risks:

• Moving before real results are visible makes it look self-serving.
• If the champion feels like you’re offloading selling work to them, they may resist.
• Pushing too many expansion asks too quickly can dilute focus from the original project.

Enablement’s role in making multi-threading stick 

In my experience, the intent is rarely the problem with multithreading. 

Most reps know they should be doing it; the real challenge is execution.

Under deal pressure, they fall back on a friendly champion or chase the most responsive contact, and suddenly the opportunity is single-threaded again.

This is where I believe enablement can play a very important role. 

Whoever is responsible for enabling a better way of selling in the sales organisation should not just be pointing out the risk of relying on one person; instead, they should design the development, assets, systems, and habits that make multithreading the default. 

If this is executed appropriately, multi-threading can become a repeatable part of the sales process rather than a tactic only the most seasoned AEs can pull off.

Process and deal gates

If multithreading isn’t built into the sales process, it will always be optional – and optional means inconsistent (at best). 

Enablement can anchor multithreading by working with Ops and leadership to define what “good coverage” looks like at each stage. 

That might mean requiring two functions engaged before a deal moves to proposal, or a mutual action plan created before security review.

These expectations need to live in CRM workflows and opportunity reviews, not just in training slides. 

When reps know they’ll be asked, “Who else is missing from this deal?” rather than only, “What’s the next step?” it shifts the behaviour from ad hoc to standard operating procedure.

Skills and coaching

If you’ve read this far, you’ll have noticed that multithreading isn’t a single skill; it’s a bundle of them: mapping influence, expanding permission, balancing conversations across functions, and knowing when to bring new people in. 

Training needs to treat it that way.

Reps need practice in spotting who’s missing, deciding how to approach them, and making the ask with confidence. The closer the exercise gets to a real deal situation, the more useful it becomes.

Workshops where teams build live account maps together are a good start, surfacing blind spots and debating the best ways to fill them. 

But scenario-based exercises take this further.

You can, for example, put reps in front of a realistic situation: procurement has appeared late in the cycle with new requirements, or the champion has gone quiet while IT is suddenly active. 

Ask them to plan – and then roleplay – how they’d adapt, who they’d involve, and which talk tracks they’d use to regain balance. These kinds of drills force reps to connect theory with execution.

Roleplays can also be designed around practising the small but high-stakes moments: asking a champion for an introduction, tailoring a value pitch to a sceptical finance lead, or addressing concerns from security. 

Reps should walk away not only with strategies, but with the confidence that comes from saying the words out loud.

Obviously, once training has been initiated, coaching is what ensures all this continues to develop and solidify. 

Managers should consistently reinforce the behaviours that make multithreading stick. That means asking in every deal review, “Who’s not engaged yet?” or digging into whether veto-power personas have been touched. 

Coaching can also spotlight successful moves in real deals – like when a rep secured legal’s buy-in early – so the rest of the team can learn from them. 

And if managers don’t yet feel comfortable leading these conversations, enablement’s role is to coach the coaches first.

Buyer-facing assets

Even if a rep runs flawless meetings, most selling happens when they’re not in the room. As Nate Nasralla notes in one of his podcast episodes, “…Buying decisions rarely happen in sales calls; they happen in internal meetings. That’s why your assets need to sell when you can’t.”

Champions need simple, credible material to carry the story forward, and that’s also where enablement can be the difference-maker.

Enablers can liaise with marketing, sales leadership, and top sales reps to create a small set of high-utility assets: one-page briefs by persona, a crisp executive brief template, a business case template, a two-slide forwardable that outlines ROI, and so forth. 

Paired with talk tracks and proof points (e.g., customer references), these assets give champions the tools to bring others into the fold without diluting the message. The more reps see that these materials actually move deals forward, the more naturally multi-threading becomes part of their motion.

If you want to go deeper, I’ve put together a dedicated piece on buyer enablement assets that accelerate consensus, where I break down the most impactful content types for influencing deals. 

Alongside that, this guide on AI prompts for sales explores how AI can help reps generate business cases, executive briefs, and other assets – once you’ve built the right templates unique to your organisation.

Systems and signals

Enterprise deals can create chaos: conversations spread across Slack threads, calls, and hallway chats you’ll never hear. Left unmanaged, coverage gaps are invisible until it’s too late. 

Technology is how enablement can cut through that chaos.

The goal should be visibility. 

Things enablement could do include collaborating with Ops to configure CRM to capture role, function, and influence level for each contact, using alerts to flag single-threaded opportunities early; or layering in intelligence tools that show when a new stakeholder is engaging with content or who hasn’t been touched by stage three. 

Digital sales rooms can also take this a step further by centralising assets and updates, giving every stakeholder a direct way in, while letting reps see who’s actually leaning in, and act accordingly. 

Cross-functional orchestration

Finally, there’s the internal side. 

AEs alone can’t credibly engage every stakeholder in a complex enterprise deal. As I’ve already shared, multithreading requires deal squads: the rep plus SEs, CS, product, finance, legal, IT, sales leadership – whoever the buyer expects to see.

Enablement can’t run those squads directly, but it can make them far easier for reps to mobilise. 

The implementation of a central deal workspace – whether in the CRM or a digital sales room – can ensure account maps, notes, and key documents are visible to everyone involved. 

On top of that, enablement can provide job aids that flag common triggers for bringing in a specialist (e.g., procurement questions = loop in finance, security checklist = involve SEs).

Another overlooked lever is building awareness of what each function actually contributes in the context of a deal. When reps know what product, legal, or CS can bring to the table, they’re more confident about asking for support at the right time.

The outcome: reps stay in control of the orchestration, but they’re not improvising; they have the scaffolding to know who to involve, when, and why.

Are we truly multi-threading? The metrics that matter

It’s easy to talk about multithreading as a best practice; it’s harder to know if your team is actually doing it.

That’s where metrics come in. 

Of course, you don’t want to track everything under the sun, but monitor the few signals that tell you if deals are truly de-risked and moving towards consensus.

Here are the core metrics I recommend:

1. Stakeholder coverage: Average number of unique stakeholders engaged per qualified deal. Break down by role/department to ensure it’s not just more of the same.
2. Coverage balance: The percentage of deals with engagement across at least 3 functions (e.g., Finance, IT/Security, Operations). This avoids “false multithreading” where reps add three stakeholders from Sales but ignore other departments that hold veto power.
3. Time-to-first-multi-thread: Median time from opportunity creation to engaging a second persona. Faster spread signals healthier coverage.
4. Consensus milestone rate: The percentage of deals where key functions (e.g., Finance, Security, Legal) are engaged before the proposal stage. Late involvement = late stalls.
5. Outcome impact: Win rates and cycle lengths when deals are multi-threaded vs. single-threaded. A baseline that proves whether the practice actually shifts results.

​​Multi-threading is as much about timing and balance as it is about volume. These metrics help you cut through the noise and see whether reps are building real consensus or just collecting names.

For enablers, the job doesn’t end at measurement. The real test is: are you turning these signals into coaching, training, and content that help reps get better at it?

Conclusion

There’s little point in rehashing everything I’ve already covered in this playbook.

You know how difficult it is to sell into enterprise environments today.

You’ve seen how even the most “sureshot” deals can turn uncertain overnight.

And you’ve felt how much effort reps, managers, and cross-functional colleagues put into building safety nets around opportunities.

It is hard work.

But it’s also necessary work.

My hope is that this playbook gives you fresh angles on multi-threading – ideas you may not have had the time or headspace to experiment with yet.

And if you’re in enablement, working alongside sellers in these enterprise motions, remember: you have more levers to support multi-threading than it may seem. 

The path isn’t always easy, but the impact is undeniable.