9 minute guide · Updated 2026-10-19

How to Sell a SaaS Business: A Step-by-Step Guide

Plan a SaaS sale from valuation and buyer materials to diligence, closing, and transition without losing momentum.

How to sell a SaaS business, from decision to handover

Learning how to sell a SaaS business is mostly learning how to run a sequence well: decide what you are selling and why, set a defensible price range, reach the right buyers, negotiate a letter of intent, survive diligence, close, and hand over without the product stalling. Each stage has its own failure modes. Most failed small software sales do not collapse because the price was wrong on day one; they collapse because the revenue story could not be reproduced, an asset could not transfer, or the founder ran out of energy halfway through diligence.

This guide covers the end-to-end process. For the detailed evidence-gathering work that should happen before you talk to anyone, read how to prepare a startup for sale, which includes a 90/60/30-day plan and a data-room checklist. This page is general information, not legal, tax, or investment advice. A sale is a contract with lasting consequences, and the U.S. Small Business Administration recommends having an attorney review the sales agreement and seeking advice from a lawyer and a business valuation expert (SBA, “Close or sell your business”).

Step 1: Decide what kind of sale you want

Before valuation, answer four questions in writing.

Why are you selling? Buyers will ask, and “burnout” or “I want to build something else” is acceptable if the business itself is healthy. A vague or shifting answer makes buyers look for hidden decline.

What exactly is for sale? A whole company (shares or membership interests), or a set of assets such as the code, domain, customer list, and brand? The answer changes taxes, liabilities, and the transfer checklist. See asset purchase vs stock purchase for the trade-offs.

What do you need at closing? Some sellers need maximum cash at close; others will accept seller financing or an earnout for a higher headline price. Decide your floor before a buyer anchors you.

How long will you stay? Most buyers of owner-operated software want a transition period. Know how many weeks of handover you can genuinely commit to, and whether you would accept a consulting arrangement afterwards.

The SBA describes three broad ways to transfer a business: an outright sale with immediate transfer and payment, a gradual sale, or a lease arrangement (SBA). For small SaaS products, outright sales are most common, but partial or staged deals exist when buyer and seller disagree on risk.

Step 2: Build numbers a buyer can reproduce

Your price range is only as credible as the numbers beneath it. Prepare at least these, each with a written definition:

  • MRR and ARR, normalized so annual prepayments are spread across their term and one-time charges are excluded. The MRR vs ARR guide and MRR and ARR calculator help standardize the math.
  • Trailing-twelve-month revenue and profit, reconciled to payouts and bank deposits. See TTM revenue.
  • Seller's discretionary earnings (SDE) with every add-back documented. See SDE vs EBITDA.
  • Churn and retention by month and cohort. The churn rate guide covers definitions.
  • Concentration: the share of revenue from your largest customers, channels, and platforms.

A common mistake is presenting a payment-processor total as MRR. A processor's trailing 30 days can include annual plans, one-time purchases, and refunds. On RevenueBug, the headline figure is trailing 30-day revenue calculated from a connected payment provider, not subscription MRR, and it is not an audit of profit or ownership (methodology). It can reduce early skepticism, but buyers will still want the underlying exports.

Step 3: Set a price range, not a single number

Value the business from at least two angles, usually an ARR-based view and an SDE-based view, then explain the gap. The SBA lists income, market, and asset approaches as distinct valuation methods (SBA). The micro-SaaS valuation guide walks through a full worked example, and the SaaS valuation calculator makes your assumptions explicit.

Write down a low, base, and high case with the specific assumptions behind each. When a buyer pushes on price, you can then point to which assumption they disagree with, instead of arguing about a multiple in the abstract.

Remember that headline price and cash at closing differ. Escrows, holdbacks, seller notes, earnouts, working-capital adjustments, and taxes all reduce or delay what you receive. Private-target M&A data from SRS Acquiom, which covers deals much larger than most micro-SaaS sales, reported that 88% of 2025 deals with private targets involved some form of escrow or holdback (DealLawyers summary of the SRS Acquiom 2026 study). Expect some portion of your price to be conditional.

Step 4: Choose how to reach buyers

There are three common routes for small SaaS sales.

Marketplaces. Listing platforms give you reach and standard workflows but may charge listing or success fees and will shape how you present the business. Compare options on fees, buyer verification, and what happens to your confidential information. RevenueBug's comparisons with Acquire, Flippa, and Empire Flippers lay out the differences.

Brokers and advisers. A broker can run a structured process, screen buyers, and push for competitive tension, usually for a success fee. This tends to be worth more as deal size and complexity grow.

Direct outreach. Competitors, adjacent tools, agencies, and existing customers are often the most motivated buyers because they can capture synergies. A direct sale needs a clear teaser, an NDA, and discipline about what you disclose and when.

You can combine routes. On RevenueBug, a founder can mark a verified profile “For sale” and receive private buyer inquiries through startups for sale. RevenueBug relays inquiries only; it does not broker, escrow, provide legal help, or transfer businesses, and for-sale listings must reveal the product's identity. If you have not yet created a profile, start at add your startup.

