What is bundling and unbundling in product strategy?

The cycle

An incumbent assembles many capabilities into a bundle. Because it must serve all of them, none is outstanding. A new entrant picks one, makes it dramatically better, and wins the customers for whom that capability is the point. As the entrant grows, it adds adjacent capabilities and becomes a bundle. Somebody unbundles it.

This is not a law, but it recurs often enough to be a useful lens on where a market is in its life.

Why unbundling works as a wedge

Bundles defend with switching costs and integration, not with quality of any single part. That is the seam. A focused product only needs to be better at one thing than a bundle can afford to be — and it usually can be, because the bundle's roadmap is split across a dozen priorities.

The entrant's advantage is not being smarter. It is having a narrower obligation.

Zoom entered a market with many well-funded conferencing products by being obsessively good at one thing: joining a call working, every time, quickly. Everything else was secondary, and the incumbents could not match the focus because their conferencing was one module inside a suite.

Why re-bundling follows

Focus that wins a wedge eventually caps it. Once you have most of the customers who care intensely about that one capability, growth means either raising prices or selling more to the same people.

Rippling's compound-startup approach makes the re-bundling explicit — payroll, devices, identity and benefits sold as one because the same underlying employee record powers all of them. That is the strong form: the pieces share a substrate and each addition makes the others better.

The weak form is a set of products sharing only a brand and a bill. Customers detect this quickly, and the bundle discount becomes the only argument for it.

The trap: unbundling yourself

The cycle describes what a new entrant does to an incumbent's bundle. It is not advice to split your own product.

Foursquare separating check-ins into Swarm is the standard illustration: internally the two use cases were distinct, and to users it meant one habit now required two apps, with the friction landing entirely on the people who liked the product most. The reasoning was sound and the outcome was still bad, because users experience a split as a subtraction.

Before splitting, ask whether the problem is genuinely that two audiences want different things — or that your own teams want clearer ownership. Only the first is a product reason.

Reading a market with the lens

Ask what the dominant bundle is, and which part of it customers complain about while continuing to pay. That gap is where a wedge exists. Then ask what makes the bundle sticky — data, workflow, procurement, compliance — because that is what you will eventually have to overcome, and being better at one feature has never been sufficient on its own.