Microsoft earns more in a quarter than Salesforce does in a year — that gap is a competitive weapon

Horizontal software — CRM, HCM, collaboration, workflow — sells to everyone, across every industry. It’s the biggest, most visible SaaS battlefield, and it runs on one brutal dynamic: the fight to climb from point tool to suite to platform, because the higher you climb, the deeper the moat and the harder a giant can hurt you.

A point tool solves one problem well but is dangerously replaceable. A suite bundles many tools and raises switching costs. A platform is typically the most defensible form of all — third parties build on it, customers build their own processes on it, and their data, workflows, and entire ecosystem get deposited onto you, so switching becomes nearly unthinkable. That’s why Salesforce and ServiceNow strain so hard to be seen as platforms, not products. But breadth is only a moat when the ecosystem and integrations create real switching cost — bolt together enough weak modules and you get complexity, not defensibility.

Hanging over the whole battlefield is the bundler. Microsoft posted ~$82.9B of revenue and ~$31.8B of net income in a single quarter — its three-month revenue is nearly twice Salesforce’s entire year (~$41.5B). That scale isn’t just a scoreboard; it’s ammunition. With hundreds of millions of Office and Windows seats, Microsoft can fold a new capability — Teams, Copilot, Dynamics — into an existing subscription for “free,” and push it to more customers overnight than any standalone rival can reach in years. That’s the distribution leverage that turned Teams into a noose around Slack.

The bundle also explains why so many “great products” in horizontal software make disappointing investments. A superior standalone tool can win every feature review and still lose the market, because the buyer already owns a “good enough” version inside a suite they won’t rip out. In horizontal software, the incumbent’s distribution is often a deeper moat than the challenger’s product is an advantage — which is why position, not the feature checklist, decides who compounds.

So the investment lens for horizontal software isn’t “which product is best?” — it’s positional. How high has this company climbed, and how deep is the switching cost it has actually earned? Is it riding distribution leverage, or exposed to someone else’s? The uncomfortable truth this chapter drives home: the standalone point tool with shallow switching cost is the most fragile animal on this field — great product, thin moat, one bundle away from irrelevance. Position beats features, every time.

This is Chapter 9 of “Compounding in the Cloud.”