- What is the most important metric to verify when buying an online tool or app?
- Monthly churn rate is the most critical metric, and it is the one sellers most commonly misrepresent — intentionally or otherwise. Verify churn independently by exporting all active subscriptions from the billing platform and calculating the monthly cancellation rate yourself, not from a summary the seller provides. A product claiming 1% monthly churn but with flat MRR over 12 months is mathematically inconsistent unless growth is also zero — investigate the discrepancy. After churn, verify the composition of the active user base: a product with 500 subscribers where 200 are non-renewing lifetime deal users has an effective recurring MRR from only 300 customers and a true churn rate that is meaningfully higher than the headline figure.
- Do I need technical skills to buy a software tool or app?
- No, but you need access to someone technical before you close. The financial, customer, legal, and traffic due diligence areas can all be completed without coding knowledge. The technical review — codebase quality, dependency audit, API risk assessment, and infrastructure evaluation — requires a developer. Hiring an independent developer for a one-time technical review ($300–$1,000) is standard practice for any tool or app acquisition over $10,000. Frame it as a structural inspection before buying a house: even if you plan to hire a developer post-acquisition to maintain the product, the pre-acquisition technical review gives you leverage to negotiate price, reveals what you are actually inheriting, and protects you from discovering critical technical debt after closing.
- How long does tool and app due diligence take?
- For a small tool ($5,000–$50,000 acquisition price), plan for 1–2 weeks of active due diligence after the seller grants access. Financial and revenue verification (2–3 days), churn and cohort analysis (1–2 days), technical codebase review by a developer (3–7 days), customer base and concentration analysis (1 day), API dependency audit (1–2 days), and legal and IP review (1–3 days if you use a lawyer). For deals above $100,000, budget 3–5 weeks and consider a formal Quality of Earnings (QoE) report ($2,000–$8,000) from an independent accountant. Tools with complex infrastructure — multi-region deployments, significant mobile components, or third-party data licensing — take longer to review on the technical side.
- What due diligence red flags should cause me to walk away from a tool acquisition?
- Walk away or demand a significant price reduction if you find: (1) MRR that cannot be reconciled with bank statements by more than 10% — unexplained discrepancies indicate revenue fabrication or undisclosed costs; (2) Monthly churn above 8% — the product will shrink faster than you can replace customers regardless of your growth efforts; (3) No source code repository access before closing — the code is the core asset; a seller who refuses developer access during due diligence has something to hide; (4) AI API or third-party costs exceeding 40% of revenue — a single pricing change by the provider can make the product uneconomical; (5) Core infrastructure accounts (Apple App Store developer account, payment processor, hosting) that cannot be independently transferred to a new owner's accounts without the seller. Any single confirmed red flag is grounds to renegotiate; two or more is grounds to walk away.