The SaaS Business Model: Rule of 40, Metrics, Pricing, and How SaaS Makes Money

Key Takeaways

- SaaS makes money from customers who stay, not customers who buy once. The whole model bends toward retention, because keeping a customer costs far less than winning one. Every metric, every pricing decision, and every product choice points back to that one fact. Founders who grasp it early build differently, and the ones who treat SaaS like a one-time sale usually struggle. Many work with a dedicated saas application development services partner precisely to get the retention mechanics right from the start.

- The Rule of 40 is the fastest sanity check on a SaaS business. Growth rate plus profit margin should total at least 40 percent. It stops you from chasing growth at any cost or hoarding margin while the business stalls.

- A handful of metrics tell the whole story. Recurring revenue, churn, customer acquisition cost, lifetime value, and the ratio between the last two. Master those five and you can read almost any SaaS company's health in minutes.

- B2B SaaS carries requirements consumer SaaS does not. Single sign-on, permissions, audit trails, admin controls. These add cost and time, but you cannot sell to businesses without them.

How Do SaaS Companies Make Money?

SaaS companies make money through recurring subscriptions. A customer pays a smaller amount on a repeating schedule, monthly or annual, for as long as they keep using the product, instead of handing over one large payment at the moment of purchase. That single change in how the money arrives reshapes the entire business.

Here is the shape of it. A SaaS company spends heavily upfront to build the product, long before it earns much. Then, if the product is good and customers stay, the subscription revenue accumulates month after month and eventually overtakes the build cost. The longer a customer stays, the more valuable they become, because the cost of keeping them is far lower than the cost of acquiring them in the first place.

That one fact, that the profit lives in retention rather than in the first sale, explains almost everything about how SaaS companies behave and why they are run so differently from one-time-purchase software businesses. It is why they obsess over churn. It is why onboarding gets so much attention. It is why the product keeps getting better after launch instead of being declared finished. The model only works if customers stay, so the whole operation, product, marketing, and support alike, bends toward keeping them.

The economics are also why SaaS attracts so much investment. Once the product exists, serving one more customer costs very little. Revenue can grow far faster than costs, and a well-run SaaS company reaches a point where each new customer is almost pure margin. That is the prize every SaaS founder is chasing, and understanding it is the starting point for everything else in this article.

What Is the Rule of 40 in SaaS?

The Rule of 40 is the quickest single check on whether a SaaS business is healthy. It says the company's growth rate plus its profit margin should add up to at least 40 percent. That is the whole rule, and its usefulness comes from how it balances two things that usually pull against each other.

Growth and profitability trade off. A company can grow fast by spending heavily, which hurts margin. Or it can protect margin by spending little, which slows growth. The Rule of 40 refuses to favor either one blindly. It says: whatever mix you choose, the two numbers together should clear 40.

The power of the rule is that it lets very different companies be judged on one scale. A young company burning money to grow fast and a mature company growing slowly but printing profit can both be healthy, and the Rule of 40 captures both. The company that fails is the one doing neither: growing slowly and barely profitable, stuck in the middle with no clear path out in either direction. That is the danger zone, and the rule flags it instantly.

I find it useful even for early-stage products that are nowhere near 40, because it forces the right conversation. If you are not going to be profitable yet, you had better be growing fast enough to justify it. If you are not growing fast, you had better be moving toward profit. Drifting on both is the failure pattern the rule exists to catch.

What Are SaaS Metrics?

SaaS metrics are the numbers that measure the health of a subscription business. There are dozens, but five carry most of the weight. Master these and you can read almost any SaaS company in minutes.

The relationships between these matter more than any single number. Recurring revenue tells you the size and direction of the business. Churn tells you whether the bucket leaks. CAC tells you what growth costs. LTV tells you what a customer is worth. And the LTV-to-CAC ratio ties it together: if a customer is worth more than three times what it costs to win them, the acquisition engine is healthy. If the ratio drops below one, the company loses money on every customer it acquires, which is a fast road to failure no matter how impressive the growth chart looks, because faster growth at a negative unit economic just burns cash quicker.

One more metric deserves a mention, because it separates good SaaS businesses from great ones: net revenue retention. This measures whether your existing customers spend more over time, through upgrades and expanded usage, even after accounting for the ones who leave. A net revenue retention above 100 percent means the business would grow from its existing customers alone, before signing a single new one. That is the quiet engine behind the most successful SaaS companies.

