Skip to main content

3 posts tagged with "playbook"

View All Tags

When Your Champion Goes Quiet: The 5-Play Re-Engagement Workflow for Stalled B2B Deals [2026]

ยท 13 min read
sunder
Founder, marketbetter.ai

Stalled deal re-engagement workflow โ€” diagnose silence, multi-thread, surface what changed

Your champion replied to every email for three weeks. Demo went great. Pricing was sent. Maybe a verbal yes. Then โ€” silence. Seven days. Twelve. Twenty-one.

The deal isn't in closed-lost yet. It's worse: it's sitting in the slack space between "qualified pipeline" and "lost to no-decision." Every forecast call, your AE moves the date out another two weeks. Nobody has the heart to mark it dead. Nobody has a plan to revive it.

This is the most expensive failure mode in B2B sales. Gartner's research shows the average B2B buying group has 6โ€“10 people, and the journey now averages 11.5 months for considered purchases. Champions go quiet not because they hate you โ€” they go quiet because something changed inside their org that you can't see.

This playbook is a 5-play workflow for AEs and SDRs to systematically re-engage stalled deals. Not a "just check in" template. Specific diagnostic plays that surface what actually changed and re-open the conversation when generic follow-ups won't.

It pairs with the signal decay curve โ€” buying intent has a half-life, and the longer your deal sits in silence, the more aggressively you need to instrument for fresh signal.

Why Champions Actually Go Quietโ€‹

Before the plays, the diagnosis. Champions disappear for four reasons, and the right play depends on which one you're dealing with:

ReasonWhat's actually happeningSignal you'll see
Priority shiftA higher-priority project (often forced by leadership) pulled their attention. Your deal didn't get worse โ€” it got out-prioritized.Champion still active on LinkedIn / posting about new initiatives unrelated to your space
Internal blockerProcurement, security, finance, or a peer raised an objection your champion couldn't answer. They're stuck and embarrassed to come back without a path forward.Job postings in adjacent functions, new hires in procurement or IT, vendor consolidation news
Champion changed rolesPromoted, moved internally, or left the company. The replacement doesn't know you and your deal lost its sponsor.LinkedIn role change, new title, "open to work" updates
Buying group expandedA new exec or department got pulled into the decision, and your champion is now waiting on their input before re-engaging.New executives showing up on website visits, new contacts viewing pricing pages

The plays below tell you how to spot which one you're in and what to do.

If you only run one generic follow-up cadence, you treat all four the same โ€” and you lose three of them. The whole point of this workflow is to diagnose before you write.

Play 1: The Silent Diagnostic (Day 7โ€“10 of Silence)โ€‹

Before you send anything, instrument. The biggest mistake AEs make is firing off a "just checking in" before they know what's actually happening inside the account.

What to check, in this order:

  1. Your champion's LinkedIn activity in the last 14 days. Are they posting? Liking? Commenting? Active = priority shift or internal blocker. Inactive = role change risk.
  2. Their role/title. Same as it was on the demo call? Use LinkedIn Sales Navigator job change alerts if you have them set up. If not, search their profile manually.
  3. Other contacts at the account. Who else from the org has visited your site, opened recent emails, or shown up in your CRM in the last 30 days? This is where website visitor identification earns its keep โ€” you want to know if buying group activity continued without your champion.
  4. Public signals. Funding round? Layoffs? New executive hire? Acquired? Search Google News for the company name plus "announce" in the last 30 days. Anything material reshuffled their priorities.
  5. Your own CRM. Did anyone else from the account open your last 3 emails? View pricing pages? Get added to the opportunity?

You're building a 5-minute brief: what changed at the account between the last reply and today. The brief decides which play comes next.

This is the same diagnostic logic from the three-layer signal stack โ€” you're stacking public, behavioral, and account-level signals before you act.

Play 2: The Multi-Thread Pivot (When the Champion Is Inactive)โ€‹

If your diagnostic shows the champion has been quiet on LinkedIn too, you have a role-change or burnout problem. Don't waste another email on them. Pivot to multi-threading.

The play:

  • Identify 2โ€“3 other contacts at the account: their boss, a peer in the same function, or someone in a department that would benefit from your product.
  • Send a separate, short email to each, referencing the champion by name but not assuming they're still the decision-maker.
  • The hook: "I've been working with [Champion] on [specific outcome]. Wanted to make sure this initiative continues to have a path forward โ€” wondering if it makes sense to loop you in directly."

