Swipe file
Welcome Email Swipe File
A welcome email is the first piece of content the buyer reads outside of the website. The patterns below win because they sound like a person writing to a person; they fail when they look like a templated newsletter blast. Plain-text, one CTA, founder voice.
Verified · editorial policy
TL;DR
As of , the short version is: A welcome email is the first piece of content the buyer reads outside of the website. The patterns below win because they sound like a person writing to a person; they fail when they look like a templated newsletter blast. Plain-text, one CTA, founder voice.
Welcome Email Swipe File TL;DR
- Element
- Welcome emails
- TL;DR
- A welcome email is the first piece of content the buyer reads outside of the website. The patterns below win because they sound like a person writing to a person; they fail when they look like a templated newsletter blast. Plain-text, one CTA, founder voice.
- When to use
- After every email opt-in or purchase. The first email's open rate sets the tone for every email after it.
- When NOT to use
- Never skip the welcome email. If you don't have a real one, write a 4-sentence plain-text one this hour.
- Brunson lens
- Story
- Patterns
- 12 named patterns with formula + example + structural notes
- Last verified
- May 21, 2026
When to use
Rewrite this when
After every email opt-in or purchase. The first email's open rate sets the tone for every email after it.
Do NOT touch when
Never skip the welcome email. If you don't have a real one, write a 4-sentence plain-text one this hour.
12 named patterns
Pattern 1
Plain-Text Founder Intro
Formula
Subject: '<First name>, welcome.' Body: 4-sentence founder note + single CTA.
Example
Subject: 'Maryan – welcome.' Body: 'Hey, Maryan here. You just opted in for the diagnostic. Here's the link. Reply if you have questions.'
Why it works
Plain text, founder voice. Open rates higher than templated; reply rates much higher.
Pattern 2
Expectation Timeline
Formula
'Here's what happens this week. Tomorrow: <X>. In 3 days: <Y>. In 7 days: <Z>.'
Example
'Tomorrow: I'll send the rewrite checklist. In 3 days: I'll ask how your diagnostic went. In 7 days: I'll send the founders' office hours invite.'
Why it works
Dated timeline. Reduces 'where's the next email?' churn and builds anticipation for the sequence.
Pattern 3
Single-CTA Welcome
Formula
<2-sentence framing> + <one clear button>
Example
'You're in. The first thing to do is run your diagnostic.' [Run Diagnostic →]
Why it works
One CTA per email. Two or more CTAs cut the click on each by roughly half.
Pattern 4
Founder Photo + 'My Story'
Formula
<Founder photo> + <2-paragraph story> + <CTA>
Example
Maryan photo + 'I built this because my own SaaS flatlined for 6 weeks post-launch. Here's the diagnostic that came out of that.' + CTA
Why it works
Personal welcome with a photo. Higher click-through; pairs well with the /about page founder letter.
Pattern 5
Reply Prompt
Formula
'Reply with <one specific question>. I read every one.'
Example
'Reply with the URL of your live page. I'll glance at it before I send tomorrow's email.'
Why it works
Reply prompts boost engagement scoring with email providers. Use only if you actually read replies.
Pattern 6
First-Asset Delivery
Formula
<Subject>: '<Asset name> – inside.' Body: link + 1-line use instruction.
Example
Subject: 'Diagnostic checklist – inside.' Body: '[Link]. Best result: run it on a live page, not a mockup.'
Why it works
Direct asset delivery. Highest click rate of any welcome pattern; lowest reply rate.
Pattern 7
Cohort-Match Welcome
Formula
<Subject>: 'A note for <cohort>.' Body: cohort-specific framing.
Example
Subject: 'A note for post-launch SaaS founders.' Body: cohort-tailored welcome with cohort-specific examples.
Why it works
Welcome segmented by opt-in cohort. Higher relevance, higher next-email open rate.
Pattern 8
Setup-Walkthrough Welcome
Formula
<Embedded 60-90s Loom walkthrough> + <transcript>
Example
Loom: '60-second walkthrough of the dashboard.' + transcript below.
Why it works
Walkthrough video. Cuts first-week support tickets; higher activation rate.
Pattern 9
Founder-Signed Welcome
Formula
<Personal note> ending with '– <Founder first name>'
Example
'Welcome. Reply any time. – Maryan'
Why it works
Personal sign-off. Avoids the 'Sincerely, The Team' corporate voice. Trust lift is small but real.
Pattern 10
Honest Sequence Preview
Formula
'You'll get <N> emails over the next <time>. Reply STOP if it's not the right time.'
Example
'You'll get 5 emails over the next 7 days. Reply STOP if it's not the right time.'
Why it works
Honest disclosure of the sequence. Reduces unsubscribes among engaged readers; increases unsubscribes among uninterested ones (which is fine).
Pattern 11
Welcome + Bonus
Formula
'Welcome. Bonus inside: <named asset>.'
Example
'Welcome. Bonus inside: the 30-day rewrite checklist.'
Why it works
Welcome with an unexpected first bonus. Builds goodwill, increases next-email open.
Pattern 12
Survey Welcome
Formula
'Welcome. One question: <single survey question>.'
Example
'Welcome. One question: what's the single biggest thing breaking on your launch right now? Reply with one word: traffic, conversion, retention, other.'
Why it works
Survey welcome. Reply data segments the list for future emails. Lower click rate than asset-delivery patterns, higher long-term value.
Common implementation mistakes
- Welcome email designed to look like a marketing blast (template, header image, footer). Read as spam, opened less.
- Three CTAs in the welcome email. Cuts click on each; never use more than one CTA in the first email.
- Welcome email signed 'The Team' on a small SaaS. Buyers know there's no team; using 'the team' breaks trust.
- Welcome email scheduled for next day. The first 60 minutes after opt-in is the peak open window; send within that window.
- Welcome email that doesn't link to the actual asset the buyer opted in for. Lose half the buyer base in 24 hours.
Real examples from indie SaaS teardowns
Pattern names above are illustrative. These are real, named, dated funnels from the Unlock SaaS teardown set where the welcome email demonstrates the pattern in a shipping product. Funnel-hack the real ones.
story lens
Loops – Founder-led with category jargon
Loops sells the SaaS-specific email job. The funnel ignores marketers and talks to founders.
Loops IS an email tool. Their own welcome email is the canonical founder-led, plain-text, single-CTA reference.
From the teardown: The marketing copy uses SaaS-native vocabulary (loops, lifecycle, transactional, segments by Stripe event) without translation. This signals 'we understand your stack' faster than any 'built for SaaS' tag line.
story lens
Tella – Founder-demos-the-product as story
Tella turned async sales video into a product category. The funnel runs on the output.
Founder voice carries into the welcome email. The same voice that shipped the demo videos signs the first email.
From the teardown: The story is told through founder-recorded demos embedded on the marketing site, which are themselves Tella videos. The recursion makes the demo unfakeable.
story lens
Beehiiv – Creator-success showcase
Beehiiv positions against Substack on creator monetization, not features. The funnel sells the upgrade path.
Creator-success showcase is the welcome – first email points at named creators succeeding in the product.
From the teardown: The story is told through specific creator case studies with named newsletters and stated revenue outcomes. Brunson Hard-Rule applies: only use named, opt-in case studies; do not fabricate. Beehiiv does this well and the funnel benefits.
story lens
Plausible Analytics – Operational transparency as proof
Plausible sells transparency as the product. Open revenue dashboards do the conversion work.
Operational transparency as the welcome – first email is dated, signed, and pointed at the public dashboard.
From the teardown: The story is told through public artifacts: open source code on GitHub, a public revenue page, named founders writing blog posts about real failures and pivots. The reader does not need to take a marketing claim on faith because the receipts are linked.
Which Brunson job does this element do?
This element sits in the Storylens. Knowing the lens tells you what the element is supposed to accomplish, not just what shape it takes – so you don’t rewrite a Story element using Hook tactics or vice versa.
People also ask
What is a welcome email swipe file?
A welcome email is the first piece of content the buyer reads outside of the website. The patterns below win because they sound like a person writing to a person; they fail when they look like a templated newsletter blast. Plain-text, one CTA, founder voice.
When should I rewrite my welcome email?
After every email opt-in or purchase. The first email's open rate sets the tone for every email after it.
When is the welcome email not the right thing to fix?
Never skip the welcome email. If you don't have a real one, write a 4-sentence plain-text one this hour.
Questions founders ask about welcome email copy
How long should a welcome email be?
Under 200 words for plain-text founder voice. Longer than that and the open rate drops. The welcome email's job is to deliver the first asset and set up the sequence, not to re-sell the product.
Should the welcome email come from the founder's name or the brand?
Founder's first name + brand domain ('Maryan from Unlock SaaS'). Personal sender + branded domain earns higher opens than either alone.
Should I include an unsubscribe link prominently in the welcome email?
Yes, in the footer like every email. Prominently above the footer is unnecessary. The buyer opted in; respect that without pre-suggesting they leave.
Related Brunson terms
Apply these patterns to your live page
The free 90-second Launch Diagnostic checks whether the welcome email is actually the broken step on your page, or whether the bottleneck is upstream.