What Is a SaaS Pricing Model?

A SaaS pricing model is how the product charges its subscribers, and it is one of the most consequential decisions a SaaS company makes. It is not just a number on a page. It shapes who buys, how revenue grows, and even how the product has to be built.

Most real products combine these. A common pattern is tiered packages with a per-seat element inside each tier, plus usage limits that nudge heavy users to upgrade. The pricing model has to match how the product delivers value: if value scales with the number of people using it, per-seat fits; if value scales with volume processed, usage-based fits.

The critical point that founders miss is that pricing has to be designed into the product, not bolted on later. A usage-based model needs accurate metering built in from early on. A tiered model needs the ability to enforce feature limits per plan. Teams that decide pricing in the final weeks before launch discover that the model they want requires plumbing the product was never built for. Pricing belongs in the earliest design conversations, right next to the features.

What Is SaaS Product Management?

SaaS product management is the discipline of deciding what the product should do and in what order. A SaaS product manager owns the roadmap, weighs customer needs against business goals, and uses data on how the product is actually used to prioritize. It is a distinct job from project management, which is mine: product management decides what to build and why, while project management makes sure it actually gets built well and on time.

What makes SaaS product management different from managing a one-time software product is the feedback loop. Because the product is live and instrumented, the product manager can see exactly how customers use it, which features get adopted, which get ignored, and where people get stuck and churn. That data drives the roadmap. A SaaS product manager is measured by whether the product drives adoption, retention, and revenue, not by whether it matched a specification written a year ago.

This is why the best SaaS product managers spend so much time looking at the metrics from the previous section. Churn is not just a finance number to them. It is a signal pointing at a specific problem in the product, and their job is to find it and fix it before it costs more customers.

What Is SaaS Marketing?

SaaS marketing is the work of attracting, converting, and keeping subscribers. It shares tools with other marketing, but its goal is different. A traditional sale ends at purchase. A SaaS subscription only becomes profitable months or years in, so SaaS marketing weights retention and expansion as heavily as it weights winning new customers.

That difference shows up everywhere. Free trials and freemium tiers let customers experience value before paying, which fits a model where the relationship matters more than the first transaction. Product-led growth, where the product itself drives adoption through its own use, has become a dominant strategy precisely because it lowers acquisition cost and improves retention at the same time. And onboarding, often considered a product concern, is really a marketing one too, because a customer who never reaches value will churn no matter how good the sales pitch was.

The metrics tie back in here as well. SaaS marketing lives and dies on CAC and the LTV-to-CAC ratio. A marketing channel that wins customers who churn quickly is worse than no channel at all, because it costs money to acquire customers who never pay back their acquisition cost. Good SaaS marketing optimizes for customers who stay, not just customers who sign up.

What B2B SaaS Development Actually Involves

Most of the SaaS work my team does is B2B, software sold to other businesses rather than to consumers, and b2b saas product development carries requirements that consumer products often skip entirely because individuals never ask for them. These are not optional polish. They are the price of admission for selling to companies.

B2b saas software needs single sign-on, so employees can log in with their company credentials. It needs role-based permissions, because a company has administrators, managers, and regular users who should see different things. It needs audit trails, because businesses have to know who did what and when. It needs admin controls, so a customer's own IT team can manage their users. And it needs integrations with the other business systems the customer already runs.

These enterprise features explain why b2b saas solutions cost more and take longer than consumer apps with similar surface functionality. Enterprise software saas and enterprise saas solutions add even more: heavier compliance, deeper security review, and procurement processes that can take months. A founder building b2b saas software needs to budget for this enterprise layer from the start, because retrofitting single sign-on and granular permissions into a product that was not designed for them is painful and expensive.

The upside is that B2B customers, once won, tend to stay far longer than consumers and pay far more. The churn is lower and the contracts are larger. The enterprise requirements are the cost of reaching that more durable, more valuable kind of customer.

Why Churn Is the Number That Decides Everything

If I could make a SaaS founder watch only one metric, it would be churn. Not because the others do not matter, but because churn quietly determines whether any of the others can save you. A business with high churn is running up a down escalator, and most fail not from a lack of growth but from an inability to keep what they win.

