How to Buy a Micro-SaaS: Multiples, Diligence and Red Flags

If you want to buy a micro SaaS, you're buying a small software product with paying subscribers, usually run by one founder or a tiny team. The appeal is obvious. Margins are high, there's no storefront or fleet, and the work can often be done from anywhere. The catch is that everything you're paying for can fade fast: customers churn, code rots, the founder was the support team, and payment accounts don't always move cleanly. This guide covers what small SaaS businesses sell for, how to value one, what to check before you wire money, and the red flags that should end a deal. It also covers when building a product costs less than buying one.

What micro-SaaS businesses sell for

Small SaaS deals are priced on profit, not the high revenue multiples you see in public software stocks. Acquire.com's January 2026 multiples report says:

• The median profit multiple for confirmed SaaS sales was 3.9x in both 2024 and 2025.
• Average profit margins were about 71% in 2024 and held steady in 2025.
• The average time on market was 81 days, and most deals closed within 90 days.
• For contrast, public SaaS revenue multiples fell from about 17x in 2022 to about 5.5x at the end of 2025.

Empire Flippers, another large marketplace, values listings as monthly net profit times a multiple, using the 12-month average of revenue minus all expenses. Its own guidance says a SaaS business with 40% margins earns a higher multiple than one with 20% margins at the same revenue, and that lower churn makes a business "fundamentally more valuable."

Keep one thing in mind. Marketplace data reflects deals that closed on that marketplace. Your target may be better or worse than the median, and asking prices are usually above sale prices.

Worked example: valuing a $6,000 MRR product

Here's a hypothetical product with $6,000 of monthly recurring revenue.

At the 3.9x median profit multiple, that's about $202,000. At 40 times monthly profit, a common marketplace framing, it's about $173,000.

Now stress-test it. Say monthly revenue churn is 5%. Then you lose about $300 of MRR every month, and you need to add $300 of new MRR just to stay flat. Is anything bringing in new customers today, or is the business coasting on customers it signed years ago? If new sales stop and churn continues, MRR falls to roughly $3,200 within a year.

Illustration, not a prediction: these numbers are hypothetical and show how valuation and churn interact. They are not a forecast for any product. Your results depend on the specific business and how you run it.

What would change the price:

• Owner hours. If the founder works 30 hours a week on it, the real profit is lower once you pay someone for that time.
• Growth. A product adding customers is worth more than one that's flat.
• Concentration. If one customer pays 25% of MRR, you're partly buying a single relationship.
• Stack risk. An old framework, no tests and one server nobody understands means cleanup money after closing.

The diligence checklist

Ask for everything below before you sign anything binding. Walk away if the seller won't provide it.

Financial

1. Stripe or payment-processor exports for at least 24 months, not screenshots. Reconcile them to bank deposits.
2. A customer list with plan, start date, MRR and cancellation date. Calculate churn yourself.
3. Refunds, chargebacks and disputes by month.
4. Every expense, including the founder's own unpaid time. Estimate what it would cost to replace that time.
5. Tax returns for the entity, if the seller files separately for the product.

Product and technical

1. Read-only access to the repository, with its commit history.
2. A walkthrough of deployment: how code gets from a laptop to production.
3. A list of every third-party service, what it costs, and whether its account can be transferred.
4. Dependency and security status. Are libraries years out of date? Are there known issues?
5. An error log and uptime history for the last 90 days.
6. Who holds admin passwords, domain registrar access and DNS.

If you can't judge code yourself, pay a senior engineer for a few hours of review. It's the cheapest insurance in the deal.

Customers and market

1. Talk to three to five customers, with the seller's permission.
2. Search for competitors that launched in the last two years. AI tools have made some simple SaaS products easy to copy.
3. Check whether a large platform could add your product's main feature for free.

Moving the accounts: payments and app stores

The transfer is where small deals often go wrong. Plan it in the purchase agreement.

Stripe. For a sale, Stripe's support guidance says you first contact Stripe Support to confirm what needs to change. Stripe then lets you edit the legal name, tax ID, bank account and owner details in the dashboard. If you move to a new Stripe account instead, customer data can be copied, but subscriptions, invoices, plans and coupons do not copy and have to be recreated.

Apple App Store. Apple allows transferring an app between developer accounts. Reviews, ratings and the bundle ID move with it. But TestFlight must be turned off first, Sign in with Apple needs extra steps, and some items such as Apple Pay merchant IDs don't transfer. For auto-renewable subscriptions, the seller must share an app-specific shared secret with you before the transfer.

Google Play. Google's help center says user data, ratings, reviews and store listings move with a transfer. Payout and earnings reports don't. Firebase, Google Analytics and AdMob have to be reconfigured, and requests are reviewed within two business days.

Make the final payment depend on these transfers being complete, and hold some of the price back until they are.

Red flags that should end the deal

• Revenue in the seller's deck that doesn't match the processor export.
• Churn the seller "doesn't track."
• A large share of revenue from annual plans that all renew in one month you haven't seen yet.
• Mostly lifetime-deal customers who pay nothing more but still use support.
• Code that only the founder can deploy, with no documentation and no willingness to do a handover period.
• Accounts registered to the seller personally that can't be moved, such as a personal Apple developer account tied to other apps.
• Pressure to close fast. Remember, the average listing on Acquire.com took 81 days to sell.

Financing a micro-SaaS purchase

Most small software deals are cash, seller-financed, or a mix. SBA 7(a) loans can finance acquisitions of online businesses. SBA's SOP 50 10 8.1 lets lenders skip the physical site visit for virtual businesses if they verify operations another way. But the same rules apply as for any acquisition: 10% equity, 1.25x debt service coverage on historical results, and a lender-ordered valuation. Many lenders don't want to lend against a product with no fixed assets. Our SBA 7(a) guide covers the details.

Buy or build?

Buying makes sense when the value is the customers: steady MRR, low churn, and a channel that keeps bringing new ones in. Building makes sense when the value is mostly the code or the idea: a product with few customers, or a niche where you already have distribution. A $40,000 asking price for a product with $800 of MRR is mostly paying for software, and software can often be rebuilt for less, in your own accounts, on a modern stack. For a broader comparison, see buying an app business vs a Main Street business and buy a business or build one.

How Ottomind can help

We can help on both sides of that decision. If you're buying, Ottomind Studio can modernize the product after closing, or rebuild it on accounts you own, at a fixed price agreed after a scoping call; focused MVPs start from $25,000 and are targeted for production within about four weeks of scope sign-off.

If you'd rather start with a ready-designed product than buy one, the Ottomind Store sells apps we build and brand for you. You can own 100% (typically $12,000 or $18,000) or own 80% (typically $8,400 to $16,800), and 80% stakes can be paid at $500 a month with no interest. A new app starts with no subscribers. If you want existing MRR from day one, buying a proven micro-SaaS is the better fit.