HomeFind your caseWe send outbound, but it books no meetings

Case · GTM

A common situation · not a client story

We send outbound, but it books no meetings.

B2B companies with a product that works for its current customers, running cold email or LinkedIn outreach that brings few replies and fewer meetings.

Usually seen inCold email and LinkedIn outreach
First testWhere your emails land
PracticeGTM

What you're probably seeing

If this sounds familiar, you're in the right place.

  • Plenty of sends, few replies, and most replies are out-of-office messages.
  • Bounces climb, or emails land in spam and promotions folders.
  • The replies that do come in are from the wrong people or the wrong companies.
  • Interested replies wait a day or more for an answer.
  • Nobody can say which list, message or step produced the meetings you did get.

The usual ways out

What teams usually try. Each works somewhere. None works everywhere.

The wayWorks whenThe catch
Send moreThe list, inbox placement and message already workMore sends multiply bounces and spam complaints
Buy a new toolThe current tool is the bottleneckIt rarely is; the list and the message move with you
Rewrite the copyEmails reach the inbox and get readCopy can't fix an unverified list or a spam folder
Buy a bigger listYour market is under-coveredUnverified addresses damage your sending domains
Hire an SDR or an agencyThe system works and needs more handsThey inherit the same broken parts
Warm intros and referralsYou have a network in the marketDoesn't scale on its own

What other companies did. Their published results, not ours.

We read each company's own write-up and asked one question: would our diagnostic's tests have led to the same call? We judge the approach, not the result.

CompanyWhat they didWhat they publishedSource
SaaStrB2B events and media company with a large database of past sponsors and attendees. Outbound sold event tickets and sponsorships. Before the AI tools, human reps sent 75–285 emails a month, and SaaStr moved the budget for two human SDRs to AI.Ran an AI SDR tool (Artisan) for outbound. About 90% of contacts came from its own database, not bought lists. It waited out a 2–3 week inbox warm-up, uploaded fresh contacts up to twice a week, and routed replies to humans.Over six months: about 19,850 messages sent (under 2,000 by humans in the same period), 6.7% response rate, 4% positive response rate. Outbound AI produced 10% of SaaStr London ticket revenue. No outbound meeting count given.They noted: In weeks when the founders gave it more time, response rates rose 10–20%. The warm-up felt slow but was needed. Stopping the same contact being emailed by several AI agents was manual work.6 Months of AI SDRs: What's Worked, How They Brought In $1M+ in 90 Days, and the Real Data Everyone's Asking ForNov 2025
Verkada (EMEA team)Cloud physical security company selling to multi-site organisations in 80+ countries. The EMEA growth team covered 28 European countries, each with different data vendors and privacy rules.Replaced a single US-tuned email validator with layered regional validators and multi-source enrichment. Then used its own first-party data (past emails, call transcripts, lost deals) to choose and route outbound targets, because third-party intent data was mostly unusable under European privacy rules.Data coverage rose from 50% to over 80%. Email validation accuracy above 95%. About 10% of email waste removed. Outbound reply rate doubled from the first-party signal workflow. No timeframes or baselines dates given.They noted: Before the change, 15% of emails marked as validated still bounced, because the US-tuned validator gave false positives on European email providers.How Verkada GTM team expanded in 28 European countries using ClayUndated · vendor story
RipplingHR, spend and IT platform with tens of thousands of customers. A 30-person growth team was asked to double the cold email channel, which meant hundreds of thousands of personalised emails a month.Built a pipeline that enriches leads, stores them in Snowflake and pushes personalised sequences into Outreach, with more than 12 message variants. Team members test new copy without engineering help.Cold email performance doubled year over year in 2023. The page does not define which metric doubled.How Rippling uses Clay to scale growth experiments and email personalizationUndated · vendor story

Our read

Reasonable call. One thing showed up late. The clearest gains started with the list and the inbox, but most write-ups report one end number, so it is hard to tell which stage was leaking.

Clay's customer story on Verkada says 15% of emails its old validator passed still bounced, and fixing verification came before its reply-rate gain (which the story credits to its first-party signal workflow); that is what our first test checks. SaaStr bought a tool, but its write-up credits its own database, a warm-up period and human reply handling, and it gives no outbound meeting count, so the reply-to-meeting stage is not measured. Rippling reports a doubling of cold email performance without saying whether that means opens, replies or meetings, or anything about bounces and inbox placement.

What we would test first: Count how many sent emails bounce, and check whether the addresses were verified before sending.

What the diagnostic would test

The tests that rule the wrong ways out.

On your own systems and data, read-only first. The number of tests sets the diagnostic's price, quoted before it starts.

  1. 1

    Sent to delivered: how many addresses bounce, and were they verified?

  2. 2

    Delivered to inbox: which folder your emails land in, at the major providers.

  3. 3

    Inbox to read: the sender name, the subject and the first line.

  4. 4

    Read to reply: is the problem you describe one the reader actually has?

  5. 5

    Reply to interested: is the offer worth a reply?

  6. 6

    Interested to meeting: how fast, and how well, replies are handled.

This week, without us

Three things you can do yourself.

  1. 1

    Run your list through an email verification tool before the next send.

  2. 2

    Send your sequence to test inboxes at the major email providers, and see which folder it lands in.

  3. 3

    Read every reply from the last month and sort them: auto-reply, interested, not now, not interested, wrong person.

Sound like you? Bring it to a 30-minute call. We'll tell you which tests your case needs, and what they cost.

Back to every case

This page describes what teams in this situation commonly face. It is not a client story.