How StoneHaven Drove $1M+ in New ARR From Cold Outbound for a Mid-Market B2B SaaS Platform

The numbers

The company

The client is a mid-market B2B SaaS platform with real pipeline pressure and a sales team that needed predictable meetings on the calendar. They were already running outbound. The problem was that they were running all of it the wrong way.

Everything went out through a single inbox on the company's main domain. Volume capped at roughly 8,000 emails a month. Replies sat at 1.1%, about 88 a month, which converted to only 3 to 4 booked meetings. For a company that needed pipeline to scale, that was not close to enough.

The challenge

The volume problem was the obvious issue. The reputation problem was the dangerous one.

Sending cold volume off the primary corporate domain was eroding the domain's sending reputation. As that reputation degraded, the damage spread past the cold campaigns. Internal email and customer email started landing in spam. So the same channel that was supposed to generate pipeline was quietly making it harder for the company to talk to the people it already did business with.

That left the client stuck. They needed far more outbound volume to hit pipeline targets, and every additional cold email off the main domain made the reputation problem worse. There was no safe way to scale from where they were.

The process

StoneHaven rebuilt the entire sending operation off the client's main domain and onto isolated infrastructure. No cold volume ever touched the primary domain again, which let corporate reputation recover on its own while the new system did the heavy lifting.

1. Infrastructure and deliverability. StoneHaven stood up 25 dedicated sending domains carrying 600 inboxes, fully separated from the client's corporate domain. The stack was diversified across three infrastructure types so no single point could take the whole operation down:

• A primary enterprise mail provider as the bulk workhorse: 5 domains, 500 inboxes, around 90,000 sends a month.
• A premium mail provider for C-suite and top-tier segments: 10 domains, 50 inboxes, around 20,000 a month.
• Dedicated SMTP as a volume buffer: 10 domains, 50 inboxes, around 13,000 a month.

SPF, DKIM, and DMARC were configured and verified on all 25 domains before a single email went out. That groundwork produced 98% inbox placement from the very first send.

2. Warmup and sending discipline. Each infrastructure type got its own warmup over 2 to 3 weeks. Sending stayed inside safe per-inbox caps the entire way. Spam complaints were held under 0.3% and bounce rate under 7%, the two thresholds that burn domains.

3. Domain rotation. At 120,000 sends a month, 10 to 20% of domains degrade in any given month. StoneHaven kept a 20 to 25% warmed reserve on standby and swapped any burning domain within 1 to 3 days. The result was zero days of lost sending across the engagement.

4. Copy and sequencing. Emails were plain text, spintax kept every send unique. The cadence was a 5-touch sequence. Around 50 to 70% of booked meetings came from steps 2 through 4.

5. List and targeting. StoneHaven worked a total addressable market of 600,000+ contacts and re-hit it every 90 days with fresh angles, so the lists never went stale and the same contacts could be re-engaged without burning them.

The results

By the second week of campaigns, the funnel was running at steady state. Each month it looked like this:

• 120,000 emails sent produced 3,000 replies at a 2.5% reply rate.
• Those replies produced 360 positive replies, 12% of all replies.
• Positive replies produced 72 booked meetings, 20% of positives.
• A 70% show rate held roughly 50 meetings every month.
• Around 14% of held meetings closed, for about 7 new customers per month.

Over the full 6-month engagement, the totals were:

The before-and-after, side by side:

Beyond the numbers

The biggest shift was not a metric on a dashboard. It was that pipeline stopped being a gamble.

The client's corporate domain reputation recovered fully, because no cold volume ever touched it again. Internal and customer email went back to landing where it should. And the sales team's problem inverted: instead of waiting for a handful of meetings to trickle in, reps had more calls than they could comfortably take.

"We went from a few meetings a month and emails landing in spam to our reps complaining there are too many calls to take. The pipeline is finally predictable."— Head of Growth at a mid-market B2B SaaS platform

Methodology and data note

The figures in this case study come from real campaign and CRM data over a six-month engagement, anonymized to protect the client's confidentiality. Volume, reply, meeting, and revenue numbers reflect the steady-state funnel that held from roughly week two onward. Average contract value and customer counts are rounded.

FAQ

How long did it take to see results?

The funnel hit steady state by the second week of campaigns, once inboxes finished warming. From there, the system produced about 72 booked meetings and 7 new customers a month.

Why move cold sending off the company's main domain?

Cold volume on a primary corporate domain degrades its sending reputation, which pushes internal and customer email into spam. StoneHaven ran all cold volume on 25 isolated sending domains so the corporate domain was never touched, and its reputation recovered fully.

What kind of volume is safe to send?

This build ran at 120,000 emails a month across 600 inboxes, held inside safe per-inbox caps, with spam complaints under 0.3% and bounce rate under 7%. Staying inside those limits is what keeps domains alive at scale.

Does this work for B2B SaaS specifically?

Yes. This engagement was for a mid-market B2B SaaS platform and produced $1M+ in new ARR from cold outbound over six months at a ~$24,000 average contract value. The approach fits any B2B model with a large addressable market and a deal size that justifies booked-meeting volume.