SaaS

What Is a SaaS Business Model? A Plain-English Guide for Founders

By James KillickJuly 15, 2026

TL;DR: A SaaS business model means you host software in the cloud and customers pay a recurring fee to use it, instead of buying a licence once. It runs on multi-tenant architecture to keep costs low, and it lives or dies on metrics like MRR, churn, and LTV to CAC. Get the pricing model and the architecture right early, because retention matters more than new signups.

A SaaS business model is simple once you strip the jargon out: you build the software once, host it in the cloud, and customers pay a recurring fee to use it over the internet. No one buys a licence and installs it on their own server. You keep the product running, and the customer keeps paying as long as it earns its fee. If you are turning a proven program or a piece of expertise into software, this is the model you are building toward, and getting the multi-tenant basics right from day one saves you a rebuild later.

What does a SaaS business model actually mean?

In a SaaS business model, one provider hosts an application centrally and every customer connects to it over the internet. Nobody installs anything on their own machine. The provider handles the servers, the security, and the updates for every customer at once.

This flips the old software deal on its head. Traditional software was a one-off sale: pay once, own a licence, install it yourself. SaaS is an ongoing exchange. The customer pays every month or every year, and the product has to keep earning that payment. Retention becomes just as important as getting new customers in the door.

How does SaaS work under the hood?

The technical backbone of SaaS is multi-tenant architecture. One instance of the software serves many customers at once, but each customer's data stays separate and locked down, even though everyone shares the same servers underneath. That separation happens in the application and the database, not by spinning up a new copy of the app for every customer.

Here is why that design matters:

  • Shared infrastructure cuts cost. One server setup can support thousands of customers, so running costs per customer drop as you grow.
  • Updates go out once. A new feature or a security fix reaches every customer at the same time. Nobody has to install anything.
  • Access needs only a browser or an app. Customers get in without setting anything up on their end.
  • Security sits with the provider. You manage encryption, access rules, and compliance in one place, not customer by customer.

Get the tenant isolation model sorted before you write any application code. Bolting multi-tenancy onto an app that was not built for it is slow and expensive to fix. The businesses that get this wrong early pay for it for years.

What are the main SaaS pricing models?

SaaS revenue is almost always subscription based, but how you structure that subscription changes your growth, your cash flow, and how customers see the value. Picking the wrong one early is a common early-stage mistake, which is why it is worth validating your SaaS idea before you lock in a model.

The four common models are:

  1. Flat-rate subscription. One price, full access, billed monthly or yearly. Easy to sell and easy for the customer to budget.
  2. Per-seat pricing. Customers pay per user. Revenue grows as their team grows. Common in collaboration and productivity tools.
  3. Usage-based pricing. Customers pay for what they use, measured in transactions, API calls, or data volume. Revenue moves with customer activity, which makes forecasting harder. If you are weighing this up, usage-based pricing in the AI era is worth a read before you commit.
  4. Freemium. A free tier that gets people in the door, with paid plans for the features that matter. Works best when the product spreads on its own or costs little to run per free user.
Pricing modelRevenue predictabilityBest suited for
Flat-rateHighSimple, single-use-case products
Per-seatMedium to highTeam and collaboration tools
Usage-basedLow to mediumAPI products, infrastructure tools
FreemiumLow at firstHigh-volume consumer or small business markets

Most mature SaaS businesses land on a hybrid: a base subscription that covers core access, plus usage charges for the features that get hammered hardest. That balances your need for predictable income against the customer only paying for what they actually use.

Which metrics actually tell you if your SaaS business is healthy?

SaaS runs on its own set of numbers, and they are not the same as general business metrics.

The ones that matter most:

  • Monthly Recurring Revenue (MRR). Total subscription revenue in a month, excluding one-off fees. This is the number to watch every week.
  • Annual Recurring Revenue (ARR). MRR times 12. Used for yearly planning and talking to investors.
  • Churn rate. The percentage of customers or revenue you lose in a period. High churn kills growth even when new signups look strong.
  • Customer Lifetime Value (LTV). Total revenue one customer brings in before they cancel.
  • LTV to CAC ratio. LTV against what it costs to get that customer (Customer Acquisition Cost). A ratio above 3:1 is generally seen as healthy.
