← Back to Blog
Case StudyJune 6, 2026·6 min

SaaS Startup Case Study: How a 12-Person Team Booked 90 Meetings in One Quarter From Cold Outbound

By Brendan Ward

In late 2025, a 12-person B2B SaaS company building workflow automation software for healthcare operations engaged Growtoro to launch their first structured outbound program. They had no SDR team, no cold email infrastructure, and a founder doing all sales while also leading product. The goal: validate whether cold outbound could become a real channel before hiring a sales team.

The 90-day result: 92 booked discovery calls from cold outbound, 31 qualified opportunities, $310K in net new pipeline, and the data to justify hiring two SDRs in Q1 2026. The breakdown of what made it work is below — usable as a template for any early-stage B2B SaaS considering cold outbound.

The Starting Point

  • Product: Workflow automation for healthcare operations teams (revenue cycle management, prior authorization tracking).
  • Team: 12 people. Founder doing sales, 2 customer success, rest engineering and product.
  • Revenue: $1.2M ARR, 18 customers, average ACV $66K, growing 8% month-over-month inbound.
  • Sales motion: Inbound-only. Founder converting 1 in 4 inbound demos to deal.
  • Outbound prior experience: None. Founder had tried sending 50 cold emails 6 months earlier; got 1 reply.

The strategic question wasn't "should we do outbound?" — it was "before we hire 2 SDRs at $80K loaded cost each, can we prove outbound works for this ICP?"

The ICP Definition

The biggest mistake the founder had made in the prior cold email attempt: targeting "healthcare." The tightening that made the program work:

  • Vertical: Independent specialty medical groups (not hospitals, not large health systems).
  • Size: 15–60 providers (large enough to feel the operational pain, small enough to evaluate quickly).
  • Specialty: Dermatology, GI, orthopedics, women's health (specialties where prior-auth volume creates real workflow pain).
  • Role: Director of Operations, Practice Administrator, COO, or equivalent.
  • Geography: US only.

This ICP defined a TAM of approximately 4,200 specialty medical groups, with a usable target list of ~2,800 contacts after enrichment.

The Signal Layer

The conversion-multiplier on the program was overlaying buying signals on the tight ICP. The signals we tracked:

  • Recently posted job openings for revenue cycle, billing, or prior-auth roles (signals operational scaling pain).
  • Recent expansion (new location, increased provider count) per LinkedIn announcements.
  • Recent leadership change in operations or finance roles.
  • Tech stack signals (using competitor EHR/PM systems with known prior-auth workflow gaps).

The combined signal layer narrowed the active outreach list per week to ~120–180 high-priority accounts.

The Infrastructure

Standard setup, executed completely. The configuration:

  • 4 dedicated sending domains (lookalike variants of primary domain).
  • 3 inboxes per domain = 12 total sending inboxes.
  • SPF/DKIM/DMARC configured on all 4 domains (see the auth guide).
  • 30-day warm-up using a curated warm-up network.
  • Verified sending capacity: ~360 messages/day at steady state (30/inbox).
  • Inbox placement testing weekly via GlockApps.

End-of-warmup placement results: 94% Gmail primary, 88% Outlook primary, 92% aggregate. Production-ready.

The Sequence

Standard 4-email cadence following the structure in the 4-email sequence guide. The specific copy approach:

Email 1 (Day 1, 75 words): Signal-based opener referencing the specific operational role expansion or job posting, hypothesis about the prior-auth workflow pain, soft question.

Sample: "Hi Lauren — saw [Practice Name] just posted for a Prior Authorization Specialist. Usually means the team is hitting the manual workflow ceiling — somewhere around 200+ auths/week. Curious whether you're already using a system to track aging auths, or still wrestling it through spreadsheets. — Brendan"

Email 2 (Day 3, 110 words): Specific operational data point from a comparable practice, second soft question.

Email 3 (Day 6, 130 words): Concrete case from a similar specialty practice (anonymized) with specific outcome numbers + soft meeting CTA.

Email 4 (Day 10, 40 words): Breakup — "closing the loop" pattern, future-touch option.

The Sending Cadence

  • Volume: 280–320 sends/day at steady state.
  • List size per campaign: 800–1,200 prospects.
  • Campaign duration: 16–18 days per campaign (full sequence).
  • Total campaigns in 90 days: 5 (with overlapping waves).

Total sends across the 90 days: ~9,200.

The Results

Top-level numbers (90 days):

  • Sends: 9,184
  • Replies: 738 (8.0% reply rate)
  • Positive replies: 367 (50% of total replies)
  • Meetings booked: 92
  • Qualified opportunities: 31
  • Pipeline generated: $310K (avg deal size $10K — smaller than their existing avg ACV because some prospects matched lower tiers of their pricing)
  • Closed-won in 90 days: 4 deals, $42K ARR (more in pipeline at end of quarter)
  • Cost per meeting (all-in): $97

The reply rate of 8.0% was on the high end for B2B SaaS outbound — driven by the tight ICP + strong signal targeting + healthcare-specific copy nobody else was sending.

What Drove the Numbers

Three factors, in order of impact:

1. The signal layer. Healthcare operations teams in our target band are bombarded with generic vendor outreach. Signal-based opening lines that referenced a specific job posting or expansion event consistently produced replies even when the recipient had ignored 100+ prior cold emails.

2. The ICP tightness. Specialty medical groups of 15–60 providers were narrow enough that we could speak to specific operational patterns in the copy. A generic "healthcare CTO" pitch wouldn't have produced these numbers.

3. Founder availability for discovery calls. The founder protected discovery-call time aggressively. Speed-to-meeting averaged under 36 hours from reply to booked call. Founder discovery quality was a meaningful differentiator vs. SDR-led discovery.

What Didn't Work (and Was Iterated)

Iteration 1 (Week 3): Initial copy referenced "AI-powered automation." Reply rate was 5.4% — fine but below target. Iterated to remove the AI framing entirely; reply rate climbed to 8.2% in the following two-week wave.

Iteration 2 (Week 6): First-touch meeting CTA was producing 22 meetings but only 8 qualified. Shifted to soft interest-check CTA (see the CTA testing guide); per-meeting qualification climbed from 36% to 51%.

Iteration 3 (Week 8): Found that reply handling was slipping on Fridays (founder typically blocked Friday for product work). Set up a Slack alert routing Friday replies to the founder's phone, recovering meetings that would have been lost to delayed response.

The ROI Calculation

Total program cost (90 days, all-in including infrastructure, data, agency fees): $26,500.

Pipeline value generated: $310K. Even at conservative close-rate assumptions (15–20% across the next 4 quarters), expected closed-won revenue from this 90-day investment: $46K–$62K within 6 months, plus ongoing customer LTV.

Payback period: under 4 months. Pipeline ROI: 11x. Justified the SDR hire and a 2x scaling of the outbound program in Q1.

The Bottom Line

A 12-person SaaS startup with no prior outbound infrastructure can hit 90+ cold-sourced meetings in a single quarter — when ICP is narrow, signals are strong, infrastructure is properly built, and founder discovery quality is high. The pattern generalizes to most B2B SaaS in the 5–50 person range.

For an end-to-end cold outbound program with similar ICP targeting, infrastructure, and execution, build a campaign runs the full workflow from ICP definition through booked discovery calls.

Ready to launch your next campaign?

Build your outreach campaign in 90 seconds with our AI Campaign Builder.

Build a Campaign

Related Dispatches