Salesforce generated roughly $34 billion in revenue in fiscal year 2024. By IDC's estimates, the Salesforce ecosystem — the partners, ISVs, consultancies, and developers building on the platform — generated more than four times that. Over $140 billion in new business value, flowing to companies that Salesforce didn't build and can't directly control.
That ratio is the most important number in platform strategy. It's not just a measure of size. It's a signal that Salesforce has built something that generates far more value than it captures — and that the businesses in that ecosystem have a strong financial reason to keep it healthy.
The ratio isn't magic — it's the output of deliberate decisions
The $1:$4 ratio didn't happen because Salesforce is large. Plenty of large software companies have produced no meaningful ecosystem at all. The ratio exists because Salesforce spent decades making decisions that made it attractive for other businesses to build on top of theirs.
Those decisions are measurable. The AppExchange launched in 2006 — eighteen years of consistent investment in distribution infrastructure. Salesforce invested heavily in developer tooling, documentation, and certification programs that turned Salesforce expertise into a career path. They kept APIs open and extensible rather than building every vertical themselves.
The ratio is the compound interest on those decisions. And like compound interest, the early years of the return look unremarkable. It's only after a decade or more that the gap between building a closed product and investing in an open platform becomes hard to explain away.
Atlassian is another example of the math working at scale. Its marketplace generated $1.8 billion in sales in 2024. That figure represents revenue that went entirely to the ecosystem — to the developers and companies who built apps, not to Atlassian's income statement. What it did produce for Atlassian was a set of products indispensable enough that enterprises pay for Jira not just for the core tool, but for the universe of integrations, automation layers, and workflow extensions that have grown around it.
The partner stories make the numbers concrete
Aggregate ratios can be abstracted away. The individual partner stories are harder to dismiss.
Veeva Systems is the most striking. A life sciences CRM built entirely on Salesforce's platform, Veeva grew to a $2.4 billion ARR business — now publicly traded — without building its own CRM infrastructure from scratch. Veeva leveraged Salesforce's extensibility to move faster into a specialist vertical than any general-purpose CRM could. That's the compounding benefit of open platforms going in both directions: Veeva got to market faster; Salesforce got a reference case for vertical extensibility that no internal product team could have built.
Bold Commerce tells the same story at the smaller end. Four people in a basement building Shopify apps. They identified that merchant checkout was underserved, built a focused product, and used Shopify's distribution infrastructure to reach customers they never could have found with a standalone product. They now have over 300 employees, more than 760,000 merchant installs, and have facilitated over $5 billion in GMV. The platform didn't just give them a market. It gave them a scalable distribution channel with zero sales team required.
Appfire is a different kind of partner story — an aggregator rather than a builder. They identified that the Atlassian marketplace was fragmented with hundreds of small, independently-owned apps, and began systematically acquiring and consolidating them. That strategy is only possible because the marketplace ecosystem is large enough and economically sound enough that individual apps have real enterprise value. Appfire's existence is a signal of ecosystem maturity: when people start building acquisition theses around your marketplace, you have built something permanent.
Revenue share as an investment signal
How a platform structures its revenue share tells you a great deal about whether it is treating its developer ecosystem as a customer acquisition channel or as a revenue extraction target.
Shopify charges 0% revenue share on a developer's first $1 million in lifetime earnings from the App Store. Atlassian made the same move for apps built on Forge, their hosted extension framework. HubSpot charges 0% revenue share entirely — no cut at all — and has built an $840 million per year partner economy as a result, with the average independently-built app earning $280,000 in annual revenue.
These decisions have an obvious short-term cost. They represent revenue the platform is choosing not to take. But the logic is clear: the goal is to attract the long tail of developers building niche, high-value tools. The developer who is building a specialist compliance integration for a small vertical doesn't have much margin to give up to the platform. A 30% cut would make the economics unworkable. A 0% threshold sends a different message: we want you here, and we're willing to subsidise your early growth to get you.
The platforms that have treated their app stores as profit centres — taking large revenue cuts from the start, applying inconsistent policies, or competing directly with developers who built successful apps — tend to produce thin, low-quality ecosystems. The developers who could build the most valuable extensions go elsewhere.
The compounding return
The $1:$4 ratio isn't static. For Salesforce, it has grown over time as the ecosystem has matured, as more enterprises have embedded Salesforce-dependent workflows, and as the switching cost for the ecosystem as a whole has become nearly prohibitive.
This is the point that doesn't show up in any single-year analysis: ecosystem returns compound. Every year that the marketplace grows, every new app that becomes indispensable to a segment of customers, every developer who builds their career around the platform adds another layer of structural lock-in that has nothing to do with the core product.
A competitor building a better CRM than Salesforce faces a product challenge they can solve in a few years. A competitor who wants to replicate the ecosystem faces a challenge that cannot be solved by any amount of engineering investment alone. You cannot fast-forward twenty years of developer trust.
That's what the $4 ratio actually represents. Not a revenue split. A structural competitive advantage that has been accumulating for two decades — and that will keep accumulating for every year the flywheel stays in motion.