Here is the math that makes churn so decisive. Imagine two SaaS companies that each add 100 customers a month. The first loses 2 percent of its customers monthly. The second loses 8 percent. In the early months they look similar. But over a couple of years, the first company's customer base climbs steadily while the second's flattens out, because at 8 percent monthly churn the losses eventually match the additions and growth stops entirely, no matter how hard the company sells. The only difference between thriving and stalling was the churn rate.

This is why I tell founders that fixing churn beats accelerating acquisition almost every time. Spending more to acquire customers who leave quickly just pours water faster into a leaking bucket. Find why customers leave, fix that, and every other growth effort suddenly works better because the customers you win actually stay. Churn is not just a finance metric. It is a diagnosis of whether the product is genuinely delivering value, and it points straight at the problems worth solving.

For B2B SaaS specifically, churn should be low, under 5 percent annually in a healthy business, because business customers do not switch tools casually once a product is embedded in how they work. If a B2B SaaS is churning hard, it usually means the product never became essential to the customer's daily work, and that is a product problem no marketing budget can fix.

The Psychology Behind SaaS Pricing

Pricing is part math and part psychology, and the psychology is where founders most often leave money on the table. Beyond the mechanical models covered earlier, a few principles shape how subscribers actually respond to price.

Subscribers anchor on the tier above and below the one they pick. This is why three tiers usually outperform one or two. The middle tier looks reasonable next to a premium one, and the premium tier makes the middle feel like a sensible choice rather than the top of the range. A single flat price gives the customer nothing to compare against, which often means they undervalue what they are buying.

Annual billing changes behavior as well as cash flow. Customers who pay annually churn less, partly because they have committed and partly because the renewal decision comes up once a year instead of twelve times. Offering a discount for annual payment is not just a cash-flow play. It is a retention strategy disguised as a discount, and it usually pays for itself in lower churn.

And the worst pricing mistake is pricing on cost rather than value. A SaaS product that saves a business many hours a week or wins it new revenue is worth a fraction of that value, not a markup on what it cost to build. Founders who price by adding a margin to their development cost almost always underprice, because the value to the customer has little to do with what the software cost to make. Pricing on value, not cost, is one of the most consequential decisions a SaaS company makes, and one of the most commonly botched.

A Real B2B SaaS Build: SmartSkip

SmartSkip, a B2B SaaS platform

Type: B2B SaaS | Milestone: over 2,000 paying users in year one

SmartSkip is a B2B SaaS product Clockwise Software built that reached over 2,000 paying users in its first year. That number is the one I want to focus on, because it illustrates the metrics from earlier in this article in a real setting.

Two thousand paying users in year one is a strong start, and it is a number plenty of SaaS products never reach, but the number that determined whether SmartSkip was a healthy business was not the user count at all. It was whether those users stayed. A B2B SaaS that signs 2,000 users and keeps them is on a very different trajectory from one that signs 2,000 and loses a third of them each year. The recurring revenue, the churn, and the lifetime value are what turn a user count into a business.

The build itself carried the standard B2B requirements: the permissions, the admin controls, the reliability that business users expect because they are running real work through the product. Those requirements are why B2B SaaS development takes the effort it does. They are also why, when the product worked, the customers stuck around. Business customers do not switch tools casually once the tool is embedded in how they work, because switching means retraining staff and migrating data, which is exactly the durability that makes the B2B SaaS model attractive in the first place.

What Is SaaS Development, and What Does Building One Involve?

Stepping back to the foundation: what is saas development? It is the work of designing and building subscription, multi-tenant software. What is saas software, in turn, is any software delivered this way, hosted by the vendor and accessed over the internet by subscription. Saas app development covers the full arc of creating one, and developing saas applications well takes a specific discipline that differs from ordinary software work in three ways.

First, multi-tenancy. One running application serves many customers with their data isolated, and this architecture decision shapes everything downstream. Second, billing is a core subsystem, not an afterthought, because the whole business runs on subscriptions. Third, the work does not stop at launch, because a SaaS product is never finished. It evolves for as long as it has customers.

People ask about the saas application development framework and the saas software development tools that go into this. The honest answer is that the tools matter less than the structure. A solid build uses well-understood, conventional technologies arranged into a clean architecture, rather than chasing whatever is fashionable. The saas application development service that delivers a lasting product is the one that gets the structure right, then picks proven tools to build it, in that order.

