Is it SaaS? Is it ARR?

Here is one of the most common startup arguments since the invention of coffee-fueled board meetings: “We sell software, so we’re SaaS.” Not so fast. And its equally chaotic cousin goes like this: “We made money last month, so let’s multiply it by 12 and call it ARR.” Also not so fast. In the software world, two questions sound similar but do very different jobs: Is this actually a SaaS business? and Does this revenue actually count as ARR?

If you mix those two up, you can end up with messy reporting, confused investors, bad planning, and the kind of spreadsheet that makes a CFO stare into the middle distance. This article breaks down both questions in plain English. We will look at what makes a company truly SaaS, what annual recurring revenue really means, what belongs in the metric, what definitely does not, and why smart operators treat ARR as a useful compass rather than a magical fairy tale.

Why These Two Questions Matter So Much

“SaaS” is a business model label. “ARR” is a revenue metric. They often travel together, but they are not the same thing.

A company can sell software without being a clean SaaS business. For example, it might close large one-time implementation projects, build custom features for every customer, and rely heavily on service hours to make the product work. That may be a solid business, but it is not the same as a scalable, repeatable, shared-product SaaS model.

Likewise, a company can have software revenue without having much true ARR. If customers are paying one-time license fees, short consulting fees, or unpredictable project invoices, that money may be real revenue, but it is not recurring in the sense investors and operators usually mean. That distinction matters because ARR is supposed to describe the durable, repeatable, forward-looking part of the business.

In other words, SaaS answers, “What kind of business are we building?” ARR answers, “How much predictable recurring revenue do we really have?” Put those together correctly, and you have a much clearer picture of scale, efficiency, and long-term value.

What Makes a Company Truly SaaS?

1. The product is delivered as a service, not sold like boxed software wearing a fake mustache

At its core, SaaS means software is delivered to customers on demand, usually through the browser or a hosted application. The vendor runs the infrastructure, maintains the software, handles updates, and delivers the service continuously. Customers use the product without managing servers, patching systems, or buying a giant perpetual license and praying nothing breaks.

That delivery model changes the customer relationship. Instead of “buy once, install once, good luck,” SaaS is ongoing. The provider keeps earning the customer every month or every year through uptime, support, features, and product value.

2. The business is designed for repeatability and shared product value

A true SaaS model is not just hosted software. It is also a business built around a repeatable product, shared customer experience, and scalable operations. That means the company is not reinventing the wheel for every new account. Customers may have different plans, seats, workflows, and integrations, but the company is still selling a core product that can scale across many customers.

This is where a lot of businesses get tripped up. If every customer needs major custom development, ongoing engineering hand-holding, or a unique version of the product, you may have software-enabled services rather than pure SaaS. Again, that can still be profitable. It just behaves differently. Gross margins are often lower, onboarding is heavier, and scaling is harder because growth depends on people and projects, not just product adoption.

3. Pricing usually follows a recurring pattern

Most SaaS businesses charge on a subscription basis, a committed contract basis, or a structured usage model. Monthly seats, annual contracts, recurring platform fees, and committed minimum usage arrangements all fit comfortably here. The key idea is not merely “people pay us.” The key idea is “people keep paying us under a recurring structure because the product keeps delivering value.”

That is why SaaS founders obsess over renewal, expansion, and churn. A good SaaS business does not win the customer once. It wins the customer, keeps the customer, and ideally grows the account over time.

4. SaaS is not just software plus invoices

Some businesses market themselves as SaaS because they have a login screen and a cloud bill. Cute, but incomplete. If the economic engine is mostly professional services, implementation projects, or custom work, then the company may not deserve a full SaaS label. It may be a hybrid model. That is not an insult. It is simply a more accurate description.

Think of it this way: if removing the services team would make the business collapse next Tuesday, the business may not be as product-led or as SaaS-native as the homepage copy suggests.

So, What Is ARR Exactly?

ARR is the recurring revenue baseline you expect over a year

ARR stands for annual recurring revenue. In practical terms, it represents the predictable subscription or contracted recurring revenue you expect to generate over the next 12 months from your current customer base, assuming no dramatic plot twists. It is meant to capture the recurring part of the business, not every dollar that happens to land in the bank.

For many businesses, ARR is calculated by taking MRR and multiplying it by 12. If you have annual contracts, you can also total the annualized value of those subscriptions directly. For multi-year agreements, the clean approach is to normalize the contract to an annual amount instead of stuffing the full contract value into one heroic but misleading number.

What usually belongs in ARR

• Recurring subscription fees
• Annual contracts for software access
• Monthly plans annualized into a 12-month view
• Recurring add-ons and platform modules
• Contracted support or maintenance that is truly recurring
• Committed minimum usage fees when they are contractually predictable
• Multi-year subscription deals normalized to one year

