Email, newsletters and lifecycle: Marketing Wiki

Do it

The steps from the launch plan that belong to this topic, in plan order.

Own your channels before you need them

Set up domain email with SPF, DKIM and DMARC1h
Phase 1 is 250 cold emails. Without this they land in spam and you burn the domain.
Reserve every handle you might want45m
X, LinkedIn, Reddit, GitHub, Product Hunt, Discord, YouTube, Bluesky. Same name everywhere.
Build the logo pack45m
PNG, SVG, 1024×1024 square, favicon. Every directory form asks for a different one.
Put email capture on the site45m
Even with nothing to send yet. The list you start today is the launch audience in Phase 2.
Wire the transactional email sender45m
Separate domain or subdomain from marketing mail, so one cannot poison the other.

Start the owned list

Launch the newsletter2h
Pick a cadence you can hold on your worst week, not your best one.
Build a 7-day email course as the lead magnet16h
Converts better than a PDF and teaches them to open your emails at the same time.
Build a welcome sequence from your greatest hits3h
Your five best pieces, sent automatically. Zero marginal cost, permanently.
Hold the cadence for twelve weeks12h
Twelve consecutive sends is where a list stops being a liability and starts being an asset.
Ask for the date they are working toward, and time the emails to it2h
A launch, an event, a filing deadline: an email due two weeks before their date gets read, and one due two weeks after signup is noise. Add one date field to the form and count the sequence back from it.

Automate the lifecycle

Automate welcome and activation8h
Behaviour-triggered, not day-based. “Has not activated after 48h” beats “day 2”.
Automate the trial-expiry sequence4h
Day −3, day −1, expiry day, day +3. The last one converts more than you expect.
Build proper dunning4h
Card retries, an updater for expired cards and a short email sequence. Stripe’s own billing page says it recovered $8.2B in failed payments in 2025; read any recovery figure as the vendor’s own.
Build the win-back sequence4h
Sent 30 and 90 days after cancellation, and only when you have actually shipped their reason.
Put an upgrade prompt at the limit moment10h
When they hit the ceiling, not on a schedule. Context is the entire conversion rate.
Automate the review ask after a win4h
G2 weights a review down from day one — gently for 90 days, hard after 18 months — so the Phase 2 count is already shrinking. Send the ask after the third win, once per user, never on a schedule.

Plays

Reusable patterns that explain how: backed by read sources first, then practitioner advice, then our own ideas.

Announce the price rise for new customers, with a date, before you raise itBacked · 1 source
Before raising your price, email trial users and free accounts that the price rises for new customers on a fixed date, and that anyone who subscribes before then keeps today’s price. The date turns a vague "later" into a decision, existing customers stay on their old price, and you learn at once whether the new price holds.
Reply in person to every cancellation reason within a dayBacked · 1 source
Make the billing portal ask why a customer is cancelling, then have the founder reply personally to each answer within a day: a pause or smaller plan for price, an honest date for a missing feature, a question for a lost comparison. Some come back, and the reasons, counted monthly, tell you what to fix next.
A teardown series: one company’s funnel per issueOur idea
Structure the newsletter as a recurring teardown: each issue dissects one real company’s funnel, pricing, or emails with screenshots and honest scores. The format solves the blank-page problem forever, readers forward issues about companies they know, and featured companies reshare — distribution built into the premise.
"What we shipped, what we learned" — a changelog with a pulseOur idea
Send a recurring "what we shipped and what we learned" issue: the changes, the reasoning, one honest miss, one lesson. Customers get a reason to log back in, prospects get visible momentum, and the archive becomes public proof the product is alive — the cheapest retention email you’ll ever write.
The one-question issue that fills your roadmapOur idea
Occasionally send an issue that’s one question long: "What are you stuck on with [topic]?" Answer every reply personally. Replies train inbox providers to trust your domain, the answers hand you a content and roadmap backlog written in customers’ words, and a fraction of the threads become sales conversations you didn’t chase.
The first-value email: one action, one link, on signup dayOur idea
Send every new signup one email on day zero that names the single action after which your product is worth using, links straight to where they take it, and says how long it takes. A welcome email that lists features spreads attention thin; one that points at the first win gets it done, and the rest of onboarding follows.
One question to everyone who signed up and stalledOur idea
Email everyone who signed up but never reached first value, one at a time and from the founder: a single sentence asking what stopped them. The replies are the most specific onboarding research you will get, a few people come back because someone asked, and telling them when the thing they named is fixed often brings more back.
The month-two email: what to do when the quick wins are doneOur idea
Around week five, email customers the habit or feature that keeps paying off once setup is done, with one concrete example of it working. Usage quietly drops in the second month when the first wins are behind people; an email that hands them the next level of value gives them a reason to keep the tab open.
A quarterly "here is what you got out of it" recap per customerOur idea
Once a quarter, send each customer a short recap in their own data: what the product did for them, how that compares with last quarter, and one thing they have not tried yet. People forget value they do not see, and a recap in their own numbers is the renewal argument made months early, without a sales call.

What the evidence says

Evidence, weak

Stripe’s billing page says $8.2B in failed payments were recovered in 2025 and $14 recovered for every $1 spent on its tools, and lists Smart Retries, expired card updates, recovery and retention automations and cancellation surveys. It states no share of involuntary churn recovered. Two earlier readings of a 55% average recovery rate could not be found on the page.

A vendor’s own landing-page totals with no stated method, and a figure two readers reported was not on the page when it was checked directly.

Re-checked 2026-11-10 by Claude, reading the page directly: not confirmed. The page does not state a 55% recovery rate (the only 55% is a sample tax rate). It says $8.2B in failed payments were recovered in 2025 and $14 for every $1 spent. The claim was rewritten to that.

Changed in the plan: Plan text corrected 2026-11-10, twice: the first version had 30-50% of involuntary churn with no primary source; the second had a 55% that the page does not carry. It now quotes the totals the page does state.

Stripe Billing (read in full)

True as of 2026-11-10; to be re-checked by 2027-02-10.

Sources

Where it sits in the plan

1.6Own your channels before you need themin Ship-ready
4.6Start the owned listin Find the one channel that works
5.3Automate the lifecyclein Compounding engine

Email, newsletters and lifecycle