MetricWhat it measuresWhy it matters
MRRMonthly subscription revenueShows growth and momentum
ARRYearly subscription revenueUsed for planning and reporting
Churn rateCustomers or revenue lostShows how well you retain people
LTVRevenue per customer over timeSets your long-term unit economics
CACCost to get one customerBenchmarks your marketing and sales spend

Keep one-off fees, like setup or consulting charges, out of MRR and ARR. Mixing them in makes the business look healthier than it is, and it misleads you and any investor reading the numbers.

How do you turn a program or expertise into a SaaS platform?

A lot of founders reading this are not starting from a blank page. They already run a proven program, a service, or a piece of specialist knowledge, and they want to turn it into something that scales without them in every session. That shift from delivering a service to running a platform is exactly what founders and consultants ask us about when they turn a program into a platform.

The path usually looks like this: pull the repeatable parts of what you do into software, keep the judgement calls as a premium tier or a human add-on, and price it so the software carries the weight while you carry the relationships. Consultants and specialists who get this right stop trading hours for dollars and start building something with recurring, compounding revenue. Early growth for these products tends to come from usage and word of mouth rather than big ad spend, which is why it is worth understanding AI-led growth for early-stage SaaS before you plan your first year.

If this is where you are at, our page for founders turning expertise into software covers the questions to answer before you write a line of code, including what to build first and what to leave as a manual process for now.

I have worked with enough founders building subscription products to notice the same pattern every time. They obsess over new signups and ignore churn, because acquisition is visible and exciting, and churn is quiet and easy to explain away. A 5% monthly churn rate means you replace your entire customer base roughly every 20 months. That is not a business, that is a treadmill. The founders who build something that lasts treat retention as a product problem, not a support problem. They ask why people leave and fix the product, not just the ticket.

The second mistake I see just as often is mixing up cash and revenue. A founder closes a big annual deal and drops the whole amount into that month's MRR. The number looks great. Six months later, when that customer churns and nothing replaces it, the drop is brutal. Clean metrics are not paperwork. They are the only way to actually see your business.

*James*

How Devwiz builds SaaS platforms founders can run on

Devwiz has shipped over 200 apps, including platforms for the NSW Government, Briometrix, Vivid, and Huskee. Founders and consultants come to us when they are ready to turn a program, a service, or a piece of expertise into real software, not a prototype that falls over the first time it gets real traffic. Our AI programs work is built around exactly this: taking what you already know how to do and building the platform that runs it at scale.

If you are weighing up a SaaS build, get in touch and we will walk through the architecture, the pricing model, and the metrics you will need to track from week one.

Frequently asked questions

What is a SaaS business model in simple terms?

A SaaS business model delivers software over the internet on a subscription. The provider hosts and maintains the app, and customers pay a recurring fee to use it instead of buying a licence and installing it themselves. The relationship only continues as long as the software keeps earning its fee.

How do SaaS companies make money?

SaaS companies earn recurring revenue through subscriptions, usually structured as flat-rate, per-seat, usage-based, or freemium plans. Most mature SaaS businesses combine a base subscription with usage charges on top for the features that get used the most.

What is multi-tenancy and why does it matter for SaaS?

Multi-tenancy means one software instance serves many customers at once, with each customer's data kept separate. It keeps infrastructure costs down as you add customers, and it means an update or a fix goes out to everyone at the same time, with no manual install needed.

What metrics should a SaaS founder track first?

Monthly Recurring Revenue, churn rate, and the LTV to CAC ratio matter most early on. Keep one-off fees like setup or consulting charges out of MRR, because mixing them in makes the subscription business look healthier than it actually is.

What makes a SaaS business last long term?

Retention is the biggest driver of long-term SaaS success, more than new signups. A product built on solid multi-tenant architecture, with a pricing model customers trust and a fix-the-product approach to churn, builds revenue that compounds instead of leaking away.

About James Killick

10+ years building digital products · 200+ apps shipped since 2015

James is a co-founder of Devwiz and an AI product specialist. Since 2015 he has helped ship 200+ apps for founders, businesses and government, including work for NSW Government, Briometrix and Huskee. He builds AI-first platforms and writes about turning a proven program into software. He also hosts the Up in the AI podcast.

More articles by James · James's personal site · LinkedIn · AI Orchestrators

Tags: SaaS, subscription pricing, MRR, churn, multi-tenant architecture, SaaS metrics

Browse all Devwiz articles·See our case studies