If you're an SDR in 2026 and you're not using Claude for at least a third of your daily workflow, you're getting outworked by people who are.

This isn't speculative. It's the consistent pattern we see across the GTM teams using MarketBetter: the SDRs who pair Claude with their existing tools (Sales Navigator, CRM, sequencer, enrichment) are booking 2–3x more qualified meetings — not because they grind harder, but because Claude eats the parts of the job that used to eat their day.

This pillar is the single page that pulls it all together. It's a map. Each section links into a deeper, hands-on guide so you can go as shallow or as deep as you want.

Use this guide if you want to:

• Understand which sales tasks Claude is actually good at (and which still need a human)
• See concrete workflows for prospect research, Sales Navigator, email personalization, and CRM hygiene
• Compare Claude vs. ChatGPT vs. Codex for SDR work
• Get a daily routine you can copy and run starting tomorrow

Let's get into it.

What Claude actually is (and why SDRs care)​

Claude is Anthropic's family of large language models — the same kind of underlying technology behind ChatGPT, but built with a different design philosophy. For sales work, three things matter:

1. Long context. Claude can hold the equivalent of a 500-page document in working memory. You can drop in a whole company's 10-K, a quarter of call transcripts, or a CSV with 2,000 leads, and ask questions across all of it. Most sales workflows benefit from this more than from raw "intelligence."
2. Reasoning that holds together. When you ask Claude to compare 30 prospects against your ICP and prioritize them, it doesn't lose the thread halfway through. That matters when the output is a worklist you're about to grind through.
3. Claude Code. The CLI version of Claude can read files, run scripts, hit APIs, and do real work in a terminal — not just chat. That's what unlocks the workflows in this guide.

If you've never opened Claude Code, start with The AI-Powered SDR: How Claude Code + MarketBetter Changes Everything. It's the on-ramp.

For a deeper head-to-head on which model to use when, see Claude vs ChatGPT for Sales Teams and Codex vs Claude Code for Outbound Sequences.

The five things Claude is genuinely good at for SDRs​

Most SDR teams trying AI fail because they pick the wrong tasks. AI is not magic — it's a very specific kind of leverage. After watching dozens of GTM teams roll this out, five jobs consistently produce a return.

1. Prospect research at scale​

The before: an SDR opens a LinkedIn profile, copies the bio into a doc, hunts for the company's last funding round, reads the latest blog post, then attempts a "personalized" opener. Twenty minutes per prospect, fifteen prospects a day.

The after: Claude reads the LinkedIn profile, the company about page, the last three blog posts, and a Crunchbase entry, then drafts a one-paragraph "what to actually open with" briefing. Two minutes per prospect, sixty prospects a day, and the openers are sharper because Claude can hold all four sources in working memory at once.

Hands-on walkthrough: Claude Code SDR Part 2: Prospect Research and Automate Lead Research with Claude Code.

2. Personalized cold email at volume​

There's a chasm between "generic AI-written email" and "actually personalized email." The difference is the inputs. If you hand Claude a job title and a company name, you get generic slop. If you hand it the prospect's last LinkedIn post, a snippet from their company's earnings call, and your ICP framing, you get something a human couldn't tell from a hand-written email — at 30x the speed.

We've broken the workflow down step by step in Claude Code SDR Part 3: Personalized Cold Emails and AI Email Personalization at Scale. Templates that have produced real opens: AI Sales Email Templates with Claude Code.

3. Sales Navigator → enriched list pipeline​

Sales Navigator is a goldmine, but it's also a UI nightmare. Most SDRs end up exporting CSVs and gluing tools together. Claude Code can sit in the middle of that pipeline — taking a raw export, hitting enrichment APIs, scoring against ICP, and dropping a ready-to-sequence list into your CRM or MarketBetter campaign.

Full walkthrough: Automate LinkedIn Sales Navigator with Claude Code and Claude Code SDR Part 4: LinkedIn to Pipeline.

4. CRM cleanup and duplicate hunting​

This is the boring, underrated win. Every SDR org we look at has tens of thousands of dirty records — duplicate companies, inconsistent job titles, missing fields, accounts owned by reps who left two years ago. Claude is unreasonably good at this kind of pattern work because it can hold the whole CSV in context and make consistent, explainable decisions.

For a real example of what dirty data costs you and how to fix it: When CRM Has 3 Records for the Same Company and Claude Code SDR Part 7: CRM Cleanup.

5. Pipeline analysis and reporting​

The other underrated win. Once a week, drop your CRM export into Claude and ask: "What changed in pipeline this week? Which deals look at risk? Which reps are leaning on a single mega-deal?" In ten minutes you get a weekly business review most ops teams take two days to produce.

Deep dive: AI Pipeline Velocity Optimization with Claude Code and Claude Code SDR Part 6: Lead Scoring.

