1,000 emails a day and ~11 meetings a month, hands off
Clay records → clean, check, personalize → Smartlead campaigns
This company had Clay for research and Smartlead for sending, but nothing reliable in between. Every launch meant wrangling CSVs, which was slow and hurt their sending reputation. We built one pipeline that runs the whole thing: clean intake, no duplicates, suppression lists, personalized copy by persona, sending caps, and reply sorting. At 1,000 emails a day and a 2% reply rate, that is around 440 replies and roughly 11 meetings a month.
What it's worth
Meetings on the calendar
- Emails per month
- ~22,000
- Reply rate
- 2%
- Replies per month
- 440
- Positive replies
- ~44
- Meetings held
- ~11
- meetings per month
- ~11
Rep time back
- Hours a day on CSVs and list cleanup
- 1.5 hrs
- Working days per year
- 240
- Hours back per year
- 360 hrs
- Rep cost
- $25 / hr
- per year
- $9,000
How this was calculated — every assumption
- Send volume and the 2% reply rate are measured. The two steps below the reply line are modeled at ordinary cold outbound rates: 1 in 10 replies is positive, 1 in 4 of those takes a meeting.
- We stop at meetings. What closes from a meeting depends on the sales team and the product, not the pipeline, so putting a revenue figure on it would credit this system for someone else's work.
- Rep time is costed at $25/hour over 240 working days, against about 1.5 hours a day previously spent on CSVs and list cleanup.
Results at a glance
- ~11 meetings a month from cold outbound, hands off
- ~$9,000 a year of rep time back
- 1,000 emails a day, fully automated
- Reply rate lifted to 2% with copy written per persona
- Sending reputation and CAN-SPAM compliance protected throughout
The problem
The pieces were there but nothing connected them. No automatic sync of clean records. No duplicate or suppression handling. Personalization that risked deliverability. No way to sort and route replies. Every launch started with CSV wrangling, which slowed things down and damaged the sending reputation. A burned domain does not just cost you the current campaign. It costs every campaign after it.
What was built
Intake
Pulls ready rows out of Clay, normalizes the fields, and verifies them. Only clean records get in.
Cleanup
Removes duplicates by email and domain. Suppresses customers, partners, competitors, and anyone who unsubscribed.
Personalization
Copy written per industry, company size, and role, with a fallback when a detail is missing. The fallback matters. Bad personalization reads worse than none.
Sending
Campaigns assigned by persona, with daily caps, warmup, and inbox rotation to protect deliverability.
Replies
Sorted automatically into positive, neutral, negative, out-of-office, or bounce, with instant alerts and reschedules.
Visibility
Everything logged to Supabase, with daily summaries and error alerts. Nothing drifts unnoticed.
What keeps it from breaking
Suppression lists are global
Customers, partners, competitors, and unsubscribes are blocked across every campaign at once. Per-campaign lists are how you cold-pitch your own customer.
Deliverability comes first
Daily caps, warmup, and inbox rotation hold volume below what the setup could technically push. You can buy back sending capacity. You cannot buy back a burned domain.
Compliance is built in
CAN-SPAM handling and SPF, DKIM, and DMARC are part of the pipeline, not a checklist someone runs later.
How the approach worked
Sending an email was never the hard part. The hard part was doing it at volume without a person watching: duplicates, suppressions, deliverability, and replies all handled properly. Build the guardrails first, then let it run. Once they hold, volume is just a dial.
The results
The whole flow runs itself. The reply rate rose to 2% with copy written per persona, and the system sends up to 1,000 emails a day while staying compliant and protecting the sending domain. That works out to around 440 replies and roughly 11 meetings a month, plus about $9,000 of rep time no longer spent in spreadsheets. What closes from there is the sales team’s to claim, not this pipeline’s.
Tools & technologies
Have a process like this slowing your business down? Tell me your stack and goals and I'll send back a build plan.
Take the stack assessment →