Founding offer: 50% off for 3 months for our first 10 customers. 10 left · code FOUNDING10 →
ReplyDak

Cold email infrastructure for SaaS startups

Updated 17 October 2026 · 7 min read

Short answer

A SaaS startup doing outbound needs separate sending domains, about one warmed mailbox per 30 emails a day, and a sequencer, so 300 emails a day means roughly 10 mailboxes on 4–5 domains. Founder-led outbound usually starts with 3–10 mailboxes; an SDR team typically runs 10–20 per rep. Measure positive replies and meetings booked per 100 prospects, not opens, and keep your main product domain out of cold sending.

Two stages of SaaS outbound

Founder-led outboundSDR team outbound
Who sendsFounder or first sales hire2+ SDRs, each with their own mailboxes
GoalFind the first 10–50 customers, learn the pitchFill a predictable meeting pipeline
Emails per day50–300300–600 per SDR
Mailboxes3–1010–20 per SDR
Domains (2–3 mailboxes each)2–54–10 per SDR
ReplyDak cost (mailboxes)$35 for 10$87 for 30, $269 for 100

The volumes assume about 30 emails per warmed mailbox per day, including follow-ups. That is a cautious number that keeps each mailbox well under provider limits; see cold email sending limits. Price your own setup with the cost calculator.

Set up the infrastructure

  1. 1

    Keep your product domain clean

    Your app's domain sends password resets, invoices and onboarding mail. Never risk it on cold outreach. Read protect your main domain.

  2. 2

    Buy lookalike domains

    For acme.io, use names like getacme.com or tryacme.io. Check availability with the domain checker and forward each one to your homepage.

  3. 3

    Create 2–3 mailboxes per domain

    Use real people's names (the founder, SDRs). Prospects reply to people, not to sales@.

  4. 4

    Authenticate

    SPF, DKIM and DMARC on every domain. ReplyDak sets these automatically on Cloudflare; the details are in SPF, DKIM and DMARC for cold email.

  5. 5

    Warm up for about three weeks

    ReplyDak ramps each mailbox from about 2 to 30 emails a day over roughly 21 days and slows or pauses if signals turn bad. Use the time to build your list and write copy.

  6. 6

    Connect to your sequencer

    Export mailboxes as CSV into Instantly, Smartlead or your tool of choice. See connecting mailboxes.

Sequencing for SaaS

  • Short sequences. 3–4 emails over about two weeks. Later steps rarely add much and raise complaint risk.
  • One idea per email. Lead with the problem your product solves for that role, not a feature list.
  • Plain text, few links. One link at most, no images or tracking-heavy templates in the first email.
  • Segment by trigger. Funding rounds, new hires in a role, a tool they use or just dropped. Triggers give you a reason to write now.
  • Rotate mailboxes. Let the sequencer spread sends across all mailboxes so no single one carries the load.
  • Easy opt-out. A plain line such as 'Not relevant? Reply and I will stop' keeps complaints down and meets bulk sender rules.

Measuring replies, not opens

Open tracking is unreliable because many mail clients load images automatically or block them, and tracking pixels can hurt placement. Track these instead, per campaign and per 100 prospects contacted:

MetricWhat it tells youWhere to look
Bounce rateList quality; keep it very lowSequencer bounce report
Reply rateWhether people engage at allSequencer inbox
Positive reply rateWhether the offer and targeting workTag replies as positive, neutral, negative
Meetings bookedPipeline createdCalendar or CRM
Spam complaints / unsubscribesWhether you are annoying the marketGoogle Postmaster Tools, opt-out replies
Test one change at a time: a new segment, a new first line or a new offer. Give each variant a few hundred prospects before you judge it.

Scaling from founder to SDR team

  • Give each SDR their own domains and mailboxes so one person's mistakes do not hit the whole team.
  • Add new domains a few weeks before you need them, so they finish warmup on time.
  • Retire a domain that keeps landing in spam rather than pushing more volume through it.
  • Review the deliverability checklist monthly.

A worked example

Say a seed-stage SaaS founder wants to contact 1,000 new prospects a month with a 3-step sequence. That is about 3,000 emails a month, or roughly 150 per working day. At 30 per mailbox that needs 5 mailboxes; most founders buy 10 so warmup and follow-ups have headroom and one flagged domain does not stop outreach.

ItemQuantityMonthly cost at ReplyDak
Google Workspace mailboxes10$35
Sending domains4about $4.33 ($13 a year each)
WarmupIncluded$0
Sequencer1 seatYour tool's price

Paying in India? The same setup is ₹289 per mailbox with a GST invoice, and domains are ₹1,099 a year. See all plans on the pricing page.

Common SaaS outbound mistakes

  • Sending from the product domain because it is already set up.
  • Skipping warmup to hit a launch date, then burning new domains in week one.
  • Buying a large unverified list; high bounces damage every mailbox that sends to it.
  • Judging campaigns by open rate instead of replies and meetings.

Set up 10 Google Workspace mailboxes for founder-led outbound for $35 a month, warmup included.

Domains, DNS, Google Workspace mailboxes and warmup. From $2.69 per mailbox ($35 for 10).

FAQ

How many mailboxes does a SaaS founder need for outbound?

Divide your daily target by about 30. A founder sending 150 emails a day needs about 5 mailboxes on 2–3 domains; 300 a day needs about 10 on 4–5 domains.

Should a SaaS startup send cold email from its product domain?

No. The product domain carries transactional mail like sign-ups and invoices. Use separate lookalike domains for outreach so a reputation problem cannot affect your app's email.

How soon can a new SaaS outbound setup start sending?

Plan for about three weeks of warmup before full volume. You can send small amounts during warmup, but most teams use that time to build lists and write sequences.

What should SaaS teams measure in cold email?

Bounce rate, reply rate, positive reply rate and meetings booked per 100 prospects. Opens are too unreliable to steer by.

Sources

Related