SaaS Insider
The consolidation nobody predicted
Unbundling was supposed to be the permanent condition of SaaS. Instead, buyers spent two years cutting vendor counts, and the tools that bundled well are winning categories they were not supposed to.
- Author 01
WebTechOS Editorial
- Published 02
2026-07-18
- Read 03
7 min
For a decade the received wisdom was that best-of-breed beats suite. Buyers would assemble specialised tools, integration would get cheap enough not to matter, and the suite vendors would be hollowed out from every direction at once.
That is not what happened. Integration did get cheaper, but integration was never the real cost — the real cost was the human overhead of owning fifty vendor relationships, fifty security reviews, fifty renewal negotiations and fifty places where data could be wrong. That cost scales with vendor count and no amount of API quality reduces it.
The bundles that worked
PostHog is the clearest case. Product analytics, session replay, feature flags, experiments and error tracking are five categories with five well-funded specialists, and each of PostHog's modules is slightly behind the best-in-class option. Buyers took the bundle anyway, because one contract and one data model beat five marginally better tools.
HubSpot's marketing, sales and service hubs work on the same logic and have for longer. The strategic weakness is identical in both cases: bundles win on consolidation and lose on depth, so they are perpetually vulnerable to a buyer who genuinely needs depth in one module.
Every module slightly behind best-in-class, and buyers took the bundle anyway.
Where unbundling still wins
Depth beats breadth wherever the category is a company's core competitive surface. A developer-tools company will run Plain over a support suite because developer support is how it competes. A data-intensive business will run Hex alongside a BI tool rather than accepting either alone.
The pattern that has emerged is a bundle at the base and specialists at the edges — consolidate the categories where you are ordinary, and buy depth only where being ordinary would cost you customers. That is a more useful buying principle than either doctrine on its own.
WebTechOS accepts no payment for coverage, placement or scores. Where a piece references pricing, it reflects published list rates at the date shown.
Keep reading
All insights →The agent pricing reckoning
Per-seat licensing assumed software helps a person work. Agents do the work. Four billing models are now fighting to replace the seat, and three of them will lose.
AI Agent HubWhy most agent projects fail in month three
The demo works. The pilot works. Then something changes upstream, nobody notices for two weeks, and trust never comes back. A field guide to the failure that kills more agent projects than capability ever has.
Customer Support TechCustomer support after deflection stopped being the metric
Containment rates became contractual, and then immediately stopped being interesting. What replaced them says more about where support tooling is headed than any product roadmap.