Can you sell a SaaS with no revenue?
Usually not as a business. People who buy SaaS companies are buying revenue, and they price a deal as a multiple of it. With no revenue there is little for them to price, so most pre-revenue products never find a buyer. The code is a different matter. AI labs license real source code and the git history behind it to train and evaluate coding models, and they pay whether or not the product ever made money. The license is non-exclusive, so you keep ownership, keep the product and are paid each time a license closes. To see what yours would earn, get a valuation.
The rest of this guide explains what business buyers look for, why a pre-revenue SaaS rarely clears that bar, and what licensing the code involves.
What do buyers look for when you sell a SaaS?
A business buyer wants a cash flow they can own. They look at the same handful of numbers on almost every deal:
- Recurring revenue. Monthly or annual recurring revenue is the base of the price. Deals are quoted as a multiple of it, or of profit for smaller products.
- Growth. A product growing month over month earns a higher multiple than a flat one.
- Churn. Low churn means the revenue will still be there after the sale. High churn cuts the multiple fast.
- Profit and costs. Hosting, support and paid tools all come off the top.
- Owner dependence. If the product only runs because the founder answers every ticket, the buyer is buying a job.
- Traffic and acquisition channels. Buyers want to know where new customers come from and whether that will last.
Acquisition marketplaces are built around these numbers. Their listings lead with revenue, profit and growth charts, because that is what their buyers search on.
Why is a pre-revenue SaaS so hard to sell?
Because almost every one of those numbers is zero or unknown. A buyer cannot apply a multiple to nothing, and without customers there is no churn data to show the product is wanted. What remains is the code, a domain and maybe a design, and a business buyer assumes they could rebuild those, or have them built, for less than the risk is worth.
There are exceptions. A product with a waitlist, a strong niche or an unusual technical asset can attract an acqui-hire or a strategic buyer. These deals are rare, slow and hard to plan around. For most founders with a working product and no paying users, listing it as a business ends in silence or a token offer.
The work still has value. Business buyers are simply the wrong audience for it.
What can you do with a SaaS that has no revenue?
License the codebase. AI labs need large amounts of real, private source code to train and evaluate coding models. Public code is already in their data. What they lack is the software that companies and developers kept to themselves, and a SaaS repo with a few years of commits is exactly that.
Three things make this different from a sale:
- You keep the code. The license is non-exclusive. You keep full ownership and full internal and commercial use.
- You can keep running the product. Nothing is deployed, published or changed. Labs receive a scrubbed copy of the repos you select and never touch your servers, databases or customers.
- You can be paid more than once. The same repo can be licensed again, and you are paid each time a license closes and the buyer pays, within 15 days.
This works for live products, shelved ones and SaaS products that were shut down. If the company behind it has folded, the guide to sell dead startup code covers who holds the rights.
What do AI labs value in a SaaS codebase?
Labs grade code on how much real engineering it shows. Revenue, users, design and whether the product still runs make no difference. These things do:
- Long commit history. Years of genuine commits, fixes and refactors carry most of the value. Across the licensing program, history makes up about 79% of licensed tokens.
- Tests. Unit and integration tests show what the code is meant to do and how it was checked. Labs use them to grade models.
- Real production patterns. Billing, subscriptions, permissions, multi-tenancy, background jobs, webhooks and third-party integrations are the parts of SaaS that are hard to fake and hard to generate.
- Database migrations. A long trail of schema changes shows how a real product evolved under real requirements.
- Several repos. A SaaS often spans an app, an API, workers and infrastructure code. Each repo is counted and can earn on its own.
What lowers the value is code that is mostly generated, copied from a starter kit or squashed into a few commits. Keep the history as it is. No clean-up is needed: secrets and personal data are stripped from the review copy, code and history both, before any buyer sees it.
Should I sell the business or license the code?
If you have real revenue and growth, a business sale may still be the right move. If you do not, the comparison looks like this:
| Selling the business | Licensing the code | |
|---|---|---|
| What the buyer pays for | Revenue, growth, customers | Source code and git history |
| Revenue needed | Yes, usually a track record | None |
| What changes hands | Company, code, domain, customers | A scrubbed copy of selected repos |
| Ownership afterward | Moves to the buyer | Stays with you |
| Keep running the product | No | Yes |
| How often you are paid | Once | Each time a license closes |
| Time to a first figure | Weeks or months of diligence | Minutes after connecting Git |
The two are compatible. A non-exclusive license leaves you free to sell the company later, as long as you disclose the license to the buyer.
How much is SaaS code worth without revenue?
Code is valued by the token, a short chunk of text of a few characters. Value per license is source tokens at $100 per million plus history tokens at $40 per million. A typical repo earns about $1,000 to $1,500 per license. A deep one with years of history and tests earns about $2,500 to $4,000, and a few long-lived codebases have earned tens of thousands of dollars.
Those figures are illustrative and conservative, and they do not depend on revenue. A SaaS that never had a paying customer is valued exactly like one that did, if the code and history are the same size and quality. For the full method and an estimator, read how much is my code worth.
How do you license a SaaS codebase?
The process is short and has no upfront cost:
- Check the rights. Only submit code you own. If investors, a client or a former employer may have a claim, check the agreements first.
- Request access. Fill in the valuation form and you are set up.
- Sign and connect. Read the agreement, sign once and give read-only access to GitHub, GitLab or Bitbucket. Pick only the repos you want valued.
- See the estimate. A real per-repo figure appears within minutes. You can withdraw any repo at that point.
- Get paid. Code is graded on the review copy and taken to buyers in batches. Each license that closes pays you.
For why labs pay for code at all, read sell code for AI training. For more on SaaS products specifically, see sell my SaaS.
Can I sell my SaaS side project?
Yes, on the same terms. A side project with a real history is often a typical repo, and an unfinished one still qualifies if the code is real and yours. Check that your employment contract did not claim work done outside your job, and keep the commit history intact.
If the product has no revenue and you have stopped building it, licensing the code is the one route that pays for it today. Get a valuation to see the figure for your repos.