The MQL is dead. Nobody wants to say it out loud.

Marketing keeps scoring them. Ops keeps routing them. AEs keep marking them "no response" and moving on. Everyone knows the model is broken. Everyone keeps running it anyway. The Demand Gen Report's 2026 outbound benchmark found that 95% of cold B2B messages now get zero engagement — the MQL follow-up motion is producing statistical noise. Cold outbound didn't die; the buyer moved. By the time your MQL fires and your AE sends the first touch, the buyer has already decided who they trust — and Forrester's 2023 trust research is unambiguous about who that isn't: vendor salespeople sit at 29% trust, the lowest of any source in the buying process, while peers land at 90%+ and other customers at 85%. The rep quota data reflects the same collapse — Salesforce's State of Sales has average rep quota attainment falling from 44% to 28% year over year. The MQL-to-cold-follow-up motion isn't a hard funnel; it's a broken one.

Here's the uncomfortable truth: MQL scoring was designed for a world where one person made a purchase decision. That world is gone. In 2026, a $100K+ enterprise deal is decided by a room of 14 to 23 people, and the person who filled out your form is almost never the one who signs the contract.

Stop pretending MQLs work. This is the sales execution playbook for the world that actually exists — the one where Marketing hands you a lead, and you have 6-9 personas to cover, three exec transitions to survive, and a champion who might get promoted, quit, or lose their internal battle at any moment.

If you're a CRO, VP of Sales, or head of Revenue Operations, this is the parallel to what your CMO is reading. They're rebuilding demand gen around the buying group. You have to rebuild execution around the same reality — or the leads they source will keep dying in your funnel.


Why MQLs stopped working

The MQL model — Marketing Qualified Lead — was born in the mid-2000s. Eloqua, Marketo, and the first wave of marketing automation platforms all assumed the same thing: score the individual, hand them to sales when the score crosses a threshold, and Sales closes the deal.

That assumption held when the average B2B purchase involved three or four people, most of whom worked in the same building. It hasn't held for a decade.

The uncomfortable truth: the average enterprise buying committee for a $1M+ deal now includes 14 to 23 stakeholders, spread across 6-9 functions, often distributed across 3-5 geographies. Gartner's canonical B2B buying group research first put the number at 6-10 in 2017. By 2024, Forrester was documenting committees of 10-14 for mid-market deals. Attainment Labs' 2024-2026 revenue benchmark data pegged enterprise committees at 14-23 stakeholders — with 6-9 distinct functional personas that all need coverage before a deal closes.

An MQL score scores one of them. Usually the wrong one.

The person filling out your gated whitepaper form is a research analyst, a curious individual contributor, or a champion who has zero authority to sign a contract. Meanwhile, the person who will block the deal — the InfoSec director, the procurement lead, the divisional CFO — has never touched your website and never will.

SiriusDecisions (now part of Forrester) called this out as early as 2019: demand units, not individual leads, are the true unit of B2B purchase decision-making. The industry response was to publish white papers about "buying groups" and then continue scoring individuals.

Forrester's own follow-up research is damning: buying group–qualified accounts convert at 3-5x the rate of MQL-qualified individuals. Yet fewer than 20% of B2B revenue teams have actually rebuilt their qualification model around buying groups. The rest are running 2010's playbook against 2026's buyer.

There's a second shift that broke the MQL model, and most demand gen leaders are still in denial about it: buyer research has moved to AI chatbots — before the MQL fires. G2's 2026 Buyer Behavior Report found that 51% of B2B software buyers now start their vendor research inside an AI chatbot (ChatGPT, Claude, Perplexity, Gemini), overtaking Google as the #1 entry point for software discovery. By the time an individual crosses your MQL threshold, they've already asked an AI to list the top vendors, compared feature matrices, and formed a shortlist. Your MQL isn't a signal of nascent interest; it's a receipt for a decision that's already forming. And because the buying group is 14-23 people, each of those stakeholders is running the same AI-first research independently — before any single one of them fills out your form.

Everything you've been told about MQLs is wrong — or at least, dangerously incomplete. And the sales side of the house is where the damage compounds.


The buying group reality: 14-23 stakeholders, 6-9 personas, distributed authority

Nobody wants to say this, but the buying group isn't a metaphor. It's an operational fact that changes every downstream sales motion.

Here's what "buying group" actually means for an enterprise deal in 2026:

