Running a 30-Day Cold Outbound Campaign with Smartlead

Cold outbound email is a deliverability problem before it is a messaging problem. You can write the world’s best sequence and still land in spam if your domains are fresh, your inboxes are unwarmed, and your sending volume ramps too fast. This playbook fixes that problem first, then deals with everything else.

The campaign architecture: three sending domains, nine inboxes (three per domain), Smartlead as the sequencer, Apollo plus Clay for list build, and Glockapps for deliverability monitoring. Total ramp time: 30 days from domain purchase to full-volume sending. At the end of day 30, you should be sending 450–1,350 emails per day across nine inboxes and seeing a 2–3% positive reply rate on a well-targeted list.

Days 1–5: Domain and Inbox Setup

Domain purchase and DNS configuration. Buy three domains from Google Domains or Namecheap. These should be variations of your primary brand domain — not random domains. Good patterns: get[yourbrand].com, try[yourbrand].com, [yourbrand]hq.com. Avoid hyphenated domains and country TLDs for US outbound (they flag spam filters).

For each domain, configure these DNS records within 24 hours of purchase:

# DNS records required for each sending domain
# Replace yourdomain.com with your actual domain

# SPF record (TXT record on root domain)
v=spf1 include:_spf.google.com ~all

# DKIM (Google Workspace generates this — copy from Admin > Apps > Gmail > Authenticate email)
# Will look like: google._domainkey.yourdomain.com
# Value: v=DKIM1; k=rsa; p=[long key string]

# DMARC (TXT record on _dmarc.yourdomain.com)
v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com; pct=100

# MX records (if using Google Workspace)
# Priority 1: ASPMX.L.GOOGLE.COM
# Priority 5: ALT1.ASPMX.L.GOOGLE.COM
# Priority 5: ALT2.ASPMX.L.GOOGLE.COM
# Priority 10: ALT3.ASPMX.L.GOOGLE.COM
# Priority 10: ALT4.ASPMX.L.GOOGLE.COM

Verify all records using MXToolbox within 48 hours. A missing DMARC record is the single most common cause of deliverability problems on new domains.

Inbox provisioning. Create three Google Workspace inboxes per domain (nine total). Inbox naming convention: use real-sounding first name combinations, not generic names. sarah@gettryacme.com, not sales@gettryacme.com. Add a profile photo and a 2–3 sentence email signature to each inbox — Gmail’s spam filters treat inboxes with complete profiles differently than blank ones. Enable two-factor authentication on every inbox before connecting to Smartlead.

Connect to Smartlead. In Smartlead, navigate to Email Accounts → Add Account → Google Workspace. Connect each of the nine inboxes via OAuth. After connecting, set these per-inbox sending limits inside Smartlead: daily sending limit of 30 emails, minimum time between emails of 5 minutes, randomization of ±3 minutes. These conservative limits apply only during warmup — you’ll increase them after day 14.

Days 1–14: Inbox Warmup

Smartlead has a built-in warmup feature called Warmup. Enable it for all nine inboxes on day one. Warmup works by sending real emails to a network of other warmed inboxes and automatically replying to them — building a positive sending reputation for your domain and inbox before you send any cold outreach.

Smartlead Warmup settings for days 1–14:

  • Daily warmup emails: Start at 5/day on day 1, increase by 2 emails per day. By day 7 you should be at 17 warmup emails/day per inbox; by day 14, at 29/day.
  • Reply rate: Set to 40% (Smartlead’s warmup network will automatically reply to 40% of your warmup emails — this simulates engagement).
  • Read emulation: Enable. This tells the warmup network to mark your emails as read before replying, improving your engagement signal.
  • Spam rescue: Enable. Smartlead will check if warmup emails land in spam and mark them as not-spam — building domain reputation.

Do not send any cold outreach during days 1–14. Your domains are establishing reputation. Any bounce or spam complaint during this period will set you back significantly.

Glockapps monitoring during warmup. Set up Glockapps ($29/month for the basic plan) and run an inbox placement test on each of your nine inboxes at days 5, 10, and 14. A passing warmup score is:

  • Google inbox placement: ≥85%
  • Microsoft/Outlook inbox placement: ≥75%
  • Spam rate: ≤5%

If any inbox falls below these thresholds at day 10, do not advance it to cold outreach at day 15. Keep warming for another 7 days and retest. A failed warmup is the most common reason cold campaigns collapse in week three.

Days 5–12: List Build with Apollo and Clay

While warmup runs in the background, build your contact list. Target list size for a 30-day campaign: 600–1,200 contacts. This supports 50–100 new contacts entering the sequence per day across nine inboxes.

