How to buy a micro SaaS: a practical acquisition guide

Buying a small, profitable SaaS is often faster than building one from zero. You skip the part where you guess whether anyone wants the product, because paying customers already answered that question. The trade-off is you inherit someone else's code, someone else's churn, and sometimes someone else's technical debt.

This guide walks through where micro SaaS businesses actually get listed, how to evaluate a deal before you fall in love with the revenue number, what due diligence to run, and how to negotiate without overpaying for a business that might not survive the transition.

What counts as a micro SaaS acquisition

There is no strict cutoff, but in practice "micro SaaS" acquisitions in 2026 typically mean:

• Monthly recurring revenue from a few hundred dollars up to roughly $20,000
• A small, often solo-maintained codebase
• One founder or a tiny team running support, sales, and development
• A sale price commonly in the 2x to 4x annual revenue range, though this varies a lot by growth rate, churn, and how much of the business depends on the founder personally

Above that range you are closer to a small business acquisition with lawyers, escrow services, and formal due diligence on both sides. Below it, the deal often looks more like buying a side project than buying a company.

Where micro SaaS businesses get listed

Deal flow comes from a handful of consistent sources:

• Dedicated acquisition marketplaces. Platforms built specifically for buying and selling small SaaS and content businesses, where sellers list revenue, traffic, and asking price upfront.
• Indie founder communities. Indie Hackers, niche Slack and Discord groups, and X threads where founders mention they are ready to sell, often before a listing goes anywhere public.
• Direct outreach to founders who seem to have stalled. A product with a stale changelog, an unanswered support inbox, or a founder who has publicly said they are burned out is sometimes open to an offer nobody asked them for.
• Broker-assisted sales. For larger micro SaaS deals, brokers who specialize in small SaaS transactions can filter for legitimacy and handle structuring in exchange for a commission.

Public marketplaces are the easiest starting point because the numbers are disclosed upfront. Direct outreach tends to produce better prices because there is no bidding pressure, but it takes longer and requires more legwork.

What actually predicts whether a micro SaaS is worth buying

Revenue is the headline number. It is not the number that predicts whether you will regret the purchase in six months. Weigh these instead:

Revenue concentration and churn

A product earning $3,000 a month from 300 customers paying $10 is a fundamentally different asset than one earning $3,000 a month from three customers paying $1,000. Ask for a customer list with tenure and payment history, not just a revenue chart. High concentration means your entire business depends on whether two or three people stay happy.

Churn matters more than the current MRR. A product losing 8% of revenue monthly needs constant new signups just to stay flat. Ask for at least 12 months of churn data, not a snapshot.

How much depends on the founder

Some products run themselves. Others run because the founder personally handles every support ticket, manually onboards every customer, or is the reason people trust the brand on social media. Ask directly: what happens to signups, support response time, and churn if the founder disappears for a month? If the honest answer is "it falls apart," you are not buying a business, you are buying a job.

Codebase health, not just feature count

A long feature list built by one person over three years, with no tests, no documentation, and dependencies several major versions behind, is a liability disguised as an asset. Get read access to the repository before you commit to a price, not after. If the seller resists a code review, treat that as a signal.

Traffic and acquisition channel dependency

If most signups come from one channel (a single SEO ranking, one App Store category, or one influencer partnership), that revenue is more fragile than it looks. Ask for traffic source breakdowns over the last 12 months, and check whether any single channel accounts for more than half of new signups.

Due diligence checklist before you make an offer

Run through this before any money changes hands:

