The SaaS bundling conversation has evolved substantially over the past few years. The “build vs buy” question has been joined by an equally complicated “buy this vs buy that bundle” question, with major platform players offering increasingly comprehensive product suites and smaller specialists competing on best-in-class capabilities.

Where do bundles actually deliver value in 2026, and where are they better avoided? After watching this dynamic play out across multiple organisations and roles, here’s what I’ve concluded.

When bundles actually deliver value

The bundles that work share specific characteristics.

The components are genuinely integrated, not just co-located. Microsoft 365’s integration of Outlook, Teams, OneDrive, SharePoint and the broader Office stack produces real workflow benefits because the integration is genuine — files referenced in chat, calendar events created from email, document collaboration that doesn’t require sending files back and forth. The components inside the bundle work better together than equivalents from separate vendors would.

The buyer values comprehensiveness over specialist capability. Organisations that don’t have specific best-in-class needs for any individual component, and that prefer the simplicity of vendor consolidation, generally benefit from bundle adoption. The capability of the bundle’s individual components doesn’t have to be the absolute best in each category if the integration and the simplicity produce sufficient value.

The pricing produces actual savings. Some bundles do produce meaningful savings over equivalent point-tool combinations. The discount math works when the buyer would otherwise have purchased many of the components separately. Bundles that produce theoretical savings only because they include components the buyer wouldn’t have purchased aren’t actually saving money.

The vendor relationship is one the buyer would invest in anyway. The procurement, contract management, and ongoing relationship overhead of major vendor relationships is substantial. Buyers consolidating to a vendor they’d already need a major relationship with are reducing the relationship management burden; buyers consolidating with vendors they’d rather have less involvement with are accumulating concentration risk.

When bundles destroy value

A few patterns that produce poor bundle outcomes:

The buyer accepts a meaningfully worse component because it’s in the bundle. The Salesforce Sales Cloud bundled with various marketing automation tools is a recurring example — the marketing automation in the bundle is generally meaningfully weaker than purpose-built alternatives, but buyers accept the weaker option because it’s bundled. The cost of the inferior tool over years often exceeds the savings of the bundling.

The bundle creates lock-in that’s expensive to escape. Once integrated workflows, data structures, and team processes have grown around a particular bundle, transitioning out becomes substantially more expensive than the original adoption suggested. The buyer can be effectively trapped at price increases that wouldn’t be acceptable to a buyer with real alternatives.

The bundle includes components the buyer doesn’t actually use. The “we paid for it so let’s use it” pressure to adopt components that aren’t actually well-suited to the buyer’s needs produces real opportunity costs. The components that get used despite being suboptimal create friction; the components that don’t get used represent wasted spend.

The bundle’s pricing structure penalises usage growth disproportionately. Some bundle pricing structures produce escalating costs as the buyer’s use of the bundle grows, in ways that the initial purchase economics didn’t make clear. The “cheap to start, expensive to scale” pattern is common in bundle pricing and not always understood by buyers.

What’s specifically going on with the major bundle vendors

Microsoft has been the dominant bundling player and continues to expand. The Microsoft 365 bundle now includes Teams, the productivity suite, security and compliance tools, increasingly comprehensive AI capabilities through Copilot, identity management through Entra, and various other components. The argument for adoption is genuine for organisations already deeply committed to Microsoft. The argument against is concentration risk, the lock-in dynamics, and the fact that some of the bundled components are noticeably weaker than purpose-built alternatives.

Google’s Workspace bundle competes for similar customers but has a genuinely different character. The collaborative document editing in Docs, Sheets, and Slides remains best-in-class for real-time multi-person editing. The integration with Gmail and Calendar produces a coherent everyday work experience. The constraints are around enterprise functionality where Microsoft has historically been stronger, and around the specific workflows that require Microsoft Office file format compatibility.

Salesforce’s bundle continues to expand through both organic development and acquisition. The platform genuinely supports workflows that require deep integration between sales, marketing, customer service, and analytics. The constraints are the cost (which has continued to increase faster than alternatives), the implementation complexity, and the variable quality of newer components compared to the core CRM.

HubSpot’s bundle has positioned itself as the alternative to Salesforce for mid-market companies, with substantively integrated marketing, sales, and service tools at lower price points than Salesforce’s enterprise offering. The constraint has been the complexity ceiling — HubSpot works extremely well up to a certain scale of business and starts producing limitations beyond that scale.

Atlassian’s bundle for engineering and project workflows has had a complicated few years, with the cloud transition producing some operational challenges and pricing changes that produced customer pushback. The integration of Jira, Confluence, and the broader product suite remains genuinely valuable for engineering organisations, and the company appears to be working through the transition challenges. The competitive pressure from Linear, Notion, and other newer alternatives is real.

How buyers should approach the decision

A practical framework I’ve found useful:

Start with the components you’re sure you need at high quality. If a single component is essential and a specific best-in-class option is the right answer, build the rest of the stack around that decision. Don’t compromise on a critical capability to fit a bundle.

Assess the integration value honestly. The integration benefit of a bundle is real but specific. Map out the actual workflows that would benefit from integration and compare to the workflows where best-in-class point tools would be better. The comparison often reveals that specific integration benefits are overweighted in bundle marketing.

Calculate the realistic cost over a multi-year horizon. The bundle pricing at the point of purchase is one piece of the picture. The price escalation through the contract term, the cost of specific add-ons that are likely to be needed, and the cost of expanding to additional users or use cases all matter. The realistic cost calculation is often substantially higher than the entry pricing suggests.

Consider the lock-in implications. If circumstances change and the bundle no longer fits, what would it cost to move? The buyers most happy with their bundle decisions had explicit awareness of the lock-in implications going in. The buyers least happy were surprised by lock-in dynamics they hadn’t fully thought through.

Don’t underestimate the relationship management burden of multi-vendor stacks. Best-of-breed point tools produce real overhead in vendor management, contract administration, billing reconciliation, and integration maintenance. The benefit of best-of-breed needs to be weighed against this overhead.

What I’d recommend

For organisations under 50 people that have basic productivity and collaboration needs, the major productivity bundles (Microsoft 365 or Google Workspace) generally make sense as the foundation, supplemented by point tools where specific best-in-class capability genuinely matters.

For mid-sized organisations (50-500 people) the analysis becomes more complex and depends substantially on the specific workflows. The blanket recommendation toward bundles becomes less clear, and component-by-component analysis becomes more important.

For larger enterprises, the bundling decisions are usually made at the platform layer (which CRM platform, which infrastructure platform) with point tools selected within those platform decisions. The blanket bundle adoption rarely makes sense at scale.

For specific workflows where best-in-class matters most — engineering tools, design tools, analytics tools, specialised vertical applications — the point tool generally produces better outcomes than the bundled component, regardless of organisation size.

The honest summary: SaaS bundles produce real value in specific situations and produce real costs in others. The reflexive position of either “bundles are always cheaper” or “best-of-breed is always better” produces worse decisions than thoughtful situation-specific analysis. The buyers who do the analysis well end up with stacks that combine bundles and point tools in ways that match their actual needs. The buyers who don’t do the analysis end up with whatever the most aggressive vendor sales team convinced them to buy.