Platform built it natively
K4 · §3.5.0 · Banks/Big Tech
A product built on a platform whose owner can add the same feature for every existing user. Apple, Google, AWS, Stripe, Slack, CRMs, CMSs, and payment systems can turn a paid add-on into a built-in checkbox. The danger is assuming a standalone product can beat free distribution from the platform it depends on.
Signs your idea has this
- 01Most product value comes from one platform API or data layer.
- 02The platform has announced or hinted at the same workflow.
- 03Users already live inside the platform during the job.
- 04The platform can bundle the feature without paying to reach new users.
- 05Switching away from the add-on is easy because the data stays on the platform.
- 06The main defense is only a nicer interface for work that already lives inside the platform.
- 07The platform already controls the nearby product layer.
Public idea database
No public examples yet. The idea database is still small, and we are not making one up.
Rare survivors
Survived by serving a distinct engineering workflow and product taste, not by copying a native tracker feature.
Survived by changing how documents and databases work together, not by offering a thinner office-suite feature.
Why this pattern exists fundamentally
Platforms defend valuable workflows by bundling them. A standalone product can survive only when it owns a different audience, a different product shape, or a workflow the platform keeps ignoring. A nicer interface rarely beats built-in distribution.
Related patterns
Got an idea that looks different? Run the same framework before building.
Check whether the platform can absorb it