The platform layer began consolidating, and every point solution felt the ground shift

There was a shop in Kozhikode that sold the best chai in the neighbourhood. The owner had been there for twelve years, built a loyal following, and never missed a day. Then the building's landlord opened a tea stall in the lobby. Same building. Lower rent (he was paying it to himself). Better signage. The chai was worse, frankly. But the landlord had the foot traffic, the location, and the patience to wait.

Within eighteen months, the original shop closed. Not because the tea was inferior. Because the landlord controlled the building.

That story is playing out across the software industry right now, at a speed that should concern anyone who has built a product on top of someone else's platform.

The Absorption Pattern

If you are a product leader at a company that built its core value on a platform you do not own, this is the part where I tell you something you probably already suspect but have not said aloud in a leadership meeting. The platform is coming for your category. It may not be this quarter. It may not be next year. But the absorption pattern is as predictable as gravity, and it has been accelerating.

Here is how it works. A platform creates an open surface, APIs, integrations, a marketplace. Third-party developers build tools that fill gaps the platform left. Users adopt those tools. The platform watches which tools get traction. Then, quietly, the platform begins building native versions of the most successful ones. Not all of them. Just the ones that proved there was demand.

Best-of-breed is becoming the platform's unpaid R&D department.

I watched this happen from the inside at Adobe. For years, Adobe's creative tools had a thriving plugin market. Designers installed third-party extensions for colour palette generation, stock photo integration, font management, prototyping workflows. These plugins were not trivial. Some of them were built by teams of ten or fifteen people who had invested years understanding design workflows better than Adobe's product teams did.

But Adobe was watching. And one by one, the capabilities that those plugins had pioneered started appearing as native features. Stock photo integration became Adobe Stock. Colour tools became built-in. Prototyping capabilities evolved into Adobe XD. The plugin developers who had built real businesses on Adobe's platform had no structural defence. They had done the market validation. Adobe did the absorption.

The plugin developers were not stupid. They were structurally exposed. There is a difference.

The Platform Tax

Every platform relationship involves what I call the platform tax. It is not the percentage cut on marketplace revenue, though that exists too. The platform tax is the ongoing cost of building on a foundation you do not control. It is the API change that breaks your integration overnight. It is the terms of service update that restricts your data access. It is the native feature announcement that makes your entire product roadmap irrelevant during a Tuesday keynote.

The platform tax is not a line item on your P&L. It is a risk factor that compounds over time.

At Freshworks, I lived inside this tension from the other side. We integrated deeply with Salesforce. Our products worked alongside their CRM, extending it, complementing it, making it more useful for specific customer segments. But we were also competing with Salesforce in adjacent categories. That dual position, partner and competitor simultaneously, shaped our product strategy in ways that most people outside the company never saw.

Every integration decision was also a competitive calculation. Build deeper into the Salesforce surface and you reach more customers. But you also become more dependent on a company that could decide, any quarter, that your category is worth absorbing. Pull back from the integration and you lose distribution. Lean in and you lose independence.

The platform is never neutral. It is patient.

That patience is what makes platform competition different from ordinary market competition. A direct competitor tries to take your customers today. A platform competitor lets you build the market, validates the demand, and then uses its distribution advantage to offer a "good enough" native version that customers adopt because it is already in their workflow. The platform does not need to build a better product. It needs to build one that is close enough and already there.

Why "Good Enough" Wins on Platforms

This is the part that is hardest for product-minded founders to accept. You built the better tool. Your users agree. Your NPS is higher. Your feature set is deeper. Your support is more responsive. On every measure of product quality, you win.

But product quality is not the variable that determines outcomes in platform competition. Distribution is. And the platform owns distribution the way a landlord owns the front door.

I have seen founders spend months building feature comparison charts, convinced that if they could just show customers the objective superiority of their tool, the market would choose rationally. But markets do not choose rationally when one option is already embedded in the workflow. They choose conveniently. They choose the thing that does not require a separate login, a separate contract, a separate integration. They choose the thing that is already there, even when the thing that is already there is worse.

This is not a failure of the market. It is how platform economics work.

The absorption pattern is accelerating because AI has given platforms a new capability advantage. Microsoft is embedding Copilot across every surface. Salesforce is building Einstein into every workflow. Google is layering Gemini into Workspace. Each of these moves absorbs territory that third-party AI tools had staked out. The startups that built AI-powered extensions for these platforms are watching the platform replicate their core functionality as a native feature, bundled at no additional cost.

What Defence Looks Like (and What It Does Not)

If you are reading this and recognising your own situation, here is what I have observed from watching this pattern across multiple companies and platforms.

There is no defence based on feature superiority alone. Features can be copied. But features that live on someone else's platform can be absorbed entirely. The only structural defences are the ones that create value the platform cannot replicate without fundamentally changing what it is.

Depth in a vertical that the platform will never prioritise is one defence. Platforms are horizontal by nature. They serve the broad middle. If your product serves a narrow, specific segment with needs the platform will never address natively (because the segment is too small to justify the platform's engineering investment), you have a position that absorption does not threaten easily.

Owning the customer relationship directly, rather than through the platform's marketplace, is another. But this is harder than it sounds, because the platform's distribution is often why you have customers.

The hardest option, and the most durable, is building your own platform surface. Becoming the thing others build on, rather than the thing built on top. But that requires a different kind of company, a different kind of ambition, and a runway that most startups do not have.

None of these options are easy. The structural reality is that building on a platform is a trade: distribution today for vulnerability tomorrow. Every point solution founder makes that trade knowingly or unknowingly.

The chai shop in Kozhikode understood something that took the software industry decades to articulate. When you build your livelihood inside someone else's building, you are not just renting space. You are renting permission. And permission, by its nature, can be revoked.

The question worth sitting with is not whether the platform will come for your market. It is what you will have built, independent of the platform, when it does.