Where to Buy a SaaS Business: Revenue, Code and Owner Work
By Graham Ashler · Last checked October 2026
Founder & Editor · Deal Field Guide
Where to buy a SaaS business starts with Acquire.com for direct founder conversations, or Empire Flippers, FE International and Quiet Light for broker-listed opportunities; Flippa is another self-directed source. Pick the route around your technical support, available capital and diligence skills, then verify that customers, code and billing can survive the founder's departure.
The attractive number is monthly recurring revenue. The difficult question is what must happen every month for that revenue to recur.
A subscription does not remove customer choice, software maintenance or support. My preference is a modest product whose customers keep using it over a larger one whose founder is quietly holding everything together.
Where to buy a SaaS business, by the process you can handle
Start where the service model fits your needs. The marketplace's category, the seller's claims and the provider's screening are separate things; none is a warranty that the business will work for you.
Provider descriptions are Provider published terms (dated), checked October 24, 2026. Fit judgments are our interpretation.
| Source | Useful starting point | What you still need to establish |
|---|---|---|
| Acquire.com | A SaaS-focused search with direct founder conversations and transaction tools | The revenue quality, technical condition, contract transfer and work needed after closing |
| Empire Flippers | A broker-led online-business purchase with a published migration process | That the individual SaaS fits your skills; the source code and customer obligations still need specialist checks |
| FE International | A SaaS acquisition through its buying/advisory route | The engagement scope, buyer requirements and case-specific cost and process |
| Flippa | A broad SaaS category for a buyer prepared to screen listings | The meaning of listing verification, seller identity, complete costs and the handover |
| Quiet Light | Broker-listed businesses, including SaaS | The actual business records and technical evidence, rather than just the public summary |
| Direct founder outreach | A product or niche you already understand | Identity, title, records, contracts and the entire transaction process without assuming a platform supplies them |
Sources for service and access scope: Acquire buyer pricing, Empire Flippers buying process, Flippa pricing, FE International buying services and Quiet Light listings.
The Deal Decision Check
Requirement: You can commission technical diligence, understand a subscription business and want to speak directly with the founder. Evidence: Acquire publishes SaaS listings and paid access to founder conversations and deal tools. Rule: That service model fits a buyer willing to run the acquisition. Result: supported by the stated evidence for the sourcing route. Next step: Browse public listings and identify which one deserves deeper work.
If your requirement is “software I never need anyone to maintain,” the service model does not fit that wish. Neither a broker nor an AI coding tool turns an operating product into an obligation-free asset.
If you need to compare how much of the deal each provider handles, start there before paying for access.
Compare SaaS buying routes and responsibilities
Access plans: do not pay before confirming the listing
Public browsing can help you decide whether a source has the right kind of business. Paid access should follow a specific search need, not substitute for it.
Acquire's subscription terms list Basic as free, Premium at $390 a year and Platinum at $780 a year. The same help page describes Premium access by startups with up to $250,000 in trailing-twelve-month revenue. The pricing FAQ instead describes startups priced up to $250,000. Evidence: Provider published terms (dated), checked October 24, 2026; finding: conflicting. Ask which plan covers the exact listing before subscribing. Both pages describe Platinum access to all sizes.
Flippa publishes free access and an optional Premium subscription. Empire Flippers' published process requires identity verification, proof of funds and a listing unlock before detailed access. Provider published terms (dated), checked October 24, 2026, Flippa pricing and Empire Flippers buying process. Read current payment, diligence and cancellation terms rather than relying on an old review.
We did not verify a universal buyer charge for FE International or Quiet Light from the pages inspected. Treat the applicable fee as Not verified, not zero. Confirm the service and cost in writing.
The funding frame: a $240,000 SaaS purchase with $304,000 available
A SaaS business may need no physical stock, but it still needs operating cash, professional review and a budget for the technical work discovered during diligence. Financing does not remove those needs.
This is a fictional, unfinanced purchase in US dollars. Every amount is a User assumption, not a quote, valuation or typical market cost.
| Capital item | Assumed amount |
|---|---|
| Business consideration | $240,000 |
| Physical inventory | $0 — none in this scenario |
| Legal, financial and technical diligence | $12,000 |
| Payment/escrow and transaction allowance | $1,000 |
| Defined post-close technical remediation | $15,000 |
| Additional working capital | $12,000 |
| Reserve | $24,000 |
| Total funding required | $304,000 |
The $15,000 remediation line covers a specific assumed backlog, not a second reserve for every possible problem. Replace it with scoped work and estimates. Unknown technical liabilities need investigation; they should not disappear into a cheerful contingency percentage.
With $280,000 available, this case is short $24,000. Deal Decision Check result: does not fit as funded. The listing price being below $280,000 is not enough.
Any seller financing needs its own schedule. Count the unpaid purchase price once, show cash at close separately, and subtract debt payments from the cash you expect to keep.
Rebuild recurring revenue before valuing it
Monthly recurring revenue, or MRR, is a measure of recurring subscription revenue normalized to a month. It is not the month's bank deposits, total sales or profit.
Annual plans are where confusion gets costly. A customer paying $1,200 for a year contributes $100 a month to a simple annual-plan MRR calculation. The buyer may inherit months of service after the seller has already received the cash. Your accountant and lawyer should address that prepaid-service obligation in the terms and funding plan.
Stripe's subscription documentation describes the billing lifecycle, including subscription states and payment collection. Provider published terms (dated), checked October 24, 2026. Your revenue record should distinguish customers who are paying, trials, cancellations, unpaid invoices and one-time charges; a raw subscription count is not enough.
Here is a fictional one-month MRR roll-forward, with all figures User assumptions:
| Movement | Assumed monthly recurring revenue |
|---|---|
| Opening MRR | $18,000 |
| New customer MRR | +$1,000 |
| Expansion from existing customers | +$300 |
| Canceled customer MRR | −$900 |
| Downgrades | −$400 |
| Closing MRR | $18,000 |
The headline is flat. Underneath it, $1,300 of new and expansion revenue replaced $1,300 lost to cancellations and downgrades. Flat MRR does not prove that customers stay. Request a monthly series and customer cohorts, not one roll-forward.
Define every retention calculation before comparing it. Use the same opening cohort, period, treatment of discounts and currency. Keep new customers out of the calculation of what happened to the opening customer group.
The owner-cash bridge: what remains after keeping it running
Reconciled subscription revenue needs complete hosting, support, vendor and maintenance costs beneath it. Then price the founder's unpaid work that you must perform or replace.
Continue the fictional example, monthly in US dollars:
| Monthly operating item | User-assumed amount |
|---|---|
| Recurring revenue | $18,000 |
| Payment fees and refunds | −$600 |
| Hosting | −$1,200 |
| AI/API usage | −$800 |
| Existing development contractors | −$2,000 |
| Existing support expense | −$400 |
| Other software and operating costs | −$400 |
| Available before unpaid owner labor, debt and tax | $12,600 |
| Additional cost to replace the founder's unpaid work | −$5,000 |
| Labor-adjusted cash before debt and tax | $7,600 |
The new $5,000 is for work not covered by the existing contractors and support expense. Subtracting all development cost again would double-count it. Assuming the contractors do the founder's work without evidence would make the opposite mistake.
Stress the assumptions. If MRR falls by $3,600 and all listed costs stay unchanged, labor-adjusted cash falls to $4,000. If the AI/API bill also rises by $1,000, it falls to $3,000. These are simple sensitivity cases, not forecasts or return promises.
The business can still be worthwhile. It is just a different purchase from “$18,000 a month on autopilot.”
Field Notes: the product is only part of the job
Basis: Operator experience. Our publisher has built and run SaaS, along with content and affiliate sites, Amazon FBA, KDP, iOS subscription apps and YouTube channels. He has not worked as a broker or bought or sold through the providers covered here. These are operating observations, not acquisition case studies.
The hard part is often the small stream of work that never ends: a dependency changes, a customer cannot log in, a payment fails, a report is wrong, a browser update breaks something, or a valuable user needs a feature that is awkward to add.
Ask the founder to show the last month of support and maintenance, with private customer information appropriately protected. What did they fix? What did they postpone? What required their personal knowledge? A neat product tour rarely answers those questions.
A founder who understands every corner of the product can solve a problem in minutes. A new owner may need hours just to find the relevant code. That is why documentation and a reproducible deployment matter more than a statement that the software is “simple.”
A nontechnical owner still needs a technical plan
You do not have to be the developer. You do need someone capable of evaluating the system and maintaining it after the seller leaves.
Price that person before you price the business. Have them explain, in plain language, what it costs to operate, what can break, whether backups restore successfully and what urgent work is needed. If nobody can give you that explanation, the technical condition is unresolved.
Do not let a seller's offer of a few support calls stand in for an ongoing maintenance plan. Transition help ends. The product's obligations do not.
The transfer register: code, customers and billing must all work
Ownership of a repository does not by itself deliver a working business. The product needs its infrastructure, rights, customer relationships and payment arrangements to function together.
| Asset or dependency | Evidence to request | What acceptance should demonstrate |
|---|---|---|
| Code and intellectual property | Repository history, creator/contractor rights and license inventory | Buyer has the rights needed to operate and change the product |
| Deployment and infrastructure | Hosting/services register, build instructions and secrets inventory | An authorized person can deploy and recover the product without the founder's personal account |
| Data and backups | Data map, access controls, restore procedure and test evidence | The agreed backup can restore a usable system and data handling meets the applicable obligations |
| Customer contracts | Terms, negotiated agreements and consent/assignment provisions | Required consents or new agreements are identified and obtained |
| Billing | Subscription export, unpaid invoices, prepaid periods and processor guidance | The buyer can collect payments through an approved setup |
| Domains and communications | Registrar, DNS, email and transactional-mail register | Buyer controls renewal, delivery and recovery channels |
| Third-party APIs | Current contracts, quotas, cost history and change notices | Access, pricing and usage limits remain workable under the buyer's arrangement |
| Key people | Contractor scope, availability and replacement options | Critical work has a named owner after transition |
For Stripe accounts involved in a sale, Stripe says to contact support first about the information that must change. Provider published terms (dated), checked October 24, 2026, Stripe business-sale transfer guidance. Do not infer processor approval from having repository access or a signed asset agreement.
Use your advisers for privacy, security, tax and contract obligations. A marketplace's document builder does not know every negotiated customer contract in the business.
AI can lower development cost and weaken differentiation
Treat the AI claim as two questions: does it improve the economics, and does it make the product easier for customers or competitors to replace? The answers can point in opposite directions.
An AI feature can reduce manual work, but it can also introduce usage cost, model dependence and quality failures. Ask for cost per paying customer and per task, including heavy users. A small average bill can hide a few customers who are unprofitable to serve.
My preference is to pay for retained customers and a solved workflow, not for how quickly an AI tool can reproduce a demo. Distribution, trusted integrations, reliable data and customer habit may be valuable; “built with AI” tells me very little about any of them.
Require evidence for any claimed savings. If the founder still corrects the output manually, include that time. If a model or API changes, identify who fixes the product and what alternative exists. Those are underwriting questions, not predictions that every small SaaS will succeed or fail.
Ask for a deal record, not a sales pitch
Your first request should make the next decision possible. Keep one record showing each claim, source, period, result and unresolved question.
| Claim | Source and period to request | What would settle it? |
|---|---|---|
| “MRR is stable” | Monthly billing export and customer cohorts | A reconciled roll-forward explaining new, expansion, cancellation and downgrade revenue |
| “Almost no support” | Ticket export and founder task log over representative weeks | Hours, severity, unpaid work and who handles exceptions |
| “Easy to maintain” | Recent releases, incidents and dependency inventory | An independent technical review and realistic maintenance scope |
| “All customers transfer” | Customer agreements and processor guidance | Required approvals identified; no assumption that a login transfers legal relationships |
| “Great margins” | Complete hosting, API, contractors, software and refunds | Cash and labor-adjusted earnings calculated on the same period |
When a seller cannot produce a record, mark the question unresolved. When records disagree, mark it conflicting. Neither condition becomes safe because several less important checks passed.
Your next step
If you can evaluate the technical work, fund the full acquisition and want direct founder conversations, Acquire is a logical source to inspect. Browse public listings first and resolve the buyer-plan access conflict before paying for a particular deal.
Browse SaaS businesses on Acquire.com
We have no active referral links as of October 24, 2026. This is an ordinary provider link; our affiliate disclosure explains our intended funding model.
Use our online business buying guide for the sequence from initial screen to closing. A business that needs skills or reserves you do not have can be a good business and still be the wrong purchase for you.
How we researched this guide
Deal Field Guide helps you buy or sell an online business with clear eyes — comparing the real routes, showing the money after fees, and telling you what owning each kind of business is actually like, with the source behind every number.
Research note: We checked the linked primary provider and Stripe pages on October 24, 2026, compared their published services and recomputed the fictional examples. We did not buy through these providers, inspect a private codebase, audit a live business or confirm a transaction quote. Provider screening and tool descriptions remain published claims, not our test of a completed deal. We use software, including AI, to organize research and drafting and remain responsible for what we publish. Graham Ashler is an editorial pen name; see About for our publisher and scope.
This is general information, not legal, tax or investment advice.
Sources
- Acquire SaaS listings, buyer pricing and subscription terms.
- Empire Flippers marketplace and buying process.
- FE International SaaS buying route, Flippa SaaS category and Quiet Light listings.
- Flippa verification explanation and pricing.
- Stripe subscription lifecycle and business-sale account guidance.