Committee size, by deal band (Attainment Labs 2024-2026, Forrester, Gartner): - $25K-$100K SMB deals: 4-7 stakeholders, 3-5 personas - $100K-$500K mid-market deals: 8-14 stakeholders, 5-7 personas - $500K-$1M+ enterprise deals: 14-23 stakeholders, 6-9 personas - $5M+ platform deals: 25-40 stakeholders, 8-12 personas

Persona coverage for a typical enterprise SaaS deal: 1. Economic buyer (usually a VP or C-level with budget) 2. Executive sponsor (higher up, blesses the direction) 3. Technical evaluator (Head of Eng, Head of Data, InfoSec) 4. End-user champion (the person who actually wants this) 5. End-user skeptic (the person who has to switch tools) 6. Procurement (owns the contract and negotiates terms) 7. Legal (owns MSA, DPA, security addendum) 8. Finance (owns the business case) 9. Adjacent-team stakeholder (integrations, workflows they depend on)

Miss any one of these and the deal stalls. Miss two and it dies.

Authority is distributed. There is no single "decision maker" for enterprise software anymore. There is a network of people, any one of whom can say no. The CRO who thinks the champion "will sell internally" is watching a coin flip. Champions win the internal sale about 30% of the time when unsupported by AE-driven multithreading. They win about 70% of the time when the AE has directly built relationships with 4+ other stakeholders — the Armis case study (below) puts the number closer to 40-55% depending on deal complexity.

Research is distributed too — and AI-mediated. Each of the 14-23 stakeholders is now doing their own vendor research inside an AI chatbot before your AE ever reaches them. The CFO asks ChatGPT for total-cost-of-ownership comparisons. InfoSec asks Claude for a SOC 2 posture breakdown across vendors. The end-user champion asks Perplexity which tool their peer companies actually use. They arrive at the buying-group table with pre-formed opinions your Marketing team never influenced and your AE never saw coming. Scoring an individual MQL misses this entirely — the "hand-raiser" is one voice in a room where every other voice has already been shaped by an AI answer engine.

Timelines have stretched. Gartner and Bain both document average enterprise sales cycles growing 22-38% between 2022 and 2025. Buying groups are the reason. More stakeholders = more meetings = more delays = more chances for a champion to leave or a budget to freeze.

And the buying group itself is now at war with itself. Gartner's 2025 buying-group research found that 74% of B2B buying groups experience "unhealthy conflict" inside the committee — competing priorities, unresolved requirements, functional-line disagreements about scope. Three-quarters of the rooms your AE is trying to close are actively disagreeing internally. A cold sequence to a single champion does not resolve that conflict; a multithreaded, warm-path-covered buying-group motion does.

An AE working an enterprise deal in 2026 isn't selling a product. They're project-managing a 12-person cross-functional consensus build, timed against corporate change, budget cycles, and personnel churn.

Now go re-read your MQL definition and tell me it's still fit for purpose.


The 5-step transition from MQL nurture to buying group activation

Stop pretending MQLs work. Here's what actually needs to change in your sales execution model, step by step.

Step 1: Redefine the qualified unit as the account, not the individual

The first change is a definitional one. An "MQL" is a person. A "qualified account" is a set of people plus a set of signals. Your CRM should stop routing individual leads to AEs and start routing accounts with buying group activity to AEs.

Practically: when three people from Acme Corp visit your pricing page in the same week, that's a qualified account — even if no single person crossed the MQL threshold. When a signal fires on Acme (Series B raise, exec transition, competitive displacement rumor), that's a qualified account.

The routing rule is: signal + account + fit → route to AE. Not: score + person → route to SDR.

Step 2: Map the buying group before you touch the account

Before an AE spends a single hour on outreach, they need to know who they're selling to — all 14-23 of them.

The mapping should include: - The 6-9 personas by function - Named individuals in each persona slot (from LinkedIn, ZoomInfo, or your enrichment stack) - Existing relationships between your team and any of those individuals (via relationship intelligence or a shared connector graph) - Prior touch history from Marketing (which of these 14-23 have engaged?) - Political intel: reporting lines, likely champions, likely blockers

This is a 45-minute exercise per account. It replaces the 45 minutes an SDR would have spent qualifying an MQL. The ROI difference is 10x — because you're now working from a complete map, not a single hand-raiser.

Step 3: Cover the buying group with warm paths, not cold sequences

Here's where the model really breaks from the MQL era.

Commsor's 2026 State of B2B Outbound report clocked cold email reply rates at 1-3% and cold call connect rates at 4-8% — down from 8-12% and 15-18% respectively in 2020. Cold outbound isn't dead, but it's a very expensive way to cover a 14-person buying group. You'd need to send 400-600 cold touches to get 4-6 replies.

