ARR: annual recurring revenue, what it shows, and the pitfalls of treating it like cash

Announcing that the company has crossed a million ARR sounds much better than saying that it makes eighty-three thousand a month. It's the same deal described two ways, and the second number is the operational truth while the first is the stage version. The problem is not using ARR, it is confusing the stage version with the bank balance, and this confusion brings down more startups than lack of market.

ARR, annual recurring revenue, is probably the most cited and least understood metric in the SaaS vocabulary. It appears in pitch decks, in round headlines and in board conversations, almost always rounded up and almost always treated as if it were guaranteed money. Before using it, it is worth understanding exactly what it is and, above all, what it promises without being able to deliver.

What is ARR and how does it relate to MRR

ARR is annual recurring revenue: the predictable amount the company would receive in twelve months if its current customer base remained intact. It is not an independent metric from MRR, it is the same number seen on a different scale. Annual recurring revenue is nothing more than monthly recurring revenue multiplied by twelve, projected for a one-year horizon.

This direct relationship has a consequence that many people forget: ARR and MRR carry exactly the same information. If you know one, you know the other. There is no insight in ARR that is not equally available in MRR, because one is just the other in a broader lens. The choice between them is a choice of communication and horizon, not of substance.

Therefore, everything that applies to MRR applies to ARR. The same rules about what counts as recurring apply: implementation fee does not apply, one-off project does not apply, one-off charges do not apply. The same four movements govern the evolution of the number: what new customers enter, what grows through expansion, what shrinks through contraction and what is lost through cancellation. Anyone who doesn't have a clean MRR doesn't have a clean ARR, because the defect in one can spread completely to the other. I detail the breakdown of these movements in the article about MRR and monthly recurring revenue.

When it makes sense to use ARR instead of MRR

If both carry the same information, the practical question is which one to use in each situation. The answer depends on your business's sales cycle and the conversation you're having.

ARR fits best when contracts are long and the sales cycle is annual. In SaaS that sells to large companies, with contracts of twelve months or more and few high-ticket customers, reasoning on a monthly basis is artificial. Nobody renegotiates monthly, nobody cancels in the middle of the quarter, the natural unit of planning is the year. In this world, talking about ARR reflects the real pace at which money moves and contracts are renewed.

ARR is also the lingua franca of boards and investors. Conversations about fundraising, company valuation and long-term goals take place on an annual scale, because the multiple that defines valuation focuses on annual revenue. When it comes to twelve to twenty-four month strategy, ARR better communicates the size and trajectory of the business than a monthly number that always seems too small for the ambition.

MRR, on the other hand, is the instrument of daily operation. Anyone who sells monthly plans, has a low ticket and high volume of customers, or operates a product where people come and go frequently, needs monthly granularity. Important changes happen too quickly to wait for the annual frame to reveal them. For tracking week-to-week health, adjusting pricing, reacting to a cancellation spike, or measuring the effect of a product change, MRR is more honest because it's more immediate.

The rule I use is simple: operate in MRR, communicate in ARR when the public and the horizon ask for it. The short number governs the decisions of the day. The long number tells the story to those looking from afar. The two coexist without conflict, as long as no one forgets that they are the same thing on different scales.

The trap of treating ARR like cash

Here lies the most expensive mistake, and it is almost universal among founders who have not yet taken a fall. ARR is not money in the bank. It's a projection of what would happen in a year if nothing changed, and in SaaS things change all the time.

A customer who signs an annual contract for sixty thousand reais adds sixty thousand to the ARR at the time of signing. But what goes into the cash register depends entirely on how he pays. If you paid everything in advance, the money is there today, but it represents a service that you still need to deliver over the next twelve months, and in accounting a large part of it is an obligation, not a profit. If paid monthly, the cashier receives one-twelfth per month, and the other eleven-twelfths depends on the customer continuing to pay.

The confusion happens when the founder looks at the ARR, sees a big number and starts spending as if it were already available. It contracts based on projected revenue, assumes fixed costs backed by an annualization that has not yet taken place, and discovers too late that the distance between recognized revenue and effective cash flow is where companies fail. The ARR describes the recurring basis. Cash flow describes your ability to pay your bills. They are different dimensions, and treating them as synonymous is like confusing the card limit with the account balance.

The discipline is to always keep the two readings separate. ARR answers “how big is my recurring base”. The cashier responds "how much money do I have to spend this month". Every investment decision needs to respect the second, even when the first seems to invite bigger bets.

The trap of ignoring churn in the projection

The second trap is more subtle and perhaps more dangerous, because it disguises itself as rigor. The ARR definition carries a built-in and often forgotten hypothesis: the phrase "if the base remained intact". It never remains intact. Every month some customers cancel, others reduce, and today's ARR is not the ARR you will have a year from now, even if you don't sell anything new.

Treating ARR as a stable value that only goes up ignores that there is a continuous leak underneath. A company reporting a rising ARR may actually be losing base, and only masking the loss with new sales that run ahead of the cancellation. The aggregate number goes up while the underlying health worsens, because the acquisition is plugging a hole that no one measured.

The ARR only becomes an honest snapshot when you read it along with the rate at which the base evaporates. The right question is not "what is my ARR", it is "what is my ARR and how much of it do I lose per year without doing anything". Without the second data, the first is an optimistic promise. This is exactly why churn and net retention are not metrics separate from revenue, they are the correction of reality that prevents ARR from becoming fiction. I explored this point in the article about churn in SaaS.

The practical consequence for those who project growth is direct. Adding all expected sales to the current ARR, without discounting what the base will lose along the way, produces a goal that looks achievable on the slide and falls apart during execution. The realistic projection starts from today's ARR, subtracts the expected evaporation from the base and only then adds the expected acquisition. The difference between these two accounts is the difference between a company that hits its target and one that spends the entire year wondering why the number isn't enough.

ARR as a communication metric, not a management one

Reducing everything to a practical phrase: ARR is an excellent communication tool and a terrible daily management tool. It compresses the recurring health of the business into a single annual scale number, perfect for aligning board, investors and strategic goals. But the same compression that makes it communicable hides the granularity that the operation needs to react in time.

Use ARR to tell the story and scale ambition. Go back to MRR and its four moves to understand what's really going on and where to move. And never, under any circumstances, treat either as a bank balance, because recurring revenue and cash are distant relatives that many people present as twins.