Not All Revenue Is Created Equal

Revenue is one of the first numbers management looks at. It is also one of the easiest numbers to misunderstand.

A business can report strong revenue growth while the quality, predictability and economics of that revenue deteriorate underneath it.

A three-year contracted subscription is not economically equivalent to a customer topping up an account each month. An annual subscription paid upfront is not twelve months of revenue on the day the cash arrives. Usage-based revenue can be highly attractive, but it behaves differently from committed recurring revenue.

And revenue growth tells management surprisingly little if the cost of delivering each additional dollar is poorly understood.

Good finance should make those differences visible and that information actionable.

In brief

Management should be able to answer a few basic questions about revenue quickly:

• What has actually been earned?

• What has been invoiced and collected?

• What is contractually committed?

• What is genuinely recurring?

• What depends on customer usage or behaviour?

• What does it cost us to deliver each revenue stream?

• And what does an additional £1 or $1 of revenue actually contribute to the business?

Those questions become increasingly important as companies combine subscriptions, consumption, implementation fees, professional services, minimum commitments, prepaid credits and other forms of monetisation.

ARR is useful. It is not a synonym for revenue.

ARR has become one of the default languages of technology businesses.

That is useful when it describes what it says: annual recurring revenue.

The problem starts when almost every source of revenue finds its way into the ARR number.

Consider three customers currently generating $10,000 a month.

One has signed a three-year contract. Another has a monthly subscription that can be cancelled at short notice. The third buys roughly $10,000 of credits each month but has made no commitment to continue doing so.

All three might currently annualise to $120,000.

They are not the same $120,000.

The first provides significant contractual visibility. The second is recurring, but carries greater near-term churn risk. The third may be excellent revenue, but multiplying recent consumption by twelve does not make it contracted ARR.

That distinction matters because management invests against it.

A company with highly committed recurring revenue can generally make hiring, infrastructure and capital allocation decisions with greater confidence than one producing the same current run-rate from discretionary consumption.

Lumpy billing does not make revenue non-recurring. Lack of recurrence or commitment does.

Investors will usually look through this distinction quickly. Headline ARR matters less than the quality of the revenue underneath it: contract duration, renewal terms, customer concentration, committed versus discretionary usage, churn, expansion and the assumptions used to annualise the base.

The clearer those definitions are internally, the more credible the story becomes externally.

Separate revenue streams before combining them

Economically different revenues should remain visible for long enough to understand how they behave.

Depending on the business, management may want to distinguish between contracted subscriptions, cancellable subscriptions, committed usage, uncommitted usage, overages, prepaid credits, implementation revenue, professional services and other one-off revenue.

The precise categories matter less than the discipline.

If materially different revenue streams are combined too early, management loses information about predictability, retention, customer behaviour and margin.

It also makes forecasting considerably harder.

Cash, billing and revenue are different things

A core finance discipline is separating bookings, billings, cash collections and recognised revenue.

They are related, but they are not interchangeable.

If a customer pays $120,000 upfront for twelve months of service, the company may receive $120,000 of cash immediately. That does not normally mean it has earned $120,000 of revenue immediately.

Where the service is delivered over twelve months, revenue is generally recognised as the service is provided. The unearned balance remains deferred until the associated obligation has been satisfied.

This is more than an accounting technicality.

Without the right treatment, monthly performance can become badly distorted. A business can appear extraordinarily profitable in one period and considerably less profitable in the next even though its underlying economics have barely changed.

Good revenue recognition allows management to compare periods properly.

Usage-based revenue requires different infrastructure

Usage-based businesses create another layer of complexity.

Traditional SaaS benefited from committed contracts, relatively predictable pricing and low marginal delivery costs. AI-native software can look different. Where customer activity drives meaningful compute, model or infrastructure costs, the cost of serving the customer rises with usage.

That makes pricing and finance architecture much more important.

The underlying flow needs to connect:

Customer activity → usage → pricing → billing → collections → revenue recognition → COGS → gross profit → reporting

For a business with hundreds of customers making top-ups or consuming services continuously, finance should not be reconstructing that chain manually at month-end. We explore the broader systems architecture behind this in When Bookkeeping Stops Being Enough →.

The underlying data should show who generated the activity, what they consumed, what they were charged, when the revenue was earned, whether cash was collected and what it cost to deliver the service.

This matters because a contract can look attractive on the top line while being uneconomic at the gross profit level. Historically, software businesses often lost money because they spent heavily on sales and marketing. Increasingly, some businesses can lose money simply by serving the customer.

That is a much harder problem to repair after the contract has been sold.

Modern metering, billing and payments platforms can automate much of this workflow. The important point is that the systems preserve the underlying economics as activity moves through the business.

Build around a common set of dimensions

One of the most important design decisions is creating consistency across systems.

