Founder Letter Swipe File

TL;DR

Founder Letter Swipe File TL;DR

12 named patterns

1. Pattern 1

   Origin Scar

   Formula

   '<Year>, I <specific failure event>. That's when I learned <one specific lesson>. This product is <how the lesson became code>.'

   Example

   'In 2024 I launched a SaaS that did $147 in 6 months. That's when I learned post-launch isn't a marketing problem – it's a diagnostic problem. Unlock SaaS is the diagnostic I wish I'd had.'

   Why it works

   Origin + scar + lesson + product. Single tight loop. Earns more trust than a resume in 50 words.

2. Pattern 2

   Public Body of Work

   Formula

   'I've shipped <product 1>, <product 2>, <product 3>. <Honest sentence on what failed and what worked>.'

   Example

   'I've shipped three SaaS products in 5 years. Two flatlined post-launch. The third is doing $4k MRR. This is the diagnostic that came out of those failures.'

   Why it works

   Public body of work + honest sentence on outcomes. Use only if the work is publicly visible.

3. Pattern 3

   Why-Now Framing

   Formula

   'The thing that changed is <named shift>. Pre-<shift>, founders did <X>. Post-<shift>, founders need <Y>. This product is <Y>.'

   Example

   'The thing that changed is post-launch silence. Pre-AI, founders shipped and got attention. Post-AI, they ship into a flooded feed and go silent. This product is the diagnostic that names what's broken in the silence.'

   Why it works

   Names the macro shift the audience is feeling. Earns relevance, not just trust.

4. Pattern 4

   Customer-First Bio

   Formula

   'Hi. I built this for <cohort> like <named real customer>. <One specific outcome they got>.'

   Example

   'Hi, Maryan here. I built this for indie SaaS founders like [named real customer], who went from a 6-week flat Stripe line to 8 paying buyers in 30 days.'

   Why it works

   Customer-first framing. Founder bio comes after the customer outcome, not before.

5. Pattern 5

   Public Numbers

   Formula

   '<Current revenue / users / public metric>. <One honest sentence about what's working and what isn't>.'

   Example

   '47 buyers, $2,300 MRR, 6 months in. Diagnostic conversion is healthy. The retention surface still needs work.'

   Why it works

   Live numbers + named gaps. Counterintuitive trust lift. Most founders won't do it; you should.

6. Pattern 6

   Three Times I Was Wrong

   Formula

   'Three things I used to believe and now don't: <belief 1, what changed>, <belief 2, what changed>, <belief 3, what changed>.'

   Example

   'I used to believe more traffic was the answer. It wasn't. I used to believe a redesign would fix it. It didn't. I used to believe email lists weren't worth the effort. They are.'

   Why it works

   Updates-to-priors framing. Signals the founder learns from contact with reality.

7. Pattern 7

   Public Letter

   Formula

   Direct address, second-person. 'Dear <cohort>, here's what I noticed about <pain>. Here's what I built. Here's what it's not.'

   Example

   'Dear post-launch founder, here's what I noticed about the 6 weeks after launch. Here's what I built. Here's what it isn't – it's not a course.'

   Why it works

   Letter format. Higher dwell, higher conversion when the founder writes the prose personally.

8. Pattern 8

   Identity Statement

   Formula

   'I'm not <thing the audience expects>. I'm <thing closer to them>. <Why that matters for the product>.'

   Example

   'I'm not a growth marketer. I'm a founder who launched into 6 weeks of silence. That's why the diagnostic is built around what a founder can self-run, not what a marketer would optimize.'

   Why it works

   Identity disclosure that reframes the founder as peer, not vendor.

9. Pattern 9

   Skin In Game

   Formula

   'I use this on my own products. <Specific outcome on the founder's own product>.'

   Example

   'I run the diagnostic on every product I ship. It caught a Wrong Person error on my last launch and saved me 6 weeks of misdirection.'

   Why it works

   Eating your own dogfood, named specifically. The most cited proof of operator credibility.

10. Pattern 10

    Public Promise

    Formula

    '<Specific public commitment>. <Verifiable accountability mechanism>.'

    Example

    'I publish monthly transparency reports at /press/transparency. If the metrics don't move, the reports will say so out loud.'

    Why it works

    Public commitment + accountability mechanism. The commitment alone is cheap; the mechanism is the trust unlock.

11. Pattern 11

    Founder Email

    Formula

    'Reply to <founder email> any time. <Sentence on what you reply to>.'

    Example

    'Reply to maryan@unlocksaas.com any time. I read everything within 24 hours and respond to most.'

    Why it works

    Direct email + honest response time. Most founders hide. Showing up earns trust no logo strip can match.

12. Pattern 12

    Two-Founder Voice

    Formula

    <Founder 1 photo + line> + <Founder 2 photo + line> + <joint sentence>

    Example

    Two founder photos side-by-side, each with one line on what they do, then 'Between us, 12 years of founder mistakes you don't have to repeat.'

    Why it works

    Solo founders skip; two-founder teams should use the side-by-side. Triangulates trust between the two.

Common implementation mistakes

• Founder letter that's actually a resume. 'I worked at X, then Y, then Z' tells the buyer nothing about whether the founder understands their pain.
• Photos with no faces (logos as avatars). Removes the trust unlock the page exists for.
• Founder letter buried at /about with no link from the homepage. The buyer can't find the trust page; it might as well not exist.
• Letter written in third person. 'Maryan is a founder who...' reads as bio copy, not as a letter. Use first person.
• Length over substance. A 200-word letter with one named scar beats a 1,000-word bio with five accomplishments.

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 founder letter demonstrates the pattern in a shipping product. Funnel-hack the real ones.

• 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-demos-the-product as story. The founder's own videos ARE the about page proof.

  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.

  Read the full Tella teardown →

• story lens

  Loops – Founder-led with category jargon

  Loops sells the SaaS-specific email job. The funnel ignores marketers and talks to founders.

  Founder-led with category jargon. The voice tells you exactly which cohort the founder writes for.

  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.

  Read the full Loops teardown →

• story lens

  Lemon Squeezy – Pain narrative tied to a specific indie audience

  Lemon Squeezy sold a category swap (MoR), not a feature. The funnel reframes payments into compliance relief.

  Pain narrative tied to a specific indie audience. The about page IS the cohort-match document.

  From the teardown: The funnel speaks to the specific founder who sells globally and has hit the first VAT letter or sales-tax registration prompt. Story carries an emotional weight that pure feature copy cannot, because the reader has felt the pain.

  Read the full Lemon Squeezy teardown →

• story lens

  Plausible Analytics – Operational transparency as proof

  Plausible sells transparency as the product. Open revenue dashboards do the conversion work.

  Operational transparency as proof. Public roadmap, public revenue, public team – the about page is the receipts.

  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.

  Read the full Plausible Analytics teardown →

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

Questions founders ask about founder letter copy

Related Brunson terms

• Story →