This works because it gives the other contact two safe options: "Yes, [Champion] is no longer driving this โ€” let's talk" or "Yes, [Champion] is still on it, they're just busy โ€” here's the status." Either answer unsticks you.

The trap to avoid: sending the same email to five contacts at once. That reads as desperation and gets your domain marked as spam. One email at a time, each tailored to that person's function.

If the contact you reach out to isn't on LinkedIn or in your CRM, the B2B data enrichment workflow is what gets you their direct email in 30 seconds.

Play 3: The Forcing-Function Email (When You Suspect a Priority Shift)โ€‹

If the champion is active everywhere except your deal, it's a priority shift. They didn't lose interest โ€” your deal just got bumped. Generic check-ins reinforce the bump because they require them to context-switch back to your problem without giving them a reason.

The fix: give them a forcing function. Something with a hard deadline that requires action, not just attention.

Variants that work:

  • The expiring price/term. "The Q3 pricing we discussed locks on July 1. Want to confirm whether you'd like to extend the conversation or revisit in Q4 so we don't accidentally lose the discount."
  • The pulled resource. "We're moving our implementation team to a new project on July 15. If onboarding doesn't start by then, the next start window is September. Wanted to flag so you can plan accordingly."
  • The departing context. "Our [solutions engineer / product lead] who scoped your environment is rolling off this account on [date]. If you have any technical questions, this week is the right window to get them answered while the context is fresh."

