1
Define the platform concept and target community first
Before filling in any other section, write a one-paragraph description of the specific problem your platform solves and the precise community it serves. Every subsequent section should be anchored to this definition.
π‘ If you cannot name a community of at least 500,000 people who share the unmet need you are solving, the niche may be too narrow to build a sustainable business around.
2
Build market sizing from the community up
Identify the total population of your target community using two independent sources β industry reports, census data, or platform-specific audience data. Then estimate what percentage you can realistically reach in Years 1, 2, and 3.
π‘ A credible beachhead is 0.5β2% of your SAM in Year 1. Projecting 10% in the first year will immediately flag unrealistic expectations to any experienced investor.
3
Map competitors at the niche level, not just the platform level
List at least four alternatives your target users currently rely on β including subreddits, Discord servers, Facebook Groups, and niche forums β not just mainstream platforms. Explain specifically why each falls short.
π‘ Users of niche communities are often loyal to existing informal solutions. Your competitive section must explain why they would switch, not just why your features are better.
4
Define the core engagement loop before the feature roadmap
Write one paragraph describing the single action that makes users return daily β posting, reacting, messaging, or discovering content. Then build your Phase 1 feature roadmap backward from that loop.
π‘ Every Phase 1 feature should directly support the core loop. Any feature that does not strengthen retention belongs in Phase 2 or later.
5
Choose and model two to three monetization streams
Select revenue models appropriate to your platform's engagement pattern and community norms. For each stream, estimate ARPU, adoption rate, and the MAU threshold required before that stream generates meaningful revenue.
π‘ Advertising is the default assumption for social platforms, but it requires 100k+ DAU to be material. Subscription and transaction-fee models can generate real revenue at much lower scale.
6
Build the financial model from user cohorts, not revenue targets
Model user acquisition by cohort β Month 1 users, Month 2 users, etc. β with a retention curve for each. Sum the cohorts to get MAU, then apply ARPU to get revenue. This approach makes your assumptions visible and testable.
π‘ Include a sensitivity table showing what happens to runway if Month 6 MAU comes in at 60% of plan. Investors test downside scenarios before anything else.
7
Write the executive summary last
Distill the single most compelling data point from each section into a 1β2 page summary. Lead with traction if you have it, or with the size and sharpness of the problem if you do not.
π‘ For a social platform, the strongest executive summary opens with a vivid description of the underserved community β make the reader feel the problem before presenting the solution.
8
Stress-test growth assumptions with an advisor before sharing
Have someone with consumer app or community-growth experience review your MAU projections and K-factor assumptions before sending the plan to investors or accelerators.
π‘ A K-factor assumption above 0.5 for a new platform is aggressive and will be challenged β be prepared to defend it with specific referral mechanics and comparable benchmarks.