How to sell a SaaS company, and what to do with the records beyond ARR

How to sell a SaaS company: the short answer

Selling a SaaS company comes down to three proofs: recurring revenue that holds up under scrutiny, clear ownership of the code and product, and a diligence file with no surprises. Build those before contacting a single acquirer, then run a managed process from teaser through letter of intent to closing.

A second decision sits alongside the sale. The records the business created while building and supporting its product, such as pull requests, engineering tickets, support threads and product decision documents, can be licensed to AI developers as training and evaluation data. For a company with 50+ full-time employees at peak (contractors excluded), SourceX can run that license before the sale or apart from it, as one-time cash that never touches ARR.

What should be ready before a SaaS company goes to market?

Acquirers price a SaaS business on the quality of its recurring revenue and diligence it on ownership and risk. Put these items together first.

• Monthly recurring revenue by customer for several years, reconciled to the general ledger and billing exports
• Gross and net revenue retention by cohort, logo churn and the recorded reasons customers left
• A sell-side quality of earnings review, or at minimum clean monthly closes with deferred revenue tied out
• Signed IP assignment or invention agreements from every employee and contractor who wrote code or product content
• An open-source license scan of the codebase, with any copyleft components explained
• Customer MSAs and DPAs indexed by assignment, change-of-control and data-use clauses
• A security file: SOC 2 report if one exists, the latest penetration test and an incident log
• A systems inventory showing where engineering, support and product history lives and how far back it goes

Start the IP item early. The Copyright Office's circular on works made for hire explains that work an employee prepares within the scope of employment belongs to the employer, while commissioned work from outside contributors qualifies only in listed categories and with a signed written agreement. Contractor code without a written assignment is a familiar diligence finding, and it would also cloud any records license. This is general information, not legal, tax or financial advice. Confirm with your own counsel, tax adviser or professional body before acting.

How to sell a SaaS company in eight steps

1. Set the objective. Decide between a full exit, a majority recapitalization or a minority growth round, how long the founder stays, and whether an earnout is acceptable. The answer shapes the buyer list.
2. Engage a software M&A advisor. Look for closed deals at your ARR range and with your likely buyer types. Read how the engagement letter defines a transaction, so everyone knows whether a separate records license falls inside or outside it.
3. Build the metrics pack. Prepare an ARR bridge (new, expansion, contraction, churn), cohort retention, gross margin with hosting costs broken out, CAC payback and the rule of 40 if you track it.
4. Map the buyer universe. Strategic software acquirers, PE platforms and add-on buyers, growth equity funds, and search funds or independent sponsors for smaller profitable products.
5. Prepare the teaser, CIM and data room. Add a technical overview: architecture, hosting, release cadence, test coverage and the systems inventory from the checklist above.
6. Run outreach through to an LOI. Collect indications of interest, hold management presentations and code walkthroughs, then negotiate a letter of intent. Exclusivity normally begins when the LOI is signed.
7. Get through confirmatory diligence. Expect a financial QoE, a third-party code scan, a security review and a legal review of IP, contracts and privacy commitments.
8. Sign and close. Negotiate the purchase agreement and disclosure schedules, agree any transition services, and settle escrow or holdback terms.

Where does a records license fit in a SaaS sale?

The cleanest window is steps 1 to 3, before the CIM goes out. At that point the license is the owner's call, the proceeds arrive as one-time cash, and the data inventory SourceX asks for doubles as diligence preparation. Once an LOI with exclusivity is signed, a license generally needs the acquirer's written consent, and after closing the acquirer makes the decision. The page on whether a company should license its data before selling walks through each stage.

Demand for these records comes from a shift in what AI developers build. Agents that carry out multi-step work need examples of real work, with decisions and outcomes, and that material rarely appears on the public web. The Copyright Office's report on generative AI training (Part 3, released as a pre-publication version in May 2025) discusses licensing approaches for training data and notes that model performance depends heavily on data quality.

What different SaaS acquirers look for

Which SaaS records can be licensed, and which stay out?

The company's own operating records can be in scope. Data that customers store inside the product usually cannot, because MSAs commonly limit hosted data to providing the service.

Related sell-side guides cover selling an MSP business and selling an IT consulting or systems integration firm, where ticket and project histories play a similar role.

Common mistakes when selling a SaaS company

Illustrative example: a vertical SaaS seller

Illustrative: Kestrelpoint Scheduling (fictional) sells practice software to veterinary clinics. It peaked at 140 full-time employees and holds nine years of Git history, Jira tickets since its second year and every support ticket since launch. The founder wants to exit in about 18 months.

During preparation, the advisor runs the company through a fit screen and, with the founder's permission, sends a referral link. The company inventories its systems and history, SourceX agrees one all-in price and terms with the founder, AI data buyers review the opportunity, and the license is signed before the teaser goes out. The CIM then tells a clean ARR story, adds a short note that engineering and support records are licensed exclusively for AI training for an agreed term, and the agreement sits in the data room for acquirers to read.

How a software M&A advisor makes the introduction

You make the introduction; the company does the work with SourceX. Get the owner's permission, note the basic fit facts in a company introduction record, then share your referral link or submit the referral form. SourceX qualifies the company, the company completes its inventory, price and terms are agreed, data buyers review, and the deal closes with delivery under the agreed redaction rules. You never handle code, tickets or customer files.

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company, and payment comes only after the data buyer pays and SourceX receives its fee. No reward is guaranteed, and the reward is never deducted from what the company receives. Check your engagement letter and any professional rules that apply to you before accepting a referral reward; referral opportunities for M&A advisors sets out how the program works for deal teams.

Next step

Before acquirer outreach starts, run the company through the company fit checker and compare it with the who qualifies baseline. If it fits, register as a partner and send the owner your referral link, or have the owner apply directly at sourcex.si/apply.