How to Hire a SaaS Developer or Development Company

When founders decide to build, the next question is how to staff it. There are really two paths: hire individual developers, or engage a saas software development company that brings a full team. For most SaaS products, the second path fits better, and here is why.

A SaaS product needs more than a saas app developer writing code. It needs design, frontend and backend engineering, QA, and project management working together. When you hire a saas developer individually, you are responsible for assembling and coordinating all of those roles yourself. When you engage one of the established software development saas companies, that coordination is handled, and the team has built products like yours before.

The cost gap between European and US software development companies is large, often two to three times for comparable work, which is why so much SaaS gets built through nearshore and offshore teams. The quality gap is far narrower than the price gap. What matters more than geography is whether the team has shipped SaaS products before and can show you the technical decisions they made on each one.

If you do choose to hire a saas developer or a team, judge them on the quality of their questions, not the polish of their pitch. A team that probes your domain, challenges your assumptions, and slows you down before speeding you up will serve you better than one that says yes to everything and starts coding immediately.

The Mistakes That Sink SaaS Businesses

Five Mistakes I See SaaS Founders Make

1. Treating the launch as the finish line. Founders budget for the build and forget that a SaaS product is never done. The launch starts the real work. Plan for the ongoing evolution from the beginning, because a product that stops improving ages out of relevance within a couple of years.

2. Ignoring churn until it is a crisis. A leaky bucket cannot be filled by pouring faster. If customers leave as fast as you win them, no amount of marketing saves the business. Watch churn from the first paying customer, and treat every cancellation as a signal pointing at a fixable problem.

3. Deciding pricing too late. Pricing shapes how the product has to be built, especially for usage-based models that need metering. Teams that leave pricing for the final weeks discover the product cannot support the model they want. Decide pricing in the earliest design conversations.

4. Building consumer-grade software and trying to sell it to enterprises. B2b saas software needs single sign-on, permissions, and audit trails. A product built without them cannot be sold to businesses, and adding them later is painful. If your customers are companies, build the enterprise layer from the start.

5. Chasing growth while ignoring the Rule of 40. Growth at any cost feels good until the money runs out. A business that grows fast while bleeding cash, with no path to balance, is fragile. Use the Rule of 40 as a regular check that growth and profitability are not drifting dangerously out of balance.

How SaaS Businesses Grow Through Their Stages

A SaaS business does not stay the same shape as it grows. It passes through stages, and the metrics that matter shift at each one. Knowing which stage you are in keeps you from optimizing the wrong thing.

In the earliest stage, before product-market fit, almost no metric matters except whether a small group of customers genuinely needs the product and keeps using it. Founders who obsess over growth rate here are measuring the wrong thing, because there is nothing yet worth growing. The only question is whether the core value is real.

Once product-market fit arrives, the focus shifts to the acquisition engine. Now CAC and the LTV-to-CAC ratio become central. The business needs to prove it can win customers profitably and repeatably, not just that a few early adopters love it. This is where many SaaS companies stall, because finding one channel that reliably acquires customers below their lifetime value is genuinely hard.

In the scaling stage, with the acquisition engine working, attention turns to retention and expansion. Net revenue retention becomes the headline metric, because growth from existing customers is cheaper and more durable than growth from new ones. The Rule of 40 starts to matter here too, as investors and the founders themselves ask whether the growth is balanced against a path to profit.

The mistake I see is founders importing the metrics of a later stage into an earlier one. A pre-fit product does not need a sophisticated acquisition dashboard. It needs ten customers who would be upset if the product disappeared. Matching the metric to the stage is part of running a SaaS business well, and it saves enormous wasted effort chasing dashboards that do not yet mean anything.

What Makes a Strong SaaS Software Company?

Whether you are choosing a vendor to build your product or evaluating SaaS software companies as products to buy, the same qualities separate the strong from the weak. The good saas software companies share a few traits that are visible if you know where to look.

They retain customers. This sounds obvious, but it is the single most telling signal. A SaaS company whose customers stay for years has built something genuinely useful and reliable. One with high churn is filling a leaky bucket, and no amount of marketing polish hides that for long. When you evaluate SaaS software companies, ask how long their typical customer stays. The answer tells you more than any feature list.

