Framing the Platform Strategy Model

Strategic intent: Synthesize the platform strategy into its essential triplet (product / marketplace / extension platform) and characterize the underlying network through the seven key properties — because the type drives every subsequent go-to-market decision.

#Overview

The Boundaryless framework introduces the Platform Strategy Model (PSM) — a synthetic abstraction of how a platform strategy is expressed in terms of three value-proposition elements:

1. A product/service bundle targeted to a core customer
2. One or more marketplace interfaces connecting that customer with other stakeholders
3. An extension platform element, attracting third parties that extend the bundle with apps, plugins, or user-generated content

Not all three are always present. Substack is a SaaS without a marketplace. Many strategies have no extension platform. The most advanced — Shopify is the textbook example — feature all three: product (SaaS e-commerce), marketplace (Shopify experts), extensions (templates and apps).

This technique frames the PSM and then characterizes the network through the seven key properties of the underlying relationship, which determine which tactics will work for liquidity and growth.

#When to use it

• After Designing Platform Experience — or as a shortcut directly from ecosystem exploration
• Before deciding go-to-market tactics or liquidity strategy
• When borrowing tactics from a "comparable" platform — verify first that the platforms are actually comparable along these dimensions
• When the team is using marketplace metaphors loosely

#Composition

1. #1. Frame the Platform Strategy Model

   Use the Platform Strategy Model Canvas to capture the synthetic abstraction of your strategy. For each of the three value-proposition elements, articulate:

   • Product/service bundle — who is the core customer? What is the bundle?
   • Marketplace(s) — who connects to whom? What's exchanged?
   • Extension platform — are third parties extending the bundle? Through what mechanism?

   Note that not every strategy needs all three. The PSM should reflect the actual strategy, not an aspirational one.

   Canvas: Platform Strategy Model Canvas (beta)

2. #2. Characterize the network — the 7 key properties

   Once the PSM is clear, characterize the underlying relationship in the marketplace. The PDT Growth Guide identifies seven properties:

   1. Level of supply commoditization vs differentiation

      • Commodity (e.g., kWh of electricity) — price/availability competition
      • Differentiated (e.g., Airbnb listings) — quality/match competition
      • Highly bespoke (e.g., M&A advisory) — unique matches

   2. Symmetry vs asymmetry of the core relationship

      • Are the two sides equally needed and similarly motivated, or asymmetric?

   3. Geographic flexibility — local vs global

      • Hyper-local (food delivery), regional, global (with language/payment/regulation per region)

   4. Single-tenancy vs multi-tenancy

      • Do producers serve one platform or many simultaneously? Multi-homing is a known liquidity threat.

   5. Transaction frequency and lifetime

      • High-frequency (rides, food) → habit-forming tactics
      • Low-frequency (real estate) → SEO, paid acquisition, trust-building

   6. Transaction value (AOV)

      • Low-value/high-frequency vs high-value/low-frequency change everything about tactics

   7. Monogamous vs polygamous behavior

      • Do users use one platform exclusively, or multiple in parallel?

3. #3. Map the property combination to behavior

   Network-effect behavior changes dramatically based on the property combination. For example:

   • Commodity supply + multi-tenant + high frequency → race to liquidity, churn risk, multi-homing pressure (e.g., ride-hailing)
   • Differentiated supply + monogamous + medium frequency → strong defensibility, high LTV (e.g., Airbnb)
   • Bespoke supply + low frequency + high value → trust-driven, slow growth, sales-loop dominant (e.g., M&A advisory)

   The team's job is to identify which combination applies and what it implies for tactics.

4. #4. Identify analogues and disanalogues

   Find platforms that share the property profile (these are valid comparables for tactic borrowing).

   More importantly, identify disanalogues — platforms that look similar superficially but differ on one or more properties. Borrowing tactics from disanalogues is a common failure mode.

   "We're like Airbnb" — rarely true. Airbnb is two-sided, medium-frequency, highly differentiated, fragmented on both sides, and global. If your platform differs on any of these, your tactics will need to differ too.

#Inputs

• Required: outputs of Designing Platform Experience — or alternative shortcut: outputs of Understanding Ecosystems directly
• Recommended: Wardley Map and platform plays (from the exploration phase)
• Recommended: quantitative analogues from comparable platforms

#Outputs

• Platform Strategy Model captured on the PSM Canvas — synthetic view of the three value-proposition elements
• Seven-property characterization of the underlying network
• Behavior implications — what the property combination implies for liquidity and growth tactics
• Analogue / disanalogue map — comparable platforms with matched properties, plus warnings about superficially-similar disanalogues
• Direction-setting input for the next techniques: liquidity strategy and growth tactics

#Process heuristics

• Start from the relationship, not the product — the seven properties characterize the relationship between sides; the product accommodates the relationship
• Property combinations matter, not properties in isolation — high-frequency + low-AOV is very different from high-frequency + high-AOV
• Beware false analogues — superficially similar platforms can differ on one critical property and require completely different tactics
• The PSM is also a communication tool — useful to align stakeholders on a strategic abstraction before diving into details

#Validation criteria

• PSM Canvas filled with the three value-proposition elements (or explicit "not present" for missing ones)
• All seven network properties characterized with evidence/hypothesis
• Behavior implications articulated per property combination
• At least 2 truly comparable platforms identified
• At least 1 disanalogue identified with reasoning

#Common mistakes

• Forcing all three PSM elements — not every strategy has an extension platform; making one up dilutes focus
• Property-by-property thinking without combination analysis — the combinations are what matters
• Borrowing tactics from disanalogues — Uber's tactics don't transfer to a yearly-frequency marketplace
• Treating PSM as a final design — it's a synthetic abstraction; deeper design (motivations, transactions, experience) should follow

#Used in pipelines

• Go-to-market & Liquidity — as Phase 1

#Connections

• Inputs from: Understanding Ecosystems and/or Designing Platform Experience
• Feeds: Building Liquidity — type drives liquidity tactics
• Feeds: Choosing Growth Tactics — properties match tactics
• Connects to: Network Effects & Defensibility — flywheels build on the PSM and properties

#Related reading

• Identifying a Platform Strategy Model and its potential go-to-market strategy — the canonical Boundaryless essay
• Apply Value Chain Analysis with Wardley Maps to identify a Platform Opportunity
• The PDT Growth & Product Guide — chapter "Not all networks are equal: the seven key properties" in Legacy PDT Growth