A founder update is a short, recurring letter from you to people who already use or pay for the product. Its job is trust, retention, soft asks, and product learning. It is not a marketing newsletter, not an onboarding drip, and not a feature dump. Pick a small list (paying customers first), choose biweekly or monthly, stick to a fixed outline, keep it around 300-500 words, and measure replies more than open rate.
What is a founder update actually for?
You are writing to people who already said yes once. The letter should make them feel they still know what is going on, and that you are listening. Done well, it earns a reply, a renewal, a referral ask you can make later, or a clear "this feature does not help me."
It is for:
Trust. Early buyers are betting on you as much as the product. A calm, honest update keeps that bet warm.
Retention. People churn when they forget why they signed up. A short "here is what changed for you" message reminds them.
Soft asks. One question or one small request per letter beats a pitch deck in email form.
Product learning. Replies are cheap research. Treat them like tickets with context, not vanity comments.
It is not:
A feature dump. Shipping five things and listing all of them is a changelog, not a letter.
Launch hype. "Excited to announce" belongs on a public post, not in a private update to people who already bought.
An onboarding sequence. Behavior-triggered emails that push someone to a first win are a different system. If you need that path, use a guide such as Aura++ on how to write onboarding emails that get users to a first win. One sentence: founder updates go to people who already activated; onboarding tries to get them there.
A public changelog email. A public changelog can re-engage silent users on a page or in-app. MakerHunt covers how to write a changelog that brings silent users back. Your founder letter is personal, scoped, and usually smaller.
Who should get the founder update?
Start narrow. Expand only when replies stay useful.
Paying customers first. Anyone on a paid plan, pilot, or active invoice. These people have the most to lose if you go quiet, and the most signal when they reply.
Optional: free but active users. People who logged in or finished a core job in the last 14-30 days. Active free users can teach you; dormant free signups usually just dilute the list.
Never spam churned or cold contacts without a clear opt-in. If someone cancelled, send a separate cancel or win-back path, not this letter. If someone never activated, do not "warm" them with a founder update they did not ask for.
Keep a simple sheet: email, plan (paid/free), last active date, opted in (yes/no), notes. When in doubt, leave them off.
The running example (made-up)
Mapquill is an illustrative, made-up product, and every number about it below is made up too.
The setup: a solo founder builds Mapquill, a tool that turns messy customer interview notes into a one-page product decision brief. There are 18 paying customers and about 40 free users who still open the app weekly. The founder wants a biweekly letter those 18 people will actually read, not another marketing blast to 400 waitlist emails.
How often should you send?
Pick one cadence and stick to it until you have a reason to change.
Biweekly works well for early stage when you ship often enough to have something real, but not so often that every letter is fluff.
Monthly is safer if weeks go by with little to say. A thin weekly letter trains people to skip you.
Weekly only if you truly ship a lot and you can keep each letter short. Most early products cannot sustain that without inventing drama.
For Mapquill (made-up), biweekly on Thursdays is the pick: enough time to ship something honest, predictable enough that customers expect it.
Put the next send on your calendar the day you finish the previous one. Missed cadence kills trust faster than a short letter.
What subject lines stay human?
Lead with a fact: what shipped, what you learned, or one number. Skip teasers and fake urgency.
What shipped: "Mapquill: interview brief export is live" (made-up)
What you learned: "We watched 6 calls. The brief was too long." (made-up)
One number: "18 paying teams. Here is what changed this sprint." (made-up)
Honest delay: "No big ship this fortnight. One fix and one ask."
Avoid: "You won't believe what we shipped", "Big news inside", "Excited to share", and subject lines that sound like a press release. If you would not say it face to face, do not put it in the subject.
What outline should every founder update follow?
Use the same six blocks every time. Readers learn where to look. You spend less time staring at a blank doc.
Block | Purpose | Length guide |
|---|---|---|
1. One-sentence state of the product | Orient the reader. Where are you right now? | 1-2 sentences |
2. What shipped since last time | Concrete changes that affect them | 3-6 bullets or a short paragraph |
3. One real thing you learned from users | Proof you are listening; invite correction | 1 short paragraph |
4. What's next (honest, scoped) | Set expectations without roadmap theater | 2-4 bullets max |
5. One soft ask or question | Get a reply or a tiny action | 1-3 sentences |
6. How to reply | Make the path obvious | 1 sentence |
Rules for the blocks:
State of the product is not a vision speech. "We are focused on turning notes into a one-page brief for research-heavy SaaS teams" is enough.
What shipped should be customer-facing. Internal refactors only if they remove a pain people felt.
What you learned should be specific. "Users want speed" is empty. "Three customers paste raw Notion dumps and skip our template" is useful.
What's next names the next two weeks, not the next year. If something slipped, say so once.
Soft ask is one thing: a question, a 15-minute call, a screenshot of a broken flow, or permission to quote a win. Not a survey of twelve questions.
How to reply means "hit reply to this email" unless you truly need a form. Most early lists should prefer reply.
How long should the letter be?
Aim for about 300-500 words of body text. That is enough for the six blocks without becoming a blog post in their inbox.
Cut when:
You are explaining why something is hard more than what changed.
You have a second soft ask. Delete it.
You are pasting changelog noise (dependency bumps, cosmetic tweaks nobody asked for).
You are repeating last letter's "what's next" without admitting it slipped.
If you truly have nothing, send a shorter letter: one honest paragraph, one fix, one ask. Silence for months trains people to assume you disappeared. Empty hype trains them to ignore you. Short and real beats both.
What tone traps kill the letter?
Fake cheerfulness. "We are thrilled and grateful and blessed" reads like a template. Calm and specific reads like a founder.
Roadmap theater. A long public-looking roadmap in a private email looks like you are performing strategy. Scope the next slice.
"Excited to announce." If it needs a press tone, put it on the site or changelog. In a founder update, say what shipped and who it helps.
AI-sounding filler. Vague claims, stacked adjectives, and empty pivots. If a sentence could sit in any SaaS email, rewrite it with a fact from your week.
Hidden pitches. Do not smuggle an upsell into every block. One soft ask is enough.
Where should you send from?
Prefer your own domain mailbox when the list is tiny (under a few dozen). A personal you@yourdomain.com thread is the highest-trust path. When the list grows, or you want scheduling and a clean unsubscribe, use a simple tool.
Options checked on official pricing pages on 2026-10-15:
Resend: free transactional tier includes 3,000 emails/mo (100/day cap on Free). Marketing/broadcast plans start free for 1,000 contacts; paid Pro marketing plans start at $40/mo for 5,000 contacts (as of Oct 2026). Good if you already send product email from Resend.
Loops: free plan covers up to 1,000 contacts with 4,000 total marketing + transactional sends per rolling 30 days. Growth starts at $49/mo for up to 5,000 subscribed contacts with unlimited sends on paid plans (as of Oct 2026). Built for SaaS product email + audiences.
Buttondown: first 100 active subscribers are free, including custom-domain sending and hosted archives; add-ons are priced separately (as of Oct 2026). Fits a short letter style if you want newsletter UX without a heavy marketing suite.
Prices change. If a page disagrees later, trust the page. For password resets and receipts, make sure those messages still land; deliverability basics are a separate playbook, such as this DEV guide to tiny-SaaS deliverability. This post is about the update letter, not SPF/DKIM setup.
What should you measure?
Keep it light.
Replies. Count how many people write back. A reply with a complaint or a tip is gold.
Activated asks. If you asked for a call, a screenshot, or permission to quote, track how many completed it.
Unsubscribes. A spike after a pitch-heavy letter is feedback. Fix the letter; do not panic over one person.
Open rate, lightly. Opens are noisy (privacy features, bots, image blocking). Do not obsess. Use opens only as a weak subject-line hint.
When replies turn into recurring product themes, tag them the way you would support tickets. IndieHunt's guide on turning support tickets into product priorities is the right companion if the inbox becomes a roadmap input.
When should you pause or kill the update?
Pause when:
You cannot write something true for two cycles in a row (no ship, no learning, only filler).
You are in a crunch where a hurried letter would create support debt you cannot answer.
The product is pivoting hard and last month's "what's next" would mislead people. Send one clear pause note, then resume when the story is honest again.
Kill or replace the format when:
Replies stay near zero for months and customers tell you they prefer in-app notes or a public changelog.
The list outgrows a personal letter and you need segmented product news instead of a founder letter.
You are only sending to inflate a vanity "newsletter" habit while customers ignore it.
A one-line pause email ("Taking October off this letter while we finish X; next send on DATE") is better than ghosting.
A 14-day plan to write and send the first one
Day | Focus | Done when |
|---|---|---|
1 | Define the list | Paid customers exported; optional active free users marked; churned excluded |
2 | Pick cadence + send day | Biweekly or monthly written on the calendar |
3 | Choose channel | Domain mailbox or Resend/Loops/Buttondown account ready; from-name is you |
4 | Draft the outline shell | Six headings pasted into a doc; no filler yet |
5-6 | Fill what shipped + learned | Only customer-facing ships; one specific learning with a real detail |
7 | Write state + what's next | One honest sentence each; next slice scoped to two weeks |
8 | Write one soft ask | Single question or tiny action; reply path clear |
9 | Cut to 300-500 words | Second ask gone; jargon cut; read aloud once |
10 | Subject line | Fact-first; three options, pick the plainest |
11 | Send yourself a test | Links work; from-name correct; unsubscribe or reply path obvious |
12 | Send to the list | First letter out on the chosen day |
13-14 | Answer replies same day | Every reply gets a human answer; learnings noted for next letter |
Sample founder update (illustrative, made-up)
Below is a made-up Mapquill letter. Treat names and numbers as fiction.
Subject: Mapquill: brief export is live + one ask
Hi team,
Mapquill is still the same job: turn messy interview notes into a one-page product decision brief for research-heavy SaaS teams.
What shipped since last time
Export the brief as a clean PDF (not just Markdown).
Faster paste from Notion: we strip the junk wrappers that broke headings.
A "too long" warning when the brief crosses one page at default print size.
What I learned
Three of you paste raw call transcripts and ignore the template. The brief then becomes a wall of text. I am testing a "transcript mode" that forces three bullets before free-form notes. Tell me if that would help or annoy you.
What's next (next two weeks)
Transcript mode behind a flag for volunteers.
Fix the slow load when a workspace has 50+ briefs (yes, that is on me).
One ask
If you exported a PDF last week, hit reply with "worked" or "broke" and which browser you used. That is the whole ask.
Reply to this email anytime.
Thanks,
Alex
FAQ
Can I send the same letter to free users and paying customers?
You can, if the content is truly shared. Split the list when the ask differs (paid customers get a renewal or pricing note; free users get an activation tip). Early on, one honest letter to paying customers is better than a diluted blast to everyone who ever typed an email.
What if I have nothing to ship this cycle?
Send learning + next + ask. Or send a short "no big ship" letter. Do not invent a feature announcement. Customers prefer an honest quiet cycle over fake progress.
Should investor updates and customer updates be the same email?
Usually no. Investors want runway, metrics, and asks for intros. Customers want product truth and how it affects their work. You can reuse facts, but write two letters. Mixing them makes customers feel like extras in a fundraising story.
Do I need a fancy template?
No. Plain text or simple HTML with your name, a clear subject, and a reply path beats a branded newsletter shell that looks like marketing. Add branding later if the list grows and trust is already there.
Write the first letter this fortnight. Keep the list small, the outline fixed, and the ask singular. When you want early customers who care about new AI and SaaS tools, launch your early-stage product on EarlyHunt.