Step 1: Apollo search. In Apollo’s People search, filter by: job title (target decision-makers for your ICP), company headcount range, industry, and geography. For a US outbound campaign targeting VP-level buyers at 50–500 person SaaS companies, you should find 5,000–20,000 matching contacts. Export 1,500–2,000 to a CSV — you will filter this down.

Step 2: Clay enrichment and filtering. Import the Apollo CSV into Clay. Add these enrichment columns:

  • Apollo email verification (1 credit/row) — filter to verified emails only. Unverified emails bounce at 20–40% rates and will destroy your domain reputation.
  • Claygent: “Does [company name] use [your product category]?” — filter to Yes. This reduces list size by 40–60% but improves reply rates dramatically by targeting people who already have the problem you solve.
  • Clay formula column: exclude contacts whose email domains are on free email provider lists (Gmail, Yahoo, Hotmail). Work email only.

After filtering, you should have 600–1,200 contacts with verified work emails and confirmed ICP relevance. Upload this final list to Smartlead as a Lead List before day 14.

Days 15–21: Sequence Design and Launch

Sequence structure. Four emails over 14 days. This is the structure that consistently produces 2–3% positive reply rates without burning the sequence:

  • Email 1 (Day 0): Pattern interrupt + specific observation about their business. 80–100 words. No pitch. End with a single soft question. Subject line: 3–5 words, lowercase, no symbols.
  • Email 2 (Day 3): Social proof + specific outcome relevant to their role. 60–80 words. One customer name if you have permission. End with the same question reframed differently.
  • Email 3 (Day 7): Relevant piece of content or insight (not a blog post link — a specific data point or observation). 50–70 words. No explicit ask.
  • Email 4 (Day 14): Breakup email. Genuinely final. “I’ll stop reaching out — if timing changes, here’s how to find me.” 30–50 words. No pitch.

Smartlead sequence configuration:

// Smartlead Campaign Settings (match these exactly for deliverability)

