<!-- Developer platform brief · from Chapter 14 of The Product 360 Handbook -->

# Developer platform brief · [Product] · v[n] · [Date]

**Owner:** [PM]   **Engineering lead:** [Name]   **Developer relations:** [Name]

## Target builder (the hard side)
- Who they are (partner type, role, skill level):
- The hard problem we solve for them:
- What they use today instead:

## Job story
When [situation], I want to [motivation], so I can [expected outcome].

## Surfaces
| Surface | Purpose | Status | Audience |
|---|---|---|---|
| Public API | | | |
| SDKs | | | |
| MCP server (agent to tool) | | | |
| A2A agent and Agent Card (agent to agent) | | | |
| Sandbox and test data | | | |

## Access tiers
| Tier | Who qualifies | What they can do | Review required? |
|---|---|---|---|
| Open | | | |
| Certified partner | | | |
| Strategic | | | |

## Reward model
How builders share in the value they create: [listing, revenue share, co-sell, lead sharing, certification badge, marketplace placement].

## Versioning and deprecation
- Versioning scheme:
- Minimum deprecation notice: [period]
- How breaking changes are announced:
- Support window for old versions:

## Registry and marketplace listings
Where builders' work, and our own servers and agents, will be discoverable: [public registries, private enterprise registries, marketplaces].

## Success metrics
| Metric | Definition | Target |
|---|---|---|
| Time to first working integration | | |
| Active builders (shipped in last 90 days) | | |
| Third-party integrations used weekly | | |
| Share of customer value from third-party integrations | | |

## Risks and open questions
-