What Claude is NOT good at (don't waste time here)​

This is the part most "AI for sales" content skips. The list of things Claude shouldn't be doing in your workflow:

• Actually sending the email. Claude drafts; your sequencer sends. Mixing the two is how you end up with deliverability problems and brand damage.
• Live discovery calls. Claude is a research and prep tool, not a replacement for the conversation. The SDRs who try to use it on live calls sound exactly like what they are.
• Anything that needs a relationship. Referral asks, expansion conversations, exec sponsorship — these are still 100% human. Claude can help you prep, but a Claude-written DM to a CFO will read as Claude-written, and they will clock it instantly.
• Hard objections you don't understand yet. If you can't articulate why a prospect might say no, Claude can't either. It can help you brainstorm, but it can't shortcut the muscle of actually understanding your market.

We wrote a longer take on this: Why General AI Won't Replace the SDR Stack and Why Open-Source GTM Agents Won't Replace the SDR Platform.

Claude vs. ChatGPT vs. Codex: which one when?​

Short version of a long argument:

• ChatGPT — Best for one-off brainstorms and quick rewrites in a browser. The product layer is more mature for non-technical users.
• Claude (web) — Best when you need to drop in a long document (an RFP, a deck, a transcript) and ask deep questions. The long-context advantage is real.
• Claude Code — Best when the work is repeatable and touches files, APIs, or your terminal. This is where the 10x leverage lives.
• Codex / OpenAI CLI — Best when the work leans heavier on code generation than on reading/reasoning over content. Decent for sequencer integrations.

Full comparison matrices: Codex, Claude, ChatGPT for GTM Comparison, Claude vs ChatGPT for Sales Teams, Codex vs Claude Code for Outbound Sequences, and the practical OpenAI Codex CLI GTM Guide.

If your team is debating whether to build something custom or buy a platform, read Build vs Buy: The AI SDR Stack Decision before the next meeting.

The 10-part Claude Code SDR series, in order​

If you want the hands-on path, work through the series in order. Each part is ~10 minutes to read and another 15–30 to set up:

1. Part 1 — The AI-Powered SDR: How Claude Code + MarketBetter Changes Everything
2. Part 2 — Prospect Research with Claude Code
3. Part 3 — Personalized Cold Emails at Scale
4. Part 4 — LinkedIn to Pipeline
5. Part 5 — Competitive Intelligence
6. Part 6 — Lead Scoring with AI
7. Part 7 — CRM Cleanup
8. Part 8 — Meeting Prep
9. Part 9 — Follow-up Sequences
10. Part 10 — The Complete Playbook

Tangential but useful: AI Buyer Persona Research Automation with Claude Code, AI Objection Handler with Claude Code, Multi-language Cold Outreach with AI, and AI Sales Onboarding Automation.

A realistic Claude-powered SDR day​

Here's what a 9-to-5 actually looks like for an SDR who has internalized this workflow. Adjust to taste.

9:00 — Triage and target list (30 min)​

Open Claude Code. Hand it last night's MarketBetter signal feed plus your CRM export. Ask: "Which 25 prospects should I prioritize today, ranked by signal strength and ICP fit, with one sentence each on why?" Paste the output into your day list.

Underlying mechanics covered in: From Buying Signal to Booked Meeting in 24 Hours and Visitor ID to First Outreach in 30 Minutes.

9:30 — Research sprint (45 min)​

For the top 10 prospects, run a research macro. Claude reads LinkedIn, the company about page, last earnings call (if public), and last 3 blog posts. Produces a one-paragraph "what to open with" briefing per prospect. Total time: ~4 minutes per prospect, parallelized.

10:15 — Personalized outbound block (75 min)​

For each researched prospect, Claude drafts an email + LinkedIn DM + voicemail script using your templates and the research briefing. You read, edit (always edit), and queue in the sequencer. Expected output: 20–25 outbound touches that don't read as templated.

11:30 — Live calls (90 min)​

This is human time. Claude shouldn't be on the call. But before each call, give Claude 30 seconds: "Pull the meeting prep brief for [prospect name]." It hands you the angles, the questions you should ask, and the likely objections.

Covered in Claude Code SDR Part 8: Meeting Prep.

1:00 — Lunch (you, not Claude)​

2:00 — Follow-ups and replies (60 min)​

For replies that came in overnight, paste them into Claude and ask for a draft response in your voice. Same for follow-ups on cold opens. The model gets better at "your voice" the more you correct it — keep a one-page style doc and feed it in every time.

Workflow: Claude Code SDR Part 9: Follow-up Sequences.

3:00 — Round 2 outbound block (90 min)​

A second outbound sprint, weighted toward prospects from this morning's research that you didn't get to yet. Same flow as 10:15.

4:30 — Pipeline hygiene + end-of-day reporting (30 min)​

Claude runs the daily CRM cleanup macro — flags duplicates, missing fields, stale opportunities, and accounts assigned to nobody. You spend ten minutes resolving the top five issues. Then Claude drafts your end-of-day update for your manager from your activity log.

The longer template version of this day: Claude Code SDR Part 10: The Complete Playbook.

Common questions​

Do I need to know how to code to use Claude Code?

No. Claude Code is a command-line tool, not a programming language. You type instructions in English. The reason it's powerful for SDRs is that it can read your CSVs and hit web pages — not that you're writing software.

Will my SDR manager freak out about prospects being touched by AI?

If they're paying attention, the question they'll actually care about is the output, not the tool. SDRs using Claude well are not the ones sending mass-templated AI slop — they're the ones sending sharper, more researched messages than the rest of the team. That conversation tends to land on "show me your workflow," not "stop using it."

What about deliverability? Doesn't AI content get flagged?

Email providers don't flag content because "AI wrote it" — they flag patterns: same body across thousands of sends, links to suspicious domains, low engagement, sudden volume spikes. Claude-drafted but human-edited emails sent at SDR cadence don't trigger any of that. If you want to go deep, we wrote about it in the context of why most signal-based selling rollouts fail in 90 days.

How does Claude compare to a purpose-built AI SDR tool like 11x, Regie, or Nooks?

Different categories. Claude is a general-purpose model you wire into your existing tools. Purpose-built AI SDR platforms are end-to-end products that try to replace the SDR seat. We have a strong opinion on this — Why General AI Won't Replace the SDR Stack — and you can see the head-to-heads in our reviews like Landbase Review 2026.

Where does MarketBetter fit?

MarketBetter is the signal and orchestration layer underneath the workflows in this guide. Claude is the research and writing engine; MarketBetter is the system that surfaces which accounts are in-market right now, routes them, and tracks what happens. The 10-part series is named "Claude Code + MarketBetter" for a reason — they're complements, not competitors. See the AI SDR tech stack for the full picture, or how to build an AI SDR with MarketBetter.

Where to start tomorrow​

If you read nothing else from the links above, do these three things this week:

1. Read Part 1 and install Claude Code. Twenty minutes.
2. Pick one workflow from the five above — most teams start with prospect research because the time savings are immediate and obvious.
3. Run it on your real worklist for one week. Don't try to automate the whole stack at once.

The SDRs who win at this don't move fastest. They move first on the workflow they understand best and then expand from there.

If you want the signal layer that decides which prospects belong in your Claude pipeline in the first place — that's what we built MarketBetter for. Book a demo or keep reading the SDR automation pillar and the B2B intent data pillar for adjacent territory.

Every SDR leader we talk to has the same blind spot: they treat buying signals like inventory.

Inventory sits on a shelf. It is the same on Monday at 9am as it is on Thursday at 4pm. Work the queue when you have capacity. It will still be there.

A buying signal is the opposite. It is perishable inventory — closer to a sushi plate than a can of soup. The first hour after a signal fires is worth more than the next 24 combined. By the time most ops teams have routed it through Slack, owned it in the CRM, and added it to a sequence, the buyer has already had three vendor conversations and picked their shortlist.

This post puts numbers on that decay. It draws on three years of pipeline data from B2B teams we work with, plus a meta-analysis of 11 published speed-to-lead studies. Then it gives you a four-tier response window your team can implement this week.

The thesis is simple: the decay curve is the math underneath every other signal-selling decision — routing, triage, sequencing, escalation. If your team is operating without it, you are leaking the majority of the pipeline you paid for.

What Counts as a Buying Signal​

Not all intent is created equal. The decay curve we're going to walk through assumes a "tier-1" signal — meaning a signal that has high closed-won correlation when worked in the first window. The buying signal hierarchy breaks down which signal types actually predict revenue. Quick recap of what counts as tier-1:

• Identified website visit (visitor ID on pricing/product page, not blog)
• Champion job change at a closed-won account, into a similar role
• Solution-specific job posting (hiring for a role that uses your category)
• In-product event (free trial signup, demo request, feature usage)
• Detected RFP or vendor evaluation language in public sources

Top-of-funnel noise — generic third-party intent surges, follower growth, podcast mentions — does not decay the same way because it was never worth that much to begin with. We'll focus on signals where the buyer has done something that meaningfully raises their probability of buying right now.

The Decay Curve, Plotted​

Here is the median half-life pattern across the engagements we've audited:

Three things to notice:

1. The first 4 hours is where 48% of the value evaporates. Not the first day. Not the first week. The first half of one work shift. If your team's median response time is "next business day," you are routinely handing buyers to whichever competitor responded by lunch.

2. The curve is steepest at the front. A signal worked at minute 10 is worth roughly 1.5x the same signal worked at minute 60. That is the single highest-leverage 50 minutes in the entire SDR workflow. Most orgs spend that window on stand-up.

3. After day 3, the signal stops being a signal. It becomes a cold prospect with a slightly warm pretext. You can still work it. You should not call it intent-driven outbound. The hit rate is no longer materially different from a well-targeted cold list.

The InsideSales/MIT study from 2011 found that contact rates dropped 10x between minute 5 and minute 30. Salesforce's State of Sales replicated the directional finding across multiple cohorts. Drift's 2019 conversational marketing benchmark put the contact-rate cliff between 5 and 10 minutes. The numbers shift cohort to cohort. The shape of the curve does not.

Why Decay Accelerated in 2026​

The curve is not the curve it was in 2019. Three forces compressed it.

Buyer panels evaluate in parallel, not serial. A modern B2B buyer doesn't research one vendor at a time. They open five tabs, fill out three forms, and read two G2 comparison pages in a single afternoon. The first vendor in the conversation gets to frame the criteria. The fifth vendor is often disqualified before they reply.

AI-driven outreach raised the floor on response speed. When your competitor is using an AI agent to draft and send a relevance-checked email within four minutes of a website visit, your "we batch responses every morning" workflow is not slow — it is invisible. The shortest response time wins, and the shortest response time is now measured in single-digit minutes.

Buying committees decay faster than buyers. Even if your individual contact stays warm, the deal does not. Modern B2B purchases involve 6–10 stakeholders. Each one of them has a half-life of attention. By day 3, the champion has moved on to three other priorities, and re-mobilizing the committee costs more than the original outreach would have.

If you want a deeper read on what changed about pipeline economics this year, our breakdown of why most signal-based selling rollouts fail in 90 days gets into the org-design side. This post is the math side.

The Cost-Per-Hour of Delay​

The decay curve becomes operational when you put dollars on it. Here is the working formula:

Pipeline at risk per hour =
  (Signals/day × Avg deal size × Win rate at minute-0)
  ÷ 24
  × Hourly decay factor at current response time

Walk through a representative mid-market case. A team with 80 tier-1 signals per week, $42K ACV, and a baseline 12% win rate when worked inside the first hour.

• Total pipeline created if all signals worked at minute 0: 80 × $42K × 0.12 = $403K/week
• Same signals worked at the 4-hour mark (52% value remaining): $210K/week
• Same signals worked next business day (31% remaining): $125K/week
• Delta from 0-hour to next-day response: $278K/week, or ~$14.4M/year

This is not a hypothetical SaaS calculator. This is the number that shows up in QBR slides under "pipeline we modeled but did not generate." If you find yourself defending the spend on intent data, this is the number to put in front of the finance team — and the number to fix first.

If you have not yet priced your full stack against pipeline contribution, our analysis of the true cost of an SDR stack in 2026 walks through how to attribute spend to signal yield, not seat count.

The Four-Tier Response Window​

Once a team accepts the decay curve, the workflow rewrites itself. You stop thinking in queues and start thinking in windows. Here is the four-tier model that survives in production:

Tier 1 — Minute 0 to 15: Automated Touch​

This window belongs to automation. No human can read, qualify, draft, and send inside 15 minutes consistently. So you don't ask them to.

What runs in this window:

• Auto-enrichment of the company and contact
• A relevance check against ICP (firmographics, tech stack, recent funding)
• A drafted first-touch email queued for the owner, not sent
• A Slack alert to the owner with one-click send/edit/skip

The goal here is not to send the email at minute 5. The goal is to make sure that by minute 16, the rep has everything they need to send a high-quality, personalized email in under 60 seconds.

Tier 2 — Minute 15 to 60: SDR Owner Touch​

The SDR who owns the account gets the first human shot. The "first 30 minutes of an SDR morning" used to be inbox triage; now it is signal triage. Our 30-minute morning workflow guide walks through what that looks like in practice.

In this window:

• Rep reviews the drafted email, edits the personalization line, sends
• Rep checks LinkedIn for any mutual context to layer in
• Rep adds the contact to a 5-touch sequence calibrated to the signal type
• Rep logs a follow-up reminder for the 4-hour mark

If the rep doesn't act inside 60 minutes, the signal escalates.

Tier 3 — Hour 1 to 4: Manager Escalation​

This is where most orgs lose the most value, because they have no escalation path. The signal sits in a Slack channel, the SDR is in a meeting, and the window closes.

The pattern that works:

• At the 60-minute mark, if no rep touch has been logged, the signal escalates to the SDR manager
• Manager can re-route to an available rep, take it themselves, or push it to an SDR pool
• The originating rep is not punished — escalation is a system safeguard, not a performance flag

We covered the routing math separately in our piece on signal-based SDR routing by intent tier. The 4-hour ceiling is the operationally important part: past it, the conversation has changed from "outbound to a warm signal" to "outbound to a lukewarm one."

Tier 4 — Hour 4 to 24: Sequenced Recovery​

If the signal made it to hour 4 without a human touch, you have lost roughly half its value. You still work it, but you stop treating it as urgent. It enters a calibrated sequence:

• Day 1: A single, well-researched outbound email (no urgency framing — that ship has sailed)
• Day 3: LinkedIn connection request with a relevance line
• Day 5: A second email with a different angle (often a case study from the same vertical)
• Day 8: Voicemail + follow-up text
• Day 14: Last-touch, "closing the loop" email

After day 14, the contact rolls back into the standard cold outbound list. Pretending a 14-day-old signal is still hot is one of the most common ways teams overestimate their pipeline.

What Most Teams Get Wrong About "Speed-to-Lead"​

The phrase "speed-to-lead" got hijacked by the inbound demo-request workflow, where the only signal that counts is a filled form. The decay curve applies to every signal type — and that is where most operations design breaks down.

Three failure modes we see repeatedly:

Conflating signal types. Treating "downloaded ebook" with the same urgency as "visited pricing page twice" guarantees you'll either burn out your reps on noise or sleep on the real intent. The three-layer signal stack framework is one way to keep these separated by tier in your routing logic.

Designing for the median, optimizing for the average. "Our median response time is 2 hours" sounds fine until you remember the curve is non-linear. A team with a median of 2 hours and a long tail of 24-hour responses is leaving more pipeline on the table than a team with a flat 3-hour response. Look at the 90th percentile, not the median.

Treating signals as additive to existing workflow. If you bolt signal alerts onto an SDR who is already at 95% capacity calling their named account list, you have added noise, not capacity. The decay curve makes one demand on your org design: signal-driven work has to displace lower-value work, not stack on top of it. If you can't say what gets cut, you can't say you've operationalized signals.

The Three-Week Implementation​

Most teams can move their median response time from "next business day" to "under one hour" inside three weeks. Not because the technology is hard — because the org changes are well-defined.

Week 1 — Measure the current curve. Pull six months of signal data. For each signal, calculate (a) time from signal fire to first human touch, (b) time from first touch to first reply, (c) conversion to meeting. Plot the conversion-to-meeting rate against the time-to-touch bucket. You will see your own decay curve. It will be uglier than you expect.

Week 2 — Build the automation tier. The minute 0-to-15 window is non-negotiably automated. Set up the enrichment, the relevance check, and the drafted email queue. Most teams already have the components; they just have not wired them into a single triggered workflow.

Week 3 — Install the escalation rule. The hour-1 escalation to the SDR manager is the single highest-leverage change. It guarantees no signal sits in a Slack channel longer than 60 minutes without a human eye. Once this rule is in place, your decay curve flattens within the first reporting cycle.

By the start of week 4, you have a system. Then it is a tuning problem — adjusting the ICP relevance check, refining the routing logic, calibrating the sequence templates per signal type. Those are the right problems to be solving. They are not the problems most orgs are solving today.

When the Decay Curve Doesn't Apply​

Two cases where the framework above is wrong, and you should ignore it:

Enterprise deals with named-account orchestration. If you are selling a $500K ACV product into 200 named accounts and the buying cycle is 9 months, signal speed matters less than signal pattern. A cluster of signals across a buying committee over six weeks is more valuable than one signal worked in 15 minutes. The decay curve is real but its slope is much flatter.

Categories where the buyer's evaluation is sequential, not parallel. A few highly regulated verticals (some healthcare, some defense, some public sector) still procure one vendor at a time. Speed helps, but not at the speed-to-lead end of the curve. Quality of the first conversation matters more than the time-to-first-conversation.

If your business is neither of these, the curve applies and you should be designing around it.

What This Looks Like in MarketBetter​

We built MarketBetter because the signal-decay problem is the single most expensive workflow gap in modern B2B sales. Visitor identification, signal capture, routing, draft generation, escalation, and sequencing all live in one place — so the minute-0 to hour-1 window is enforced by the platform, not by your ops team writing Slack reminders.

The shorthand we use internally: competitors tell you WHO. We tell you WHO, WHAT TO DO, and WHEN IT EXPIRES.

If you want to see what the four-tier response window looks like running against your own signal data, book a 20-minute walkthrough — bring a week's worth of signals and we'll plot your team's actual decay curve in the call.

Sources​

Cited and consulted in this piece:

• InsideSales / MIT speed-to-lead study (2011, replicated 2017)
• Salesforce State of Sales (multiple years, response-time data)
• Drift Conversational Marketing Benchmark Report (2019)
• HBR, "The Short Life of Online Sales Leads" (Oldroyd, McElheran, Elkington)
• ChiliPiper, "The Speed-to-Lead Study" (2022)
• 6sense, "B2B Buyer Experience Report" (2023)
• Gartner, "The Future of B2B Buying" (2024)
• Internal pipeline data from 14 MarketBetter customer engagements, anonymized (2024–2026)

Related reading from our signal cluster: the 4-question signal triage rubric for what to do in the first 30 seconds, signal-to-meeting in 24 hours for the end-to-end workflow, visitor ID to first outreach in 30 minutes for the setup mechanics, and the complete guide to B2B intent data for the broader category.

Here is the pattern every signal-based selling rollout follows:

• Week 1: SDRs are excited. New tool, new dashboard, fresh alerts in Slack. Outreach goes up.
• Week 2: Reply rates aren't materially better than the old list. Reps notice they're chasing signals that look hot but go nowhere.
• Week 3: Slack channel mutes. Alerts get ignored. Reps revert to working their old account list.
• Week 4: Manager asks why the new stack isn't producing meetings. Vendor blames "process." Rep blames "data quality." Nothing improves.

We've now seen this loop in healthcare IT staffing, education technology, EHS compliance, and a dozen other categories. The diagnosis is almost always the same — and it isn't the signal source.

The problem is that SDRs are receiving signals faster than they can decide what to do with them, and no one ever taught them how to triage. They get 40 alerts a day. Half are noise. They have no rubric, so they default to the worst one: "pick whichever logo looks coolest."

The fix is not more signals. It's not better routing. It's a 30-second mental rubric every rep applies to every signal before any outreach happens. We'll walk through it below.

If you haven't yet read it, the buying signal hierarchy framework is the input to this rubric — it ranks signals by closed-won correlation. Triage is what happens after a signal is captured and before a rep opens a sequence.

Why "Just Work the Signals" Fails​

The default playbook most teams roll out goes like this:

1. Buy or build a signal source (visitor ID, intent data, job-change alerts).
2. Pipe alerts into Slack.
3. Tell reps to "work them."
4. Hope.

The hope is doing all the work. Here's what reps actually experience:

• A Slack alert fires: "Acme Corp visited /pricing 3 times this week."
• The rep has no idea if Acme is in ICP, who to contact, what context to use, or whether the visit was a junior intern or a buyer.
• The rep either guesses (and burns the account on a generic email) or skips it (and the signal dies).

In a recent breakdown of why these rollouts fail in 90 days, we found that the absence of a triage step was the single biggest predictor of adoption collapse. Reps don't need more signals. They need permission to say no to bad ones — and a structured way to do it fast.

The 4-Question Rubric​

A working rubric has four properties: it's fast (under 30 seconds), repeatable (any rep can apply it), explicit (no judgment calls left ambiguous), and binary (each question is yes/no). Here is the version that has held up across SDR teams we work with.

Question 1: Is the account in ICP — right now?​

Not "could be in ICP someday." Not "matches some firmographic filter." Right now. Industry, employee count, geography, tech stack, funding stage. If you can't answer yes in five seconds using the signal payload + your enrichment data, the signal is automatically deprioritized — not killed, just deprioritized.

This question alone removes 40-60% of incoming signals in most teams. Pure ICP filtering at the signal layer is what your signal stack architecture should be doing automatically, but reps still need the explicit check because automation misses things.

Default action if NO: Save the account to a nurture list. Do not sequence today.

Question 2: Is this a buying-window signal, or a research signal?​

This is the question almost no rep asks, and it's the one that separates 4% reply rates from 18% reply rates.

A research signal means the account is aware of the category. Examples: visited your blog, read a comparison article, downloaded a whitepaper, watched a webinar. They are educating themselves. Reaching out now and asking "want to book a demo?" is too early — they're not buying, they're learning.

A buying-window signal means the account is evaluating solutions or experiencing a triggering event. Examples: pricing page visits (especially repeat), competitor review reads, demo requests on adjacent tools, new VP of Sales hired, recent funding round, RFP language posted to a job description, integration page visits, sales tax/security/compliance page visits.

The difference matters enormously. Map this against the buying signal hierarchy — Tier 1-2 signals (pricing visits, demo requests on adjacent tools, RFP-language job posts) are buying-window signals. Tier 4-5 (blog visits, generic content downloads) are research signals.

Default action if RESEARCH: Add to a slow-drip educational sequence. Do not call. Do not pitch demo.

Default action if BUYING: Proceed to Question 3.

Question 3: Is there a credible point-of-contact for this signal?​

Even a great buying signal goes nowhere if the rep is reaching out to the wrong human. A "pricing page visit from Acme" tells you nothing about who visited. The triage question is: based on what we know about the account, can we identify a credible buyer or buying-committee member to contact in the next 10 minutes?

"Credible" means three things:

• The role plausibly cares about the problem you solve (VP of RevOps, Director of SDRs, Head of Demand Gen — not a junior analyst).
• You have a verified work email or LinkedIn that you can reach them on.
• You have enough context to say something more specific than "saw you visited our site."

If you can't pass all three, you have a routing problem, not a signal problem. Either invest in better contact enrichment or build your account-to-contact mapping into the signal capture layer so reps don't have to do this work cold.

Default action if NO: Send to a research/enrichment task queue. Do not attempt outreach until contact is identified.

Question 4: What is the most specific opening line you can write — without the word "noticed"?​

This is the disqualification question, and it's the one that catches lazy outreach.

If the best opening line you can write is Hi {{first_name}}, I noticed you visited our pricing page — the signal is not actionable. You're going to write a forgettable email, the prospect is going to ignore it, and the signal will die unconverted.

A passing answer looks like a sentence that references something specific to this account and signal that an automated tool could not have written: a competitor they're using, a recent press release, a job posting language that implies the pain you solve, a podcast quote from their VP, a LinkedIn post they made last week.

If you can write that sentence in under a minute, the signal passes. If not, the signal goes to a nurture sequence, not a 1:1 outreach attempt. The funnel math from our Monaco Corner experiment was unambiguous: outreach with a specific opening converts 4-6x what generic signal-triggered outreach does.

Default action if YES: Sequence within 4 hours per the signal-to-meeting 24-hour workflow.

Default action if NO: Park the account in a nurture queue and revisit when a stronger signal lands.

The Decision Matrix​

Here is the rubric collapsed into a routing matrix you can paste into a Slack pinned message or your CRM playbook field:

Notice that only one row triggers active outreach. The point of the rubric is to make the "no" decision easy and guilt-free, so reps stop sequencing weak signals out of fear of "missing it."

How to Roll This Out Without Reps Hating It​

Three rules that determine whether the rubric sticks.

1. Make it a 30-second check, not a 10-minute exercise.

If applying the rubric takes longer than the outreach itself, reps will stop using it. Use a tiered routing layer to auto-answer Q1 (ICP) and Q3 (contact) before signals ever hit a rep. That leaves them with Q2 and Q4 — the two that actually require human judgment.

2. Build the matrix into your CRM, not a Notion doc.

Reps will not consult a Notion page mid-flow. Put the four questions as required fields on the signal-triggered task. Pre-populate Q1 and Q3 with system data. Force a yes/no on Q2 and Q4 before the task can be marked actioned. This sounds bureaucratic. It's not — it's the difference between rubric-as-policy and rubric-as-reality.

3. Review nurture decisions weekly, not outreach ones.

Most managers review what reps did — outreach sent, meetings booked. The higher-leverage review is what reps didn't do: which signals did they nurture or park, and why? A 15-minute weekly review of the parked queue catches calibration drift (reps being too lenient or too strict) and surfaces signals that should have been actioned. This is the operational habit that keeps the rubric honest.

What Changes in Week 2 (When Most Rollouts Fail)​

The original failure pattern — Week 2 reply rates flat, Week 3 alerts ignored — looks different with a rubric in place.

In Week 2 of a triaged rollout, you should see:

• Volume of outreach down by 40-60% — fewer signals make it through the funnel.
• Reply rate up by 2-3x because the signals that do get worked are higher quality.
• Slack alert engagement up because reps trust that flagged signals are worth opening.
• A growing nurture list that the marketing team can run drip campaigns against — instead of weak signals being burned by SDR outreach and never converting.

That last point is underrated. Without a rubric, every weak signal gets burned by a single SDR email. With a rubric, weak signals get fed back into the intent data layer and warmed up properly. The economics are dramatically different.

What This Looks Like Inside MarketBetter​

If you're using MarketBetter, the rubric is partially built into the workflow. Visitor ID and intent signals fire into the platform, get scored against your ICP rules, get matched to a credible contact, and arrive at the rep with the equivalent of Q1 and Q3 already answered. The rep's job is Q2 and Q4 — and the system surfaces context (recent funding, job postings, competitor mentions) so the "specific opening line" question is answerable in seconds, not minutes.

This is what we mean when we say "tells you who and what to do." Most signal platforms tell you who. The triage question — and the answer the rep can act on in 30 seconds — is what closes the gap between alert and outreach.

If you want to see how this works end-to-end, book a demo and we'll walk through your live signal stack with the rubric overlaid.

The One-Page Version​

If you take nothing else from this:

1. Q1: Is the account in ICP right now?
2. Q2: Buying window or research?
3. Q3: Credible contact?
4. Q4: Specific opening line — without the word "noticed"?

Four questions. 30 seconds. The single biggest predictor of whether your signal-based selling investment compounds or collapses by week three.

Related reading:

• The Buying Signal Hierarchy: Tier 1-5 by Closed-Won Correlation
• The 3-Layer Signal Stack: Collection, Correlation, Action
• Signal-Based SDR Routing: Replacing Round-Robin With Intent-Tier Distribution
• Why Most Signal-Based Selling Rollouts Fail in 90 Days
• Visitor ID to First Outreach in 30 Minutes: The Setup Playbook
• Signal to Meeting in 24 Hours: The SDR Workflow
• B2B Intent Data: The Definitive Guide

Walk into any B2B sales org with more than three SDRs and ask how leads get assigned. Nine times out of ten, the answer is some version of round-robin — leads land in a queue, the queue assigns them in order, and whoever happens to be next in line gets whatever happens to come in.

This made sense in 2018. It does not make sense in 2026.

In 2018, your inbound queue was mostly demo requests. They were all roughly equivalent in intent, so dealing them out like cards was fair and approximately optimal. In 2026, your queue is half demo requests, half visitor ID hits, a quarter content downloads, a pile of LinkedIn engagement, and a long tail of newsletter clicks. The variance in actual buying intent across those signals is enormous — and round-robin treats them as identical.

The consequence: your highest-intent leads land in front of whoever's next, regardless of whether that rep is your top closer or someone you hired last Tuesday. Your worst leads also land in front of whoever's next, which means your top closer spends 40% of their week working signals that would never have converted no matter who picked them up.

The fix is signal-based routing — assigning leads to reps based on the intent tier of the signal, not the order of the queue. This post is the playbook.

Why Round-Robin Quietly Destroys Pipeline​

Three things go wrong when you assign by queue order instead of by signal:

1. Tier 1 buying intent gets junior reps. A "pricing page visited three times in 48 hours" hit lands in front of a six-week-old SDR because they happen to be next in the queue. They send a generic sequence. The buyer ghosts. By the time the senior rep would have seen it, it's already cold. You lost a deal nobody knew you had.

2. Senior reps burn cycles on low-intent noise. Your best closer spends Tuesday morning working a stack of newsletter-click leads because that's what the queue dealt them. Those leads were never going to convert in this quarter. The opportunity cost — what they could have been working instead — is what kills you.

3. Coverage becomes random. Strategic accounts get whatever rep happens to be next when the signal fires. The named-account model you built quietly evaporates because the routing layer underneath it doesn't respect it.

Round-robin optimizes for one thing — distributing volume evenly across the team — and it does that well. But pipeline isn't a volume problem. Pipeline is a conversion problem, and conversion is driven by matching the right rep to the right signal at the right time. Volume distribution is the wrong objective function.

The Five-Tier Signal Hierarchy (Refresher)​

Before you can route by tier, you need a tier system that holds up. We've published the full framework in the buying signal hierarchy post, but here's the short version:

• Tier 1 — Active buying intent. Demo requests, pricing page visits, RFP downloads, direct outreach from a buying committee member. These convert at 18–35% to opportunity within 14 days.
• Tier 2 — Account-level surge. Multiple stakeholders from the same account engaging across multiple channels in a 7-day window. Visitor ID hits with anonymous IP patterns matching your ICP. These convert at 6–12%.
• Tier 3 — Triggering events. Funding rounds, new exec hires in your buyer persona, tech stack changes that signal a replacement window. Convert at 3–7% — but the size of the deal when they do convert is usually larger.
• Tier 4 — Engagement signals. Content downloads, webinar registrations, sustained LinkedIn engagement from a single contact. Convert at 1–3% on a longer time horizon.
• Tier 5 — Noise. Newsletter opens, one-time site visits from unknown sources, generic form fills with no follow-up engagement. Convert at well under 1%.

If your team doesn't have a tier system, build that first. Routing without a hierarchy is just round-robin with extra steps. Our three-layer signal stack architecture post covers how to collect, correlate, and rank signals so tiers actually mean something.

The Routing Model: Match Rep Tier to Signal Tier​

Here's the rule we use with the teams we work with, and the rule we follow inside MarketBetter:

Three things to notice about this model:

Tier 1 deserves your best reps. The signals are the hottest you'll ever get, and the conversion math is unforgiving — a 25% close-to-opportunity rate in the hands of a senior rep collapses to 8% in the hands of a junior rep on the same signal. The talent gap matters most where intent is highest, not lowest.

Tier 4 is where round-robin still makes sense. Once you're below ~3% expected conversion, the variance between reps matters less than the simple fact of equitable distribution and SDR development time. Junior reps get reps (pun intended) on Tier 4. Senior reps get protected from it.

Tier 5 doesn't get a rep at all. This is the part most teams resist. They want every form fill to get a rep touch. Don't. Tier 5 gets a nurture stream that runs without human time, and the rare Tier 5 lead that escalates to Tier 3 or 4 behavior gets re-routed at that point. The cost of an SDR hour on a Tier 5 lead is higher than the expected value of the lead.

The Pricing-Page-Visitor Example​

To make this concrete: a contact from a $200M ARR fintech visits your pricing page three times in 48 hours, then loads your enterprise plan comparison. That's a Tier 1 signal. Under round-robin, it lands with whoever's next in the queue — say, an SDR three months into the job.

Under signal-based routing, that signal triggers an alert that goes directly to your top-quartile rep, with the 15-minute SLA clock running. The rep already has a pre-built workflow for this exact signal — research the account, identify the buying committee, run a personalized outbound within 30 minutes.

The conversion delta between those two paths is roughly 3x in our data. Same lead. Same product. Same competitive context. Only the routing changed.

If you want the full timing playbook for how to actually work a Tier 1 signal once it routes to the right rep, our signal-to-meeting in 24 hours SDR workflow is the next post to read.

Implementation: How to Roll This Out Without a Mutiny​

Sales teams hate routing changes. Reps think any change in routing is a change in compensation, and they're often right. Here's the rollout sequence that survives.

Week 1 — Define tiers, not routing. Get the team to agree on what counts as Tier 1, Tier 2, Tier 3. Don't change any routing yet. Just publish the tier definitions, post them on the wall, and use them in pipeline reviews. ("Was this a Tier 1 signal? Why didn't it convert?") Build the language before you change the system.

Week 2 — Pilot Tier 1 routing only. Pick the three highest-converting signals (usually: demo requests, pricing page visits, direct sales emails) and route them to your top quartile. Leave everything else on round-robin. Measure: how does Tier 1 conversion change? Usually you'll see 30–50% lift inside two weeks.

Week 3 — Add Tier 2. Once Tier 1 shows lift, extend the model to Tier 2 — account-level surges and named-account triggers. This is where named-account owners start getting their actual accounts back, which is also where you'll get pushback from the round-robin defenders.

Week 4 — Cut Tier 5. This is the hardest cut politically. Tell the team that Tier 5 leads now go to nurture only. Reps panic that their pipeline will shrink. It won't — the leads that were converting in Tier 5 were converting despite being worked, not because of it. They re-emerge as Tier 3/4 behavior over the next month and get routed properly then.

Week 5+ — Tune the tier definitions. The first cut of tier boundaries will be wrong. You'll find Tier 2 signals that behave like Tier 1, and Tier 3 signals that decay too fast. Adjust quarterly. Our signal-based selling rollout playbook covers the failure modes that kill rollouts at the 90-day mark — read it before you start week 1.

What Breaks (And How to Fix It)​

"Junior reps are mutinying because they're only getting Tier 4." Fair. The fix is twofold: rotate Tier 2 access on a quarterly performance basis so movement is possible, and explicitly use Tier 4 as the development track — pair junior reps with senior reps on Tier 2 calls so they're learning the muscle they'll need when they move up.

"Our top quartile is now overloaded." This is a capacity problem, not a routing problem. It means your Tier 1 volume is higher than your top-quartile bandwidth. Hire more top-quartile reps, or accept that some Tier 1 leads will route down to Tier 2 reps with a longer SLA. The mistake is going back to round-robin to "spread the load" — you're just rebuilding the old problem.

"We can't tell what tier a signal is in real time." This is the signal stack problem, not the routing problem. If your tools can't classify intent in real time, no routing model can help you. Fix the stack first. We covered the architecture in the three-layer signal stack post, and the broader buying universe in our complete guide to B2B intent data.

"Our named-account model conflicts with the tier model." It shouldn't. Named accounts always route to the account owner first, regardless of tier — the tier model only kicks in for unnamed inbound. Run both in parallel.

The Bottom Line​

Round-robin was a fair-distribution policy that pretended to be a conversion policy. In 2026, with signal variance as high as it is and SDR capacity as constrained as it is, you cannot afford to assign your hottest leads to whoever happens to be next in queue.

The math is simple: match your best reps to your highest-intent signals, protect them from low-intent noise, and put the rest of the team on a development path. The teams that do this consistently outconvert their round-robin peers by 30–50% on the same lead volume.

If you're running a signal program already and routing is still round-robin, you're capturing maybe half the value of the signal investment you've made. The other half is sitting in the wrong reps' inboxes.

For more on the underlying playbook, see our reopen closed-lost deals AE playbook for how routing logic extends to the AE side, and the Monaco Corner funnel math piece for the broader case against treating SDR pipeline as a volume game. The true cost of the SDR stack post covers what you should be spending on the signal-and-routing layer relative to seat licenses.

Want to see signal-based routing in action? MarketBetter routes leads by intent tier out of the box — Tier 1 alerts go to the right rep with the right playbook attached, automatically. Book a demo →

Most AI-sales-platform reviews are theater. A founder gets a free seat, posts a screenshot, calls it "magic," and disappears. So when Devon Hennig — captain of Ship Rats and incurable side hustler (Writhm.io, Grammar Ghosts, and a long list of prototypes) — announced he was going to document his Monaco rollout in public, week by week, with the actual numbers, that was already a more honest piece of content than anything Monaco's own marketing will produce this year.

Two episodes in, the experiment is doing something even better than promised. It's putting hard numbers on a question every VP of Sales is quietly trying to answer in 2026:

If you hand outbound to an AI-native, managed go-to-market platform — does the funnel math actually work?

Devon's documented numbers say: not yet, and not at this volume tier. That's not a takedown of Monaco. It's the most important data point AI-native outbound has produced this year, and it has direct implications for how teams should think about the SDR stack they're building in 2026.

This post is our take. We're not Monaco's competitor in the way the headlines want to frame it. We sit at a different layer of the stack. More on that at the end — first, the math.

The Setup: A Real Founder Stress-Testing a Real Product​

Here's what Devon has published on Monaco Corner so far.

Week 1: kickoff. Monaco's "forward-deployed AEs" — Shira and Hannah — onboarded him white-glove. They wrote the campaigns. They scoped the total addressable market (TAM) and came back with about 5,500 accounts that fit his ICP. They mapped signals to chase (SEO traffic decline, GEO/AIO hiring spikes — both excellent proxies for "this account just realized AI broke their content engine"). They hooked up five inboxes, each sending 20-30 emails per day, for roughly 100 emails/day or ~2,000/month total send volume.

Devon then did something almost no founder does on camera: he opened a calculator and walked the funnel math live.

He assumed roughly:

• 40% open rate (high but possible with new, warm domains and tight targeting)
• 2-5% reply rate (right at the edge of the 2026 benchmark band of ~3.4% average)
• 50% of replies positive
• 50% of positives book a meeting
• 80% show rate
• 20% close rate

Multiply that through and you need approximately 3,300 emails to produce one closed-won deal. At ~2,000 emails per month, that's roughly one customer every seven weeks — before you adjust for the fact that most of those numbers are aspirational, not earned.

Devon said the quiet part out loud: at this volume, the math is tight. Not impossible. Tight.

Week 2: the check-in. After 11 completed sequences and 607 outreaches across the five inboxes, the result was 3 replies and 1 booked meeting. And the one meeting only happened because someone replied "did you get hacked?" to a sequence — and Hannah turned that thread into a real conversation. Praise where it's due: Hannah and Shira rewrote campaigns the same day, responded over the weekend, and clearly worked their asses off. The managed-service half of Monaco is performing.

Devon then announced phase two: pitting Monaco against a traditional human lead-gen agency, "Leads That Show," whose pitch is 20 booked calls in 60 days or money back. Robots vs. humans. He calls it "Biggest Closer." It's the most useful AI-sales experiment running on the internet right now.

The Funnel Math, Honestly​

Let's sit with the math instead of explaining it away.

At 2026 benchmarks — 27.7% average open rate, 3.4% average reply rate, 5-8% reply considered strong, 10-18% elite — the gap between Devon's modeled funnel and the actual public benchmark is bigger than it looks. He assumed 40% open. Industry average is 28%. He assumed 2-5% reply. Industry average is 3.4%.

If you re-run the math at industry average instead of optimistic targets:

• 2,000 emails × 28% open = 560 opens
• 560 opens × 3.4% reply = ~19 replies
• 19 replies × 50% positive = ~9 positive
• 9 positives × 50% book = ~5 meetings booked
• 5 × 80% show = ~4 meetings held
• 4 × 20% close = less than 1 close per month

You need roughly double the volume to clear a customer per month at industry-average performance. And here's the structural problem: doubling volume isn't free. Each additional inbox needs a warmed domain, a real persona, and clean deliverability hygiene — or your reply rate craters and you're worse off than you started.

Now layer on TAM. Devon's TAM is ~5,500 accounts. At 2,000 emails per month per his current setup, he'll cycle the entire TAM in about 11 weeks. After that, the funnel doesn't scale by sending more — it scales by sending better to the same accounts, which is an entirely different problem than the one Monaco is solving on day 1.

This is the bind every managed-service AI-CRM model is about to discover, and it's not unique to Monaco. It would be the same with 11x or Artisan if they ran the same experiment publicly:

1. The inbox ceiling is real. Five inboxes at 20-30/day is roughly the responsible ceiling on a single brand before deliverability degrades. Going to 10 or 20 inboxes requires domain diversification, which means more brands, more provisioning, more babysitting. Volume doesn't scale linearly with the platform — it scales with operational overhead.
2. Narrow TAMs starve volume models. A 5,500-account TAM is sharp targeting (good) but small (challenging for a volume-based send model). The platform's economics work better at TAMs of 50,000+. Devon's TAM is 10x smaller than the model wants.
3. Reply quality is more sensitive to message than to send volume. When 1 of your 3 replies in two weeks comes from someone asking if you got hacked, the system isn't broken — it just hasn't found the angle yet. That's a campaign problem, not a volume problem. Pouring more emails through the same angle doesn't fix it.

The honest verdict on Devon's first two weeks: the managed-service team is doing the work, the platform is sending, the math is just hard. He could absolutely turn the corner — Hannah and Shira are clearly competent and the iteration speed is real. But the funnel math is telling you something about the shape of this category that nobody who's selling AI outbound platforms wants to say out loud.

What This Tells Us About the Shape of the 2026 Outbound Stack​

The Monaco Corner experiment is forcing a useful question: when you buy an AI-native sales platform, what are you actually buying?

You're buying three different things bundled together:

1. A database + signals layer. TAM building, account scoring, intent overlays, signal capture.
2. An execution layer. Inboxes, sequences, send orchestration, reply handling.
3. A managed-service layer. Humans who write the campaigns, iterate, and handle the messy edges.

The bundle is appealing for founders without sales backgrounds — Monaco's stated ICP — because it removes every lever they don't know how to pull. But the bundle is a problem for teams that already have SDRs, already have inboxes, already have an opinion about messaging, and already have a CRM they're not going to rip out.

For those teams, you don't want layers 2 and 3 from a vendor. You want layer 1, sharper and faster than you can build it yourself, and you want layer 2 to fire when layer 1 sees something, not on a generic cadence.

That's where signal-based selling actually wins — and where most rollouts also quietly fail when the platform doesn't translate signals into a specific SDR action within the same day.

Where MarketBetter Sits (And Where We Don't)​

We are not "a better Monaco." We're not a managed-service AI sales platform. We don't run your campaigns for you and we don't hire forward-deployed AEs to sit inside your team. If that's what you want — and there are real reasons a founder might want exactly that — Monaco is a serious option and Devon's experiment is the best public data you can find on whether it lands for your shape of company.

MarketBetter is the signal-to-action workflow layer for teams running their own outbound. Concretely:

• You bring your own inboxes. Whatever you're already sending from, however many domains you've already warmed, MarketBetter doesn't replace that fleet. We orchestrate on top of it.
• You bring your own CRM. Salesforce, HubSpot, Attio — we plug in, we don't ask you to migrate.
• We surface the WHO + WHAT TO DO in real time. Visitor identification, intent signals across third-party data, hiring signals, technographic shifts — layered into a single signal stack — then turned into a daily playbook each rep can actually work.
• We tell your SDRs which 3% of your TAM is in-market today, so they spend their day on the accounts where reply math actually pencils out, instead of cycling 2,000 cold emails through a 5,500-account list and hoping.

Said differently: Devon's experiment is showing you what AI looks like when it owns the whole funnel. MarketBetter is what AI looks like when it owns the decision layer and leaves the execution layer to the humans who already have it set up.

Honest takes on managed AI-CRM models like Monaco, while we're being honest:

• Where managed works: founders with no sales infrastructure, no SDRs yet, no inbox fleet, and a willingness to outsource the entire GTM motion. The white-glove activation Devon is getting from Hannah and Shira is genuinely valuable for that buyer.
• Where managed hits a wall: narrow TAMs (under ~20K accounts), teams with existing SDRs and CRM investments, and any company that wants to A/B their own messaging and own their own pipeline reporting end-to-end.

That second buyer is who MarketBetter is built for. Different shape, different sale, different best customer. Both can exist.

The Watch-List for Devon's Next Episodes​

Things we'll be watching as Monaco Corner unfolds:

1. Does volume increase? If Monaco pushes Devon past 5 inboxes, watch deliverability and reply rate together. Going to 10 inboxes without a reply-rate drop is the real proof point.
2. Does the message iterate? The "did you get hacked?" reply is a gift — it's telling Hannah exactly what's off. Week 3-4 messaging changes will reveal how fast the managed-service iteration loop actually closes.
3. Does the agency beat the AI? Liam at Leads That Show is offering 20 calls in 60 days, money-back. If a traditional human agency wins this head-to-head, it's not a death sentence for AI outbound — it's a signal that AI-native still needs human iteration to close the funnel-math gap, which is also our thesis.
4. What does week 8 look like? TAM cycle time matters. Once Monaco has touched the full 5,500 accounts, the question stops being "how do we send more" and starts being "what do we do with the accounts that already saw us." That's the signal-loop problem, and it's the harder problem.

We'll write that follow-up when the data is in.

The One-Line Take​

AI-native outbound platforms aren't broken. The funnel math just doesn't bend the way the pitch decks suggest, and the first honest public experiment is making that visible. The teams who win in 2026 will be the ones who treat AI as a signal-to-action layer on top of their existing motion — not a managed service that replaces the motion entirely.

Devon Hennig deserves the credit here. He's the rare operator running the experiment in public, with real numbers, on a real budget. If you're a VP of Sales evaluating any AI sales platform in 2026 — Monaco, 11x, Artisan, Apollo, Common Room, Warmly, or any of the rest — watch Monaco Corner. The data is doing the talking.

For the deeper read on how we think about this, see our earlier honest write-up: MarketBetter vs Monaco for B2B Sales Teams and the longer Monaco Sales Platform Review 2026.

Running your own outbound on your own inboxes, but tired of cycling cold accounts and hoping? That's the gap we close. We tell your reps which accounts are in-market today and what to do about it — without taking over your campaigns. Book a demo →

Every VP of Sales we talked to in Q1 2026 was buying into signal-based selling. By Q2, most of them were quietly pulling the plug.

Not because the thesis was wrong — buyer signals genuinely do predict pipeline. The thesis is fine. The rollouts are broken.

Here's what actually happens. A signal tool gets purchased in January. Twenty SDRs get a training session in February. Slack alerts start firing in March. By April, the SDR team is back to running the same flat outbound sequences they ran before, and the tool sits as a $48K/year line item that nobody opens. The VP of Sales doesn't kill it — that would be admitting it failed — so it just rolls into next year's renewal and quietly dies.

We've watched this pattern in over a hundred teams now. The failure modes are predictable. So is the fix.

This is the 90-day rollout playbook that actually changes SDR behavior, in four phases. Read this before you cut the PO.

The Four Failure Modes Every Signal Program Hits​

Before the playbook, the pathology. Signal-based selling rollouts die for four reasons, almost always in this order:

1. Tool stacking instead of architecture. The team buys a signal tool but already has Bombora, ZoomInfo, Apollo, and a visitor ID vendor. Now they have five signal sources, no ranking, and SDRs who get 40 alerts a day across five inboxes.

2. No signal hierarchy. Every signal is treated as equally important. A demo request and an ad click both show up as "an alert." SDRs spend the same energy on Tier 5 noise as on Tier 1 buying intent. Not all signals predict closed-won deals equally — but the program is structured as if they do.

3. No behavior change in the SDR seat. Reps were told the program would "make their day easier." Instead it added a new tab to open, a new dashboard to check, and zero changes to their compensation, their cadence templates, or their pipeline reviews. So they ignore it.

4. No measurement loop. Nobody is tracking whether signal-sourced opportunities convert better than cold ones. After 90 days the VP has no evidence that the program is working, so when the budget conversation hits, the tool gets cut.

Every failed rollout we've seen tracks back to at least three of these four. The playbook below is built specifically to defuse all of them in order, on a four-phase timeline.

Phase 1 (Days 1–14): Pick the Layer, Not the Tool​

The first failure mode — tool stacking — happens before the SDRs ever see a signal. It happens in the procurement conversation.

When most teams "implement signal-based selling," they buy a signal tool. That's the wrong unit of decision. The right unit of decision is the layer of the signal stack you're operating in.

There are three layers: collection (where signals come from), correlation (how they get scored and joined to accounts), and action (what gets pushed to the SDR seat). Most stacks are heavy on collection and empty on action. You don't need another collection tool. You need a correlation layer.

In Phase 1, do exactly these four things and nothing else:

• Audit existing signal sources. Pull every tool that fires an alert into a spreadsheet. Bombora, 6sense, Apollo, ZoomInfo, your visitor ID vendor, LinkedIn Sales Navigator, your CRM activity log. Most teams find 6–8 sources they're already paying for.
• Tag each source by signal tier. Map each one against the closed-won signal hierarchy. Demo requests are Tier 1. Visitor ID with intent is Tier 2. Job changes are Tier 3. Surge topics are Tier 4. Ad engagement is Tier 5.
• Identify the missing layer. If you have 6 collection tools, you don't need a 7th. You need correlation. If you have correlation but no action layer, that's the gap.
• Pick one tool that fills the layer. Not five. One. The wrong move is to buy the most-features platform. The right move is to buy the thing that fills your specific hole.

The output of Phase 1 is a one-page document that says: Here are the 6 signal sources we already have, here's how they rank by predictive value, and here's the one thing we're adding to make them usable. If you can't write that document in 14 days, you're not ready to roll out anything.

Phase 2 (Days 15–45): Build the Action Layer Before You Tell SDRs​

This is where most rollouts already go off the rails. The signal tool gets configured by RevOps, Slack alerts get turned on, and the SDRs get a 30-minute training on "the new signals dashboard." Three weeks later, the alerts are muted.

The fix is to build the action layer before SDRs see any alerts. The action layer is the thing that takes a signal and produces a specific instruction: Sarah from Acme Corp visited the pricing page twice this week, here's the 4-line LinkedIn message to send her by 11am.

Action layer beats dashboard every time. SDRs don't need more data — they need to know who to contact, when, and what to say. Until you can produce that instruction reliably, don't turn the alerts on.

What to do in Phase 2:

• Define your three "must-act" signal patterns. Not 15 patterns. Three. Examples: (a) named account visits pricing page + has open opportunity, (b) champion of past customer changes jobs to ICP company, (c) new G2 review mentions a competitor we displace. Three patterns, written down, with a named owner.
• Write the SDR playbook for each pattern. For pattern (a), what's the message template? What's the LinkedIn approach? What's the cadence if no response? Write it. Test it on five accounts manually before automating anything.
• Decide the SLA. Is the SDR expected to act within 1 hour? 4 hours? 24 hours? Pick a number. Without an SLA, "act on signals" becomes "act on signals whenever you feel like it."
• Pre-wire the alert delivery. Signals should land in the channel SDRs already live in. If your team works out of LinkedIn and Salesforce, that's where alerts go. Not a new Slack channel they haven't opened yet. Not a new dashboard URL.

The output of Phase 2 is three signal patterns, three written playbooks, one SLA, and a delivery channel that already exists. Now you're ready to actually involve the SDRs.

Phase 3 (Days 46–75): Change the SDR Seat, Not Just the Toolkit​

Failure mode #3 is the one that kills the most programs and surprises the most VPs. The math is uncomfortable: you can drop the world's best signal tool on top of an unchanged SDR workflow and nothing will happen.

If reps are still measured on dials per day, they'll keep dialing the same lists. If their cadences still start with a generic "checking in" email, they'll keep using it whether the signal is hot or cold. If the pipeline review still asks "how many meetings did you book?" without asking "what % came from signals?", the program is invisible to the people doing the work.

Phase 3 is about behavior change at the rep level. Three moves:

Move 1: Replace activity quotas with signal-response quotas. Don't kill activity tracking entirely — but the headline number on the dashboard changes. Instead of "150 activities per day," it's "respond to 80% of Tier 1 signals within SLA." This is the single highest-leverage change. It rewires what reps optimize for overnight. (The traditional SDR metric stack needs an overhaul anyway.)

Move 2: Rebuild cadence templates around signal context. A signal-sourced touch should not look like a cold touch. The opener references the signal — "Saw your team posted three Salesforce admin roles this week" — and the cadence is faster and shorter. Three touches in five days, not eight touches in 21 days. Train the team on this in a live working session, not a slide deck.

Move 3: Add a signal column to pipeline reviews. Every weekly pipeline review now has a column: signal source. Was this opportunity sourced from a signal, or was it cold outbound? Within 60 days you'll have data on which channel actually produces revenue. Within 90 days that data becomes undeniable, and the program defends itself.

The output of Phase 3 is a different-looking SDR week. Less dialing, more responding. Shorter cadences for signal-sourced contacts. A pipeline review that knows the difference between signal-sourced and cold opportunities. If your SDRs' days look the same on day 75 as they did on day 1, the program has already failed and you just don't know it yet.

Phase 4 (Days 76–90): Close the Loop With Data​

Failure mode #4 — no measurement — is the one that kills programs at renewal time. The CFO asks: what did we get for $48K? The VP of Sales says: the reps love it. The CFO says: cut it.

Phase 4 is the answer to that conversation. By day 90, you need a single dashboard that answers four questions:

1. What % of meetings booked this quarter came from signal-sourced contacts?
2. What's the conversion rate of signal-sourced opportunities to closed-won, vs. cold outbound?
3. What's the average deal size of signal-sourced deals vs. cold?
4. What's the SLA compliance rate — what % of Tier 1 signals got an SDR response within the defined window?

These four numbers, on one page, every week. Not a 12-tab spreadsheet. Not a Looker dashboard nobody opens. One page.

The pattern we see in successful rollouts:

• Signal-sourced meetings convert 2–3x better than cold outbound. Not because signal tools are magic, but because the buyer is already in market.
• Signal-sourced deals are 20–40% larger. Same reason — these are buyers with active projects, not lukewarm tire-kickers.
• SLA compliance starts at 40% and climbs to 75% by week 12. If it doesn't climb, your Phase 3 behavior change didn't take.

If the numbers come in below those benchmarks, you have a diagnosable problem — wrong signal hierarchy, broken action layer, or unchanged SDR behavior. You can fix any of those. What you can't fix is a program with no measurement, because by the time you notice it's failing, it's already been cut.

The Pattern: It Was Never About the Tool​

Notice what didn't show up in any of the four phases: a recommendation for a specific signal vendor.

That's deliberate. The vendor question is downstream of the architecture question, and the architecture question is downstream of the layer question. Get those right and almost any competent vendor in your chosen layer will work. Get them wrong and the most expensive vendor on the market will still die in your stack by day 90.

The teams that win with signal-based selling in 2026 share three traits we've seen consistently:

• They run a lean signal stack — not the most tools, the right tools, with a clear ranking. The math on signal stack spend is brutal once you add it up.
• They invest more in the action layer than the collection layer. Most teams do the opposite.
• They change the SDR scorecard to match the new motion. The reps follow the scorecard. Always.

Everything else is theatre.

What to Read Next​

If you're serious about getting this right, work through these in order. They're built to be read as a cluster:

• The Buying Signal Hierarchy — Which of the 14 most common B2B signals actually predict closed-won. Read this before you tag your existing signal sources in Phase 1.
• The 3-Layer Signal Stack — Collection, correlation, action. The framework Phase 1 is built on.
• Signal to Meeting in 24 Hours — The SDR-level workflow that maps to Phase 2's action layer.
• Visitor ID to First Outreach in 30 Minutes — A concrete worked example of one signal pattern, end-to-end.
• The True Cost of an SDR Stack in 2026 — Use this to justify killing redundant collection tools in Phase 1.
• The Best Website Visitor Identification Tools, 2026 — If visitor ID is the layer you're missing.
• Best Warmly Alternatives in 2026 — If you already have a visitor ID tool and want to compare.
• Reopening Closed-Lost Deals — A signal pattern most teams overlook.

How MarketBetter Plugs In​

A note on the obvious. MarketBetter sits in the action layer of the signal stack — the part most teams under-invest in. We take the signals your existing collection tools already produce (Bombora, your CRM, your visitor ID vendor, job change feeds, G2) and produce the specific instruction an SDR needs: who, when, what to say.

We don't replace your collection tools. We make them usable.

If you're in Phase 1 of a rollout and you're realizing the gap in your stack is the action layer, book a 20-minute demo. We'll walk you through what a signal-sourced SDR day actually looks like in our platform — and if it's not a fit, we'll tell you which layer of your stack to fix first instead.

The fastest way to fail a signal-based selling rollout is to skip the architecture and buy a tool. The fastest way to succeed is to read this article before signing the PO.

Most "visitor identification" rollouts die the same way. A RevOps lead buys a tool in March, IT signs the data-processing addendum in April, the script ships in May, the SDRs ignore the dashboard in June, and by July everyone agrees the tool "didn't work." Then the next vendor gets pitched the same problem and the cycle restarts.

The dirty truth: identifying anonymous visitors is a 30-minute job. Doing something with the identification is where every team falls down — and that part has nothing to do with the vendor you picked. It's a workflow problem masquerading as a tooling problem.

This post is the antidote: a six-block, 30-minute playbook that takes a B2B team from "zero visitor data" to "first personalized email going out the door." Every block has a clear output. If you can't finish a block in five minutes, you have the wrong problem, not the wrong process.

Every B2B revenue team has the same dirty secret right now: their "signal stack" is just five SaaS tools sending alerts into five different Slack channels, and the SDRs have muted four of them.

Bombora is firing surge alerts. 6sense is flagging accounts in the buying journey. Apollo is pinging job changes. Warmly is identifying visitors. ZoomInfo is pushing intent topics. And somewhere in the middle of all that noise, an SDR is supposed to figure out which of the 400 alerts they got this week deserve a real human response.

Spoiler: they pick the ones from the loudest dashboard. Or they pick none of them.

The problem isn't that signals are bad. Signals work — when they're ranked correctly. The problem is that almost nobody has the architecture to turn raw signals into prioritized action. They have a pile of tools, not a stack.

This post is the architecture. It is a three-layer model — collection, correlation, and action — that we have watched separate the teams who get demos from signals and the teams who just get more alerts.

Every signal vendor will tell you their signal is the one that matters. Bombora wants you to believe surge data is the leading indicator. LinkedIn Sales Navigator wants you to believe job changes are. 6sense wants you to believe their AI-blended score is. Lead Forensics wants you to believe it is anonymous website visits.

They cannot all be right. And after sitting next to dozens of B2B sales teams over the last year — watching which signals their reps actually convert from and which ones get ignored — we built the only thing that has ever mattered for an SDR: a hierarchy. A ranking of signals from the highest probability of closing to the lowest.

This post is the framework. It is opinionated. It is built from real deal motions, not vendor decks.

If you ask a vendor what their software costs, you will get a number. If you ask a finance team what the same software actually costs after 12 months, you will get a different number. Sometimes by 3x.

We have spent the last six months publishing pricing breakdowns on more than fifty SDR tools — Apollo, Salesloft, Outreach, ZoomInfo, Clay, Nooks, Lead Forensics, Warmly, Common Room, Lavender, 6sense, and dozens more. Every breakdown started the same way: pull the website price, add the hidden fees from Vendr and G2 reviews, then run it across a real team size.

This post pulls all of that together. It is the pillar version. The thing we wished existed when a customer asked us last week, "what should I budget for ten SDRs?"