Key takeaway
Buying a SaaS business means buying three things at once: a stream of subscriptions, a piece of software you will have to keep running, and a set of contracts. Each needs its own check. This guide covers the steps that are specific to SaaS. The general process for any online business is in how to buy an online business, and if you are still deciding whether to buy at all, see buy vs build a SaaS business.
Step 1: Decide your criteria
Write these down before you look at listings:
- Budget, with a reserve for hosting, contractors and the first few months of surprises.
- Technical capacity. Can you maintain the code yourself, or will you pay someone? If you'll pay, that cost comes out of the profit you are buying.
- Customer type. Selling to businesses usually means fewer, larger accounts and more support. Selling to consumers means many small accounts and higher churn.
- Tech stack. A product written in a language you or your developer don't know is a larger risk.
- Time. How many hours a week you can give it, and whether support has to be answered in a particular time zone.
Criteria make it easier to say no quickly, which is most of the work.
Step 2: Read the listing's numbers
Four figures tell you most of what a SaaS listing is worth.
MRR. Monthly recurring revenue should include only active subscriptions. Ask whether it includes one-off setup fees, services or annual plans counted in the month they were paid. Each of those overstates it. ARR is MRR × 12.
Churn. Churn is the share of customers who cancel each month. Ask whether the figure is customers or revenue, and over what period it was averaged. A product losing 6% of customers a month has to replace about half its customer base every year just to stand still.
Gross margin. Revenue minus hosting, third-party APIs and payment fees, divided by revenue. A low margin means growth costs more than it appears to.
Concentration. The largest customer's share of revenue. If one account pays a third of MRR, you are buying that relationship as much as the product.
Where each figure comes from. Do not accept a number you cannot trace to a system.
| Figure | Ask for | Where it comes from | What to check |
|---|---|---|---|
| MRR | Monthly recurring revenue by month | Payment processor or billing export | Only active subscriptions, no one-off fees |
| Churn | Cancellations by month, customers and revenue | Billing system subscription list | Same period, same definition as the listing |
| Gross margin | Hosting, API and payment fees by month | Cloud, API and processor invoices | Costs match the bank statements |
| Concentration | Revenue by customer | Billing export sorted by customer | Share held by the largest accounts |
| Support load | Tickets per week and common causes | Helpdesk or support inbox | Whether the load can be handled by you |
On VALUERAQ, each listing shows automatic checks calculated from the seller's own figures, and you can save listings and searches to compare them later. Those checks describe what the seller entered. They don't confirm it.
To see how these numbers affect price, enter them in the SaaS Valuation Tool. VALUERAQ's default assumption for SaaS is 2.0× to 5.0× ARR, adjusted for growth, churn, margin, concentration, age and owner hours, with combined adjustments capped at −50% and +40%. It's a published assumption, not market data; how to value a SaaS business explains it. For the method behind those numbers, read how to value a SaaS company.
Step 3: Ask the seller the right questions
Message the seller privately through the listing. Useful first questions:
- How is MRR calculated, and can I see it by month from the billing system?
- Why do customers cancel, and what did the last ten who left say?
- Where do new customers come from, and what does each channel cost?
- Who wrote the code, and who maintains it now?
- What breaks most often, and how many support requests arrive each week?
- Which third-party services does the product depend on?
- What would you do next if you were keeping it?
Vague answers to questions 1 and 2 are a reason to slow down.
Step 4: Review the code and infrastructure
Unless you are a developer, pay one for a few hours of review before you commit. Ask them to report on:
- Code quality and structure. Whether a new developer could work on it within days or would need weeks.
- Dependencies. Outdated frameworks, unsupported libraries, and licences that restrict commercial use.
- Security. How passwords and customer data are stored, who has admin access, and whether there have been incidents.
- Deployment. Whether there is a documented, repeatable way to release a change, and whether backups exist and have been tested.
- Hosting costs. Actual invoices, and how costs change as customers are added.
- Ownership. That the seller owns all the code, including anything written by contractors.
Technical checklist for non-technical buyers
If you cannot read code, ask your reviewer to answer each of these in writing:
| Area | Question to answer | Evidence |
|---|---|---|
| Code ownership | Does the seller own all of it, including contractor work? | Written assignments or contractor agreements |
| Hosting | Who controls the cloud account, and what does it cost now? | Account access list and last three invoices |
| Third-party services | Which paid APIs and tools does the product depend on? | A list with costs and the account owner |
| Security | How are passwords and customer data stored? Who has admin access? | Reviewer's notes, access list |
| Backups | Do backups exist, and has a restore been tested? | A dated restore test |
| Documentation | Could a new developer start within days? | README, setup notes, deployment steps |
A "no" or "I do not know" is not a deal-breaker, but each one needs a fix and a cost in your offer.
Sellers are often reluctant to share a full repository before a deal is agreed. A screen-share walkthrough first, and full access after a signed letter of intent and a non-disclosure agreement, is a common compromise. The technical section of the due diligence checklist lists the rest.
Step 5: Check that contracts transfer
Most small SaaS deals are an asset sale, so each agreement has to move to you individually. Check:
- Customer terms. Whether the terms of service or any signed customer contracts allow assignment to a new owner, or need the customer's consent.
- Payment processor. Subscriptions often can't simply be handed over. Ask the processor how existing subscriptions and stored payment details are migrated to a new account.
- Suppliers. Hosting, email delivery, APIs and data providers each have their own terms on account transfer.
- Domains, trademarks and app listings, where relevant.
- Customer data. Whether the privacy policy and the data-protection law that applies to the customers permit the transfer.
Take legal advice on the purchase agreement and on anything that needs consent. The rules vary by contract and by place.
Step 6: Decide how to pay
Many small acquisitions are paid in full at closing. Two structures spread the risk:
| Structure | How it works | Suits |
|---|---|---|
| Seller financing | You pay part at closing and the rest in instalments to the seller, usually with interest | Buyers short of capital; sellers confident the business will keep earning |
| Earn-out | Part of the price is paid later only if agreed targets, such as MRR, are met | Deals where buyer and seller disagree about future growth |
Both keep the seller interested in a good handover. Both also need precise wording: what the target is, how it is measured, and what happens if you change the product. Some buyers also borrow from a lender; each lender sets its own criteria. Take professional advice on the structure and its tax effect.
Step 7: Close through escrow
Use an independent escrow service. You pay the escrow provider, the seller transfers the code, domain, accounts and customer data, you confirm receipt during an agreed inspection period, and the money is released.
VALUERAQ is not a broker or an escrow service and does not handle the purchase price. You and the seller choose the provider and pay its fee. Read the buyer safety page before sending money to anyone.
Step 8: The first 90 days
| Period | Goal | Checklist |
|---|---|---|
| Days 1 to 30 | Keep it stable | Change passwords and keys, confirm backups, answer support yourself, change nothing visible |
| Days 31 to 60 | Learn it | Track MRR, churn and support weekly, talk to the largest customers, fix review findings |
| Days 61 to 90 | Improve one thing | One change at a time, measured against the months before, use the seller's support period |
Days 1 to 30: keep it stable. Change every password and access key. Confirm backups work. Answer support yourself so you hear what customers actually ask. Change nothing customers can see.
Days 31 to 60: learn it. Watch MRR, churn and support volume weekly and compare them with the seller's figures. Talk to the largest customers. Fix the faults the code review found.
Days 61 to 90: start improving. Make one change at a time, such as pricing or onboarding, so you can tell what caused any movement in the numbers. Use the seller's support period before it runs out.
To price the product before you offer, read how to value a SaaS company and run a quick SaaS business valuation with the SaaS valuation tool.
Frequently asked questions
Do I need to be a developer to buy a SaaS business?
No, but someone has to maintain the code. If that isn't you, budget for a developer or agency from day one and have them review the code before you buy.
What churn rate is too high?
There's no single line. VALUERAQ's tool treats 2% to 5% monthly churn as its baseline and lowers the multiple above 5%. What matters more is whether the seller can explain why customers leave.
How do I check the MRR on a listing?
Ask for monthly recurring revenue by month, taken from the payment processor or billing system, and match it to the bank deposits. Check that it counts only active subscriptions and leaves out one-off fees. The table in step 2 shows where each figure should come from.
How long should the seller help after the sale?
Many small deals include a support period, often counted in weeks or a few months, in which the seller answers questions and helps with handover. Put the length and the hours in the purchase agreement, and use it before it runs out.
Can I see the code before making an offer?
Usually only in part. Many sellers give a walkthrough first and full access after a letter of intent and a non-disclosure agreement. Make your offer conditional on a satisfactory code review.
Next step
Check a SaaS asking price against its ARR, churn and margin with the free SaaS Valuation Tool.
Written by VALUERAQ Editorial Team. The VALUERAQ editorial team writes and maintains the platform's guides, methodology and glossary. Every guide is reviewed against the published methodology before publication and when the methodology changes.