Scenario · For the Rep + Sales Manager

You're single-threaded on a $400K deal.
Sales Nav shows the committee.
Now who can warmly intro any of them?

The enterprise deal review is Friday. Your manager asks the question every manager asks: who else are we talking to in the account? You list one name. The CIO. The buying committee has six. You open Sales Nav. Filter by company. See the names. Now who in your team can warmly introduce you to any of them? You Slack five colleagues. Three reply "I don't know them." Two don't reply at all.

Role: AE + Sales Manager + RevOps · Trigger: Deal review / single-thread flag · Window: Days, sometimes hours

The scenario, in real life.

It's Tuesday before Friday's deal review. The AE is working a $400K opportunity at HealthCo. She's been working with the CIO for 8 weeks. The deal is hers, but it's single-threaded. The CIO is supportive, but he's not the EB. The CFO is. The VP Procurement is. The CTO is on the committee too. The CISO will weigh in on security. The Head of Operations holds budget veto.

The manager asks: "Who else are we engaged with?" The AE says: "Just the CIO." The manager raises an eyebrow.

The AE opens Sales Nav. She filters HealthCo by title. Six names appear on the committee. She knows none of them.

"OK who do I know at HealthCo? Sales Nav shows TeamLink, none of our reps are 1st-degree connected. I post in the #revenue Slack channel: 'Anyone know the CFO at HealthCo? CISO? CTO?' I get three 'no, sorry,' two non-responses, and one 'I think Mike from Series B board knew their CTO at his last gig, maybe?' I DM Mike. Mike's traveling. By Friday's deal review, I still only have the CIO."

The manager asks why we're still single-threaded. The AE says she's working on it. The manager asks how long this has been the plan. The AE says since week 2. It's now week 9.

The buying committee at HealthCo took 8 weeks to NOT engage with. Not because the relationships didn't exist somewhere in the company's extended network, they did. But because finding them required serial Slack pings, manual cross-referencing, and a board member who happens to be on a plane.

What Sales Navigator does for this scenario.

Surfaces the committee. Then stops.

  • Buying committee filter. Filter HealthCo by title, seniority, function. You can see all 6 committee members on one screen.
  • TeamLink for first-degree connections. Shows which of your reps have direct LinkedIn ties to any committee member. Usually: none.
  • Profile data per stakeholder. Each committee member's role, history, posts. Useful for personalization.
  • InMail to each. You can DM each committee member individually. Six cold InMails. Reply rate: ~2%.

The list of people exists. The activation across them does not.

Where Sales Nav stops on this scenario.

1. TeamLink only sees your reps' LinkedIn graph.

Your team has a board with 9 members, 14 advisors, 200 employees, 30 portfolio company CEOs (if you have an investor on your cap table), and 80 alumni who've left in the last 3 years. None of those connector sources are in TeamLink. The CFO at HealthCo, who you can't find, might be one degree from your CRO's former colleague who's now your advisor. Sales Nav has no way to know.

2. Connection doesn't mean knows.

Even if a rep IS connected to a committee member on LinkedIn, that's a 30%-likely "knows them well enough to do an intro" relationship. Sales Nav has no way to score whether they've actually worked together, sat on a board together, closed a deal together. Connection = noise. Relationship = signal.

3. No prioritization across multiple paths.

If your network somehow surfaces 8 possible paths into HealthCo committee members, Sales Nav can't rank them. Which is the WARMEST? Which connector is most likely to say yes? Which has done you a favor recently? Sales Nav doesn't track any of it.

4. No memory across reps.

Sahil asked Mike (your board member) for an intro into HealthCo 4 months ago, for a different account. Mike said no, he was overwhelmed. The new AE has no idea. She'll ask Mike again. Mike will be annoyed. Connector fatigue is a real, unmeasured cost.

5. No drafted asks per committee member.

Six committee members, six different positionings (CFO cares about ROI, CTO cares about architecture, CISO about security posture, VP Ops about implementation). Six different forwardable emails the right connector should send. Sales Nav drafts none. The AE writes 6 manually, or doesn't multi-thread.

What about Actively, Clay, Gong? They still belong in the stack.

Each plays a role on the 70% of accounts without warm paths. None of them help with this enterprise multi-thread.

  • Actively, intelligent automated cadences to all 6 committee members. Lands at 1.8-2.5%. Useful when no warm path exists.
  • Clay, enrich all 6 with firmographic data. Useful. Doesn't tell you who from your network knows them.
  • Gong, surfaces buying signals from call summaries. Useful intelligence. Doesn't route the activation.
  • UserGems, alerts if any committee member moves. Useful future signal. Doesn't help the current account.

Boomerang's $15-20K spend for a 10-rep team activates the 30% of accounts where the warm path exists, lifting reply rates from 1.8% to 60-80% on those.

What activation looks like instead.

Boomerang has 4 connector sources, not 1. Each committee member gets a ranked warm path within minutes.

The moment the AE opens HealthCo, Boomerang has already mapped the committee against all four connector sources, reps, customers, board / investors / advisors, partners. For each committee member, Boomerang surfaces:

  • The 1-3 warmest paths in, ranked by relationship strength. Example: "CFO Lisa Park → Path 1: Carlos (your CRO) closed a deal with her at her previous company in 2021. Path 2: Reena (your board member) sat with her on the SaaStr Advisory Board 2023-2024. Path 3: Mike (your customer at TechCo) interviewed her for a CFO role last fall."
  • Why each path is warm, with the metadata behind it. Not "they're connected on LinkedIn", but "they closed a deal together," "they sat on a board together," "they met at this event three times."
  • The forwardable email per connector, pre-drafted with the right framing for that committee member's role and priorities.
  • Memory and connector fatigue tracking: "Mike was asked 4 months ago by Sahil for an intro to HealthCo and said no. Do not ask Mike again this quarter. Carlos is your best path."
  • A checklist for the connector. Carlos sees: "3 forwardable emails ready. Lisa Park at HealthCo. Approve all 3 with one click."

By Wednesday morning, the AE has 4 of 6 committee members in active warm-intro conversations. Friday's deal review goes differently.

Sales Nav showed the committee. Boomerang activated 4 of 6 paths in 48 hours, across connectors Sales Nav couldn't see.

What the numbers say.

  • 3-5× more multi-threaded accounts per AE compared to teams running Sales Nav alone.
  • 35-50% win rate on multi-threaded deals vs 15-25% on single-threaded deals (Forrester).
  • 20-30% larger deal sizes when multi-threading is operationalized, bigger committees mean bigger deals.

Multi-threading isn't a tactic. It's a coverage requirement. Sales Nav makes it serial and manual. Boomerang makes it parallel and automatic.

Run a multi-threading audit on your top 5 deals.

Tell us your top 5 open enterprise deals. We'll surface the warm paths Boomerang would have unlocked across the buying committee, for each.

Book a demo →