Sending Schedule:
  Days: Monday through Friday
  Hours: 8:00 AM to 5:00 PM (prospect's timezone — enable timezone detection)
  Exclude: holidays (Smartlead has a built-in US holiday calendar)

Per-Inbox Sending Limits (Days 15-21, ramp week):
  Day 15: 30 emails/day per inbox (270 total across 9 inboxes)
  Day 17: 50 emails/day per inbox (450 total)
  Day 19: 80 emails/day per inbox (720 total)
  Day 21: 100 emails/day per inbox (900 total)

Per-Inbox Sending Limits (Days 22-30, full volume):
  Target: 50-150 emails/day per inbox depending on list size
  Recommended for sustained deliverability: 80 emails/day
  Maximum safe limit: 150 emails/day (above this, spam rates climb)

Email Settings:
  Plain text mode: ON (no HTML, no images, no tracking pixels)
  Open tracking: OFF during warmup; can enable after day 21 (adds slight spam risk)
  Click tracking: OFF (rewriting links degrades deliverability)
  Unsubscribe link: ON (legally required in most jurisdictions)

Lead rotation:
  Distribute new leads evenly across all 9 inboxes
  Do not assign more than 15 new leads per inbox per day during the first week

Days 15–30: Monitoring Deliverability

Run a Glockapps inbox placement test every 5 days after launch. The metrics to watch:

  • Inbox placement rate: Target ≥80%. Below 70% means you have a deliverability problem — stop sending on that inbox, extend warmup for another 7 days, then retest before resuming.
  • Bounce rate in Smartlead: Target ≤3%. Above 5%, pause the campaign and audit your list — your email verification pass may have missed invalid addresses.
  • Spam complaint rate: Target ≤0.1%. Google’s postmaster tools will show you this for Gmail recipients. Above 0.3% triggers domain reputation damage that takes 30+ days to recover from.
  • Unsubscribe rate: Target ≤1% per email. Higher suggests your list targeting is off — you’re reaching people who have no context for why you’re contacting them.

If deliverability degrades mid-campaign: The first response is always to reduce volume, not improve copy. Drop sending to 30 emails/day per inbox. Run a Glockapps test. Check if the problem is domain-level (all inboxes on a domain failing) or inbox-level (one inbox failing). Domain-level failure usually means your SPF/DKIM/DMARC has drifted — re-verify DNS records. Inbox-level failure usually means that inbox got a spam complaint — pause it and continue on the remaining inboxes.

Reply Handling

At a 2–3% positive reply rate on 900 daily emails, expect 18–27 positive replies per day at full volume. This is a real pipeline number — do not let them sit in Smartlead. Set up Smartlead’s Slack integration to post every reply to a dedicated #outbound-replies channel. Train whoever handles replies to respond within 2 hours during business hours.

In Smartlead’s reply categorization, use these tags: interested, not-now, referral, out-of-office, unsubscribe, negative. The not-now and referral categories are high-value — add those contacts to a HubSpot sequence for 90-day re-engagement. An interested response today is often an out-of-office that becomes a deal in the next quarter.

When a positive reply comes in, move the contact out of Smartlead immediately (mark as replied and stop the sequence) and into your CRM as an active opportunity. Do not let Smartlead send the next sequence email after a positive reply — the default sequence behavior will fire automatically if you forget to stop it, and sending a follow-up after someone has already expressed interest is the fastest way to lose the deal.

What This Campaign Should Produce

At full volume (days 22–30), with 9 inboxes at 80 emails/day each: 720 emails/day, 3,600 emails/week. On a 2.5% positive reply rate: 90 positive replies per week. On a 30% reply-to-meeting conversion: 27 meetings per week. These numbers assume a well-targeted list, clean deliverability, and replies handled within 2 hours. Miss any of those three conditions and the numbers fall significantly.

The most common failure mode after a successful 30-day ramp: operators maintain full volume after the original list is exhausted and start sending to lower-quality contacts. Watch your bounce rate and reply rate weekly. If positive reply rate drops below 1%, it’s a list quality problem, not a copy problem. Pause, rebuild the list, and resume — do not try to fix a bad list with better subject lines.

Related reading: See the Smartlead vendor profile for pricing details and a comparison against Instantly and Lemlist. For list building upstream of this campaign, see the Clay waterfall enrichment playbook. The Glockapps vendor profile covers inbox placement testing in depth.

Similar Posts

  • Building a Waterfall Enrichment Workflow in Clay

    A step-by-step guide to chaining Apollo, ZoomInfo, People Data Labs, web search, and Claude inference in Clay to maximize contact enrichment coverage at minimum cost. This playbook covers the exact column setup, fallback trigger logic, per-row credit math, and the honest latency trade-offs at each provider layer. By the end, you will have a waterfall that fills email, mobile, job title, company headcount, and tech stack for 85-92% of a typical B2B contact list — without paying top-tier provider rates for every row. Intended for RevOps engineers and GTM operators who already have a Clay workspace and at least one enrichment provider connected.

  • Detecting Deanonymized Website Visitors with RB2B

    A step-by-step guide to installing RB2B’s deanonymization pixel, configuring Slack alerts for ICP-fit visitor identification, enriching identified visitors via Clay or Apollo, routing to your outbound team in HubSpot, and measuring the conversion rate from visitor identification to booked meeting. Includes publicly available conversion benchmarks (0.5–2.5% of identified visitors to meeting), an honest discussion of what RB2B can legally do in the EU vs. the US, and a frank verdict on whether RB2B is worth the $149/month for your specific use case. Links to the RB2B vendor profile and the RB2B vs. Warmly comparison for teams evaluating alternatives.

  • Routing Inbound Demo Requests with Default + Slack

    A step-by-step guide to building a responsive inbound routing system using Default’s form infrastructure, ICP scoring on firmographic and intent signals, Slack-based AE pod routing, and Linear for operational instrumentation. This playbook covers Default’s flow configuration, the scoring logic for ICP fit, the Slack channel naming convention that keeps routing noise manageable, and the round-robin fallback for unmatched leads. Includes an honest discussion of what happens to MQLs that convert but are not ICP-fit — the edge case most routing playbooks skip. Intended for RevOps engineers building or rebuilding inbound routing at Series A–C B2B SaaS companies.

  • Sequencing on LinkedIn with HeyReach

    A step-by-step guide to running LinkedIn outreach at scale with HeyReach — multi-account setup, audience building from Sales Navigator searches, a three-touch connection-to-message sequence over seven days, and safe throttling to stay within LinkedIn’s terms of service. Includes honest numbers: 15–25 connection requests per day per account, the realistic acceptance rates by persona, and how to route replies into HubSpot without manual effort. Covers the restriction risk that most LinkedIn automation guides avoid — what triggers a LinkedIn account restriction, how to detect it early, and what to do when it happens.

  • Building a Forecast Confidence Layer on Top of HubSpot with Claude

    A practical guide to replacing gut-feel deal forecasting with an AI-powered confidence scoring layer built on Claude’s API and HubSpot’s engagement data. This playbook walks through the exact Claude prompt template, an n8n workflow that pulls deal and contact activity from HubSpot, scores each deal weekly, and writes scores back to a custom HubSpot property for dashboard visibility. Includes honest cost math: approximately $50 per month to score 1,000 deals weekly using Claude Haiku, and a discussion of what the model can and cannot infer from CRM engagement signals alone. For RevOps engineers and sales leaders who want forecasting that compounds with data rather than degrading to the loudest voice in the room.

Leave a Reply

Your email address will not be published. Required fields are marked *