ACQUISITION VS BUILD DECISION - MENTAL MODELS ANALYSIS

DECISION FRAMING:
Competitor has 5K paying customers, 2-year-old SaaS product. Build time: 12 months in-house. Acquisition price: 2.8M (estimated ARR multiple 5x at 560K ARR).

MENTAL MODEL 1: INVERSION
• If this decision destroys value, what went wrong?
  - Acquisition: Overestimated synergies, customers churned post-acquisition, integration cost 3x.
  - Build: Market moved faster, launched a better product, this feature became table-stakes.
• Reverse: Protect against customer churn post-acquisition with escrow-backed integration success criteria.

MENTAL MODEL 2: SECOND-ORDER THINKING
• First order: Acquire → get customers + feature
• Second order: Get customers → must integrate → team distracted → core product neglected → new players eat market share
• Alternative second order: Build → 12 months delay → but team velocity never drops → ship 4 other features while building this → market position strengthens

MENTAL MODEL 3: OPPORTUNITY COST
• Acquire: 2.8M cash + 4 engineers for 6 months (integration)
• Build: 0 cash + 6 engineers for 12 months
• The 2.8M could fund: A competitive marketing campaign (1.2M) + top-tier engineering hire (300K/year, 2-3 years) + product experimentation budget (1.5M)
• The 6-month gap gives competitors time to launch similar features

MENTAL MODEL 4: OPTIONALITY
• Acquire now (1 year): Lock in customer base, close off competitor, move fast
• Build and wait (1 year): Keep cash, test market demand for the feature, can still acquire later
• Acquiring later is only possible if the competitor doesn't get acquired first

FINAL RECOMMENDATION: BUILD
• Opportunity cost (2.8M in growth investments) beats acquisition cost
• Market risk of waiting 12 months is lower than integration risk of acquisition
• If this feature becomes clear winner in 6 months, revisit acquisition then

KEY ASSUMPTION TO MONITOR: Is the competitor's customer retention rate above 90% annually?