Substack subscriber count hidden until social proof is real
Let the Welcome page show launch age early and approximate subscriber count later, because Substack only displays that count after 1,000 subscribers and also lets you hide it.
Why this can grow a startup
Weak social proof can hurt more than no social proof. Substack quietly gives publishers a timing rule for that problem. Before the audience is large enough, the Welcome page can lean on recency and editorial promise instead of a small number that makes the publication look untested. Once the subscriber base is meaningfully larger, the count becomes useful proof. The toggle matters because it lets the page match the stage of the publication instead of forcing one signaling strategy forever.
Source-backed example
Substack says the Welcome page shows an approximate subscriber count only after a publication has more than 1,000 total subscribers, and publishers can hide that number in Settings.
Source-reported evidence
Source: Substack Support: What is a Welcome page on Substack?
Approximate subscriber count appears on the Welcome page only after 1,000 total subscribers.
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 Substack, Brand, Conversion is relevant to substack, social proof, welcome page 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 Substack and Brand, using evidence from Substack Support: What is a Welcome page on Substack? as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next 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.