Platform Strategy

Platform Strategy

Help the user design and execute platform business strategies using frameworks from 24 product leaders who have built and scaled platforms.

How to Help

When the user asks for help with platform strategy:

1. Understand the platform type - Clarify whether they're building a marketplace, API platform, ecosystem, or developer platform 2. Identify the network effects - Help them understand which sides of the platform create value for each other 3. Assess the lifecycle stage - Determine if they're in the moat-building, opening, or closing phase 4. Design for trust and governance - Help them think through the rules that will govern platform participants

Core Principles

Treat internal platforms as products

Camille Fournier: "Platform engineering is not just maintaining cloud infrastructure... platforms are products, ultimately. You should be thinking about how do I create coherent offerings that make this company more productive?" Internal platforms need dedicated product management and focus on user (developer) productivity, not just technical elegance.

Understand the four-stage platform lifecycle

Brian Balfour: "The four steps are essentially, one is I call a Step Zero. It's the conditions of the market have been met. Step One is about a moat, Step Two is about a platform opening, and Step Three is about the platform closing for control and monetization." Platforms follow a predictable lifecycle from market consensus to closing for monetization.

Reduce cognitive load through clear interfaces

Jeremy Henrickson: "The more you can bake into a clear platform, it reduces the decision-making complexity for everyone who's working on the domain part of the problem." A well-defined platform with clear interfaces simplifies product development by reducing the cognitive load on individual teams.

Find compounding dynamics

Alex Komoroske: "Anything that is shaped like an ecosystem that has some kind of network effect... you have to know what you're looking for and find the dynamics of a thing that if it worked would work at an accelerating rate." Platform success comes from identifying "gardening" opportunities - projects with inherent compounding loops that grow on their own.

Build systems, not features

Aparna Chennapragada: "The way I think about how we are positioned and what we do with GitHub is... So it's a system, not just a product or a set of features." Long-term platform defensibility comes from building a comprehensive system and repository of context rather than just a single feature or tool.

Invest incrementally based on signals

Alex Komoroske: "Invest incrementally in ecosystem projects only as you receive signals of utility and adoption." Don't bet big on platform initiatives until you have evidence of demand and usage patterns.

Questions to Help Users

• "Which side of your platform is harder to acquire? That's probably where you should focus first."
• "What value does your platform provide to a user with zero other participants?"
• "What stage of the platform lifecycle are you in - building the moat, opening, or closing?"
• "How will you prevent the supply side from being commoditized or going around you?"
• "What compounding dynamics exist in your platform that accelerate as it grows?"
• "What governance rules will you enforce, and how will you handle disputes?"

Common Mistakes to Flag

• Building platforms in a vacuum - Not iterating based on actual product and developer needs
• Treating all participants equally - Not recognizing that power users and high-quality suppliers deserve different treatment
• Skipping the moat phase - Opening a platform before establishing defensibility
• Feature thinking over systems thinking - Building point solutions instead of comprehensive systems with context
• Over-investing before signals - Betting big on platform initiatives without evidence of utility and adoption

Deep Dive

For all 28 insights from 24 guests, see references/guest-insights.md

Related Skills

• platform-infrastructure
• retention-engagement
• pricing-strategy

Platform Strategy - All Guest Insights

24 guests, 28 mentions

---

Alex Komoroske

Alex Komoroske

"Anything that is shaped like an ecosystem that has some kind of network effect... you have to know what you're looking for and find the dynamics of a thing that if it worked would work at an accelerating rate. Lots and lots and lots of things intrinsically have this shape."

Insight: Platform and ecosystem success comes from identifying 'gardening' opportunities—projects with inherent compounding loops that grow on their own.

Tactical advice:

• Look for 'truffles'—dynamics where the value increases with the number of participants.
• Invest incrementally in ecosystem projects only as you receive signals of utility and adoption.

Timestamp: 00:34:16

Aparna Chennapragada

Aparna Chennapragada

"The way I think about how we are positioned and what we do with GitHub is... So it's a system, not just a product or a set of features... you need to have a system. You need to have kind of the ability, an entire Swiss Army toolkit, not just the autocomplete, not just a chat, not just like a software agent that runs and you kind of hand hold. You need all of this to work together."

Insight: Long-term platform defensibility comes from building a comprehensive system and repository of context rather than just a single feature or tool.

Tactical advice:

• Build systems that capture user context and repositories to create defensibility
• Focus on the 'Swiss Army toolkit' approach for complex professional workflows
• Integrate multiple AI capabilities (autocomplete, chat, agents) into a unified system

Timestamp: 00:46:01

Benjamin Lauzier

Benjamin Lauzier

"Provide guardrails for what a good experience is in your marketplace, set a clear bar for quality, and provide the right coaching and tools for supply to be successful, and then take a step back and see where the gaps are and invest more in hands-on tactics just to close those gaps more specifically."

