Digital Businesses

Acquire.com transaction diligence

Published · Reviewed by The Diligence Standard Team · Updated

Package retention, cohorts, product metrics, clean financials, technical documentation and code/IP ownership so the buyer can distinguish durable recurring revenue from founder-led momentum.

Diligence focus

  • MRR/ARR quality
  • Churn and cohorts
  • Customer concentration
  • CAC and growth efficiency
  • Code/IP ownership
  • Technical debt
  • Cloud/infra cost
  • Founder/product dependence

First evidence requests

  • MRR/ARR customer export
  • Churn/cohort analysis
  • Processor/bank reconciliation
  • Customer concentration
  • Source repository and IP assignments
  • Architecture/infra costs
  • Product roadmap and incident history
  • Founder/team responsibility map

Warning signals

  • ARR includes non-recurring setup/services
  • Low churn claim lacks cohorts
  • Founder is sole developer/product manager
  • Code contributors lack assignments
  • Cloud/API costs are not normalized
  • Top customers can cancel easily