Warm paths — introductions from mutual connections, past customers, investors, board members, professional network — convert at 30-50x the rate of cold. Norwest Venture Partners' 2025 GTM benchmark survey named warm referrals the #1 outbound tactic for the third year running, with 65% of top-performing enterprise sales teams citing it as their highest-yield channel.

The transition: for every persona slot in the buying group, ask what warm paths do we already have? Team, customers, capital partners, professional network. Only use cold when no warm path exists — and even then, name-drop a mutual context.

Boomerang's 4-source connector graph model — team + customers + capital partners + professional partners — is the mapping. When applied to a buying group, it turns a 14-person cold-outreach nightmare into a 4-5 warm-intro operation with 8-10 name-dropped cold fallbacks.

Step 4: Multithread on a signal cadence, not a rep cadence

The old cadence was: SDR emails on day 1, day 3, day 7. Rep-driven. Time-based.

The new cadence is signal-driven and buying-group-wide. Each stakeholder gets a personalized touch when a signal relevant to them fires: - The CFO gets outreach when your case study on cost-per-outcome ships - The Head of Data gets outreach when a competitor's outage hits Twitter - The InfoSec director gets outreach when you publish your SOC 2 Type II - The champion gets outreach when their manager (economic buyer) gets promoted

Signals aren't just about the company. They're about the individual — job changes, executive transitions, content engagement, warm-intro availability, competitor exits. Multithread against the signals, not against a rigid touch cadence.

MarketBetter's 2026 GTM benchmark quantified the delta: signal-driven outbound converts 3× faster than cold outbound to comparable persona targets, with meeting-hold rates roughly double. Signals are the replacement fuel for the MQL — they cut through the noise the buyer's AI-first research created, because a signal-timed touch shows up when the buyer's context has actually shifted, not when your marketing automation's drip logic decides to fire.

Step 5: Measure buying group coverage, not lead volume

The KPI shift is the hardest cultural change. Marketing measures MQLs. CROs need to measure: - Buying group coverage % — of the 6-9 personas required, how many have you touched? - Multithreading depth — how many stakeholders per active opportunity have had a personalized touch in the last 21 days? - Meetings per stakeholder — are you meeting with 1 person 3 times, or 3 people once each? (The second wins deals.) - Warm path utilization % — of your buying group touches, what % went through a warm path?

More on the metrics in a later section. But: if your dashboard still leads with MQL volume, you're managing to the wrong number.


The 5 Boomerang plays, adapted for buying group coverage

Boomerang's five warm-intro plays were designed for account-based, relationship-led selling. They map cleanly onto buying group execution.

Play 1 — Discover Paths (across the buying group). Before your AE touches Acme Corp, run the mapping: for each of the 6-9 persona slots, what warm paths exist across your team, customers, capital partners, and professional network? A modern connector graph does this in seconds. The output isn't one warm path — it's a coverage map: 4 personas warm-reachable, 3 name-drop reachable, 2 requiring cold with a signal wedge.

Play 2 — Name Drop (across the committee). Even when you can't get a direct intro to the Head of InfoSec, you may have a strong relationship with the CTO who runs him. Name-drop the CTO in the InfoSec outreach: "I've been working with [CTO name] on the platform side and wanted to loop you in on the security-posture questions before we go further." This is the second-highest converting outbound motion after warm intro — and it's underused because most teams don't systematically identify shared context.

Play 3 — Warm Intro Request (the centerpiece). For each signal that fires on the account — the CFO transition, the funding round, the competitive event — identify the strongest warm path across the graph, draft the ask in the connector's voice, and send at the moment the signal is fresh. The connector approves with one click. This is the play that lands executive-level meetings your BDR team can't. Multiply it across a 14-person buying group and you go from single-threaded to multithreaded in a week.

Play 4 — Customer Network Activation. Your closed-won customers are your highest-leverage source of buying group intelligence and warm paths. A CFO who just implemented your platform knows the CFOs at three peer companies. A Head of Data who champions you knows the Heads of Data at their industry cohort. Systematic CNA — asking closed customers for three specific peer introductions at the 30-60 day post-close mark — produces the highest-yielding warm outbound pipeline in most enterprise SaaS shops. Boomerang's Customer Network Activation playbook formalizes the ask, the cadence, and the drafted intro requests.