Insight: Effective platform management relies on setting quality guardrails and empowering supply rather than attempting total deterministic control.

Tactical advice:

• Set a clear quality bar and provide coaching tools for those who fall below it.
• Use 'hands-on' tactics (like managed services) only to close specific gaps that market forces can't solve.

Timestamp: 00:00:00

Bill Carr

Bill Carr

"Once we moved to a service-based architecture, and then teams could own their code with defined endpoints, APIs that other teams could understand that are well-documented, then we could move in that direction."

Insight: A service-based architecture with well-documented APIs is a prerequisite for team autonomy and scaling.

Tactical advice:

• Move from monolithic codebases to service-based architectures
• Ensure all internal services have defined, documented endpoints/APIs

Timestamp: 00:16:56

Brandon Chu

Brandon Chu

"The cycles for platform work are five to 10 odd times longer. You're maybe changing something on the infrastructure level, then opening up an API and then doing an alpha period for the API where developers now build on that and test things. And then you move into a beta. And then finally, two years later, some end customer actually uses that app"

Insight: Platform PMing requires a shift in psychology to manage much longer feedback loops and indirect user impact.

Tactical advice:

• Define clear principles and a 'stack rank' of constituents (e.g., merchant vs. developer) to guide policy decisions
• Design a 'canvas' for others to build on rather than a specific end-user experience
• Celebrate intermediate milestones like API alphas to maintain team motivation during long cycles

Timestamp: 41:39

Brian Balfour

Brian Balfour

"The four steps are essentially, one is I call a Step Zero. It's the conditions of the market have been met. Step One is about a moat, Step Two is about a platform opening, and Step Three is about the platform closing for control and monetization."

Insight: Platforms follow a predictable four-stage lifecycle from market consensus to closing for monetization.

Tactical advice:

• Identify the moat that creates defensibility for the platform owner.
• Establish a third-party platform with clear incentives for developers.
• Anticipate the closing stage where the platform prioritizes its own monetization and first-party applications.

Timestamp: 00:12:49

---

"Step One is then these players, somebody essentially identifies whatever the moat is, the thing that is going to help build them defensibility and help them hit escape velocity... That typically comes down to third-party content creators or app developers and other businesses. So they all establish a third-party platform that has some incentives built in."

Insight: Platform owners use third-party ecosystems to accelerate the building of their own competitive moats.

Tactical advice:

• Look for the 'value exchange' where a platform offers distribution in return for your application's engagement and data.
• Be aware that platforms often absorb the highest-value use cases into first-party features once they reach scale.

Timestamp: 00:14:36

Camille Hearst

Camille Hearst

"I think it was probably predictable to some degree that platforms would win because just of the nature of aggregation. Once you have either all of the supply or you've aggregated the demand, it's really a strong network effect. Why investors love to invest in these types of businesses, it's hard to break out."

Insight: Platform dominance is driven by the power of aggregation and the resulting network effects that make it difficult for new entrants to compete.

Tactical advice:

• Focus on aggregating either the total supply or the total demand to build a defensible network effect

Timestamp: 00:15:14

Camille Fournier

Camille Fournier

"Platform engineering is not just maintaining cloud infrastructure... platforms are products, ultimately. You should be thinking about how do I create coherent offerings that make this company more productive?"

Insight: Internal platforms should be treated as products with dedicated product management and a focus on user (developer) productivity.

Tactical advice:

• Hire product managers for internal platform teams
• Focus on outcome-based metrics like reducing cycle time or solving scaling bottlenecks

Timestamp: 00:59:04

---

"I think it gets to be like, you have 50 plus engineers. I don't think this is the kind of thing that you start when you are 10 engineers... when you hit either a lot of inefficiency where you're seeing the same people across a bunch of different teams... dealing with this instead of centralizing it."

Insight: Platform teams should generally be established once an engineering org reaches ~50 people or when redundant efforts across teams become highly inefficient.

Tactical advice:

• Look for signs of redundant problem-solving across different product teams as a trigger for centralization
• Avoid building a platform team too early (e.g., at 10 engineers)

Timestamp: 01:05:00

---

"A lot of the best platform type offerings in companies start in individual application teams. An application team has a problem and they solve it for themselves and it turns out that that's actually a really good idea... So a good platform team is often looking around for those and then sort of taking them and then assimilating them."

Insight: Successful platforms often emerge from 'harvesting' solutions already built by application teams rather than building from scratch in isolation.

Tactical advice:

• Identify successful ad-hoc tools built by product teams and stabilize them for company-wide use
• Focus on 'stabilizing and scaling' existing solutions rather than just 'zero-to-one' building

Timestamp: 01:08:06

Casey Winters

Casey Winters

