Start with the useful outcome
A team app might need a first shared task. An integration tool might need a successful import. A mobile habit app might need a first meaningful session. “Send a welcome sequence” is too broad to choose the right message.
Use evidence for the claim it supports
Our library includes first-party product documentation, implementation guidance and practical lifecycle analysis. A documented feature can establish that a workflow exists. It cannot establish that a particular email caused a conversion lift.
Every suggested email identifies the source cards and patterns behind its reasoning. Adapted ideas and hypotheses are labeled. Exact timing and copy remain proposals to check against your product.
Keep the assumptions visible
We read up to three public product pages, or use your description when the website cannot be read. You confirm the audience, commercial model, useful first outcome and known events before generation. We do not access your customer database or infer installed events from a marketing website.
Check the output before saving it
Generated drafts are checked for structure, known citations, declared variables and safe links. Missing app destinations become setup dependencies. A human still needs to check the product facts, recipient permission, tone and implementation before sending.
What this research does not claim
The current library is not 1,000 independently observed funnels. The original 1,000-funnel idea is a research ambition, not a completed claim. We do not claim a universally optimal sequence, guaranteed ROI, or proof of results for every industry.
Some of the material behind the work
- Welcome Email Sequence for SaaS: PLG, Sales-Led, and Freemium Templates
Choose the onboarding objective before copy: self-serve activation, managed implementation, and freemium adoption require different paths.
- Start Simple and Improve Gradually
Show the broader lifecycle roadmap while making the first useful implementation small and achievable.
- How we built our onboarding email flow (with actual performance data)
Prerequisite accuracy and versioned goals matter: unreliable ingestion checks previously produced irrelevant emails.
- Using Automations
Resend documents native event-driven workflows and API creation of a full graph. This makes a disabled native implementation a plausible handoff target; it does not demonstrate that every proposed lifecycle rule maps correctly.
- How Selling 3K AppSumo Deals Proved Foundational, Not Niching Down, and Other Reflections on Scaling a Bootstrapped SaaS with Paperform’s Co-Founder, Dean McPherson
Paperform asks what users want to create, then introduces broader capabilities over time. Its founder reports little subsequent upgrading under generous feature-based plans, limiting assumptions about recurring expansion campaigns.
Library reviewed September 8, 2026. Source availability and provider behavior can change. We preserve source provenance and revisit material that affects implementation.