SaaS Businesses: Deep Dive
A software as a service (SaaS) business sells ongoing access to a piece of software, billed monthly or annually. It's the model that commands the highest valuation multiples of anything on this list, for a specific reason: subscription revenue is predictable in a way that ad income, affiliate commissions and one-off product sales simply aren't. That predictability is real, but it comes with a real requirement most first-time buyers underweight, which is technical fluency somewhere in the operation.
What running one actually looks like day to day
Even a small SaaS product you didn't build requires handling customer support tickets, prioritizing and shipping bug fixes or small improvements (or managing a developer who does), and watching churn, the rate at which customers cancel, closely. Churn is the single number that most determines whether the business grows or shrinks, more than new sign-ups do in many small SaaS products. You're also watching monthly recurring revenue (MRR) trends, failed payment recovery (dunning), and usually running some amount of ongoing marketing to keep new sign-ups flowing in.
Typical profit margins
| Line item | Typical range | What drives it |
|---|---|---|
| Gross margin | 70% to 90% | Hosting and payment processing costs, which barely grow per additional customer once the product is built. Benchmarkit's 2025 survey puts the median SaaS gross margin at 77%, with mature companies clearing 75% to 85%-plus[1]. |
| Net margin (profitable, bootstrapped) | 15% to 30% | After support, product development, and marketing, before reinvestment. A 15% to 25% EBITDA margin is rated "good" and 25%-plus "excellent" for a SaaS company on Founderpath's benchmarking scale[2]. |
| Net margin (venture-backed, growth stage) | Often negative | Deliberately spending ahead of revenue to capture market share, a different objective than a solo buyer's |
| Monthly churn (healthy small-business SaaS) | 3% to 7% | Small-business-focused SaaS runs structurally higher churn than enterprise software. Below 3% monthly is exceptional for a sub-$1 million annual recurring revenue (ARR) product[3]. |
| Typical sale multiple | 2 to 3x ARR (sub-$1 million ARR) | Below $1 million ARR, a buyer is largely purchasing a job rather than a scalable asset. FE International's data puts these deals at 2x to 3x ARR, or 2.5x to 4x seller's discretionary earnings (SDE)[4]. |
The "Rule of 40," a common SaaS health benchmark popularized by Bessemer Venture Partners, says growth rate plus profit margin should add up to 40 or more[5]. A SaaS product growing at 10% a year needs roughly a 30% margin to clear that bar. A shrinking product needs an even higher margin to compensate, which is exactly the kind of business a buyer should be able to spot from the numbers before ever talking to the seller.
Pros
- Recurring, predictable revenue that's visible weeks or months in advance, unlike ad-based or transactional income.
- Very high gross margins because the marginal cost of serving one more customer is close to zero once the product exists.
- Sticky customer relationships. Switching software is genuinely annoying for a customer, which naturally suppresses churn relative to, say, an e-commerce purchase.
- Commands the highest valuation multiples of any model here, which matters just as much on the way out as on the way in.
Cons
- Requires ongoing technical maintenance. Software breaks, security patches are needed, and hosting infrastructure needs monitoring, none of which is optional.
- Churn compounds against you. A product losing 5% of revenue a month needs to replace that just to stand still, before it can grow at all.
- Customer support expectations are high and immediate. Users expect a working product now, not a next-business-day response.
- A non-technical buyer without a reliable technical hire or contractor in place is taking on real operational risk, since a single serious bug or outage can trigger a wave of cancellations.
Skills and time required
SaaS is arguably the hardest business model on this list to run without prior experience, and it's not a good first acquisition for a buyer who has never worked in or around software. Unlike a content site or a store, the product itself is the code: any bug, security gap, or infrastructure problem hits the thing customers are paying for directly, not just a marketing channel around it[6]. That risk gets priced in whether you plan for it or not. Diligence teams routinely discount a SaaS business a full turn of EBITDA, from around 6.5x down to 5.5x, when they find a legacy codebase with no remediation plan, meaning $1 million of unaddressed technical debt can cost a $2 million EBITDA business roughly $2 million in sale price[7]. Churn is similarly unforgiving of inexperience: it compounds faster than the simple math suggests, a steady 5% monthly churn rate doesn't annualize to 60%, it compounds to roughly 46%, so a buyer who doesn't catch a churn problem early can watch it snowball across a full year before the damage shows up clearly in revenue[8].
You don't need to be able to write the code yourself, but you need enough technical fluency to evaluate a developer's work, understand what a bug report actually means, and make informed product decisions, or a trusted technical hire or contractor who can. Customer support and basic product management (deciding what to build next based on what customers actually ask for) are constant, ongoing demands. Some comfort reading MRR, churn and cohort retention data is essential, since these numbers tell you about the health of the business faster than revenue alone does. A first-time buyer who already has SaaS operating, product, or engineering experience can offset a lot of this. A first-time buyer with none of that is stacking two learning curves at once, running a business for the first time and learning software operations for the first time, and should treat this model as one to grow into rather than start with.
What to check before buying one
Ask for a cohort retention chart, not just a churn percentage. A stated "3% monthly churn" can hide a business where new cohorts churn fast and only a legacy cohort is stable, a very different risk profile than uniform low churn across all customers. Confirm who currently handles the technical side (the seller, a contractor, an agency) and whether that person or relationship transfers with the sale. Check for customer concentration. A B2B SaaS product where one customer is 20% of revenue carries real key-account risk that a simple MRR chart won't show.
Real examples: Basecamp has run as a self-funded, subscription-billed project management tool for years without outside investors, prioritizing profitability over growth-at-all-costs. Ahrefs built a subscription SEO-tools business the same way, growing through organic marketing and product-led growth rather than a large outbound sales team, while staying profitable and bootstrapped.
Sources
- [1]Benchmarkit: 2025 SaaS performance metrics, gross margin benchmarks ↩
- [2]Founderpath: EBITDA margin benchmarks for SaaS companies ↩
- [3]Genesys Growth: B2B SaaS churn rate statistics ↩
- [4]FE International: SaaS valuation multiples ↩
- [5]Bessemer Venture Partners: the Rule of X (Rule of 40 background) ↩
- [6]Quiet Light: SaaS technical due diligence for non-technical buyers ↩
- [7]David Jacobs Business Broker: how to sell legacy-code SaaS with technical debt ↩
- [8]Churnkey: what's a normal churn rate in SaaS, why monthly churn compounds ↩
Next: newsletters and communities monetize an audience directly, the leanest model here but the most personality-dependent.