Play 5 — Executive Network Activation. Your CEO, CFO, board, and investors have relationships with buyers at your target accounts that your AE team will never independently build. Monthly, surface your top 15-20 target accounts to the exec team, identify which of them each exec can warm-introduce to, and draft the intro requests. Fifteen minutes of exec time per month, produced correctly, generates seven-figure ARR pipeline. Missing this play is one of the top three failure modes in enterprise sales execution — see below.

The Armis case study (a Boomerang customer running enterprise cybersecurity deals) documented multi-threading rates rising from ~15% baseline to 40-55% across active opportunities within 90 days of adopting the graph-driven Play 3 and Play 5 motion. Deals with multi-thread coverage above 40% closed 2.3x more often than deals below 20%.

That's the difference between hoping the champion sells internally and building the coverage that makes the sale inevitable.


Manual vs Boomerang buying group execution

Most enterprise sales teams are running buying group execution manually today — badly, and at high cost. Here's what changes when the motion runs through a purpose-built engine.

The manual approach The Boomerang engine
AE maps the buying group in a Google doc; loses it in three weeks Buying group persisted per account with persona coverage tracked in real time
Warm paths surface only when the AE happens to remember a mutual connection Every rep's + past customer's + investor's network auto-mapped into a firm-wide graph; warm paths ranked per stakeholder in seconds
SDR runs the same 3-touch cadence at every stakeholder Signal fires → intro request drafted → sent to the right connector for the right stakeholder same day, in the connector's voice
Multithreading = "please forward this to your team" 4-6 personalized touches per persona, warm-path routed, with drafted context per stakeholder
Executive intros happen when the CRO remembers to ask on Slack Monthly exec ask cycle: top accounts surfaced, drafted intros pre-approved, one-click send
Customer referral asks happen when Sales feels like it Systematic 30-60 day CNA on every closed-won; three named intros per customer
Loop closes when? Never. Rep forgot to update SFDC Every intro, meeting, and next step logged; connector cadence limits enforced; thank-you sent automatically when meeting books
CRO reports MQL volume up-and-to-the-right CRO reports buying group coverage %, multithreading depth, warm path utilization

That's not a small delta. That's the difference between running the MQL-era playbook badly and running the buying-group-era playbook at scale.


The metrics that matter (and the ones to retire)

Nobody wants to say this, but half the metrics on the average sales dashboard are lies of omission.

Retire these: - MQL volume — measures form fills, not committed accounts - MQL-to-SQL conversion — meaningless when the person converted is a research analyst - Cold email open rate — inbox providers now inflate this to near-100% via image proxies - Rep activity (calls/emails per day) — measures motion, not coverage

Adopt these:

1. Buying group coverage % — Of the 6-9 required personas for an active opportunity, what percentage have had a meaningful (personalized, response-generating) touch in the last 21 days? Target: 70%+ on any deal above your ACV median.

2. Multithreading depth — Average number of stakeholders per active opp with at least one personalized touch in the trailing 30 days. Target: 4+ for mid-market, 6+ for enterprise.

3. Meetings per stakeholder — Total meetings booked on an account, divided by number of unique stakeholders those meetings included. Target: <1.5. If you're above 2.0, you're re-selling the same champion instead of expanding coverage.

4. Warm path utilization % — Of all outbound touches to buying group stakeholders, what percentage went through a warm path (intro, name-drop, or prior relationship)? Target: 40%+.

5. Executive intro velocity — Number of exec-sourced buying group intros per month. Target: 1 per exec per month, minimum.

6. Champion protection rate — % of deals where the champion is still employed at the account, and still in the same role, at close. If this drops below 80%, you're running your deals too slowly.

These are the numbers a CRO should ask for in the Monday pipeline review. If your rep can tell you their MQL count but can't tell you buying group coverage on their top three deals, the operating model is still MQL-era.


Failure modes: how buying group sales dies

Single-threaded deals. The most common cause of death for a "sure thing" deal. The champion loves you, has been meeting with you for months, is scheduling QBRs internally. Then they get promoted, quit, or lose an internal battle — and the deal evaporates because nobody else at the account knows who you are. Every deal in your pipeline above your ACV median should have 4+ meaningful stakeholder relationships. Our single-threaded deals glossary walks through the diagnostic and remediation.

Missed executive transitions. A CFO or CIO takes a new role at your target account, and your team finds out three months later. That's a 30-60 day window of fresh-eyes evaluation you missed. Systematic job change tracking across your buying group personas — and against every past champion, investor connection, and customer contact — is one of the highest-ROI signal sources in enterprise sales. Miss it and you're behind competitors who caught it.

