Exit research
Micro-SaaS exits: what real acquisitions reveal
A grounded view of small software acquisitions: how long products took to sell, where transactions happened and which figures were actually disclosed.
- Exits tracked
- 136
- Total disclosed value
- $90.8M
- Median time to exit
- 7 mo
What counts as a micro-SaaS exit?
A micro-SaaS exit is the sale of a focused software product, usually operated by a solo founder or a small team. The transaction can include the codebase, domain, customer contracts, brand, data and operating processes. Deal structures vary, so a public asking price is not treated as a completed sale.
WrapperExits records completed or credibly reported transactions and labels the strength of the supporting evidence. When a sale price or revenue figure is unavailable, it remains undisclosed.
How quickly do small SaaS products exit?
The current median time from launch to exit is 7 months. The fastest observed exit is 2 months. These figures describe the available sample, not the probability that a newly launched product will sell.
Time-to-exit alone also says little about outcome quality. A fast asset sale may reflect a modest product transfer, while a longer holding period may build more recurring revenue and operational proof.
Where micro-SaaS acquisitions happen
Public marketplaces make some transactions easier to verify, while direct founder announcements and private deals often disclose fewer financial details. These are the leading recorded channels in the current dataset.
| Acquisition channel | Tracked exits |
|---|---|
| marketplace | 24 |
| direct | 15 |
| inbound | 6 |
| Build in public X | 3 |
| outbound | 2 |
| 2 | |
| 2 | |
| Meta ads + SEO + Product Hunt | 1 |
What buyers evaluate beyond revenue
Transferability
A buyer needs to understand whether the product can operate without the founder, and whether customer, vendor and model-provider relationships can be transferred.
Revenue quality
Recurring revenue, retention and customer diversity tend to matter more than a single high-revenue month.
Operational and platform risk
Support load, technical debt, API costs and dependency on search, app stores or a single AI model can change both price and deal terms.
Comparing exits responsibly
Compare like with like: completed sales rather than listings, recurring revenue rather than total historical revenue, and categories with similar customer and cost profiles. For a revenue-based view, see the AI SaaS valuation multiple guide . For segment-level comparisons, use the category benchmark table .
Data quality and limitations
Private acquisition data is incomplete by nature. WrapperExits links each record to its source and separates verified, marketplace, self-reported and estimated evidence. Aggregates exclude missing values from the relevant calculation. The results are useful for research and benchmarking, but they are not investment or valuation advice.