Building on Platforms
Platform apps can be great investments, but they are built on rented land. They deliver high margins, low churn, and "passive" distribution. Yet, a single platform update can demolish them overnight. This structural tension dictates our entire acquisition playbook.
§The Upside
Dominant platforms pipe demand directly to category leaders. You spend zero dollars on marketing. You can certainly pour capital into customer acquisition to accelerate growth. However, the platform's native gravity provides a baseline momentum that independent software struggles to replicate.
Consider our Chrome application. We own the category. Chrome expands its user base steadily every year. That ecosystem growth automatically becomes our growth. We skip the marketing campaigns entirely. The platform acts as our permanent sales engine.
Platform dependency drastically reduces churn. Users invest hours configuring Zendesk or Shopify. They embed your tool into that foundation. Extracting your software requires tearing out their established workflows. You represent a microscopic fraction of their total operating cost. Consequently, your retention anchors to the platform's retention rate, which almost always outperforms standalone metrics. As the math dictates: churn murders software.
Platforms actively want your success. Shopify algorithms promote top-tier apps. Apple supplies developers with crucial visibility tools. A robust plugin ecosystem solidifies the platform's moat. By wielding your engineering resources, Salesforce avoids hiring internal developers to maintain niche features. When you lead a category, the platform disproportionately routes new ecosystem capital your way.
§The Downside
Platforms will issue compliance mandates. Most requests are routine. Some look like demolition orders.
Chrome forced the migration from Manifest V2 to Manifest V3. Google wanted to suffocate ad blockers to protect their core advertising revenue. Their structural migration forced us to rebuild our extension from the foundation up. Justin spent his entire holiday executing a massive, load-bearing rewrite. Rebuilding a mature, complex asset simply to appease a landlord's policy shift is an atrocious waste of engineering capital. You lack leverage. You comply. You survive.
We dominate our Zendesk category. Our position is fortified, but our churn heavily correlates with users abandoning Zendesk itself. They cancel the platform. We get caught in the blast radius. Exit surveys consistently reveal regret. Users loved our tool but lost the foundation it lived on. You cannot fix this. If the platform stagnates, your revenue stagnates. A shrinking ecosystem eventually crushes your independent growth efforts.
You can hedge this risk by abstracting your architecture to serve multiple platforms. Fomo.com executed this flawlessly. They originated as Notify.app, a Shopify plugin leveraging social proof. After the acquisition, Ryan's team retooled the engine to bridge multiple ecosystems. They now power over 100 integrations. If you acquire or forge platform apps, cross-pollination is your ultimate defense. Transitioning your core asset across diverse ecosystems yields the ultimate prize. You become independent software.
§The Nightmare Scenario
The fatal strike: the platform clones your feature and evicts you.
We have not experienced this. History shows it remains rare. Platforms prefer outsourcing the heavy lifting to third-party developers. They value the developer ecosystem and avoid burning profitable bridges. You absorb their development costs while enriching their marketplace. They lack the incentive to execute you. They might compete. They rarely evict.
The glaring exception is violating the Terms of Service. Renegade WhatsApp tools operate in the gray zone, then act shocked when Meta aggressively cleans house. If you operate within the blueprints, the threat matrix remains low.
When platforms do deploy a native alternative, their solution is predictably sterile. They build broad features for the median user. You forge specialized tools for power users. Their launch frequently educates the broader market, driving uninitiated users toward your category. If your craftsmanship remains superior, you survive the initial tremor and capture the newly expanded market.
§Growth Hits a Ceiling
The ultimate constraint is hitting the ceiling.
Securing 80% of a platform's addressable market chains your trajectory entirely to the platform. Ecosystem expansion hits a hard stop. Every incremental percentage point of your growth requires the platform to expand first.
The breakout maneuver requires moving off-platform. This requires heavy lifting. You must construct independent acquisition channels, engineer standalone billing infrastructure, and battle in the open market. Yet, unlocking a massive new addressable market justifies the labor. This is especially true when your existing users already traverse multiple ecosystems and demonstrate a willingness to buy standalone tools.
We plan to deploy more capital into this strategy, despite the structural risks. You are introducing new dependencies. You risk starting from zero. We currently rank this lower on our priority matrix. But, when loyal users consistently request your tool on their new ecosystems, you must listen to the market.
§Our Approach
Platform assets currently generate roughly one-third of our revenue. We intend to compress that exposure down to 20%. Platform tools provide stable, high-margin cash flow. They demand drastically less maintenance, marketing, and sales overhead than independent software. However, the systemic dependencies are severe, and compliance taxes compound over time.
Will we continue acquiring platform apps? Yes. But with stricter parameters.
We purchase platform assets at a steep discount to their standalone cash flow valuations. The omnipresent risk of demolition justifies that haircut. We hunt for these specific traits:
- Fully constructed applications, not half-finished projects.
- Familiar, proven platforms we already trust.
- Assets protected by deep structural moats.
- Category leaders firmly welded into user workflows.
We acquire them. We reinforce their architecture. We methodically bridge them off-platform.
These are fantastic assets to yield. Just do not let them become your foundation.