Two rules: it has to be real (don't fake a deadline โ€” your reputation is on the line), and it has to give them an honest "no, not now" exit. The point isn't to pressure โ€” it's to give them permission to make a decision instead of indefinitely deferring.

A forcing function works because it converts an open-ended ask ("hey, status?") into a closed question ("do A or B by date X"). Closed questions get answered.

Play 4: The Insight Drop (When You Suspect an Internal Blocker)โ€‹

The most common failure mode for stalled deals: a peer or boss raised an objection your champion couldn't answer, so they froze. They're not ghosting you โ€” they're stuck. They'll only come back when they have a way to come back.

Your job is to hand them that way back. Not a check-in. An insight that arms them for the next internal conversation.

Examples:

  • A short customer story from a peer company that hit the same objection and overcame it. Specifics, not "lots of companies do this."
  • A new benchmark, data point, or industry report that addresses the likely objection (security, ROI, integration, change management).
  • A pre-built ROI calculator or business case template, filled in with their numbers based on what you already know.
  • A 2-paragraph FAQ on the specific concern, formatted so they can forward it to their internal stakeholder without rewriting it.

The structure of the email is short:

"Hey [Champion] โ€” saw [trigger / news / report] and thought of our conversation. [One sentence on why it matters to their internal case.] No reply needed โ€” figured it'd be useful when this comes back up internally."

The "no reply needed" matters. You're not asking them for energy. You're giving them energy. That's how you re-open a door that was closed by internal politics.

This is the same logic behind the signal-to-meeting workflow โ€” you respond to context, not arbitrary intervals.

Play 5: The Honest Walk-Away (Day 30+)โ€‹

If three of the above plays produced nothing, run the honest walk-away. Counterintuitively, this is the play that re-engages the most stalled deals in our experience.

The email:

"Hey [Champion] โ€” I haven't heard back in a few weeks, so I'm going to assume the timing isn't right and pause our outreach. No hard feelings at all. If something changes on your side and you want to pick this up, my calendar is here: [link]. Otherwise I'll plan to circle back in [Q]."

Three things this does:

  1. Removes the pressure that was keeping them from replying. Most "I'm going quiet" silence is guilt. You just absolved it.
  2. Forces a status update. Anyone who's actually interested will reply within 48 hours with "wait, don't pause โ€” here's where we are." Anyone who doesn't reply genuinely wasn't going to close.
  3. Frees your forecast. Whatever happens, you now have signal. Either you re-open with a real path, or you move the deal to closed-lost and stop dragging it through forecast calls.

The data from the reopen closed-lost playbook backs this up: deals that go to honest closed-lost status and re-engage later close at higher rates than deals that linger indefinitely in "pipeline." Honesty is faster.

The Underlying Principle: Silence Is Dataโ€‹

The thread connecting all five plays: silence is not nothing. Silence is data. The question isn't "should I follow up?" โ€” the question is "what does the silence tell me, and what specific play does it call for?"

Most stalled-deal recovery fails because reps treat all silence the same and run the same cadence. The 5-play workflow forces a diagnosis first, then a targeted play.

Here's the simplified decision tree:

You seeRun
Champion inactive on LinkedIn / role changePlay 2: Multi-Thread Pivot
Champion active, deal not moving, no internal newsPlay 3: Forcing-Function Email
Champion active, but recently a peer/exec joined the dealPlay 4: Insight Drop
You've run 2+ plays with no responsePlay 5: Honest Walk-Away
You haven't diagnosed yetPlay 1: Silent Diagnostic โ€” never skip this

How This Fits Into a Weekly Pipeline Reviewโ€‹

Run Play 1 (Silent Diagnostic) on every stalled deal during your weekly pipeline review. Five minutes per deal. By the end of an hour, you've classified every silent deal in the pipe by which play it needs.

Then batch the work. All Play 2 multi-threads go on the same morning. All Play 3 forcing functions go out together. Play 4 insight drops are the highest-leverage emails in your week โ€” schedule them when you're freshest.

This pairs naturally with the first 30 minutes morning workflow for SDRs and the daily SDR playbook for prioritized task lists. Stalled-deal work is recurring work โ€” bake it into the calendar, don't wait until forecast day to panic about it.

A Note on Toolingโ€‹

You can run this playbook in any CRM. The bottleneck isn't software โ€” it's the discipline to diagnose before you write.

That said, two pieces of instrumentation make this dramatically faster:

  1. Visitor identification on your site. When a stalled account quietly visits your pricing page or a case study, you know the conversation is alive even when the champion isn't replying. That's a Play 4 trigger you'd otherwise miss.
  2. Job change alerts on your champion list. A LinkedIn role change inside an account is the single highest-confidence trigger for Play 2 multi-threading. Most CRMs don't surface this. Either set up Sales Navigator alerts or use a tool that pushes the signal into your daily task list.

MarketBetter does both natively โ€” visitor ID plus signal-based task routing for stalled accounts. The pitch isn't "use our tool." It's: if your stalled-deal recovery rate matters, instrument the two signals above, in whatever tool you can. The plays above don't work without them.

What to Stop Doingโ€‹

If you take one thing from this playbook, it's the things to stop doing:

  • Stop running the same "checking in" cadence for every stalled deal. It treats role changes and priority shifts the same as internal blockers. It works for none of them.
  • Stop letting stalled deals sit in forecast for 60+ days. Either run Play 5 and move on, or run Plays 1โ€“4 with intent. Drifting is the worst outcome โ€” it inflates your forecast and saps team morale.
  • Stop sending bulk follow-ups across multiple contacts at once. This is the fastest way to get your domain marked as spam and tank deliverability across your entire pipeline.
  • Stop assuming silence means "not interested." In our experience, the majority of stalled deals have an internal cause that's recoverable if you diagnose correctly.

The Bigger Pictureโ€‹

Stalled deals are pipeline rot. They don't show up as lost revenue on a dashboard โ€” they show up as forecast accuracy you can't fix and quota stress you can't explain. The teams that fix this don't have magic templates. They have a workflow that converts silence from a black box into a structured diagnosis.

The 5 plays above are that workflow. Pair them with the signal-based selling principles we've written about all year, the inbound triage tier system for the front of the funnel, and the follow-up email templates for the cadences themselves.

The deals you're worried about right now aren't dead. They're undiagnosed.


Want help instrumenting the signals that surface stalled-deal risk before it's terminal? Book a 20-minute demo and we'll walk through how MarketBetter routes silent-account signals into your reps' daily task list โ€” so champions going quiet becomes a triggered workflow instead of a forecast surprise.

The Inbound Triage Tier System: How SDR Teams Hit 5-Minute Response Without Calling Every Lead [2026]

ยท 12 min read
sunder
Founder, marketbetter.ai

Inbound triage tier system โ€” routing leads by signal intensity, not arrival order

Every SDR leader has heard the rule: respond to inbound leads in under 5 minutes or you lose them. The MIT study on lead response times is gospel โ€” 21x more qualification, 78% of buyers go with whoever responds first.

So teams chase 5-minute SLAs on every lead. They route everything to a human. They build dashboards that turn red when a form sits for 6 minutes.

And then their best SDRs quit, because they're spending half their day calling people who downloaded a whitepaper out of curiosity.

The 5-minute rule is real. The way most teams implement it is broken.

This playbook is the fix: a 4-tier triage system that gets you to 5-minute response on the leads that matter, automates the middle, and stops your reps from hand-dialing tire-kickers. Built from the signal quality data we've been writing about all year and the daily SDR playbook we run internally.

The Problem With "5 Minutes On Every Lead"โ€‹

A typical mid-market B2B funnel looks like this in a given week:

  • 12 demo requests (high intent, ready-to-buy signal)
  • 40 content downloads (mixed intent โ€” some buyers, some researchers)
  • 60 newsletter subscriptions (low intent, mostly tire-kickers)
  • 200 pricing page visits with no form fill (variable intent โ€” depends on company)

That's 312 "leads" hitting your funnel. If you apply a uniform 5-minute SLA to all of them, you need roughly 4-5 SDRs working full-time just to handle inbound. Most teams have 2-3.

So what actually happens? Two failure modes:

  1. The SDR team picks favorites. They prioritize demos and ignore everything else. Half the funnel goes dark for 48 hours. Plenty of pipeline-worthy signals get missed.
  2. The SDR team tries to do everything. They call newsletter subscribers at 2 PM on a Tuesday, get hung up on, and eventually start treating every inbound lead as a low-priority chore. Quality of outreach collapses across the board.

The fix isn't more SDRs. It's better triage.

The 4-Tier Triage Systemโ€‹

Treat inbound the way an ER treats patients. Not first-come-first-served โ€” most acute first, with response times calibrated to the urgency of the signal.

TierSignal ExamplesResponse SLAHandlerChannel
Tier 1 โ€” HotDemo request, pricing page visit + ICP match, "talk to sales"5 minutesHuman SDRPhone + email + LinkedIn
Tier 2 โ€” WarmContent download + ICP fit, repeat visitor with intent pages, webinar attendee1 hourAI agent drafts, human approvesEmail + LinkedIn
Tier 3 โ€” CoolSingle content download, non-ICP form fill, light intent24 hoursAutomated sequenceEmail only
Tier 4 โ€” ColdNewsletter signup, blog comment, anonymous traffic7 days or nurtureMarketing automationEmail nurture

The point isn't the exact response times โ€” those depend on your ACV and sales cycle. The point is that the same SLA cannot apply to every lead. Signal intensity determines speed. Speed determines headcount allocation.

What Goes Into Each Tierโ€‹

Tier 1 โ€” Hot (5-minute response, human)

These are the only leads where the 5-minute rule literally applies. Characteristics:

  • Explicit purchase intent (demo, sales, pricing inquiry)
  • ICP match (right industry, right size, right title)
  • Recent on-site behavior showing active evaluation

For a mid-market B2B company, this is usually 3-8% of total inbound volume. It is by far the highest-converting bucket. Every minute of delay here is measurable pipeline lost. This is where you spend your speed budget.

Tier 2 โ€” Warm (1-hour response, AI-assisted)

These leads are evaluating, but haven't asked to talk yet. They downloaded the buyer's guide. They came back to your site twice this week. They attended your webinar and stayed for the Q&A.

The mistake here is treating Tier 2 like Tier 1. A 5-minute call to someone who just downloaded a PDF feels stalker-ish and converts worse than a thoughtful email 45 minutes later.

The right pattern: an AI agent drafts a personalized email referencing the content they consumed and their company context. An SDR scans the draft, edits if needed, and sends. The whole loop takes 90 seconds of human time. Response goes out within an hour while the topic is fresh.

This is the workflow we walked through in Visitor ID to First Outreach in 30 Minutes โ€” same logic applies to any Tier 2 signal.

Tier 3 โ€” Cool (24-hour response, automated)

Low-intensity signals. Single content downloads, non-ICP form fills, leads from outside your serviceable territory. These go into an automated sequence โ€” 3 to 5 emails over 2-3 weeks, designed to either escalate them up the tier system (by triggering a Tier 1 or 2 signal) or filter them out.

No human SDR time spent. Period. If they raise their hand later, they move up the tier system and get re-routed.

Tier 4 โ€” Cold (nurture)

Newsletter signups, blog readers, anonymous traffic, top-of-funnel content engagement. Marketing automation handles this entirely. They are not yet leads โ€” they are subscribers. Treat them accordingly. They escalate into Tier 3 or higher only when behavior signals it.

The Routing Logic (How Leads Move Between Tiers)โ€‹

Static tier assignment is brittle. Real lead behavior is dynamic โ€” a newsletter subscriber today might be a demo request next week. The system has to move them.

Three routing rules govern movement:

  1. Up-tier on intent escalation. Any Tier 2-4 lead that submits a higher-intent action (pricing visit, demo request, "contact sales" click) jumps immediately to Tier 1. The clock restarts.
  2. Down-tier on disengagement. Any Tier 1-2 lead that goes silent through three touches drops one tier. This frees SDR capacity for fresher signals.
  3. Re-rank weekly. Pull the full active-lead list every Monday. Re-score against the tier criteria. Reroute anyone whose behavior has shifted.

Most teams skip rule 3 and end up with a queue full of dead Tier 1 leads. Re-ranking is the maintenance pass that keeps the system honest.

This is the same intent-tier logic we used in the signal-based SDR routing post โ€” applied to inbound instead of outbound.

How To Automate Tiers 2 and 3 (Without Sounding Like a Bot)โ€‹

The tier system is only useful if Tier 2 and 3 don't need human attention. Here is the workflow that makes that real.

For Tier 2 (AI-drafted, human-approved)โ€‹

  1. Signal detected. Content download, repeat visit, webinar attendance โ€” whatever your trigger is.
  2. Enrichment fires. Company data, role data, recent on-site behavior, mutual connections, news mentions in the last 90 days.
  3. AI drafts the response. A short email referencing the specific content consumed, the company context, and one specific reason your platform fits their stack. Includes a soft CTA โ€” "happy to share how others at companies like yours used this โ€” open to a 15-min call next week?"
  4. SDR reviews draft. Should take 30-90 seconds. Approve, edit, or skip.
  5. Send + log. Goes into the SDR's sent folder so the next touch is from them, not a generic inbox.

The pattern we covered in From Buying Signal to Booked Meeting in 24 Hours is the template here โ€” same enrichment, same drafting loop, different SLA.

For Tier 3 (Fully automated)โ€‹

  1. Signal detected. Low-intensity action.
  2. Sequence enrolled. Lead enters a 4-touch sequence calibrated to the content they engaged with. Touch 1 references the asset. Touch 2 (4 days later) shares a related case study. Touch 3 (10 days) offers a soft CTA. Touch 4 (21 days) is a breakup email.
  3. Behavior monitored. Any open, click, or site revisit that crosses a threshold up-tiers them. They get pulled from the sequence and routed accordingly.
  4. Quiet exits. No re-engagement after 4 touches? They drop to Tier 4 and join the newsletter nurture.

The risk in Tier 3 automation is sounding generic. Avoid it by enriching the sequence with company-specific lines from public sources โ€” recent news, hiring activity, tech stack changes. Two or three concrete references per email is enough to feel human.

Why This Matters (The Capacity Math)โ€‹

Run the numbers for a typical mid-market SaaS team:

  • 312 weekly inbound leads
  • 4% Tier 1 = 12 leads โ†’ 1 hour of SDR time each = 12 hours of focused work
  • 18% Tier 2 = 56 leads โ†’ 2 minutes of SDR review each = ~2 hours total
  • 38% Tier 3 = 119 leads โ†’ 0 SDR time (fully automated)
  • 40% Tier 4 = 125 leads โ†’ 0 SDR time (marketing nurture)

Total SDR inbound load: ~14 hours/week. One SDR can handle the inbound queue with time left over for outbound. Without the tier system, the same 312 leads require 3-4 SDRs and still produces worse outcomes โ€” because the Tier 1 leads get the same treatment as the newsletter subscribers, and nothing gets the attention it deserves.

That's the unlock. Not faster response on everything. Faster response on the leads that pay back the speed.

Common Failure Modesโ€‹

A few patterns I've seen kill tier systems even when they're well-designed:

1. Tier 1 over-population. Sales leaders push to flag more leads as Tier 1 because it feels like progress. Within a quarter, 25% of leads are "hot" and SDRs are back to chasing volume. Fix: gate Tier 1 promotion on hard signals only, not gut feel.

2. No re-ranking. The Monday re-score pass falls off when the team gets busy. Within a month, the active queue is full of stale Tier 1 leads that should have been demoted. Fix: automate the re-rank. Make it a system event, not a calendar reminder.

3. Tier 2 drafts that read like spam. AI drafts without enrichment produce form-letter outreach. The whole point of Tier 2 is human-quality response at machine speed. Without enrichment, you've just built a slow spam cannon. Fix: invest in the enrichment layer first, then turn on drafting.

4. Routing without a CRM source of truth. If the tier lives in a spreadsheet, it dies in a spreadsheet. The tier must be a field on the lead record that every system reads from. Fix: pick one system of record and make tier a first-class field there.

The Tooling Layerโ€‹

You can run this system manually if your volume is small. Past about 50 weekly inbound leads, you need automation. The capability set you need:

  • Visitor identification โ€” who is on your site, even without a form fill
  • Real-time enrichment โ€” company + person data within seconds of trigger
  • Intent scoring โ€” assigns a tier based on signal combinations
  • AI drafting with context โ€” pulls enrichment + content history into the draft
  • Routing engine โ€” sends Tier 1 to humans, Tier 2 to drafts, Tier 3 to sequences, all automatically
  • Behavior-based re-tiering โ€” moves leads between tiers based on action

Several tools cover parts of this. Best lead routing software in 2026 and the ChiliPiper alternative breakdown both go deeper. Most teams stitch together 3-5 tools โ€” visitor ID, enrichment, MAP, AI assistant, scheduler.

This is what MarketBetter consolidates. We don't just identify the visitor and score the signal โ€” we draft the response, route to the right rep, and tell them exactly what to do next. The difference between knowing who's hot and acting on it in under an hour is the whole game.

The 30-Day Rolloutโ€‹

If you're starting from a flat 5-minute-everything SLA, here's the migration:

  • Week 1: Define your tier criteria. Pull last 90 days of inbound. Manually classify into 4 tiers. Confirm the distribution feels right.
  • Week 2: Set up Tier 3 automation. Build the 4-touch sequence. Stop manually responding to single-content-download leads.
  • Week 3: Set up Tier 2 enrichment + AI drafting. Pilot with one SDR. Measure response quality.
  • Week 4: Roll Tier 2 to the team. Establish the Monday re-rank pass. Lock in Tier 1 as the only human-priority queue.

By day 30, your SDRs should be spending 70% of their inbound time on Tier 1 and Tier 2 reviews. The previous 70% โ€” the busywork on Tier 3 and 4 โ€” is now automated.

The Bottom Lineโ€‹

The 5-minute rule isn't wrong. It's just narrowly true. It applies to hot, ICP-fit, ready-to-buy leads โ€” and almost nobody else.

Build the tier system. Reserve speed for the leads that pay it back. Automate the rest. Your SDRs get their best hours back, your hot leads get the response time the data says they need, and the leads who weren't going to buy this quarter don't burn capacity that should have closed deals.

The teams winning inbound in 2026 aren't the fastest on everything. They're the most disciplined about what deserves speed and what doesn't.


Want to see how MarketBetter automates Tier 1 and Tier 2 inbound response โ€” including visitor ID, AI drafting, and routing? Book a demo.

Related reading:

How to Turn Job Changes Into Closed Deals (Champion Tracking Playbook)

ยท 11 min read
sunder
Founder, marketbetter.ai

You just got an alert: your best champion from last year's biggest deal has moved to a new company. This is the moment champion tracking tools like UserGems, Champify, and MarketBetter are built for. But what happens next determines whether that alert becomes a closed deal or a wasted opportunity.

Most sales teams fumble the post-alert execution. They send a generic congratulations email, get no response, and move on. Meanwhile, the teams that consistently turn champion job changes into revenue follow a systematic, multi-channel playbook that maximizes speed, personalization, and persistence.

In this article, we lay out the complete champion tracking playbook โ€” from detection to closed deal โ€” with specific tactics for each step. We'll also show you how the right platform can automate each step so your team executes flawlessly every time.