Build a platform strategy roadmap

Platforms Fail on Prerequisites, Not on Product

The most common platform failure is launching before the prerequisites are in place — a developer portal with no developers, a marketplace with no supply, an app platform with no apps. Stripe's engineering writing and the Y Combinator library both treat prerequisites as the gating factor: if you do not have PMF on v1 and minimum partner density on day one, platform launches starve. The Reforge research on growth loops shows that platform flywheels only spin when both sides of the loop have enough density to produce value without external marketing subsidies.

How the Build a platform strategy roadmap Prompt Works

The prompt forces a 0-3 scorecard on six prerequisites before any roadmap sequencing, then requires each quarter of the 12-month plan to address the lowest-scoring prerequisite first. The partner density question is the load-bearing one — platforms with strong tech and weak partner density fail in launch month.

When to Use It

• Leadership is asking when you go from product to platform.
• A partner ecosystem is asking for API or app extensibility.
• You are building v2 and want to avoid re-architecting for platform later.
• A competitor launched a platform and the board wants a response.
• Your pricing model is bumping up against a flat curve and a platform take rate would unlock it.

Common Pitfalls

• Launching before v1 PMF. A platform MVP on top of a non-PMF product compounds both risks. Fix v1 first.
• Underestimating governance. Moderation, quality, fraud, and deprecation are the hidden costs that kill platform momentum.
• No partner density on day one. A platform with 2 partners looks empty; with 20 it looks alive. Pick the archetype whose minimum density you can actually achieve.

Sources

• Stripe Blog — Stripe
• Y Combinator Library — Y Combinator
• Growth Loops — Reforge
• Product Strategy Overview — Silicon Valley Product Group