Build feature requests on top of existing platforms

Every major platform accumulates a backlog of feature requests it will never build. The startups that mine those backlogs — shipping the functionality users are begging for on top of someone else's infrastructure — capture demand that's already been validated by millions of frustrated users.

The core insight is deceptively simple: the most popular software in the world is also the most complained-about. Every platform with millions of users generates a proportional volume of unmet needs — feature requests buried in forums, workarounds duct-taped together by power users, integrations the platform team deprioritized three roadmap cycles ago. These gaps aren't bugs. They're business plans.

The mechanism works because of a structural misalignment between platform incentives and user needs. A platform like Salesforce, Shopify, or Twitter optimizes for the broadest possible user base. That means features serving the 80th percentile get built; features serving the 95th percentile — often the most valuable, most willing-to-pay users — get ignored. The platform can't justify the engineering resources for a niche feature that serves 5% of users. But 5% of Shopify's two million merchants is 100,000 potential customers. That's a real business.

The underlying asymmetry is one of focus versus breadth. Platforms must be generalists. You get to be a specialist. You can obsess over a single workflow, a single integration, a single pain point — and build something ten times better than the platform ever would because you're not balancing it against ten thousand other priorities. The platform's inability to focus is your moat.

This framework also benefits from a powerful distribution advantage: the platform's own ecosystem. Shopify has an app store. WordPress has a plugin directory. Salesforce has AppExchange. Chrome has the Web Store. These are built-in distribution channels where users actively search for solutions to the exact problems you're solving. You don't need to generate demand — the platform already did that. You just need to show up where frustrated users are looking.

The best practitioners of this framework understand that the end state isn't staying a plugin forever. The trajectory is: feature → product → platform. You start by filling a gap, accumulate users and data, and eventually build enough standalone value that you can exist independent of the original platform — or become so essential that the platform can't remove you without user revolt.