Skip to content
Academy

How to Personalise 1,000 Cold Emails Per Day with AI (No Templates, No VAs)

AI-powered cold email personalisation that writes unique, contextual messages at scale using research automation and dynamic generation.

M
Max Beech· Founder
··12 min read
How to Personalise 1,000 Cold Emails Per Day with AI (No Templates, No VAs)

TL;DR

  • Genuinely personalised cold emails get far more replies than templates; AI makes that personalisation affordable at volume
  • The 3-step framework: AI researches prospect (LinkedIn, company site, recent news) → generates contextual hook → writes personalized email
  • Scaling challenge solved: the research and drafting that would take a person hours per batch runs automatically
  • Cost: AI API and enrichment data costs are a fraction of paying a VA to research and personalise manually

# How to Personalise 1,000 Cold Emails Per Day with AI (No Templates, No VAs)

Cold email templates don't work anymore.

"Hi {{FirstName}}, I noticed {{CompanyName}} recently {{GenericObservation}}..." is spam. Everyone knows it. Reply rates reflect it.

But actually personalising emails by hand? At scale, the research time alone makes it impossible.

An AI system can research each prospect, identify genuine insights, and write contextually relevant emails at volume, for far less than paying people to do it manually.

This is the complete framework.

Why Templates Stop Working

ApproachPersonalisationTypical response
Generic template{{FirstName}} onlyLowest
Basic template{{FirstName}}, {{CompanyName}}Low
"Personalised" template+ {{RecentLinkedInPost}}Low to moderate
VA manual researchFull custom per personHigh
AI-powered personalisationResearch + dynamic generationHigh

The insight: True personalisation (referencing specific, recent, relevant information) is far more effective than templates.

But: Manual personalisation doesn't scale. AI does.

The AI Personalisation Framework

Step 1: AI Research (Per Prospect)

What the AI researches:

  1. LinkedIn profile (latest 3-5 posts)
  2. Company website (recent news/blog)
  3. Crunchbase (funding, growth signals)
  4. Twitter (if active)
  5. Company tech stack (BuiltWith, Similar Web)

Example research output for one prospect:

{
  "name": "Sarah Chen",
  "title": "VP of Marketing",
  "company": "DataSync",
  "recent_activity": [
    "Posted on LinkedIn about struggling with content velocity (3 days ago)",
    "Company raised Series A ($8M) announced 2 weeks ago",
    "Hiring 3 content marketers per LinkedIn jobs"
  ],
  "tech_stack": ["HubSpot", "WordPress", "Ahrefs"],
  "pain_points": ["Content bottleneck", "Scaling team"],
  "triggers": ["Recent funding", "Hiring spree", "Mentioned content challenges"]
}

How AI does this:

# Simplified research workflow
def research_prospect(linkedin_url):
    # 1. Scrape LinkedIn (using Apify or similar)
    linkedin_data = scrape_linkedin(linkedin_url)

    # 2. Find recent posts
    recent_posts = linkedin_data['recent_activity'][:5]

    # 3. Analyze for pain points
    pain_points = analyze_with_gpt(
        f"What business challenges is this person discussing? {recent_posts}"
    )

    # 4. Get company data
    company_data = enrich_company(linkedin_data['company'])

    return {
        'recent_activity': recent_posts,
        'pain_points': pain_points,
        'company_triggers': company_data['triggers']
    }

Time per research: Under a minute of machine time

Cost per research: Pennies (AI API + data enrichment)

Step 2: Generate Contextual Hook

The AI identifies what to reference:

Not: "I noticed you work in marketing" (generic)

Yes: "I saw your LinkedIn post from Tuesday about struggling to hit your 40-post/month content goal with a 2-person team"

The prompt:

Based on this research:
[Paste research JSON]

Generate 3 contextual hooks for a cold email. Each hook should:
1. Reference something specific and recent (last 30 days)
2. Connect to a genuine pain point
3. Feel like you actually read their content (because you did)
4. Be concise (1 sentence)

Example good hook:
"I saw your post about struggling to scale content from 10 to 40 posts/month without hiring -we had the same challenge last year."

Example bad hook:
"I noticed you work in marketing."

Generate 3 hooks:

Output:

1. "Saw your Tuesday post about the content bottleneck -we struggled with the same thing (2-person team, 40-post goal). Managed to [X]x our output without hiring. Thought you might find our approach useful."

2. "Congrats on the Series A (£[X]M, impressive for the developer tools space). Noticed you're hiring 3 content marketers -before you scale headcount, we found a way to [X]x output with the same team size using AI. Worth a look?"

3. "You mentioned hitting 'content velocity ceiling' in your LinkedIn post. We hit the same wall at DataSync's revenue stage. Built a system that took us from 15 to 180 posts/month. Happy to share what worked."

AI picks best hook based on:

  • Specificity (more specific = better)
  • Recency (more recent = better)
  • Relevance to our product's value prop