The word doing the heavy lifting here is recurring. Not hopeful. Not maybe. Not “the customer seemed nice.” Recurring.

What does not belong in ARR

• One-time setup fees
• Implementation and onboarding projects
• Consulting and professional services
• Training fees
• Hardware revenue
• Perpetual license revenue
• Variable usage above committed minimums
• Random custom project work

These items may be perfectly valid revenue. They may even be healthy, high-margin, strategically useful revenue. But they are generally not ARR because they are not predictable, contracted, and recurring in the same way as subscription revenue.

ARR vs. Revenue vs. Bookings vs. Cash

This is where otherwise intelligent adults begin fighting over terminology.

ARR is not total revenue

Total revenue includes everything the company earned during a period: subscriptions, services, training, hardware, setup fees, and anything else recognized as revenue. ARR is narrower. It isolates the recurring, repeatable engine of the business.

A company might report $5 million in annual revenue but only $3 million in ARR because the rest came from implementation projects and non-recurring work. Both numbers matter. They just answer different questions.

ARR is not bookings

Bookings reflect the value of contracted business signed during a period. That can include one-time fees and multi-year deals. ARR is not about the full size of the signed contract; it is about the annual recurring portion of that contract.

If you sign a three-year, $300,000 software subscription, that is a great contract. But the ARR contribution is generally $100,000, not $300,000. Otherwise, your metric stops being a recurring annual view and starts becoming a drama club production.

ARR is not cash collected

If a customer prepays annually, that is fantastic for cash flow. But cash timing does not change the nature of ARR. A $24,000 prepayment for one year of software is still $24,000 of ARR, not “whatever finance feels like celebrating today.”

Edge Cases That Confuse Almost Everyone

Usage-based pricing

Usage-based and hybrid models have made ARR more interesting. If a customer has a committed minimum spend, that minimum can often count toward ARR because it is predictable and contracted. But pure overage revenue that swings wildly with usage usually should not be counted in full as ARR. Otherwise, a temporary spike can make the business look steadier than it really is.

Professional services attached to the subscription

Usually excluded. If services are one-time, project-based, or tied to an initial rollout, they do not belong in ARR. However, if a support package or managed success retainer is contractually recurring and renews along with the subscription, some companies include it. The important thing is not to be clever. The important thing is to be consistent, documented, and conservative.

Discounts

Permanent or contracted discounts should be reflected in ARR at the actual net amount the customer is paying. Temporary promotions need careful treatment. If the discount disappears halfway through the year, blindly annualizing the discounted month can understate or distort the run rate. The cleanest approach is to use the actual contracted recurring value.

Month-to-month customers

This is one of the big philosophical debates. Many teams annualize monthly subscriptions into ARR for consistency. Others prefer to focus on MRR, especially in early-stage or SMB-heavy businesses. The deciding factor is whether the metric still conveys something stable and useful. If your customer base is extremely short-term or volatile, MRR may tell the story more honestly.

How to Tell If It Is SaaS, ARR, Both, or Neither

It is probably SaaS and ARR if:

• You deliver software as a hosted service
• Customers pay under recurring contracts or subscriptions
• The product is largely shared and repeatable across customers
• Most growth comes from subscriptions, renewals, and expansion
• Non-recurring services are small or clearly separated

It is software, but not clean SaaS, if:

• Every implementation is heavily customized
• Services revenue is large and operationally essential
• Margins behave more like an agency than a software platform
• Customer success requires constant manual intervention to deliver value

It is revenue, but not ARR, if:

• The money came from one-time projects
• It came from hardware or setup fees
• It came from consulting or training
• The revenue is too variable and uncommitted to forecast as recurring

Why Investors and Operators Care So Much About ARR

Investors love ARR because it helps them understand the quality of a software business. Predictable recurring revenue is more valuable than a pile of one-off sales because it supports better forecasting, better efficiency planning, and usually better valuation logic. It also makes it easier to judge the real health of the business beyond vanity headlines.

But no serious operator should look at ARR alone. ARR without retention can be a leaky bucket. ARR without margins can hide an expensive delivery model. ARR without context can flatter a company that is buying growth at unsustainable cost.

That is why the best SaaS teams pair ARR with a broader metrics stack:

Churn and net revenue retention

If customers leave faster than you expect, ARR becomes less durable. If existing customers expand over time, ARR gets stronger and more efficient. Net revenue retention above 100% is a powerful signal because it means your installed base is growing even before you add new customers.

Gross margin

Strong software businesses often have healthy gross margins because software can scale efficiently. If margins are thin because services, support, or manual work are too heavy, the company may need to rethink how “SaaS” the operating model really is.

Rule of 40