Step 5: Run a controlled disclosure process

Disclose in stages:

  1. Teaser: category, business model, headline metrics, and asking range, without customer names or credentials.
  2. After NDA: product demo, financial summaries, cohort data, and the operating brief.
  3. After a signed LOI: detailed financials, code access in a controlled environment, contracts, and vendor accounts.
  4. Before closing: customer-level data and credentials, ideally only as part of the closing mechanics.

Keep a log of what each buyer received. Answer questions in writing where possible so your answers stay consistent across buyers. Do not hand over API keys, admin passwords, or full customer lists to anyone who has not signed definitive agreements.

Keep running the business. Revenue that dips during a sale process gives buyers a reason to retrade.

Step 6: Negotiate the letter of intent

The LOI sets the price, structure, payment terms, diligence period, exclusivity, and transition expectations. Most LOIs are non-binding except for specific provisions such as confidentiality and exclusivity, but sloppy drafting can create obligations you did not intend (Harris Sliwoski, “Letters of Intent”).

For a seller, the most important LOI terms are usually:

  • the length of exclusivity and whether it ends automatically;
  • how much is paid at closing versus deferred or contingent;
  • deal structure (asset or stock) and who bears pre-closing liabilities;
  • the scope and length of your post-sale transition and any non-compete.

Our guide to the letter of intent for a startup acquisition covers each term in detail.

Step 7: Support diligence without losing momentum

Once exclusive, the buyer will test everything you have claimed. Buyers typically follow a process like the one in our buyer due diligence guide: revenue from customer to cash, cohorts, code, security, legal ownership, and operations. Reading it from the buyer's side is one of the best ways to prepare.

Practical rules for sellers:

  • Assign a response target (for example, within one business day) and keep a shared question tracker.
  • Disclose problems early. A known issue becomes a negotiable item; a discovered issue becomes a trust problem.
  • Set a diligence deadline in the LOI and track progress weekly.
  • Expect a retrade if diligence uncovers something material, and decide in advance which concessions you would accept.

Step 8: Close and transfer

The purchase agreement replaces the LOI. It contains representations and warranties, indemnification, escrow or holdback terms, the asset or share schedule, and closing deliverables. Have a lawyer draft or review it.

For SaaS businesses, closing is mostly an account-migration exercise. Build a transfer checklist covering domains, DNS, code repositories, cloud accounts, email, analytics, app-store accounts, social accounts, and payment processors. Payment accounts need special care: Stripe, for example, asks the existing owner to contact Stripe Support before transferring an account after a sale, and the process differs when the acquiring entity is in a different country (Stripe Support). Mobile apps move through Apple's app transfer process, which has its own criteria and side effects (Apple Developer).

In an asset sale, the buyer and seller generally each file IRS Form 8594 to report how the price was allocated across asset classes (IRS, About Form 8594). Agree the allocation with your tax adviser before signing, not after.

Step 9: Hand over properly

A good transition protects any deferred payment you are owed and your reputation. Write runbooks, record walkthroughs of deployments and support workflows, introduce the buyer to key customers and vendors, and agree how support tickets and incidents will be handled during the transition. Put the transition scope (hours, duration, response times) in the purchase agreement so neither side is surprised.

Common mistakes when selling a SaaS business

  • Quoting a single valuation multiple without explaining the denominator.
  • Treating trailing processor revenue as recurring revenue.
  • Granting open-ended exclusivity in the LOI.
  • Letting the business slide during the sale process.
  • Discovering missing contractor IP assignments during diligence.
  • Comparing offers on headline price instead of cash at close, timing, and risk.

Frequently asked questions

How long does it take to sell a SaaS business?

It varies with preparation, deal size, buyer type, and financing. A well-prepared seller with clean records moves faster because diligence has fewer surprises. Build the preparation time into your plan rather than starting the clock when you list.

Do I need a broker to sell a small SaaS?

No. Many small sales happen through marketplaces or direct outreach. A broker can add value through buyer screening and competitive tension, especially for larger or more complex businesses. Compare the fee to the time and negotiating leverage you would gain.

Should I sell assets or shares?

It depends on your entity, tax position, contracts, and what the buyer will accept. Buyers often prefer asset deals for small businesses, while sellers often prefer stock deals. Read asset purchase vs stock purchase and get tax advice before agreeing structure in the LOI.

Is verified revenue enough to sell my startup?

No. Provider-verified revenue reduces doubt about the revenue figure, but buyers still examine profit, churn, code, contracts, and ownership. On RevenueBug, verification means revenue was calculated from connected payment-provider data, not that the business was audited.

What happens to my customers' data in a sale?

Customer data usually transfers with the business, but your privacy policy, data-processing agreements, and applicable law may limit how. Review them with a lawyer before closing and tell customers what they need to know.

Can RevenueBug handle the transaction for me?

No. RevenueBug lets founders mark profiles for sale and relays private buyer inquiries. Negotiation, escrow, legal documentation, and transfer happen between the buyer and seller and their advisers.

Sources