• Financials: request bank or payment processor statements, not just dashboard screenshots. Screenshots can be edited or cherry-picked.
• Customer list: verify real customers exist by reaching out (with permission) to a handful directly, or ask the seller to send a short survey on your behalf.
• Codebase: get repository access, check commit history for a single point of failure, and confirm there is no undisclosed technical debt (unpatched security issues, expired API keys tied to the founder's personal accounts, or a dependency on a service being shut down).
• Legal ownership: confirm the seller actually owns the domain, trademarks if any, and all code, including any contractor-written portions that might carry separate licensing terms.
• Contracts and obligations: check for any outstanding customer contracts, refund obligations, or reseller agreements that transfer to you.
• Support load: ask for average tickets per week and current response time. A backlog you inherit on day one is a hidden cost.

Do not skip this checklist because a deal feels time-pressured. A seller pushing hard for a fast close with limited access to real data is one of the more reliable warning signs in small acquisitions.

How to think about valuation

Micro SaaS deals commonly trade in a rough multiple-of-annual-revenue range, but the multiple should move based on the risk factors above, not just the topline number.

A product with strong metrics on every row can justify a higher multiple. A product with green revenue but red flags on churn, concentration, or founder dependency should trade lower, even if the seller's initial ask does not reflect that.

Negotiating the deal

A few practices that consistently lead to fairer outcomes on both sides:

• Anchor on verified numbers, not the seller's marketing pitch. Negotiate off the bank statements and churn data you confirmed, not the highlight reel in the listing.
• Structure part of the payment as an earnout. Paying a portion upfront and the rest over 3 to 12 months tied to retained revenue protects you if the business underperforms right after the handoff, and it signals the seller believes in what they are selling.
• Ask for a transition period. A few weeks of the founder staying available for support and knowledge transfer reduces the risk of the "founder dependency" problem above turning into a real crisis.
• Put it in writing. Even a simple asset purchase agreement covering what is transferred, payment terms, and post-sale support expectations prevents disputes later. Use a lawyer for anything above a few thousand dollars.

Common mistakes buyers make

• Falling for revenue without checking churn. A high MRR with high churn is a treadmill, not an asset.
• Skipping the codebase review. You cannot price technical debt you have not seen.
• Underestimating founder dependency. The seller's charm and support responsiveness do not transfer with the sale.
• Overpaying for growth that was paid-acquisition-driven. If growth came from ad spend the new owner has to keep funding, the growth rate alone tells you little about organic durability.
• Rushing the close because of seller pressure. Legitimate sellers with clean businesses can usually accommodate a reasonable diligence timeline.

After the acquisition: the first 90 days

Buying the product is the easy part. Keeping customers through a handoff is where deals succeed or quietly fail.

• Communicate the transition early and honestly, ideally with the previous founder introducing you rather than a surprise email from an unfamiliar name.
• Do not change pricing, branding, or core features in the first month. Stability during the handoff matters more than any quick win you are tempted to ship.
• Watch churn weekly, not monthly, for the first quarter. Early warning signs of a bad transition show up fast.
• Keep the support response time consistent with what customers were used to. A slower response time post-acquisition is one of the most common triggers for early churn.

Frequently asked questions

How much revenue do I need to consider buying a micro SaaS?

There is no minimum. Deals exist from a few hundred dollars a month up to tens of thousands. Smaller deals carry lower financial risk but often more founder-dependency risk, since tiny products are frequently run entirely by one person.

What multiple should I expect to pay?

Roughly 2x to 4x annual revenue is common for healthy micro SaaS businesses, but the right multiple depends heavily on churn, concentration, and founder dependency, not just the topline number.

Should I use a broker?

For larger deals, a broker who specializes in small SaaS transactions can add legitimacy and handle structuring. For smaller deals, many buyers negotiate directly with the seller and use a lawyer only for the final agreement.

What is the biggest risk in a micro SaaS acquisition?

Founder dependency. A product that looks automated on paper but actually runs on one person's daily manual effort can fall apart within weeks of a handoff if that is not addressed in the deal structure.

Can I finance a micro SaaS acquisition?

Some buyers use seller financing (paying part of the price over time from the business's own cash flow) or earnouts tied to retained revenue. Traditional bank financing is less common at this deal size but not unheard of for larger acquisitions.

The honest summary

A good micro SaaS acquisition is not the one with the biggest revenue number. It is the one where churn is low, the customer base is not concentrated in two accounts, the codebase does not require a full rewrite, and the founder is not secretly the entire product. Verify all four before you negotiate price, structure part of the payment as an earnout when you can, and protect the first 90 days after close more carefully than you protected the deal itself.

If you end up building or buying something in the micro SaaS space, submit it to makers.page for a free profile and a shot at an honest product review.

Related reading:

• How to get your first 100 users without a marketing budget
• Why dofollow backlinks still matter for indie startups