For more mature SaaS companies, a popular benchmark combines growth rate and profit margin. If those two numbers add up to 40 or more, that is often considered a healthy balance between growth and efficiency. It is not a law of nature, but it is a useful reality check once the business reaches scale.

Real-World Examples

Example 1: Clean B2B SaaS

A company sells workflow software for legal teams on annual subscriptions. Customers pay $24,000 per year, add seats over time, and renew reliably. Setup is light. Training is optional and minimal. That is classic SaaS, and the subscription value belongs in ARR.

Example 2: Software plus heavy services

A company sells analytics software but charges $80,000 in implementation and custom dashboard work for every $20,000 annual software contract. Customers love the service team more than the product. That is not a fake business, but it is not a clean SaaS profile. Only the recurring software portion counts as ARR.

Example 3: Usage-based API company

A company sells API access with a $50,000 annual minimum commitment plus variable overages. The minimum can reasonably count toward ARR. The overages should be treated more carefully unless they are contractually locked in and highly predictable.

Example 4: Old-school software license model

A company sells on-prem software with a one-time perpetual license fee and optional yearly maintenance. The maintenance revenue may behave like recurring revenue. The perpetual license fee does not. The business may be software, but it is not a pure SaaS business, and not all revenue belongs in ARR.

Final Takeaway: Ask the Two Questions Separately

If you remember only one thing, make it this: being a software company does not automatically make you SaaS, and making money does not automatically create ARR.

A SaaS business is defined by how software is delivered, how customers experience value, how the product scales, and how the business is monetized. ARR is defined by the recurring, contracted, predictable revenue portion of that business. When those two line up, you get a powerful operating model. When they do not, you need honest labels, clean reporting, and fewer heroic assumptions.

The smartest founders and finance teams are not the ones who stretch definitions until the dashboard looks pretty. They are the ones who make the definitions boring, consistent, and credible. Ironically, that is exactly what makes the business look better over time.

500 More Words of Practical Experience on “Is it SaaS? Is it ARR?”

In practice, this topic usually gets real the moment a company starts growing fast enough to need cleaner reporting. At the beginning, founders often use whatever shorthand helps them move quickly. A few subscriptions come in, some services revenue lands, and everyone happily says, “We’re at roughly this much ARR.” Early on, that can be harmless. The trouble starts when the company hires finance leaders, raises outside capital, or begins managing the business by targets. At that point, fuzzy language becomes expensive language.

One common experience is discovering that sales, finance, product, and customer success are all using slightly different definitions. Sales may count the full contract value of a multi-year deal. Finance may only count the annual recurring portion. Customer success may think premium onboarding belongs in recurring revenue because it happens a lot. Product may be experimenting with usage pricing that makes the whole thing harder to normalize. Nobody is acting in bad faith. They are just solving different problems. But unless leadership creates one written ARR policy, the company ends up with four dashboards and five versions of “truth.”

Another practical lesson is that recurring revenue quality matters just as much as recurring revenue quantity. Two companies can both claim $10 million in ARR, yet look completely different under the hood. One may have clean annual contracts, low churn, strong expansion, and a product customers adopt quickly. The other may rely on deep discounts, heavy onboarding labor, and nervous renewals that require heroic quarter-end saves. On paper, the ARR headline matches. In reality, the businesses are miles apart. That is why experienced operators dig into retention, expansion, logo concentration, gross margin, and payback periods instead of admiring the top-line number like it is a trophy in a glass case.

There is also a very human side to this conversation. Teams like metrics that reward momentum. Founders want the company story to sound ambitious. Boards want a crisp narrative. That creates temptation to stretch definitions at the edges. Maybe the implementation project is “strategic recurring enablement.” Maybe the custom support package is “platform success revenue.” Maybe last month’s unusually strong usage bill should absolutely be annualized because, who knows, maybe lightning will keep striking. This is where discipline matters. Conservative ARR definitions do not make the business weaker. They make it more believable. And believable numbers travel better with investors, acquirers, lenders, and future employees.

Many operators also learn that the SaaS label itself can create blind spots. A company may call itself SaaS for years while quietly operating like a services-heavy hybrid. Then growth stalls, margins disappoint, and leaders finally realize the product is not yet doing enough of the work. That recognition can be uncomfortable, but it is useful. Once a team sees the gap clearly, it can redesign onboarding, standardize implementation, reduce custom work, package support differently, and move the model closer to true software scalability.

The best practical advice is simple: define SaaS honestly, define ARR conservatively, and revisit both definitions whenever pricing or packaging changes. If you launch usage-based plans, write down what counts. If you add managed services, decide where they live. If you start bundling training into enterprise deals, document the rule. Companies do not get into trouble because metrics exist. They get into trouble because metrics drift while everyone is busy celebrating growth. Clarity may feel less exciting than hype, but clarity is what lets a business compound.

SEO Tags