The App-and-Platform Model
A platform without a great first-party app can't get good -- and a company that only sees itself as a platform will lose the apps war.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- —
Ballmer's mechanism for why some tech platforms thrive while others stagnate: a platform is anything extensible enough for third parties to build value on top of, but a platform alone is not enough. The company must also build and own a leading first-party application on that platform (Office on Windows, Outlook on Exchange) because that's what forces the platform to keep improving and gives users a reason to show up. Companies that culturally define themselves as 'just a platform company' end up starving their own first-party products, telling themselves internally that certain product bets are 'not our job,' which cedes ground to competitors who build both layers.
Origin
Extracted from Acquired
Core principles
- 01Anything extensible counts as a platform -- Windows, Azure, Office, and even a single app can be a platform
- 02A platform needs a best-in-class first-party app to prove out and harden its value
- 03Culturally identifying only as 'a platform company' becomes a self-limiting belief
- 04You must genuinely court and communicate to external developers, not assume they'll show up
- 05Extensibility should be evaluated for both the platform layer and the app layer
How to run it
- 1
Define what you're extensible around
Identify the layer(s) in your product that third parties could realistically build on top of.
- 2
Build a flagship first-party app
Invest directly in owning at least one best-in-class application on your own platform to prove the platform's value and drive usage.
- 3
Court external developers explicitly
Directly and repeatedly communicate to third-party developers that you want their apps on your platform -- don't assume the pull is obvious.
- 4
Audit internal 'platform-only' thinking
Watch for internal teams refusing new product bets by saying 'we're just a platform company' -- challenge that framing explicitly.
- 5
Balance investment between platform and app teams
Ensure the org doesn't starve first-party app development in favor of pure infrastructure work, or vice versa.
In the wild
Microsoft built Office as the best first-party application running on Windows, which both proved out the platform's capabilities and gave enterprise buyers a reason to standardize on Windows.
→ Office became the anchor product that helped Windows dominate for two decades.
Similarly, Outlook was built as the flagship first-party client for the Exchange email platform, even though other email clients existed at the time.
→ The pairing helped Exchange become the enterprise email standard.
Common mistakes
Letting 'we're just a platform company' become an excuse
Ballmer says by the mid-to-late 2000s he was hearing teams internally refuse new bets with this exact phrase, and he struggled to break that mindset even as CEO.
Assuming platform strength alone attracts developers
Ballmer's 'Developers, Developers, Developers' speech existed precisely because Microsoft could not assume third parties would automatically build for Windows -- it had to actively ask.
Is it for you?
Best for
Platform companies deciding how much to invest in owned applications versus pure third-party extensibility.
Not ideal for
Pure infrastructure businesses with no realistic path to a first-party consumer or enterprise app.
From the transcript
“if you see yourself as just a platform company a platforms need apps. You want to have the top first party app that runs on…”
“Office was the best firstparty app on Windows and that's how things get good.”
“I certainly got caught in my inability to tell people what the company needed to do because people had such a culture then of saying…”
From the episode
The Steve Ballmer Interview