Micro SaaS Due Diligence Checklist for Buyers

Formal due diligence for a large SaaS acquisition takes weeks and involves lawyers and accountants. For a micro SaaS deal, you don't need that — but you do need a short, deliberate checklist, since there's no one else doing this work for you.

Revenue and metrics

• Ask for a screenshot of the actual payment processor dashboard (Stripe, Razorpay, etc.), not just a number in the listing
• Ask what percentage of revenue comes from the top 1-2 customers
• Ask about churn over the last 3-6 months, not just the current MRR snapshot
• If analytics or traffic numbers are cited, ask for a dashboard screenshot too

Technical review

• Request repository access (or at least a walkthrough) before paying, if the seller is willing
• Check the tech stack is one you can maintain, or budget for someone who can
• Ask about any known bugs, technical debt, or deprecated dependencies
• Confirm hosting, domain, and any paid tools are transferable — and who pays for them during transition

Legal and ownership basics

• Confirm the seller actually owns the code, domain, and any trademarks — ask directly if there are co-founders or contractors with a claim
• Get a simple written agreement covering what's included, the price, and the handoff timeline, even for a small deal
• Check what data privacy obligations come with any existing customer list before you contact them

The handoff itself

Agree on a specific handoff process before paying: what gets transferred, in what order, and what a 30-minute call with the seller will cover. A seller who's unwilling to do a short handoff call is a signal worth taking seriously.

None of this needs to take more than an hour or two of focused questions. The goal isn't to turn a micro SaaS purchase into a legal ordeal — it's to make sure the basics are covered before money changes hands.