<!-- Platform map · from Chapter 14 of The Product 360 Handbook -->

# Platform map · [Product] · v[n] · [Date]

**Owner:** [PM]   **Reviewed with:** [partnerships lead, architect]   **Next review:** [Date]

## Ecosystem roles
| Role | Who (named parties or segments) | What they create or do | What they get today | Evidence |
|---|---|---|---|---|
| Owner | [us] | Architecture, access, rules | | |
| Providers | [resellers, MSPs, marketplaces] | Deliver access to customers | | |
| Producers | [partners, connector authors, customers who share content] | Create value units | | |
| Consumers | [users and teams] | Act on value units | | |

## Core interaction
On our platform, [producer] creates [value unit]; [filter] matches it to [consumer], who [acts on it].

- Value unit:
- Filter (how the right value unit reaches the right consumer):
- What a failed interaction looks like:

## Adjacent interactions (later)
1.
2.

## The four platform decisions, as they stand
| Decision | Today (deliberate or accidental?) | Proposed |
|---|---|---|
| Number of sides | | |
| Design (what we provide vs what participants provide) | | |
| Pricing structure (who pays, who is subsidized) | | |
| Governance rules | | |

## Platforms we depend on (we are a complement)
| Host platform | What it gives us | What it takes | What can change without our consent | Exit or multi-homing plan |
|---|---|---|---|---|
| | | | | |

## Platforms that could envelop us
| Platform | Shared customer relationship | Bundle they could offer | Early warning signal | Our defense (see moats, Chapter 16) |
|---|---|---|---|---|
| | | | | |