Platform Upside Test
Find products that can compound through users, data, applications, and ecosystems
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 95%
The Platform Upside Test asks what a successful initial product could become after its first wedge gains traction. The analyst maps how users, usage data, complementary applications, partners, and developers might reinforce one another. A genuine platform becomes more useful or defensible as participation grows, allowing a small initial insight to expand into an ecosystem rather than remaining a feature. Timing matters because an early platform can begin accumulating users, data, and applications before rivals. The framework does not assume every product should become a platform; instead, it uses conditional reasoning: if the first milestones occur, is there a credible next chapter with compounding value? That potential can turn an ordinary successful investment into an exceptional return while also creating a stronger strategic position.
Origin
Extracted from Masters in Business, where Greg Sands explained that Fred Wilson taught him to seek platforms and ecosystems capable of multiplying an investment’s upside.
Core principles
- 01Look beyond the initial product
- 02Seek compounding advantages from participation
- 03Test whether third parties can build on the product
- 04Value ecosystems more highly than isolated features
- 05Require a credible path from product success to platform scale
How to run it
- 1
Define the wedge
State the narrow initial problem the product solves and why users will adopt it now. The wedge must create independent value before any ecosystem exists.
Pro tip Describe the first use case without using the word platform.
Watch out A platform pitch without a useful starting product is usually premature.
- 2
Map participant growth
Identify the users, businesses, developers, or partners that could join after the wedge succeeds. Specify what each participant contributes and receives.
Pro tip Draw exchanges of value between participant groups.
Watch out More users do not automatically create a network effect.
- 3
Find the data loop
Determine what proprietary or self-refreshing data usage produces and how that data improves the offering. Check whether the loop strengthens with scale.
Pro tip Ask whether the system becomes harder to reproduce after every customer deployment.
Watch out Data accumulation has little value unless it improves decisions, performance, or switching costs.
- 4
Test extensibility
Explore whether applications, integrations, services, or workflows can be built on top of the core product. Confirm that extensions increase utility without destabilizing the core.
Pro tip Interview likely partners or developers before assuming they will build.
Watch out An integration directory is not necessarily an ecosystem.
- 5
Evaluate first-mover compounding
Assess whether entering early allows the company to accumulate users, data, applications, or standards that later entrants cannot easily match. Distinguish durable compounding from temporary launch publicity.
Pro tip Name the specific asset that improves with time and participation.
Watch out First entry offers little protection when customers can switch cheaply and no asset compounds.
- 6
Write the conditional next chapter
State the milestones that must occur before the product can expand into a platform. Then describe the larger opportunity that becomes possible if those conditions hold.
Pro tip Use an explicit statement such as, “If A and B happen, then C becomes possible.”
Watch out Do not include distant platform revenue in the base case before the enabling milestones exist.
In the wild
Demandbase begins by matching company identities to digital advertising activity. As hundreds of business customers use the product, deployments refresh its data and strengthen the underlying advantage. The initial application therefore develops into infrastructure for a broader account-based marketing ecosystem.
→ A focused B2B application becomes a defensible platform through distributed usage and self-refreshing data.
A procurement startup first helps small companies approve purchases. If adoption creates reliable supplier-performance data and vendors add services through an API, the startup could support a two-sided ecosystem. Until those usage and partner milestones occur, the investor values it as a workflow product rather than a mature platform.
→ The conditional test preserves upside without confusing aspiration with current evidence.
Common mistakes
Calling every product a platform
A platform must enable compounding participation or complementary creation. A standalone application with integrations does not qualify automatically.
Skipping the initial wedge
An ecosystem cannot develop if the first product lacks immediate value. Platform potential should extend product-market fit, not substitute for it.
Assuming first means defensible
First-mover advantage matters only when early activity accumulates users, data, applications, standards, or another durable asset.
Is it for you?
Best for
It is best for founders and early-stage investors assessing software, infrastructure, data, and marketplace opportunities.
Not ideal for
It is not ideal for deliberately narrow products whose customers value simplicity more than extensibility or ecosystem growth.
From the transcript
“we are trying to focus on things that have platform capabilities that can build ecosystems.”
“the first mover to be in market and start attracting users and the data that comes with it and the applications that get built on…”
“if we're successful, if A and B happen, can the next chapter be this extraordinary platform opportunity?”
From the episode
Greg Sands Discusses Technology and Investment
Greg Sands