Customer ID. Product. Contract. Revenue stream. Usage type. Potentially geography, infrastructure resource or another relevant operating driver.

These dimensions should follow the transaction from the commercial system into billing, accounting and reporting wherever practical.

That creates traceability.

Instead of finance trying to reconcile one set of customer names in the product database, another in billing and another in the ledger, the systems begin to describe the same economic event in the same language.

That sounds operational. It becomes strategic very quickly.

Revenue attribution is only half the problem

The next question is what it costs to deliver that revenue.

This has become particularly important in businesses where customer activity creates meaningful variable infrastructure costs.

An AI company might incur model inference charges, token costs, GPU or cloud consumption, third-party data costs or other expenditure directly as customers use the product.

Some costs may be traceable directly to a customer or transaction. Others may need to be allocated using a sensible operational driver such as tokens, compute time, API calls or jobs processed.

The objective is not false precision.

It is to get close enough to answer a much more useful question:

If this customer generates another $1 of revenue, approximately how much does it cost us to deliver it?

That is where revenue reporting starts becoming genuinely useful for management.

Gross profit tells you what the revenue is worth

Revenue without COGS can create a misleading picture.

A $100,000 customer generating a 90% gross margin is economically very different from one generating a 30% gross margin.

So are two products producing identical revenue but consuming radically different levels of infrastructure.

Management should therefore be able to move from:

Revenue → COGS → Gross profit → Gross margin

and, where useful, analyse that relationship by customer, product or revenue stream. That analysis should ultimately feed into the monthly management information used to run the business. See What Should Be in Monthly Management Accounts? → for more on this topic.

This is also where unit economics becomes useful.

Gross margin explains the economics of delivery at an aggregate level. Unit economics can take the analysis further by asking what an individual customer, workload, transaction or unit of consumption contributes.

That becomes a foundation for better pricing.

Pricing depends on understanding COGS

If finance cannot attribute direct costs properly, management will struggle to understand pricing properly.

• Should a particular usage level be bundled or charged separately?

• Are volume discounts improving retention while quietly destroying margin?

• Do large customers actually become more attractive as they scale?

• Should contracts include minimum commitments?

• Which products or workloads produce the strongest contribution?

• What price is required to maintain the desired gross margin?

These are commercial decisions, but they depend on good financial architecture.

Weak systems eventually become a pricing problem.

Finance should reconcile three views of the same business

A strong finance setup should allow management to understand revenue from three perspectives.

Financial reporting: What revenue and COGS belong in the accounts this month?

Operational economics: Which customers, products and activities are producing revenue and gross profit?

Forward view: What do current contracts, customer behaviour, usage patterns and commitments imply for future revenue, cash and margin?

Those three views should ultimately reconcile back to the same underlying economic activity.

When they do, finance stops merely reporting what happened and starts explaining how the business makes money. That distinction sits at the heart of the difference between accounting and finance. For more see Accounting Tells You What Happened. Finance Helps You Decide What Happens Next. →

The quality of revenue matters as much as the quantity

A million dollars of contracted subscription revenue is different from a million dollars of uncommitted consumption.

A million dollars invoiced is different from a million dollars collected.

A million dollars collected upfront is different from a million dollars already earned.

And a million dollars of revenue producing $900,000 of gross profit is radically different from the same revenue producing $300,000.

Good finance makes each of those distinctions visible.

Because once management understands not simply how much revenue the business has, but what kind of revenue it has, how reliably it will recur and what each dollar is worth, forecasting, pricing and capital allocation all become considerably better.

FAQs

What is the difference between ARR and revenue?

Revenue is recognised as goods or services are delivered. ARR is an operating metric intended to represent annualised recurring revenue. They measure different things and should not be used interchangeably.

Is usage-based revenue ARR?

Not automatically. Contracted minimum usage or genuinely recurring committed consumption may form part of a company's ARR methodology. Purely discretionary consumption should usually be distinguished from committed recurring revenue.

How should annual subscription revenue be recognised?

Where a service is delivered continuously throughout a subscription period, revenue is generally recognised over that period rather than entirely when the customer pays.

Why does gross margin matter?

Gross margin shows how much revenue remains after the direct cost of delivering the product or service. It helps management understand the economic quality of growth and provides an important foundation for pricing.

What are unit economics?

Unit economics analyse revenue, direct costs and contribution at a useful operating level, such as by customer, product, transaction or unit of consumption.

Let’s talk

If understanding revenue, COGS and gross margin requires several systems, spreadsheets and a month-end reconstruction, the problem is usually not the reporting itself. It is the finance architecture underneath it.

Get in touch →

Ordinal Partners builds and runs finance functions for founder-led, operator-owned and growing businesses. From bookkeeping and financial operations through strategic finance and transactions, we give operators clear numbers, better information for faster decisions, and the financial foundations to scale efficiently, raise capital or transact without distraction.