Sell a SaaS Business: Recurring Revenue, Real Work and Cash at Close
By Graham Ashler · Last checked October 2026
Founder & Editor · Deal Field Guide
Sell a SaaS business by proving the recurring revenue, documenting the work needed to keep customers and choosing a sale process you can manage. A marketplace may suit a founder willing to negotiate directly; a broker may suit someone wanting more help. Transferable billing, code rights and customer retention matter before price.
The most dangerous shortcut is treating monthly recurring revenue as profit. The second is treating working code as a business someone else can run.
I would prepare the business around one question: what stops working when you stop being available? The answer belongs in the records, the price discussion and the handover plan.
What changes your route: working software without revenue, profitable software with clean records, a service-heavy “SaaS” and a business that needs a full technical team are different sale cases. If the buyer cannot keep billing customers or legally use the code, the attractive revenue chart does not resolve the problem.
Sell a SaaS business: choose the service before the listing
Choose by how much of the sale you want to run and whether the provider accepts your business. A customer success manager, a document builder and a full broker are different kinds of help. Ask who communicates with buyers, negotiates, checks the data and coordinates the technical transfer.
| Provider or route | Fit to investigate | Published condition or service limit | What stays with you |
|---|---|---|---|
| Acquire.com standard marketplace | Founder willing to work directly with buyers using listing support, data room and closing tools | Listing approval required; its pre-revenue route is limited to qualifying functional SaaS and AI products | Buyer decisions, explanations, negotiation and the transfer work your agreement assigns |
| Empire Flippers | Profitable established SaaS whose owner wants broker-led buyer communication and migration coordination | At least $2,000 average monthly net profit over the last 12 months, 12 months of revenue and 3 months of qualifying analytics, among other screens | Evidence, diligence answers, decisions and technical cooperation |
| FE International marketplace | Owner comfortable managing a listing with a customer success manager | Separate self-serve service; obtain the current eligibility and fee terms | Listing management and deal decisions |
| FE International advisory | Owner wanting an adviser to prepare financials and run an advised process | Separate service; advisory fee must be quoted, not inferred from marketplace pricing | Accurate records, disclosure and deal decisions |
| Flippa | Owner comparing its relevant software selling package | Package, success fee and service scope need confirmation for the business | Whatever your selected package leaves to you |
| Direct buyer | Customer, competitor or operator already interested | No platform is assumed; existing agreements may still make a fee payable | Buyer checks, price testing, legal and payment process, technical handover |
Provider published terms (dated), checked October 24, 2026: Acquire pricing, seller process and pre-revenue rules; Empire Flippers seller service and listing requirements; FE marketplace and advisory; Flippa pricing.
Acquire also offers Guided by Acquire as a distinct service. Its dedicated program page advertises a 6% closing fee with no upfront fees and says it is for SaaS with at least $100,000 in trailing-12-month revenue, ideally over $5 million. The standard seller-pricing page also describes the program as for profitable SaaS. These are Provider published terms (dated), checked October 24, 2026. Do not assume the standard marketplace example below is the quote for that program or add both fee schedules together. Confirm the accepted service, eligibility, subscription treatment and fee in writing.
Deal Decision Check: working product, no customers yet
Your requirement is to sell functional, publicly deployed software without a revenue history. Empire Flippers' revenue and profit screens do not fit. Acquire's published pre-revenue rules may fit a functional, transferable SaaS or AI product; acceptance remains unresolved until its review.
The next step is to show a working demo, the assets included and the transfer plan. A repository with no live product or a coming-soon page does not meet the functional-product case in that guidance. Provider published terms (dated), checked October 24, 2026: Acquire's pre-revenue criteria.
The $300,000 proceeds bridge: cash and a note are different offers
Compare what reaches you at closing and what remains at risk afterward. A seller note is debt the buyer owes you; it is not cash you have received. A closing fee charged on the total consideration can arrive before some of that consideration does.
Fictional standard-marketplace example, USD; not a valuation. The final business price is $300,000, the listing stays in the $250,000–$1 million middle tier for four billed months, and seller professional costs are assumed to be $6,000. There is no inventory, earnout, holdback or debt payoff. Taxes are outside the example.
Acquire's published middle-tier closing rate is 7%, with a $50 monthly listing charge. Its fee-confirmation page says the final purchase price determines the final rate and fee, due in full at closing. Its buyer/seller terms, section 5.2.2, expressly include promissory notes and other deferred consideration in that fee base. Exactly $250,000 and $1 million are not used here because its public pages word those boundaries differently. Provider published terms (dated), checked October 24, 2026: seller pricing, listing subscriptions and closing-fee confirmation.
| USD proceeds item | Offer A: all cash | Offer B: $90,000 seller note |
|---|---|---|
| Total business consideration | $300,000 | $300,000 |
| Cash consideration at closing | $300,000 | $210,000 |
| Seller note, not closing cash | $0 | $90,000 |
| Closing fee on total consideration: 7% × $300,000 | −$21,000 | −$21,000 |
| Listing charges already paid: 4 × $50 | −$200 | −$200 |
| Assumed professional costs | −$6,000 | −$6,000 |
| Net closing cash from this transaction after the closing fee and assumed professional costs | $273,000 | $183,000 |
| Cumulative net cash by closing after also counting prior listing charges | $272,800 | $182,800 |
| Additional future note principal, only if collected | $0 | $90,000 |
| Total net consideration after those costs, if the note is paid in full | $272,800 | $272,800 |
The note is counted once. Interest, if any, is excluded. So are enforcement expenses and the possibility of nonpayment. The final row is a collection-dependent total, not guaranteed proceeds.
Before accepting Offer B, settle the note's security, payment schedule, default terms, reporting rights and any limits on changing the business with a lawyer. If a buyer instead proposes an earnout, payments depend on future conditions: define the metric, accounting rules, control and dispute process. Do not quietly treat the maximum earnout as money already earned.
Deal Decision Check: if you need at least $250,000 of cumulative net cash by closing, Offer A is supported by the stated evidence under the assumptions above. Offer B does not fit, even though both display a $300,000 price. Your next step is to change the terms or reject that offer, not hope the note becomes cash on time.
If you want the standard marketplace process and can explain these records to buyers, review its current seller terms next.
Review Acquire.com seller pricing and listing options
No provider pays us today. This is an ordinary official link. Affiliate disclosure.
Reconcile recurring revenue before discussing a multiple
Monthly recurring revenue, or MRR, measures a defined monthly subscription run rate. It is not the same as cash collected, bookings or profit. Define what you include, then reconcile the dashboard to billing records and customer status.
Here is a fictional monthly movement record, in USD:
| MRR movement | Amount | What to inspect |
|---|---|---|
| Starting MRR | $10,000 | Paying customer subscriptions at the opening cutoff |
| New-customer MRR | +$1,200 | New paid subscriptions; exclude free trials |
| Expansion from existing customers | +$300 | Paid upgrades or increased usage included under your definition |
| Contraction from existing customers | −$200 | Downgrades and reduced recurring commitments |
| Churned MRR | −$800 | Subscriptions lost from the opening customer cohort |
| Ending MRR | $10,500 | $10,000 + $1,200 + $300 − $200 − $800 |
On those assumptions, annual recurring revenue, or ARR, is a $126,000 run rate: $10,500 × 12. It is not proof of $126,000 earned during the previous year.
For the opening customer cohort, gross revenue retention is 90%: ($10,000 − $200 − $800) ÷ $10,000. Net revenue retention is 93%: ($10,000 + $300 − $200 − $800) ÷ $10,000. New customers are excluded from both calculations. State the period; a monthly retention figure cannot be passed off as an annual figure.
A business can add customers and still lose revenue from the customers it already has. That is why I want the movement bridge, not just the ending MRR.
Check whether the money is recurring in substance
Split subscription revenue from setup fees, implementation, consulting, affiliate income, one-time licenses and lifetime deals. A subscription invoice can still pay for a service that requires substantial human work.
Record annual prepayments separately. The cash may already be in the seller's bank while the buyer must provide months of service. Agree the treatment of deferred revenue and remaining obligations; do not treat every prepaid dollar as free cash in the handover.
Also separate failed payments, refunds, discounts, delinquent accounts and customers marked active after they stopped paying. A count of logins is not a count of subscribers.
Show the profit after the founder's necessary work
A buyer can choose to do the work, but they need to know what it is. Separate operating profit, supported owner adjustments and the cost of replacing unpaid work. Do not subtract staff who are already paid in the accounts a second time.
Say a fictional SaaS earns $5,000 a month before unpaid founder labor. The founder handles deployments, escalated support and integrations. A task-based replacement estimate is $1,500 for technical work and $600 for support each month. Cash after that additional labor is $2,900, before debt, tax and other adjustments.
Those replacement costs are User assumption, not market-rate claims. Get a realistic estimate for your stack, workload and response commitments. “An AI agent does the coding” does not resolve who diagnoses a payment failure on a Friday evening.
Keep a log with task, frequency, hours, needed skill, current worker and replacement. Include incidents and irregular maintenance. Where the owner is paid through payroll, show how that expense is treated in the earnings bridge before replacing it.
The transfer record: code access is only the first row
A working transfer gives the buyer legal rights, technical control and a functioning customer service. Use separate checks for assets and dependencies. A buyer who owns the repository but cannot deploy or bill still lacks a running business.
| Area | Evidence to supply | Buyer acceptance test | What remains unresolved until confirmed |
|---|---|---|---|
| Code and intellectual property | Repository inventory, contributor agreements, license list | Buyer controls the right repositories and can build the product | Contractor assignments and third-party license restrictions |
| Deployment | Infrastructure map, environment variables inventory and runbook | Buyer deploys a safe change and rolls it back | Credentials tied to seller-owned shared accounts |
| Billing | Processor, subscription and product mapping | Approved transition preserves the agreed billing flow | Processor approval, country/entity changes and stored-payment migration |
| Customer contracts | Contract schedule and material terms | Buyer knows commitments and required permissions | Assignment, change-of-control or consent requirements |
| Data and security | Data map, access controls, incident record and backups | Restore test; appropriate buyer access; old access revoked | Applicable privacy duties and required notices |
| External APIs | Usage, spend, limits and terms | Buyer operates under approved credentials | Credits, special pricing and nontransferable contracts |
| Support | Ticket history, known bugs and escalation runbooks | Buyer handles a representative support case | Founder-only knowledge and promised response times |
| Analytics and product records | Metric definitions and exports | Billing, usage and retention reconcile | Tracking gaps or changed definitions |
Stripe tells sellers to contact Support before transferring an account after a business sale so it can confirm the required changes. A different-country acquiring entity follows a different process. Do not substitute an email-address change for that review. Provider published terms (dated), checked October 24, 2026: Stripe's business-sale guidance.
GitHub permits repository transfers subject to its conditions, but a repository transfer is not the same as assigning intellectual property or moving all infrastructure. Review permissions, target account and plan-dependent features, then test the deployment. Provider published terms (dated), checked October 24, 2026: GitHub repository transfers.
Do not send production secrets in a public listing. Give access in stages, with appropriate confidentiality, permissions and transaction controls.
Field Notes: recurring revenue does not mean recurring ease
Operator experience. I have built and run SaaS, alongside content and affiliate sites, Amazon FBA, KDP, iOS subscription apps and YouTube. I have not worked as a broker or sold through these marketplaces. These notes concern operating the model, not a completed sale.
The owner's calendar reveals the business
The important work is not always adding features. It can be answering a confused customer, repairing an integration, updating a dependency or understanding why yesterday's new signups did not activate.
A small product can run with a modest routine workload and still need someone who understands it deeply when it breaks. Show both. A low weekly average is less reassuring if the only person who can resolve an incident is leaving.
One customer can make the chart look healthier than the product
Break out customer and channel concentration. One large annual contract can make revenue steady while renewal risk remains lumpy. A reseller can look like many end users but still be one commercial relationship.
I would also show how new customers arrive. A product with self-serve demand and a product dependent on the founder's personal network may report the same revenue. They hand over differently.
The most credible growth plan uses observed behavior
“Raise prices” and “add an enterprise plan” are possibilities, not existing earnings. A stronger case shows customer requests, tested pricing, expansion already happening or a channel that has brought qualified users at a measured cost.
Keep those opportunities outside current profit. Let the buyer choose what they are willing to pay for unproven upside.
AI can lower build cost and weaken a shallow advantage
My view: the question is not whether AI helped write the code. It is whether customers have a durable reason to keep paying and whether the buyer can maintain the product. A useful workflow, a trusted integration and real customer adoption need explaining more than the development method.
For an AI product, show model and API dependencies, usage costs, limits, prompt or evaluation processes and fallback behavior. A gross-margin figure based on introductory credits is not the buyer's steady-state margin. Run the numbers without credits and with plausible heavier use, clearly labeled as scenarios.
Do not claim a feature is protected simply because it took you months to build. Conversely, do not assume a buyer can rebuild a dependable operating product in a weekend because a model can generate a demo. Document what is actually working: onboarding, billing, support, integrations and retention.
From buyer interest to a bounded handover
Use the deal documents to define the price, conditions, assets and obligations. A letter of intent, or LOI, records the proposed terms; review any binding exclusivity or confidentiality clauses before signing. The final purchase agreement must make the closing and handover concrete.
Acquire describes a seller process covering buyer evaluation, offers, due diligence and closing with escrow. Its tools do not remove your responsibility to understand the deal. Provider published terms (dated), checked October 24, 2026: seller process.
Write the transition as tasks and tests: access, build, deploy, bill, restore, support and revoke old permissions. Define the assistance period, communication method and what additional work costs. Avoid an open-ended promise to “help until everything is comfortable.”
There is no sale date we can promise. Record quality, buyer financing, contract permissions and technical migration can each change the timeline. Keep serving customers while the sale is in progress; the business being sold is still a business you operate.
What to do before you open another listing tab
Complete the MRR movement bridge, owner-work log and transfer record. Then calculate the cash you need at closing. Those four pieces tell you more about your route than a headline valuation tool can.
If the standard marketplace process suits you, use the Acquire seller link above. If you want more of the sale handled, compare the broker and advisory scopes in our marketplace comparison. If a decisive billing or ownership question remains unresolved, resolve it before inviting offers.
This is general information, not legal, tax or investment advice.
How we checked 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.
We read official provider and platform documentation on October 24, 2026. Provider published terms (dated) is not a claim of a transaction tested by us. The financial examples and metric bridge are User assumption calculations, not a SaaS appraisal or market multiple. We did not inspect a reader's product or complete a sale. We may use software, including AI, to organize research and drafting, and remain responsible for what we publish. Our methodology.
Sources
- Acquire.com: seller pricing, subscription terms, closing-fee confirmation, pre-revenue rules and seller process.
- Acquire.com: Guided by Acquire and buyer/seller terms.
- Empire Flippers: seller service and listing requirements.
- FE International: marketplace pricing and advisory service.
- Flippa: pricing.
- Stripe: account transfer following a business sale.
- GitHub: repository transfers.