SaaS Cold Email Template
Cold email that speaks the language of SaaS buyers.
When to use
Use when selling a SaaS product to other tech companies, software teams, or digital-first businesses. SaaS buyers are sophisticated — they've seen every pitch. This template cuts through that.
Who it's for
SaaS sales reps, SDRs, and founders selling to tech teams or software-forward companies.
Why it works
SaaS buyers are ROI-focused and time-poor. This template leads with a metric they'll recognise (time saved, churn reduced, revenue increased), keeps the email under 70 words, and avoids buzzwords like 'synergy' or 'leverage'.
Email Template
Subject: Cutting {{pain_area}} time at {{company}}
Hi {{first_name}},
Most {{role}} teams at SaaS companies spend {{X hours/week}} on {{manual_pain_point}}. It's one of those tasks that's never urgent but always slow.
{{your_product}} automates this — {{specific_teams}} like {{customer_1}} and {{customer_2}} have cut this to under {{timeframe}}.
Worth a 15-minute look?
{{your_name}}
Churn/retention angle
Subject: Reducing churn at {{company}}
Hi {{first_name}},
Churn is the number that keeps SaaS founders up at night. We help {{ICP}} reduce it by {{method}}.
{{similar_company}} went from {{before_churn_rate}} to {{after_churn_rate}} in {{timeframe}} using {{your_product}}.
Happy to share the exact playbook if it's relevant for {{company}}.
{{your_name}}
Subject Line Variations
- Cutting {{pain_area}} time at {{company}}
- Reducing {{metric}} at SaaS companies like {{company}}
- How {{similar_saas}} improved {{outcome}}
- {{company}}'s {{metric}} — quick thought
Personalization Ideas
- Reference their product category and tie it to a common pain in that niche
- Check their tech stack (BuiltWith, job listings) and mention a tool they use
- Reference their pricing page — it signals insight into their business model
Common Mistakes to Avoid
- Too much jargon — even tech buyers want plain language
- Not mentioning a relevant SaaS customer as social proof
- Long feature lists — SaaS buyers want outcomes, not functionality