How would you evaluate whether to build, buy, or partner for a new capability?
Model answer
Model answerThis decision comes down to three variables: strategic differentiation, time to market, and total cost of ownership. If the capability is core to our differentiation, we build — even if it's slower. If it's commodity infrastructure, we buy. If we need speed but the capability has strategic value, we partner with the option to acquire. The mistake most teams make is defaulting to build because it feels more controlled.
Framework · Build / Buy / Partner
- DDifferentiation test
Is this capability core to why customers choose us? If yes, build - TTime to market
How urgent is this? Buying or partnering compresses timeline significantly - CCost of ownership
Build has hidden costs: maintenance, talent, technical debt — model honestly - AAcquisition option
Partner now, acquire later — if strategic, keep that door open
Related questions
- How would you define the product vision for an AI assistant in a consumer app?
- How would you manage building a platform product that serves both internal teams and external customers?
- How do you build a product roadmap when company strategy shifts mid-year?
- How do you align multiple product teams around a single company strategy?
- How do you decide when a product is ready to scale?