Substack welcome email matches the entry path
Write different welcome emails for free, paid, imported, and founding subscribers so the first inbox message reflects how the reader arrived instead of treating every signup like the same job.
Why this can grow a startup
Newsletter onboarding usually breaks because the publication keeps one generic script for four different kinds of readers. Substack already splits that path for you. Free subscribers need orientation and a reason to come back. Paid and founding members need reassurance that they bought into the right thing. Imported readers need context because they did not just click a fresh subscribe prompt. Matching the welcome email to the entry path makes the first send feel deliberate instead of automated in the bad sense.
Source-backed example
Substack's welcome-email settings include separate templates for free, paid, imported, and founding subscribers.
Source-reported evidence
Source: Substack Support: How do I set up welcome emails on Substack?
Substack supports 4 welcome-email variants: free, paid, imported, and founding subscriber.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Email, Substack, Lifecycle is relevant to substack, welcome email, audience segmentation and you can run a bounded test with a free budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Email and Substack, using evidence from Substack Support: How do I set up welcome emails on Substack? as context—not as a promised result.
- Record a baseline for: Share of target users completing the product's first-value action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Build creator and community systems around real incentives, trust, and repeat participation.