How would you evaluate a potential acquisition target from a product perspective?
Model answer
Model answerProduct evaluation of an acquisition comes down to three questions: does their user base complement or overlap ours, does their technology accelerate something we'd otherwise spend years building, and is there a culture of product thinking we'd want to absorb — or a culture clash we'd spend years fixing? I'd spend as much time on the team and culture as on the product itself. Great products with bad team dynamics are hard integration targets.
Framework · Build / Buy / Partner
- DDifferentiation test
Do they solve something we can't, or something we just haven't gotten to yet? - UUser base compatibility
Complement or cannibalize? Overlap analysis is non-negotiable - TTeam and culture
Acquisition is a people decision. Bad culture fit kills integration. - IIntegration cost
How long to full integration? Every month of limbo is a productivity tax
Related questions
- How would you prioritize building for power users vs. new users?
- A major competitor just launched a feature you were building. What do you do?
- How do you align stakeholders when they disagree on the roadmap?
- How would you evaluate the ROI of a product investment before building it?
- How do you decide when to kill a feature?