# RamAIn CFO Email Campaign - 100 Lead Test
# Target: Mid-Market + CFOs | Goal: ~20 Calls/Week
# 🎯 CAMPAIGN STRATEGY OVERVIEW
Based on Paul's 5 Building Blocks Framework:
- Lead with Pain (not product)
- Value Props (differentiated benefits)
- Social Proof (YC backing, case studies)
- CTA/Offer (value-first call)
- Subject Line (curiosity-inducing)
Campaign Structure: 4-touchpoint sequence (1 week gaps between emails)
# 📊 ICP DEFINITION: MID-MARKET + CFOs
Target Profile:
- Company Size: 100-1,000 employees (mid-market)
- Revenue: $10M - $500M
- Title: CFO, VP Finance, Finance Director, Head of Finance Operations
- Pain Points:
- Double payments to vendors
- RPA systems blocking revenue
- Finance ops team manually copy-pasting between portals for hours daily
- Invoice processing bottlenecks
- Vendor workflow inefficiencies
Why This ICP First:
- Mid-market companies have enough volume to feel the pain
- They have budget but are nimble enough to move fast
- CFOs are directly feeling the operational pain
- Easier to get decisions made vs. enterprise
# ✉️ EMAIL SEQUENCE: 4-TOUCHPOINT CAMPAIGN
# TOUCHPOINT 1: The Pain Opener (Day 1)
Subject Line Options (Test These):
- "Quick question about vendor payments at {{company.name}}"
- "Are you dealing with double payments to vendors?"
- "The copy-paste problem in finance ops"
- "Question about your invoice processing workflow"
- "Is RPA blocking revenue at {{company.name}}?"
Recommended Subject: "Quick question about vendor payments at {{company.name}}"
- Why: Specific, personalized, implies a question not a pitch
Email Body:
Code
Hi {{first_name}},
Quick question: Is your finance ops team still manually copy-pasting data between portals to process invoices?
I ask because we just finished helping a mid-market CFO who discovered they were making $47K in duplicate vendor payments every quarter because their team was manually entering invoice data across 4 different systems.
The worst part? Their RPA "solution" was blocking revenue because it couldn't handle the portal variations their vendors used.
We helped them deploy AI agents that:
• Process invoices end-to-end without manual data entry
• Eliminated the duplicate payment problem completely
• Worked across all vendor portals (even the weird ones)
• Deployed in 3 days, not 3 months
Worth a 15-minute call to see if something similar would help at {{company.name}}?
Best,
Shourya
P.S. - We're YC-backed and just launched 3 months ago, but already processing $2M+ in monthly invoice volume for companies like yours.
Why This Works:
- ✅ Leads with specific pain (double payments, manual copy-pasting)
- ✅ Uses concrete numbers ($47K, 4 systems)
- ✅ Acknowledges RPA failures (shows understanding)
- ✅ Clear value props (3 days deployment)
- ✅ Social proof (YC-backed, $2M volume)
- ✅ Soft CTA (15-min call)
# TOUCHPOINT 2: The Value Add (Day 8)
Subject Line Options:
- "The top 3 invoice processing pitfalls (and how to avoid them)"
- "Following up: vendor payment automation"
- "How {{company.name}} can eliminate duplicate payments"
- "The 15-min finance ops audit I promised"
Recommended Subject: "The top 3 invoice processing pitfalls (and how to avoid them)"
- Why: Value-first, educational, creates curiosity
Email Body:
Code
Hi {{first_name}},
Following up on my note about vendor payments.
I promised to share the top pitfalls we see CFOs fall into with invoice processing — based on 200+ conversations we've had:
**Pitfall #1: The "RPA Will Fix Everything" Trap**
Traditional RPA works great for static forms, but falls apart when vendor portals change (which they do constantly). Result: blocked revenue and frustrated teams.
**Pitfall #2: The Hidden Cost of Manual Data Entry**
Most CFOs underestimate by 60%. When you factor in error correction, duplicate payments, and delayed cash flow, the real cost is 3-4x what shows up in your budget.
**Pitfall #3: The Integration Waiting Game**
Waiting 6-12 months for IT to build API integrations between your ERP and vendor systems. Meanwhile, the problem gets worse.
**The Alternative:**
AI agents that understand context, adapt to portal changes automatically, and deploy in days — not months.
Worth a quick 15-minute call to see how this would apply to {{company.name}}'s specific workflow?
I can share exactly how we helped a similar company eliminate 90% of their manual invoice processing in under a week.
Best,
Shourya
P.S. - No integration work required. Our agents run on top of your existing systems.
Why This Works:
- ✅ Provides genuine value (educational)
- ✅ Shows expertise (200+ conversations)
- ✅ Addresses objections before they come up
- ✅ Specific promise (90% reduction in under a week)
- ✅ Removes friction (no integration work)
# TOUCHPOINT 3: The Social Proof Push (Day 15)
Subject Line Options:
- "How [Similar Company] eliminated $47K in duplicate payments"
- "Case study: Mid-market CFO solves invoice bottleneck"
- "The results are in: 90% reduction in manual processing"
- "Following up: 3-day deployment promise"
Recommended Subject: "How [Similar Company] eliminated $47K in duplicate payments"
- Why: Specific result, creates curiosity, implies case study
Email Body:
Code
Hi {{first_name}},
Wanted to share a quick win from a company similar to {{company.name}}:
**The Company:** Mid-market healthcare company, 400 employees, processing 800+ invoices/month across 6 vendor portals.
**The Problem:**
• Finance team spending 25+ hours/week on manual data entry
• $47K in duplicate vendor payments per quarter
• RPA bots breaking monthly due to portal updates
• 12-day average invoice processing time
**The Solution:**
Deployed RamAIn AI agents in 3 days. No API integrations. No IT project.
**The Results (30 days later):**
• 90% reduction in manual data entry
• Zero duplicate payments
• 2-day average processing time
• Finance team freed up for strategic work
**The CFO's Quote:**
"I was skeptical about 'AI agents' but the results speak for themselves. We literally deployed on a Tuesday and were processing invoices autonomously by Friday."
Worth seeing if we can achieve similar results at {{company.name}}?
I have 2 slots open this week for a 15-minute workflow assessment.
Best,
Shourya
P.S. - We're YC-backed and just closed our seed round, but I'm personally reaching out because {{company.name}} fits our ideal profile for this solution.
Why This Works:
- ✅ Detailed case study (specific numbers)
- ✅ Before/after contrast
- ✅ Customer quote (social proof)
- ✅ Urgency (2 slots open)
- ✅ Personal touch (personally reaching out)
# TOUCHPOINT 4: The Breakup (Day 22)
Subject Line Options:
- "Should I close your file?"
- "Last follow-up: invoice automation"
- "Permission to close your account?"
- "One last try: vendor payment automation"
Recommended Subject: "Should I close your file?"
- Why: Pattern interrupt, creates urgency, low pressure
Email Body:
Code
Hi {{first_name}},
I've reached out a few times about helping {{company.name}} automate invoice processing and eliminate duplicate vendor payments.
Haven't heard back, so I'm assuming:
1. You're all set with a solution (congrats!)
2. This isn't a priority right now (totally understandable)
3. My emails are getting buried (happens to the best of us)
If it's #3 and you ARE interested in seeing how AI agents could save your finance team 20+ hours/week, just reply with "SHOW ME" and I'll send over a 2-minute demo video.
If it's #1 or #2, no worries at all — I'll close your file and stop following up.
Either way, thanks for your time.
Best,
Shourya
P.S. - If things change in 3-6 months, feel free to reach out. We'll still be here.
Why This Works:
- ✅ Gives permission to say no (reduces pressure)
- ✅ Pattern interrupt (different from typical sales emails)
- ✅ Easy response option ("SHOW ME")
- ✅ Professional and respectful
- ✅ Leaves door open for future
# 🔄 ADDITIONAL ITERATIONS & A/B TESTS
# Subject Line Variations to Test:
Curiosity-Based:
- "The copy-paste problem ({{company.name}})"
- "Quick question about your invoice workflow"
- "Are you losing money to duplicate payments?"
Pain-Agitation:
- "Is RPA blocking revenue at {{company.name}}?"
- "The hidden cost of manual invoice processing"
- "Why your finance team is still copy-pasting"
Personalization:
- "{{first_name}}, question about vendor portals"
- "Saw {{company.name}} is hiring in finance..."
- "Congrats on {{company.name}}'s recent funding"
Pattern Interrupts:
- "Bad news about your RPA implementation"
- "Your competitor just solved this problem"
- "3-day deployment (seriously)"
# Email Body Variations:
Shorter Version (for busy CFOs):
Code
Hi {{first_name}},
Are duplicate vendor payments eating into your margins?
We just helped a mid-market CFO eliminate $47K/quarter in duplicate payments by deploying AI agents that process invoices autonomously across any vendor portal.
No RPA. No APIs. No 6-month IT project.
Deployed in 3 days.
Worth 15 minutes to see how it works?
Best,
Shourya
More Aggressive Pain Version:
Code
Hi {{first_name}},
Your finance team is manually copy-pasting invoice data between portals right now, aren't they?
I know because every mid-market CFO I talk to is dealing with the same thing:
• 20+ hours/week wasted on manual data entry
• Duplicate payments slipping through (avg $40K+/quarter)
• RPA bots that break when portals update
• 12+ day invoice processing times
We eliminate all of this with AI agents that:
• Read and process invoices like humans (but faster)
• Work across ANY vendor portal (even the weird ones)
• Deploy in 3 days without IT involvement
One CFO told us: "This should have existed 5 years ago."
Want to see it in action?
Best,
Shourya
# 📈 CAMPAIGN EXECUTION STRATEGY
# Week 1-2: Setup & Testing
- Load 100 leads into Artisan (or DIY stack)
- Set up 4-touchpoint sequence
- A/B test 2 subject lines (50 leads each)
- Monitor deliverability (keep bounce rate <5%)
# Week 3-4: Optimization
- Analyze open rates (target 40-60%)
- Analyze reply rates (target ~6%)
- Double down on winning subject line
- Refine email copy based on responses
# Success Metrics:
| Metric | Target | Action if Below |
|---|---|---|
| Open Rate | 40-60% | Test new subject lines |
| Reply Rate | ~6% | Rewrite opening hook |
| Interested Rate | 1%+ | Strengthen value prop |
| Calls Booked | 0.67% | Improve CTA clarity |
# Scaling Plan:
- 100 leads → Validate messaging (Week 1-2)
- 200 leads → Scale winners (Week 3-4)
- 400 leads → Full scale (Week 5+)
# 🎯 KEY DIFFERENTIATORS TO EMPHASIZE
Based on RamAIn's positioning:
"No Integration Work Required"
- Runs on top of existing systems
- No APIs needed
- No IT project
"Deploys in Days, Not Months"
- 3-day typical deployment
- vs. 6-12 months for traditional RPA
"Works Across ANY Portal"
- Adapts to portal changes automatically
- No brittle RPA scripts
"YC-Backed & Enterprise-Ready"
- SOC 2, ISO, HIPAA, GDPR compliant
- Trusted by forward-thinking teams
"AI That Understands Context"
- Not just form-filling
- Actually understands invoice structure
# 📝 FOLLOW-UP STRATEGY FOR RESPONDERS
# If They Reply "Interested":
Code
Thanks for getting back to me, {{first_name}}!
I'd love to show you how this works. Do you have 15 minutes this week or next for a quick workflow assessment?
I can share:
• How we deploy in 3 days without IT involvement
• Specific results from companies similar to {{company.name}}
• Exactly how the AI agents would handle your current workflow
What does your calendar look like?
Best,
Shourya
# If They Reply "Not Interested":
Code
Thanks for letting me know, {{first_name}}. Totally understand.
Just out of curiosity — is it:
1. Not a priority right now
2. Already have a solution in place
3. Don't believe AI can handle this yet
No pressure either way, just helps me understand where {{company.name}} is at.
Best,
Shourya
# If They Reply "Send More Info":
Code
Thanks for the interest, {{first_name}}!
Here's a 2-minute demo video showing exactly how the AI agents process invoices: [LINK]
And here's a case study from a similar company: [LINK]
After you check those out, would it make sense to hop on a quick 15-minute call to discuss how this would apply to {{company.name}}'s specific workflow?
Best,
Shourya
# 🎬 NEXT STEPS FOR YOU
- Set up the campaign in Artisan (or your DIY stack)
- Load 100 leads (mid-market CFOs)
- Start with Subject Line A on 50 leads
- Test Subject Line B on 50 leads
- Monitor metrics daily for first week
- Optimize based on results
- Scale to 200 once you hit 1%+ interested rate