acquisition-guides

One-Person SaaS Operational Handover: The Complete Acquisition Checklist for Solo Founder Exits

Exit Street

07 Mar 2026 — 4 min read

You've signed the purchase agreement. The wire's cleared. You now own a one-person SaaS business. Congratulations — and now the real work begins. The previous owner is walking away, and every piece of institutional knowledge lives in their head. If you don't extract it systematically during the handover period, you'll spend the next six months reverse-engineering a business you paid good money for.

This checklist covers everything you need to transfer during the operational handover of a solo-operated SaaS acquisition. Print it. Pin it to your wall. Work through it line by line.

Why Handover Is the Most Critical Phase

The handover period — typically 30-90 days post-close — determines whether your acquisition succeeds or becomes an expensive lesson. Studies from MicroAcquire (now Acquire.com) show that 34% of micro-SaaS acquisitions that fail cite inadequate knowledge transfer as a primary factor.

For one-person SaaS businesses, the risk is amplified because:

There's no team to retain institutional knowledge
Documentation is often minimal or outdated
Custom scripts, integrations, and workarounds exist only in the founder's memory
Customer relationships are personal and need deliberate transition

The Complete Handover Checklist

1. Infrastructure and Hosting

☐ Complete list of all servers, services, and hosting providers
☐ Login credentials for every hosting account (AWS, Vercel, DigitalOcean, Heroku, etc.)
☐ Domain registrar access and transfer of all domains
☐ DNS configuration documentation (especially custom records)
☐ SSL certificate management (who issues them, when they expire)
☐ CDN configuration (Cloudflare, CloudFront, etc.)
☐ Email service provider access (SendGrid, Mailgun, Postmark)
☐ Monitoring and alerting setup (Uptime Robot, PagerDuty, etc.)
☐ Backup systems and procedures — verify a backup works by restoring it
☐ Monthly hosting cost breakdown by service

2. Codebase and Development

☐ Source code repository access (transfer ownership, not just collaborator access)
☐ All branches and their purposes documented
☐ Local development setup guide — can you run the app from scratch?
☐ CI/CD pipeline documentation and access
☐ Environment variables list with descriptions (not just names)
☐ Third-party API keys and their purposes
☐ Package registry access (npm, PyPI, etc.) if applicable
☐ Known technical debt and planned improvements
☐ Architecture diagram (even a rough sketch helps)
☐ Database schema documentation and migration history

3. Financial and Billing

☐ Payment processor access (Stripe, Paddle, PayPal)
☐ Transfer of Stripe account or creation of new one with customer migration plan
☐ Subscription billing system access and documentation
☐ Current pricing tiers and any grandfathered plans
☐ Tax setup (sales tax, VAT) — especially important for multi-jurisdiction SaaS
☐ Financial reporting tools and dashboards
☐ Outstanding invoices or payment disputes
☐ Refund policy documentation
☐ Revenue recognition methodology
☐ Affiliate/referral program details and outstanding commissions

4. Customer Management

☐ Customer list with plan types, MRR, and tenure
☐ CRM access or customer database export
☐ Customer communication history (especially VIP or enterprise accounts)
☐ Support ticket system access and history
☐ Common support issues and their resolutions (FAQ/playbook)
☐ Customer churn data — who left and why
☐ Contractual obligations (SLAs, custom agreements, data processing agreements)
☐ Key customer relationships that need personal introduction
☐ Customer communication plan for ownership transition
☐ Feature requests and product roadmap promises

5. Marketing and Growth

☐ Google Analytics / Search Console access
☐ Social media account credentials (Twitter, LinkedIn, etc.)
☐ Content marketing assets (blog posts, lead magnets, templates)
☐ SEO analysis — top keywords, backlink profile, ranking pages
☐ Ad accounts (Google Ads, Facebook Ads) and historical performance
☐ Email list and automation sequences
☐ Landing pages and conversion funnels
☐ Partnership or integration listing agreements
☐ Product Hunt, G2, Capterra listings and login credentials
☐ Content calendar and publication schedule

6. Legal and Compliance

☐ Terms of service and privacy policy — who drafted them? When were they last updated?
☐ GDPR/CCPA compliance documentation
☐ Data processing agreements with customers
☐ Subprocessor list (every third party that touches customer data)
☐ Insurance policies (cyber liability, E&O)
☐ Open source license compliance
☐ Trademark registrations
☐ Any pending or threatened legal issues

7. Operations and Maintenance

☐ Daily/weekly/monthly operational tasks documented
☐ Scheduled maintenance windows and procedures
☐ Incident response playbook
☐ Vendor relationships and contract terms
☐ Seasonal patterns (usage spikes, renewal cycles)
☐ Known bugs and workarounds
☐ Automated jobs and cron tasks — what they do and when they run
☐ Manual processes that should be automated

The Handover Timeline

Week 1: Access Transfer

Focus entirely on getting access to everything. Don't try to understand it all yet — just ensure you can log into every system and the previous owner hasn't missed anything.

Week 2: Shadowing

Watch the previous owner work for a full week. What do they check first thing in the morning? What manual tasks do they perform? Where do they go when something breaks? This is where you learn the undocumented workflows.

Week 3-4: Supervised Solo

You run the business. The previous owner is available for questions but doesn't touch anything unless you ask. This is where gaps in documentation surface.

Week 5-8: Independent with Support

You're fully operational. The previous owner is available via email/chat for questions, typically with a response time of 24-48 hours.

Week 9-12: Wind Down

Final questions, edge cases, and formal end of support period. After this, you're on your own.

Red Flags During Handover

Watch for these warning signs that the handover isn't going well:

"I'll just do it for you": The seller keeps handling things instead of teaching you. Insist on learning.
"That never happens": Dismissing edge cases you're asking about. It will happen. To you. At 2am.
Missing credentials: If the seller can't find login details for services, those services might have deeper problems.
"It's all in the code": Code is not documentation. If they can't explain the system verbally, the code won't save you.
Customer complaints spiking: If customers start having issues during handover, the transition isn't being managed well.

Tools for Managing Handover

Set up these tools to track the handover process:

Password manager: 1Password or Bitwarden — transfer all credentials here, not via email or Slack
Documentation wiki: Notion, Confluence, or even a simple Git repo with markdown files
Loom: Have the seller record video walkthroughs of every major system and process
Checklist tracker: Use this article's checklist in a spreadsheet with completion dates and notes

The golden rule of SaaS handover: If the seller gets hit by a bus after week 4, could you run the business? If the answer is no, the handover isn't done yet.

A thorough handover takes effort, but it's the difference between a smooth acquisition and a costly scramble. Invest the time upfront — your future self will thank you.