Step 3: Generate Full Email

The prompt (with selected hook):

Write a cold outbound email using this hook:

Hook: "Saw your Tuesday post about the content bottleneck -we had the same thing (2-person team, 40-post goal). Managed to [X]x our output without hiring. Thought you might find our approach useful."

Recipient context:
- Name: Sarah Chen
- Title: VP of Marketing
- Company: DataSync (Series A, $8M raised)
- Pain point: Content velocity (stuck at 15-20 posts/month)

Email requirements:
- Max 120 words
- Tone: Peer-to-peer (not salesperson)
- Structure: Hook → Credibility → Soft CTA
- UK English
- Sign-off: Just first name

Product: [Product Name] - AI content generation that increased our output [X]x

Write email:

Generated email:

Subject: Your content bottleneck (saw your post)

Hi Sarah,

Saw your Tuesday post about hitting the content velocity ceiling with your 2-person team. We had the exact same challenge last year -stuck at 15-20 posts/month, knew we needed 40+ but couldn't justify hiring yet.

We built an AI system that took us from 15 to 180 posts/month (same headcount). Not templates or low-quality spam -actually good content that ranks and converts.

Sounds relevant for DataSync's post-Series A growth phase?

Happy to show you how we did it (15-min call, no pitch). Or if not the right time, totally fine.

Cheers,
Max

Time to generate (including research): A minute or two

Cost: Pennies per email

Quality: Reads as hand-written

Template vs AI Personalisation

Here's the same outreach written both ways. If you run your own A/B test, compare reply rate, positive reply rate and meetings booked, not just opens.

Template Approach (Control)

Example template:

Subject: Quick question, {{FirstName}}

Hi {{FirstName}},

I help {{Title}}s at companies like {{CompanyName}} solve {{GenericPainPoint}}.

Would you be open to a quick chat about how we can help?

Best,
Max

Trade-off: Costs nothing and sends instantly, but recipients recognise it as a template.

AI Personalisation Approach

Example AI email:

Subject: DataSync content challenge (saw your post)

Hi Sarah,

Congrats on the Series A -£8M is brilliant for developer tools.

Saw you're hiring 3 content marketers. Before you scale headcount, we found a way to [X]x content output with our existing team using AI ([N] posts → [N] posts/month).

Might save you £180K in salaries if it works for DataSync.

15-min call to show you the system? Or if not relevant, totally fine.

Cheers,
Max

Trade-off: Costs a little per email for research and generation, and runs mostly automated. In return, every email references something real and relevant to the recipient, which is what earns replies and meetings.

Common Mistakes (And How to Fix Them)

Mistake #1: AI Researches But Doesn't Understand Context

The problem: AI finds information but misinterprets it.

Example:

  • Research found: "Sarah posted about content challenges"
  • AI email: "I saw you're struggling with content"
  • Sarah's reaction: "I'm not *struggling*, we're scaling successfully"

The fix: Prompt AI to frame neutrally:

  • Not: "I saw you're struggling"
  • Yes: "I saw your post about scaling content from 15 to 40 posts/month"

Mistake #2: Too Much Personalisation (Creepy)

The problem: Referencing too many specific details feels like stalking.

Example:

"Hi Sarah,

I saw you posted on LinkedIn Tuesday at 9:42 AM about content velocity, noticed you commented on Tom's post about SEO, and saw you changed your profile picture last week..."

Creepy. Don't do this.

The fix: Reference 1 recent thing. That's enough.

Mistake #3: Personalisation Without Relevance

The problem: Referencing something irrelevant to your pitch.

Example:

"I saw you went hiking in the Lake District last weekend. Beautiful area!

Anyway, want to buy our SaaS product?"

Disconnect between hook and offer.

The fix: Only personalise around pain points relevant to your solution.

---

Want AI to research prospects and generate personalised emails automatically? OpenHelm handles prospect research, email generation, and send automation -scaling personalised outbound. See how it works →

Related reading:

---

Frequently Asked Questions

Q: How do I measure content marketing ROI effectively?

Track both leading indicators (engagement, time on page, shares) and lagging indicators (leads generated, pipeline influenced, revenue attributed). Attribution modelling helps connect content touchpoints to business outcomes over multi-touch journeys.

Q: What's the ideal content publishing frequency?

Consistency matters more than volume. For most B2B companies, 2-4 quality pieces per week outperforms daily low-quality content. Focus on maintaining quality standards while building a sustainable production rhythm.

Q: Should I prioritise SEO or social media distribution?

Both have value, but SEO typically delivers more compounding returns over time. Social generates immediate visibility but requires constant effort. Most successful strategies combine SEO-first content with social amplification.

More from the blog

Stop doing the work around the work

OpenHelm connects to your tools, reads the context, and does the steps, so you sign off on the result instead of producing it. See how it covers an entire role’s weekly workload, check the pricing, or run it yourself with the free local app.