"What data network effects are, is leveraging product usage data to make the product value stronger and stronger over time... your product being able to generate its own data, versus just relying on the big platforms to do all the work for you. That's a real edge."

Insight: Data network effects create a competitive moat by using proprietary usage data to improve product value, reducing dependence on external platforms like Facebook or Apple.

Tactical advice:

• Leverage product usage data to create personalized results or better targeting for users
• Focus on generating internal data to mitigate the impact of external platform changes

Timestamp: 52:03

Dhanji R. Prasanna

Dhanji R. Prasanna

"We believe in the power of open source and one of our core missions is to increase openness, and that means contributing to open protocols and contributing to open source. ... We want to build things that not only are good for us and our customers, but that outlast Block and outgrow Block."

Insight: Contributing to open protocols (like MCP) and open-sourcing internal tools (like Goose) builds a more robust ecosystem and attracts partners.

Tactical advice:

• Default to open-sourcing internal tools that solve general-purpose problems
• Build on open protocols to ensure long-term extensibility and avoid vendor lock-in

Timestamp: 00:27:23

Dmitry Zlokazov

Dmitry Zlokazov

"Another thing here is what I mentioned previously is us investing heavily into platform so that every solution is scalable from the get go so that we don't have any custom solutions. For example, take our credit team, they ship new products like loans or credit cards in the country literally every month. And it is just maybe 300 people."

Insight: Invest in scalable platforms early to enable small teams to launch complex products across multiple jurisdictions rapidly.

Tactical advice:

• Avoid custom, one-off solutions in favor of scalable platform components
• Build platforms that allow lean teams to multiply their output across many markets

Timestamp: 00:39:35

Gustav Söderström

Gustav Söderström

"If you don't create hard APIs to your technology, you're out. And if you think about it, it has to be that way because otherwise no one would do it... because he forced it so hard, they were the ones who did Amazon Web Services because they had such hard defined APIs."

Insight: Forcing teams to build 'hard APIs' for internal use creates the necessary infrastructure for future platform leverage and externalization.

Tactical advice:

• Mandate that all internal technology be exposed via structured, maintainable APIs
• Use hard APIs to allow internal teams to compete or collaborate without needing deep code access

Timestamp: 00:37:32

Jeremy Henrickson

Jeremy Henrickson

"The more you can bake into a clear platform, it reduces the decision-making complexity for everyone who's working on the domain part of the problem."

Insight: A well-defined platform with clear interfaces simplifies product development by reducing the cognitive load on individual teams.

Tactical advice:

• Invest in systems thinking to create a platform that simplifies the space for domain-specific work
• Iterate on the platform based on product needs rather than building it in a vacuum

Timestamp: 00:10:09

---

"The idea of a compound startup for us is that we're basically a lot of businesses that all work together... all of these different businesses benefit from being built on top of one platform."

Insight: A 'compound startup' leverages a single system of record to allow multiple vertical products to share data and underlying capabilities seamlessly.

Tactical advice:

• Start with a single system of record to avoid data replication and sync issues
• Build shared horizontal capabilities like workflow, reporting, and permissioning that all products can use

Timestamp: 00:23:40

Julia Schottenstein

Julia Schottenstein

"We think about dbt open source. It's really the guts of the data transformation... on the cloud side we build proprietary software that supercharges the development life cycle and the productionization of dbt at scale. So what we think about as leaving for our cloud offering is we deal with state, so stateful interactions and also any cross team or structural collaboration."

Insight: A successful open-core strategy keeps the core standard open source to drive adoption while charging for state, collaboration, and enterprise-scale features.

Tactical advice:

• Keep the core 'guts' of the product open source to reduce friction and build an ecosystem.
• Reserve stateful interactions and cross-team collaboration features for the proprietary/paid offering.

Timestamp: 00:29:50

Keith Coleman & Jay Baxter

Keith Coleman & Jay Baxter

"The code that decides what notes share has to be out in the open. All of the data and ratings that make it happen have to be out in the open. People should be able to take the code and data and replicate the whole service..."

Insight: Radical transparency—making both code and data public—is a powerful strategy for building trust in algorithmic systems.

Tactical advice:

• Publish core algorithms and underlying data to GitHub/public repositories for external auditing
• Ensure public code is 'runnable' by external parties to allow for true replication

Timestamp: 01:13:49

Logan Kilpatrick

Logan Kilpatrick

"What's been most exciting to me, actually, is the non-developer persona is now empowered to go and solve these really, really, really more challenging problems by giving the model enough context on what that problem is to be able to solve it."

Insight: The GPT Store platform strategy is about democratizing the creation of complex AI tools for non-coders.

Tactical advice:

• Leverage built-in tools like Code Interpreter and Browsing to add functionality without writing code.
• Use third-party integrations (like Zapier) to connect GPTs to external APIs like Notion or Gmail.

