To buy a SaaS company, define what you want to own, source deals across brokers, marketplaces and direct outreach to founders, then test three things before agreeing a price: the quality of the recurring revenue, the state of the code and who can maintain it, and how much of both depends on the founder. Price follows those answers.
That is the short version. The rest of this guide is the long one: where SaaS deals actually come from, what diligence has to prove, how the revenue gets priced, and where acquirers get caught after closing.
Why acquirers buy SaaS businesses
The appeal is structural. Revenue recurs, so the business starts each month with most of its income already committed. Delivery costs grow more slowly than revenue, so margin can expand as the customer base does. And a working product with paying customers is far easier to underwrite than a plan.
Those same features are what make SaaS easy to overpay for. Recurring revenue looks permanent on a summary page. Diligence is where you find out whether it is.
Acquirers in this market tend to fall into a few groups:
- Strategic buyers adding a product to an existing customer base, or buying a capability they would otherwise build.
- Private equity and holding companies assembling portfolios of software businesses and sharing operations across them.
- Individual acquirers and searchers buying a single profitable product to run themselves, a path covered in what entrepreneurship through acquisition involves.
Each group values the same business differently, which is part of why a defined mandate matters. If you cannot say what you are looking for, you will spend the search reading listings that were never going to fit.
Start with the mandate
Before looking at a single deal, write down what you will and will not buy:
- Revenue band and profitability. A product doing a few hundred thousand in annual recurring revenue and run by its founder is a different purchase from a business with a management team and a sales function.
- Customer type. Software sold to consumers, small businesses and enterprises behaves very differently on churn, contract length and sales cycle.
- Vertical or horizontal. Vertical software built for one industry tends to retain better and grow more slowly. Horizontal tools face more competition and can scale further.
- What you bring. Distribution, an existing customer base, engineering capacity, or operating time. The best acquisitions buy something that is missing what you already have.
- How you will pay. Your capital, debt and appetite for a seller note or earnout set the ceiling on deal size.
A mandate is also what lets brokers and founders take you seriously. A buyer who can describe the target in two sentences gets the follow-up call.
Where SaaS deals surface
SaaS deals come through three channels, and each shows you a different slice of the market.
Brokers and M&A advisors. Larger and more established SaaS businesses usually sell through an intermediary who runs a process. These deals come with prepared financials, a defined timeline and competition from other buyers. Getting on an advisor's call list early means being a credible, specific buyer before the deal is ready.
Open marketplaces. The smallest SaaS deals concentrate on listing sites. Volume is high, so is competition, and quality varies widely. Treat a listing's summary metrics as a claim to verify, not a fact.
Direct outreach to founders. Many software businesses are never listed. Founders often take a call from a buyer who already understands their product and market, especially when they have been thinking about an exit but have not engaged anyone. This channel is slow and needs persistence, but it is where competition is lowest. How deal origination works covers building that pipeline in more depth.
Buyers who close tend to work all three channels at once. The SaaS deals that fit a narrow mandate are rarely the ones being broadcast most widely.
Financial diligence: the quality of the revenue
The number on the teaser is annual recurring revenue. The work is finding out how much of it will still be there in two years.
Retention by cohort. Look at each year's group of customers separately and track what share of their revenue remains over time. Net revenue retention, which counts expansion from existing customers, tells you whether the base grows on its own. Gross revenue retention, which ignores expansion, tells you how much leaks out.
Churn trend, not just churn rate. A business whose churn improves as it grows is healthier than one whose newer cohorts churn faster, even if the blended figure looks the same.
Customer concentration. If a handful of accounts carry a large share of revenue, losing one after closing changes the business. Read those contracts closely, including renewal dates and termination rights.
Gross margin after delivery costs. Hosting, third-party services, payment processing and customer support are costs of delivering the product. Some sellers book them below the line. Put them back.
Growth source. Is new revenue coming from organic search, referrals and word of mouth, or from paid acquisition? Paid growth can be legitimate, but it stops when the spending does. Know what it costs to acquire a customer and how long that customer takes to pay it back.
Verify at the source. Screenshots and summary dashboards are not diligence. Request read access to the billing system, payment processor and analytics, and reconcile them against the bank statements and the P&L. Specialist diligence providers can run this work if you do not have it in-house.
Technical diligence: the code and who can run it
The product is the asset, and most of its value is in a codebase you did not write.
- Maintainability. Has anyone other than the founder shipped to production? Is there a test suite, version control history and a deployment process someone else can follow?
- Infrastructure cost and fragility. What does the stack cost to run each month, and does that cost scale sensibly with usage?
- Dependencies and licences. Third-party libraries, APIs and paid services must transfer on a change of control. Open-source licences need checking for terms that affect how the code can be used or sold.
- Security and data. How customer data is stored, who has access, what compliance obligations attach to it, and whether there has been any incident.
- Documentation. Its absence is not fatal, but it tells you how long the founder will need to stay involved.
A codebase only one person understands is a concentration risk in the same way a single large customer is. It is the diligence buyers most often skip and most often regret.
How the price gets set
SaaS businesses are usually priced as a multiple of recurring revenue, of profit, or of both, depending on their size and profitability. The multiple itself is set by the factors above: retention, growth, margin, concentration, founder dependence and the state of the code.
A few practical points:
- Two businesses with the same revenue can be worth very different amounts. Retention and growth source usually explain most of the gap.
- The pricing model shapes how revenue behaves. Per-seat pricing grows and shrinks with customers' headcount. Usage-based pricing tracks their activity. Flat-rate pricing is predictable but hard to grow without a price rise. Ask when pricing last changed and what churn did afterwards.
- Structure moves risk around. A seller note or an earnout can bridge a gap between what the seller wants and what the numbers support, and it keeps the founder invested in a smooth handover. Earnouts are also a frequent source of disputes, so define the targets precisely.
- Asset or share purchase. An asset deal lets you choose what to take on but means assigning every contract and licence. A share deal keeps contracts in place and brings the company's history with it. Take legal and tax advice on which fits.
Financing for smaller acquisitions often combines buyer equity, senior debt and a seller note. How to get a loan to buy a business covers the lending side, and acquisition financing covers the wider capital stack.
Where SaaS acquisitions go wrong
Buying the founder. If the founder is the lead engineer, the main salesperson and the support desk, the business you buy is smaller than the one you saw. Plan the transition before you sign: what the founder will hand over, for how long, and what happens to the work they did.
Underestimating churn after the sale. Customers who bought from a founder they knew may not renew with an owner they do not. Communicate the change deliberately and early.
Inheriting technical debt. Rebuilding or stabilising the product can consume the first year and much of the margin. Price it in during diligence, not after.
Paying for projected growth. A seller's forecast is not revenue. Price what the business has already produced.
Platform dependence. A product that lives inside another company's ecosystem, such as an app store or a single integration partner, carries a risk the seller does not control and neither will you.
Before you make an offer
- Can you state the mandate in two sentences?
- Have you verified revenue and retention at the source, not from summaries?
- Do you know what the product costs to run and who can maintain it after the founder steps back?
- Have customer contracts, licences and data obligations been checked for change-of-control terms?
- Is the financing sized so the business can carry its debt through a weak year?
If the answers hold, you are buying a working business rather than a story about one. For the wider process, how to buy a small business walks through each stage, and how long it takes to acquire a business covers what lengthens and shortens a deal.
Where to go from here
The hardest part of buying a SaaS company is seeing enough of the right deals. Deal flow for acquirers covers how BizNexus sources across off-market, pre-market and on-market channels and matches deals against a defined mandate.
