The Six Archetypes of the Platform PM
Part 1 of the Strategic Platform Product Manager series
Our 🔒 Strategic Platform PM series helps platform product leaders level up their craft, moving away from shipping solely internal focussed product outputs, towards deliverables that drive sustainable product outcomes.
This is Part 1: The Six Archetypes of the Platform PM. Over the coming weeks, we’ll dive deeper into how to navigate each archetype’s challenges and how to blend them into a complete platform PM skill set.
If you want to follow along with this series and receive future deep dives, consider pledging your support as a paid subscriber by clicking the link below, or find out more about paid access here!
Platform Product Management is one of the hardest product job most people have never done, but if you’re reading this, there’s a good chance you have been.
You don’t own the user-facing experience directly. Your “customers” are other engineers, internal teams, third-party developers, and — increasingly — machines running AI agents that call your APIs autonomously. You sell capability or enabling infrastructure, not features. Success for you means someone else’s product works better, faster, or cheaper.
And the way you approach that job depends entirely on which version of a platform PM you are.
First: what do Platform Product Managers do?
Platform PMs juggle four distinct focus areas, and the best ones know the difference.
User Discovery — Interview the teams who depend on you and end user/customers to share discovery and ideation. Gather feedback. Define golden paths. Build what people and customers need, not what you think they need
Product Strategy — Define the vision and roadmap. Balance technical debt against new capabilities. Make the hard calls about what your internal customers actually need
Thinnest Viable Platform (TVP) — Work with architects to scope the smallest set of tools and services that let stream-aligned teams focus on their domains, not infrastructure
Developer Experience — Measure usability and adoption of internal tooling like it’s a metric that matters, because it is. Your engineering workflow is a core metric for success
You aren’t running a support function, you’re running a product with an initial internal customer base that will eventually drive value another end-user or customer. That mindset shift—treating infrastructure as a structured product, not ad-hoc tasks—separates the organisations that scale from the ones that plateau.
Having spent the last decade inside platform products — such as payments and high transaction capability across PayPal, Littlepay, Masabi and Tier, and fintech infrastructure at Moonfare — and I’ve watched the same six archetypes emerge again and again.
Each one brings a superpower and a blind spot. And in 2026, as AI agents become first-class consumers of platform capabilities, some of those blind spots are turning into existential risks.
Here’s how to spot yourself — and which shape you need to grow into.