They keep improving the product. Strong SaaS companies ship steady improvements without breaking what already worked. The product you buy this year is better next year, automatically. Weak ones stagnate after launch, and the product slowly ages out of relevance. Software development saas companies that treat launch as the start rather than the finish are the ones that build durable products.

They are honest about fit. The best SaaS companies, and the best vendors who build SaaS, will tell you when their product is not right for you. A company that tries to sell every prospect regardless of fit is optimizing for its own short-term revenue at the expense of the customer relationships that the SaaS model depends on. Honesty about fit is a sign a company understands its own economics, because it knows a badly matched customer will churn and cost more than they ever pay.

The Quiet Engine: Expansion Revenue

There is a part of the SaaS business model that gets far less attention than acquisition but often matters more: expansion revenue. This is the money that comes from existing customers spending more over time, through upgrades to higher tiers, additional seats, or increased usage. It is the quiet engine behind the most successful SaaS companies, and it is worth understanding because it changes how you should think about growth.

Most founders picture growth as a stream of new customers. But a SaaS business with strong expansion revenue grows from two directions at once: new customers coming in, and existing customers growing larger. When the second effect is strong enough, the business can grow even in a month where it signs no new customers at all, simply because its existing base is expanding. That is the meaning of net revenue retention above 100 percent, and it is the single most attractive property a SaaS business can have.

Expansion revenue is also cheaper than acquisition. Selling more to a customer who already trusts you and uses your product costs a fraction of what it costs to win a stranger. The customer is already onboarded, already getting value, already paying. Growing that relationship is the highest-margin growth available to a SaaS company, which is why the best ones design their pricing and product specifically to make expansion natural.

This connects directly to pricing model choice. A per-seat model expands as the customer's team grows. A usage-based model expands as the customer uses more. A purely flat-rate model captures none of this expansion, which is one of its biggest weaknesses. When founders ask me how to think about pricing, I push them toward models that let revenue grow with the customer's success, because that alignment is what turns a good SaaS business into a great one. The customer wins, and you win alongside them, automatically.

How to Hire a SaaS Developer the Right Way

When the time comes to hire saas developer talent or a full team, the process matters as much as the choice. I have watched founders make expensive hiring mistakes that a better process would have caught, so here is how I would approach it.

First, decide whether you need a person or a team. If you have a strong technical lead and just need to fill one gap, you hire a saas software development company developer for that specific skill. If you are building a product from scratch without deep in-house engineering, you need a team, which means engaging one of the saas software companies that builds end to end rather than stitching together individuals.

Second, when you hire saas developer candidates or evaluate a development company, judge them on their questions. A developer or team that immediately starts talking about technology choices, before understanding your business, is solving the wrong problem. The ones worth hiring ask about your customers, your business model, and your constraints first. The technology serves the business, not the other way around.

Third, check the work, not the pitch. Ask any saas software development company to walk you through the technical decisions on a product they built, including a decision they got wrong and what they learned. A team that can talk honestly about a past mistake has real experience. A team with a suspiciously perfect record is either inexperienced or not being straight with you.

The cost question resolves into a few clear bands. European studios run $50 to $99 per hour for senior work. US software development companies run $150 to $300 for comparable output. Individual contractors vary widely by seniority. The right choice depends less on which band is cheapest and more on which gives you a team that has built products like yours and will still be around to evolve it next year.

Reading a SaaS Business in Five Minutes

Putting all of this together, here is the quick assessment I run when someone shows me a SaaS business and asks whether it is healthy. It takes about five minutes and uses only the concepts in this article.

Start with churn, because it gates everything else. If churn is low, the product is genuinely useful and the rest of the analysis is worth doing. If churn is high, nothing else matters until that is fixed, and I say so directly. Then check the LTV-to-CAC ratio: above three means the acquisition engine is healthy, below one means the business loses money on every customer. Then look at net revenue retention to see whether the existing base is growing on its own. Finally, run the Rule of 40 to see whether growth and profit are in balance.

Four numbers, taken in that order, tell you most of what you really need to know. A business with low churn, a strong LTV-to-CAC ratio, net revenue retention above 100 percent, and a Rule of 40 score clearing 40 is in genuinely good shape, almost regardless of what industry it serves or how big it is. A business failing several of them has problems that no pitch deck can hide. The beauty of the SaaS model is that it is measurable. The numbers do not lie, and learning to read them is the difference between guessing and knowing.

