Operator-minded founders who would rather buy cash flow than bootstrap from zero. Works for those with $50K-$500K in capital (self-funded or SBA-backed), strong operational chops, and patience for longer diligence cycles than greenfield building.
Month 1-2: deal sourcing and first LOIs. Month 3-4: diligence and close. Month 5-6: transition complete, operations running solo with AI team. Month 7-12: growth plan executes, first post-acquisition revenue milestone hit.
The playbook
- 1
Define your acquisition box
Most solo operators fail at acquisitions because they buy anything that looks cheap. Define a narrow box upfront: revenue range ($5K-$30K MRR), category (SaaS with clean recurring revenue, not services or usage-heavy commerce), tech stack you can run (avoid products built on deprecated frameworks), customer profile (ideally B2B with low churn). Write this as a one-page thesis and filter every opportunity against it. Discipline here saves you from buying the wrong business.
Notion for the acquisition thesisSpreadsheet for opportunity pipeline - 2
Source deals across multiple marketplaces
The visible inventory lives on Acquire.com (formerly MicroAcquire), TrustMRR (Marc Lou's marketplace, with a strong solo-founder pipeline), Flippa (noisy but occasionally great), and Indie Hackers' 'for sale' threads. Off-market deals — founder-to-founder — are often better priced but harder to find; build relationships via X and Indie Hackers. Your AI research analyst can monitor multiple marketplaces daily and flag matches against your thesis.
Acquire.comTrustMRRFlippaIndie HackersEmpire Flippers - 3
Run diligence with the rigor of a small PE shop
For every serious opportunity, pull: Stripe revenue data (6+ months), customer churn cohorts, support ticket volume, code health (audit with your AI CTO — is this 5 years of tech debt?), contract risk (any enterprise customers with exit clauses?), domain and trademark ownership. Your AI CFO models the unit economics; your AI CTO stress-tests the codebase. Walk away if the data doesn't match the seller's story — the solo-founder acquisition graveyard is full of 'trust me, revenue is great' stories.
Stripe Atlas data exportAI CTO role for codebase auditAI CFO role for unit economicsBrightIP for trademark / IP checks - 4
Structure the deal to protect downside
Pure cash deals are rare for profitable solo SaaS. Typical structure: 50-70% cash at close, 30-50% seller note over 12-24 months tied to revenue retention. If revenue falls below threshold, your payments adjust. For acquisitions above $250K, consider an SBA 7(a) loan (up to $5M, 10-year term) which lets you acquire with ~10% equity down. Your AI CFO models the financing scenarios; a human M&A lawyer handles the paperwork (this is not the place to skimp on legal).
SBA lender (Live Oak, Celtic Bank)M&A attorney (specialized in small SaaS)Escrow.com for payment milestones - 5
Execute a disciplined transition
The first 30 days post-close decide whether you retain revenue. Get seller support documented via a transition services agreement (4-8 weeks of availability). Move domain, Stripe, and critical accounts to your control with care — one DNS mistake can knock revenue offline for days. Brief every customer on the ownership change within the first week; most acquired SaaS that fail do so because customers found out from an outage, not an announcement. Your Manager runs the transition checklist, your AI customer support rep absorbs the tier-1 load immediately.
Notion for transition runbookStripe account transferDomain transfer (registrar to registrar)AI Customer Support role - 6
Extract human skills into AI roles
The prior team — even if small — embodied skills. Document them before they leave. What did the founder do on Mondays? Who answered support? Who managed content? For each recurring task, either (a) install a matching skill in your AI team from the Tycoon marketplace, (b) train a bespoke skill from the transition docs, or (c) retain a contractor for edge cases. By end of month 6, your AI team should be running 80%+ of the operational load.
Tycoon skills marketplaceLoom recordings from sellerNotion runbook - 7
Ship one growth experiment per month
Acquired SaaS often has years of stagnant growth because the prior founder was exhausted. Your advantage is fresh eyes plus AI team bandwidth. Your AI growth engineer ships one experiment per month: new pricing tier, new landing page variant, new paid channel, new integration. The compounding effect on a stable revenue base is where acquisition beats greenfield building — you're not fighting for survival, you're optimizing a working business.
AI Growth Engineer rolePostHogStripe event wiringLinear for experiment backlog
Pitfalls to avoid
- Buying a business you don't understand — if the tech or category is foreign, you can't detect diligence red flags.
- Overpaying because the 3x ARR multiple 'feels standard' — small SaaS varies widely; 1.5x-2.5x is often more defensible.
- Rushing the transition to save on seller support — the first 60 days break many acquisitions.
- Firing the prior support staff day one — you need them during transition even if the long-term plan is AI.
- Ignoring customer communication — your first email to the customer base is a make-or-break moment for retention.