Timestamp: 00:28:11

Marc Benioff

Marc Benioff

"You better go build an application economy... I think he wants me to build an app store. At that moment, I went to the domain registry, and I bought appstore.com. Then, I started working on it at Salesforce so that we would have the ability with our platform to build apps, and then sell them, and that you could do all these things."

Insight: A true platform strategy involves creating an 'application economy' where third parties can build and monetize on top of your core technology.

Tactical advice:

• Build capabilities for third-party developers to create and sell apps
• Secure relevant trademarks and domains (like App Store) early to define the category
• Focus on an 'exchange' model where users share capabilities

Timestamp: 09:55

Matt Mullenweg

Matt Mullenweg

"And a true platform, it's when your ecosystem makes more money than the core does. And so many times, whether it was the Facebook platform, I'm putting that in air quotes, or the Shopify platform, companies build on it and then they get the rug pulled out from under them because they're too successful."

Insight: A true platform is defined by the ecosystem's revenue exceeding the core's revenue and requires a commitment to not 'pull the rug' from successful third-party developers.

Tactical advice:

• Measure platform success by the revenue generated by the third-party ecosystem
• Ensure long-term API stability and fair terms to prevent ecosystem 'rug pulls'

Timestamp: 00:37:33

Mike Krieger

Mike Krieger

"MCP really tried to tackle that middle one [context and memory]... what if we made this a protocol and what if we made this something that was repeatable? ... I hope that's where we had, and I hope that's where more things had, which is to really have agency and have these agentic use cases."

Insight: Standardizing protocols (like MCP) for context and memory is more scalable than building individual, non-repeatable integrations.

Tactical advice:

• Expose internal product primitives as scriptable/composable elements via a standard protocol.
• Focus on 'commoditizing your complements' by making it easy for others to build integrations that work across multiple models.

Timestamp: 00:55:44

Nick Turley

Nick Turley

"I also would love it if you could start a business on ChatGPT. I think there really is a world where, as this thing hits a billion user scale, it can get you distribution, it can get you started on making something in the same way that people built on the internet"

Insight: The ultimate platform goal for AI is to enable users to build and monetize entirely new businesses within the ecosystem.

Tactical advice:

• Develop mechanisms (like GPTs) that allow users to package specialized AI capabilities
• Focus on providing distribution and tools that allow for differentiated 'app-like' experiences

Timestamp: 01:21:05

Nilan Peiris

Nilan Peiris

"we have a single global tech stack, and we have deep local infrastructure. ... you end up with a global product team that owns overall KPIs around conversion rate, et cetera. And you have local, regional teams that own the conversion rate, and the cost to do KYC for their market, and they contribute to the global product code base. So we have weak product ownership, where anyone can make code change, and pull requests, and these guys owning the vision in the center."

Insight: Scaling a global product requires a single tech stack where regional teams have 'weak ownership' to contribute local requirements directly to the core code.

Tactical advice:

• Maintain a single global tech stack to avoid fragmented regional versions of the product
• Implement a 'weak ownership' model where regional teams can submit pull requests to global product code
• Structure teams so global leads own the core vision while regional teams own local conversion and compliance KPIs

Timestamp: 00:57:45

Tanguy Crusson

Tanguy Crusson

"I would go, okay, we need to win the problem space first, and if the platform is there, let's use it. If it's not there, we'll hack it, test it, iterate on it with customers, and then whatever is good there, let's platformize it later. But that's where you see what makes us super powerful as a bigger company, can also slow us down and make us focus on the wrong assumptions."

Insight: Prioritize solving the customer problem over platform compliance in the early stages of a new product.

Tactical advice:

• Hack solutions initially to validate the concept before committing to long-term platform architecture
• Avoid simultaneous product-building and platform-building to reduce execution risk

Timestamp: 00:32:15

Farhan Thawar

Farhan Thawar

"How long would it take to build a platform layer, which exposes APIs so anyone could build NFT gating in one hour? ... If you put the gas in the tank, people could drive on that gas for a long time going forward."

Insight: Invest in infrastructure and APIs that enable others to build features rapidly rather than building point solutions yourself.

Tactical advice:

• Ask 'What has to be true so that you could write this in a day?' to identify missing infrastructure
• Prioritize building platform layers that support multiple future use cases over single-feature requests

Timestamp: 00:43:18

Josh Miller

Josh Miller

"on any new computer... the developer platform itself is much more interesting and lucrative and world changing than the first-party computer itself... Arc as a development platform is going to be much more central to what we're doing, building on top of these internet computers"

Insight: The long-term value of a new interface lies in providing the APIs and capabilities that allow other developers to build immersive experiences that were previously impossible.

Tactical advice:

• Focus on closing the 'experience gap' between web and native software
• Build the interface first to eventually own the developer platform

Timestamp: 01:19:44