How Clockwise Software Builds B2B SaaS

Clockwise Software was founded in 2014 and registered in the UK as Clockwise Software LP in August 2015. We are a distributed product studio of 80-plus people, and we have shipped 200-plus projects since founding, including 25-plus SaaS applications, much of it B2B across logistics, MarTech, marketplaces, and data backup.

As a digital product development agency, we start every SaaS engagement with the business model, not the feature list. Before we design a screen, we want to understand how the product will make money, what the pricing model implies for the architecture, and which metrics will tell the founder whether it is working. That business grounding is why our products tend to hold up: they were built to be a business, not just a piece of software.

Our publicly verifiable record includes a 4.9 out of 5 rating on Clutch across 22 client reviews, a Cost Performance Index under 10 percent, an average engineer tenure of 3.8 years, and an hourly band of $50 to $99 for senior work. Discovery is fixed-price, starting at $12,000, and produces the architecture, the pricing-aware data model, and a backlog with estimates. All of it is documented at clutch.co/profile/clockwise-software.

If you are building a SaaS business and want the model thought through before the build, the pricing, the metrics, the enterprise requirements, get in touch. Thirty minutes, no slides. We will talk through how your product will make money and what that means for how it should be built.

Contact us at clockwise.software or at linkedin.com/company/clockwise-software.

Frequently Asked Questions

How do SaaS companies make money?

Through recurring subscriptions, charged monthly or annually for ongoing access. They invest heavily upfront to build the product, then earn it back over the customer lifetime. Because one application serves many customers, serving an additional one costs little, so revenue can grow much faster than costs. Retention is where the real profit lives.

What is the Rule of 40 in SaaS?

It says a healthy SaaS company's growth rate plus its profit margin should total at least 40 percent. A company growing 30 percent with a 10 percent margin scores 40 and passes. One growing 60 percent while losing 15 percent scores 45 and also passes. It balances growth against profitability without favoring either blindly.

What are SaaS metrics?

The numbers that measure a subscription business's health. The core five are MRR and ARR (recurring revenue), churn (cancellation rate), CAC (cost to acquire a customer), LTV (lifetime value), and the LTV-to-CAC ratio. Together they show whether the business is growing, keeping customers, and acquiring them profitably.

What is a SaaS pricing model?

How a product charges subscribers. The common models are per-seat (by number of users), usage-based (by how much is used), tiered (set packages), and flat-rate (one price). Most products combine tiers with per-seat or usage elements. The pricing model must be designed into the product, not added later.

What is SaaS product management?

The discipline of deciding what a SaaS product should do and in what order, based on customer needs, business goals, and usage data. A SaaS product manager owns the roadmap and is measured by whether the product drives adoption, retention, and revenue, rather than by whether it shipped a fixed specification.

What is SaaS marketing?

The work of attracting, converting, and retaining subscribers. It weights retention and expansion as heavily as acquisition, because a subscription only becomes profitable over time. Content, free trials, product-led growth, and onboarding all sit inside SaaS marketing, because keeping a customer matters as much as winning one.

What is B2B SaaS development?

Building subscription software sold to other businesses rather than consumers. It carries requirements consumer SaaS often skips: single sign-on, role-based permissions, audit trails, admin controls, and integrations with other business systems. These add cost and time but are non-negotiable for selling to companies.

How much does it cost to hire a SaaS developer or development company?

A SaaS developer at a European studio costs $50 to $99 per hour for senior work, and a full MVP runs $75,000 to $140,000. US software development companies typically charge $150 to $300 per hour for equivalent work. Hiring a SaaS software development company rather than individuals gives you a full team, which SaaS needs.

What metrics tell you a SaaS company is healthy?

Churn under 5 percent annually for B2B, an LTV-to-CAC ratio above 3, a Rule of 40 score at or above 40, and net revenue retention above 100 percent. A company hitting these is keeping customers, acquiring them profitably, balancing growth with margin, and growing revenue from its existing base.

Verified Clutch profile at clutch.co/profile/clockwise-software with 22 client reviews. Company updates at linkedin.com/company/clockwise-software. Full SaaS case portfolio at clockwise.software.