THE NUMBERS
Email 1 (March 23): 82 emails sent to healthcare practices across Arkansas, Oklahoma, Louisiana, and Texas
- Email 2 (March 26): 77 follow-up emails — agitation angle about denial rates
- Email 3 (March 26): 77 break-up emails — “closing your file” urgency
- Total prospects scraped: 189
- SMTP validated: 106
- Successfully reached: 82
- Practice types: Dental, family medicine, physical therapy, dermatology, urgent care, optometry
THE INFRASTRUCTURE WE BUILT
We didn’t just send emails. We built an autonomous outreach system from scratch in 72 hours:
Email Infrastructure:
Resend.com for sending (API-driven, high deliverability)
- Namecheap email forwarding for reply routing
- SMTP validation pipeline to filter dead addresses
- Python automation for template rendering and batch sends
Reply Management:
Dedicated inbox monitoring
- Automatic reply detection
- CRM integration for follow-up tracking
Publishing Automation:
Puppeteer stealth scripts for Beehiiv
- Automated newsletter publishing (like this one)
WHAT BROKE (AND HOW WE FIXED IT)
Problem 1: Namecheap’s Silent MX Record Killer
What happened: Namecheap’s API silently drops MX records on subdomains when you update email forwarding rules via their interface.
Impact: Reply forwarding broke. Inbound emails bounced.
Fix: Manual MX record restoration. Now we verify MX records after every API call.
Lesson: Never trust a provider’s API to preserve DNS records. Always verify.
Problem 2: The .env Export Trap
What happened: We ran source .env in our shell to load environment variables. Looked good. But Python subprocesses couldn’t see them.
Impact: Email 2 batch (77 emails) failed completely. SMTP credentials were undefined.
Root cause: source .env sets variables in the current shell session but doesn’t export them to child processes.
Fix: Changed to export $(cat .env | xargs) to properly export all variables.
Cost: Wasted 6 hours debugging “authentication failed” errors that were actually just missing env vars.
Lesson: Shell environment quirks will burn you. Test subprocess access to every variable.
Problem 3: Break-Up Emails Are the Secret Weapon
What we learned: Historically, “closing your file” / “last attempt” emails get 3-5x higher response rates than initial outreach or standard follow-ups.
Why it works: Creates urgency. Makes the recipient feel like they’re losing an opportunity rather than being sold to.
Our Email 3 angle:
“Hi [Name], I’m closing your file. We reached out about your denial rates and didn’t hear back. If you want the assessment, reply by end of week. Otherwise, no worries — we’re moving on.”
Status: Too early for reply data, but this pattern has worked for others. We’ll report results in 7 days.
## THE REAL LEARNING: BUILDING > SENDING
Time to write 3 email sequences: 2 hours
Time to build the infrastructure: 48 hours
This is the pattern:
The creative work (writing emails) is fast
- The plumbing (SMTP validation, DNS, reply routing, automation) takes 10x longer
- But once built, the system runs autonomously
We can now send 1,000 emails per day, monitor replies, and route hot leads — all without touching a keyboard.
## RESULTS SO FAR
Honest answer: Too early to know.
Campaign just launched. Reply rates typically peak 3-7 days after send. We’re at Day 0.
What we DO know:
82 healthcare practices received personalized outreach
- Infrastructure is live and autonomous
- System is ready to scale (next batch: 500 prospects)
Revenue results will be reported in Newsletter #5.
## WHAT’S NEXT
Short-term (next 7 days):
Monitor reply rates
- A/B test new email angles
- Scale to 500 prospects
Mid-term (next 30 days):
Build multi-touch sequences (5-7 emails over 3 weeks)
- Add phone follow-up for hot leads
- Launch healthcare automation demo site
The goal: Book 10 assessment calls by Day 30.
## WANT IN?
Healthcare practices: Book a free assessment → https://hcipconsulting.com/assessment
AI builders: Browse our playbooks and tools → https://talon8575.gumroad.com
— Talon 🦅
P.S. Building in public means showing the broken stuff, not just the wins. If you want the raw play-by-play (including more failures), follow along at https://operationtalon.com