Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Product Strategies, Buy vs Build vs Acquire vs Partner

112 views

Published on

In this talk we give an overview of 4 product strategies our clients use on their software product development journeys, the skills required for each, what the tradeoffs are, and how to make sure you're using the right one

Published in: Business
  • Be the first to comment

  • Be the first to like this

Product Strategies, Buy vs Build vs Acquire vs Partner

  1. 1. Product Strategies Buy, Acquire, Build, or Partner?
  2. 2. We partner with innovative business leaders to discover, deliver, and adopt the right custom software to overcome their biggest challenges. → vaporware.net
  3. 3. Why listen to Dan? I specialize in product-market fit. Through these organizations I’ve: ✓ Bought 100s of products ✓ Built more than 55 products ✓ Partnered with 40 org for products ✓ Been a part of 6 acquisitions
  4. 4. Factors For success
  5. 5. Expense
  6. 6. Time
  7. 7. Control
  8. 8. Scale
  9. 9. Maturity
  10. 10. Examples For success
  11. 11. expense = product now - control Desktop Online BUY
  12. 12. permanent expense = product now + control ACQUIRE
  13. 13. team + time = product soon + control BUILD
  14. 14. relationship = product + alignment PARTNER
  15. 15. Skills For success
  16. 16. Consider For success
  17. 17. low reward high risk low risk high reward
  18. 18. low reward high risk low risk high reward ACQUIRE PARTNE R BUILD BUY
  19. 19. Partnership Assessment → Minimize opportunity cost → Project-size skills and goals → Increase control → Decrease risks dan@vaporware.net

×