Problem-by-Problem Platform Stair-Stepping
Solve one concrete problem, reuse the capability, then expand into a platform
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 96%
This framework builds large platforms through a sequence of validated customer problems. Begin with one narrow need, deliver a working solution, and use failures to distinguish technical shortcomings from weak demand. Retain the capabilities that create strategic differentiation, then look for adjacent customers whose problems can be solved with the same infrastructure. Each expansion should strengthen a reusable technical or commercial layer rather than merely add unrelated services. Only after the capability works across multiple contexts should the company treat it as a horizontal platform or enter ownership-heavy models such as licensing and rights acquisition. The output is a platform grounded in demonstrated demand, accumulated expertise, and recurring revenue rather than a speculative attempt to predict an entire industry's future.
Origin
Extracted from Acquired's account of how MLB Advanced Media progressed from team websites to audio, video, third-party streaming, and media rights.
Core principles
- 01Start with a real, narrow customer problem
- 02Treat early failures as evidence about unmet demand
- 03Build reusable capabilities while delivering the first solution
- 04Expand only when adjacent customers share the same underlying need
- 05Let the platform emerge from proven solutions rather than speculation
How to run it
- 1
Choose a concrete first problem
Start with a specific customer and observable need rather than a broad platform ambition. BAM began by creating websites for Major League Baseball's teams.
Pro tip Prefer a problem that can expose reusable operational or technical capabilities.
Watch out Do not describe a distant industry transformation as though it were a customer problem.
- 2
Run a bounded demand test
Deliver a limited version that reveals whether customers value the proposed outcome. Use actual behavior and payment as stronger signals than stated interest.
Pro tip Use a small package, event, or customer cohort to constrain the test.
Watch out A technically successful launch can still fail because the offering is insufficient.
- 3
Diagnose what failed
Separate failures of execution from failures of demand. BAM learned from weak audio subscriptions that fans wanted to see games, not merely hear them.
Pro tip Ask what stronger outcome customers were trying to obtain.
Watch out Do not discard the entire market thesis when one delivery format fails.
- 4
Own the differentiating capability
Bring strategically important work in-house when external providers cannot deliver the required quality. Compound expertise by repeatedly operating the capability in production.
Pro tip Hire around the bottleneck that most directly controls customer experience.
Watch out Avoid internalizing commodity work that contributes no durable advantage.
- 5
Expand through adjacent problems
Offer the proven capability to customers with similar requirements. BAM extended live-streaming expertise from baseball to ESPN, WWE, golf, HBO, and hockey.
Pro tip Choose adjacencies that increase utilization of the same core infrastructure.
Watch out Unrelated expansion produces complexity without strengthening the platform.
- 6
Upgrade the business model
Move from solving tasks to operating a reusable service, platform, or rights-based business once the capability is proven broadly. Align ownership and incentives with the larger opportunity.
Pro tip Change organizational structure when the platform needs independent talent, capital, or equity.
Watch out Premature platform positioning can distract from delivering customer outcomes.
In the wild
BAM's paid audio service attracted only about a thousand subscribers. The team inferred that fans abroad wanted to watch games, tested one live video stream, sold limited postseason packages, and then launched a full-season MLB.tv subscription in 2003.
→ The initial full-season product reportedly gained 100,000 subscribers and established BAM's live-video capability.
After proving large-scale live streaming for baseball, BAM supplied technology to ESPN, WWE, the PGA Tour, HBO, and the NHL. It eventually added media-rights economics and was spun out so it could pursue a market larger than baseball.
→ A league technology department became a multibillion-dollar independent media infrastructure company.
Common mistakes
Starting with the platform pitch
Declaring a platform before solving a narrow problem leaves the company without validated demand or differentiated capability.
Treating every failure as rejection
An unsuccessful format may reveal that customers want a stronger version of the outcome rather than no solution at all.
Expanding without a shared capability
Serving unrelated needs creates a collection of projects instead of a compounding platform.
Is it for you?
Best for
It is best for startups and internal ventures entering uncertain markets through a concrete initial use case.
Not ideal for
It is not ideal when the first use case requires infrastructure that cannot transfer to adjacent customers or markets.
From the transcript
“Bam started by solving a real problem. They didn't start out by trying to invent the future of television.”
“I think it's just a great example of stair stepping your way up into an enormous company by by solving real problems kind of one…”
“it's a really great way if you want to become a platform to solve one problem first and then figure out what under there you…”
From the episode
BAMTech, Disney and "the Biggest Media Company You've Never Heard Of”