Industry Guides 4 min read ·

Tech Platform and Ecosystem Strategy Cases for Consulting Interviews

Master platform business model cases in consulting interviews with frameworks for network effects, two-sided markets, and ecosystem strategy.

Confused? That's okay.
Practice with AI until you master it.
Start Practice → Upgrade to Pro →

Platform business models account for seven of the world’s ten most valuable companies, and consulting firms test platform strategy in roughly 15–20% of technology sector cases. Understanding network effects, multi-sided market dynamics, and ecosystem governance separates strong candidates from average ones.

Why Platform Cases Appear So Frequently

Top firms serve clients navigating platform economics daily — marketplace launches, API monetization decisions, ecosystem defense against aggregators. Based on our analysis of 800+ case prompts, platform-adjacent questions appear in three distinct patterns:

PatternTypical PromptCore Challenge
Marketplace launch“Should our client build a two-sided marketplace?”Chicken-and-egg, subsidization strategy
Platform defense“A competitor is platformizing — how should our client respond?”Moat analysis, switching costs
Ecosystem monetization“How should our client monetize its developer ecosystem?”Value capture without killing growth

In our experience working with candidates preparing for McKinsey and BCG technology practice interviews, the biggest mistake is applying standard growth frameworks without accounting for the non-linear dynamics of network effects.

The Platform Economics Framework

Every platform case can be decomposed through this lens:

mindmap
  root((Platform Strategy))
    Network Effects
      Direct effects
        Same-side usage value
      Indirect effects
        Cross-side attraction
      Data effects
        ML improvement loops
    Market Structure
      Multi-homing costs
      Winner-takes-most vs fragmented
      Regulation risk
    Monetization
      Transaction fees
      Subscription tiers
      Advertising
      Data licensing
    Governance
      Quality control
      Disintermediation risk
      Platform rules

Key Concepts You Must Know

Network Effects: Direct vs. Indirect

Direct network effects mean each additional user makes the platform more valuable to other users on the same side (e.g., social networks — more friends, more value). Indirect network effects mean more users on one side attract more users on the other side (e.g., more buyers attract more sellers on a marketplace).

In case interviews, you need to identify which type applies and quantify the strength. A common interviewer follow-up: “At what point do network effects plateau?”

Multi-Homing and Switching Costs

Multi-homing refers to users participating on multiple competing platforms simultaneously. When multi-homing costs are low (riders using both Uber and Lyft), winner-takes-most dynamics weaken. When switching costs are high (enterprise SaaS with deep integrations), incumbents hold defensible positions.

FactorLow Multi-Homing CostHigh Multi-Homing Cost
User behaviorSplit across platformsConsolidate on one
Competitive dynamicsFragmented marketWinner-takes-most
Pricing powerLimitedStrong after lock-in
Strategic implicationCompete on experienceCompete on ecosystem breadth

The Chicken-and-Egg Problem

Every marketplace faces a cold-start problem: no supply without demand, no demand without supply. In interviews, you should propose specific sequencing strategies:

  1. Single-player mode — provide standalone value before the network exists (e.g., OpenTable’s restaurant booking software)
  2. Subsidize one side — attract the harder-to-get side with economics (e.g., Uber paying early drivers hourly guarantees)
  3. Constrain geography — concentrate both sides in one market first (e.g., launching city-by-city)
  4. Piggyback — import existing supply from another platform (e.g., Airbnb pulling Craigslist listings)

Structuring a Platform Case: Step-by-Step

flowchart TD
    A[Identify Platform Type] --> B{Who are the sides?}
    B --> C[Map network effects]
    C --> D[Assess competitive dynamics]
    D --> E{Winner-takes-most?}
    E -->|Yes| F[Speed and scale strategy]
    E -->|No| G[Differentiation strategy]
    F --> H[Monetization timing]
    G --> H
    H --> I[Governance and trust]
    I --> J[Final recommendation]

For a broader view of technology industry case patterns, see our technology industry deep dive.

Step 1: Identify the platform type. Is this a marketplace (Airbnb), a platform-as-infrastructure (AWS), or an ecosystem play (Apple App Store)?

Step 2: Map the sides and their incentives. What does each side want? What is their willingness to pay? Which side is harder to attract?

Step 3: Assess network effect strength. Are effects local or global? Do they plateau? Can they turn negative (congestion, spam)?

Step 4: Determine competitive equilibrium. Based on multi-homing costs and network effect type, will this market consolidate or fragment?

Step 5: Recommend monetization approach. When should the platform start capturing value, and from which side?

Common Mistakes in Platform Cases

Based on our work with 200+ candidates, these are the patterns that cost points:

  1. Applying linear growth models — platforms grow non-linearly; doubling spend does not double users
  2. Ignoring the supply side — candidates focus on consumer acquisition and forget unit economics for suppliers
  3. Premature monetization — recommending aggressive take rates before critical mass is established
  4. Missing regulatory risk — platform dominance increasingly triggers antitrust scrutiny (EU DMA, US antitrust cases)
  5. Confusing platform with product — not every digital product is a platform; a platform must facilitate exchange between distinct user groups

Practice Prompt: Marketplace Expansion

Your client is a successful B2B procurement marketplace connecting manufacturers with raw material suppliers in North America. They generate $2B in GMV with a 3% take rate. The CEO wants to expand into Southeast Asia. How would you evaluate this opportunity?

Strong answer structure:

  • Assess whether network effects are local or global (procurement relationships tend to be regional)
  • Evaluate supply-side willingness to join a new geography (is there a chicken-and-egg problem?)
  • Analyze competitive landscape in SE Asia (existing platforms, government procurement rules)
  • Model unit economics differences (lower ASP, different margin structure)
  • Recommend a sequencing strategy (one country first, which vertical to lead with)

Key Takeaways

  • Platform cases require fundamentally different frameworks than traditional industry cases — network effects create non-linear dynamics that standard growth models miss
  • Always identify the platform type (marketplace, infrastructure, ecosystem) and map both sides before diving into analysis
  • The chicken-and-egg problem is the most-tested sub-topic; have 3–4 sequencing strategies ready with examples
  • Multi-homing costs determine whether the market will consolidate or fragment — this drives your entire strategic recommendation
  • Never recommend aggressive monetization before establishing critical mass on both sides
  • Regulatory risk (antitrust, data privacy) is increasingly relevant and shows commercial awareness in interviews

Ready to practice platform strategy cases? Explore technology industry cases in our case library for real prompts, or sharpen your structuring with AI Mock Interview sessions that provide real-time feedback on your framework quality.