No CNA follow-up. You close the deal, celebrate, and move on. The customer is at maximum affinity for 30-60 days post-close and could easily produce three peer introductions. Six months later, they're absorbed into BAU, half of the champion team has moved on, and the referral window has closed. Most sales orgs have a 0% attach rate on the CNA motion. That single omission is the biggest leak in most enterprise pipeline models.

Champion-only relationships. Your AE meets with the champion 12 times. Never meets the champion's boss. Never meets Procurement. Never meets InfoSec. This is single-threading in slow motion — the deal will close 30% of the time (because the champion is heroic) and stall the other 70% (because nobody else is bought in).

Cold outbound as the only motion for missed personas. When your buying group map shows you have no warm path to InfoSec, the default is to have your BDR send a cold email sequence. This works ~2% of the time in 2026. Instead: use Play 2 (name-drop from the CTO), or Play 5 (exec intro), or wait for a signal that gives you a warm wedge (a security incident at a peer, a new SOC 2 report you can share).

Managing to MQL volume. If your Monday dashboard still leads with MQL count, your team will optimize for MQL count. They will source individual leads instead of covering accounts. They will chase form-fillers instead of building relationships with the six other stakeholders who matter. Change the dashboard. Change the behavior.


Frequently asked questions

Is the MQL really dead? What about SMB motions where one person decides? For true SMB deals — under $25K ACV, sold to a single owner-operator — MQLs still work. The individual is the buying group. But for anything mid-market and up (5+ stakeholders, 3+ personas), MQLs are actively harmful because they route deals to reps as if a single hand-raiser represents committed intent. The uncomfortable truth is that most B2B software vendors above $10M ARR are running an enterprise motion but reporting on an SMB framework.

What replaces the MQL as the trigger for sales engagement? Signal + warm intro. That's the replacement pair. Account-level signals — three or more stakeholders from the same account engaging in a 21-day window, a job change on a persona that fits your buyer profile, a company event (funding, acquisition, exec transition, competitive displacement) on a target account — are the new trigger. Warm-path routing is the new delivery mechanism. The signal tells you when to engage; the warm intro determines whether the engagement lands in a market where 95% of cold outbound gets zero response, 51% of buyers have already shortlisted vendors in an AI chatbot before your first touch, and Forrester's 2023 trust data has vendor salespeople at 29% trust — below every other source in the buying process, and against peers at 90%+. Signal-driven outbound converts 3× faster than cold; layered with a warm path from your connector graph, it produces the highest-yielding pipeline motion in a post-MQL world. Any qualifying signal triggers a buying group mapping and warm-intro coverage motion — not a single-lead handoff.

How does buying group multithreading work if my AEs only have 3-4 hours a day of selling time? You don't multithread by sending each stakeholder a cold email. You multithread by warm-path routing. Boomerang's Play 3 (warm intro request) takes ~4 minutes per intro to review and send. Six warm-intro-based touches to a buying group take ~25 minutes and land at 30-50x the response rate of cold. The math works — but only if you have a graph that maps the warm paths for you.

How is a buying group different from an "account plan"? An account plan is a document. A buying group is an operational reality — 6-9 personas, 14-23 named individuals, with relationships, signals, and coverage state tracked in real time. Account plans get updated quarterly. Buying groups get updated weekly (or daily, when a signal fires). The account plan describes the target; the buying group describes the actual state of play.

What's the fastest way to get started if we're currently running an MQL model? Pick your top 20 active opportunities. Map the buying group on each one (6-9 personas, named). Score current coverage: how many personas have had a personalized touch in the last 30 days? For any opp below 50% coverage, run Play 1 (discover warm paths) and Play 3 (warm intro request) for the missing personas this week. Repeat weekly. Coverage will move from ~20% baseline to ~60% within 60 days, and close rates on those opps will roughly double. Then rebuild your dashboards and Monday pipeline review around buying group coverage, and retire the MQL report.



Schema markup


Build the buying group execution engine

Boomerang is the warm-intro orchestration layer for revenue teams executing against buying groups. It maps every warm path from your reps, past customers, investors, board, and professional network into every persona in your target account buying groups. When a signal fires — an exec transition, a funding event, a competitive displacement — Boomerang identifies the strongest connector, drafts the intro in their voice, and closes the loop when the meeting books.

Stop pretending MQLs work. Build the buying group motion your CMO's transformation strategy actually assumes on the other end. Book a 15-minute walkthrough →

Related Glossaries

Related Glossaries

Related Glossaries

Related Glossaries

We value your privacy
We use cookie to improve your experience on our site. By clicking “Accept All Cookies”, you consent to our use of cookies.Privacy Policy for more information.