Remaining Performance Obligations: The Fruit Already Set on Your Branches

Remaining performance obligations is the full value of work you have agreed to deliver and have not delivered yet, whether or not the customer has paid. Think of it as fruit. Every contract you sign sets fruit on a branch. The fruit is real and it is yours, but it is not ripe. You cannot count it as revenue until you do the work and it matures.

That one picture separates three terms that catch out most founders.

Your contracts are fruit, not yet picked

When a customer signs, you do not earn the money that day. You set fruit. The branch is full of value you have agreed to grow into a delivered service over the months ahead. Under accrual accounting, you only recognize revenue when the fruit matures, when the work lands, not when the contract gets agreed and not when the cash arrives.

So a customer who prepays a year of your subscription hands you two things at once: cash, and a year of work owing. The cash feels like harvest, but it is fruit you have been paid for in advance, still on the branch, maturing month by month.

That paid-in-advance fruit has a name. It is deferred revenue.

Deferred revenue is fruit you have already been paid for

Deferred revenue is the part of work where the customer’s cash is already in your account but the service is not yet delivered. On the balance sheet it goes with your liabilities, not your earnings, because you are still owing the delivery. The money is real and the work is not done, so the accounting treatment files it next to your debts.

Most founders read that line in reverse. A growing deferred revenue balance looks like good news, because the bank balance went up and the customer paid. But a growing deferred revenue line is a growing list of work owing. Spend it as profit and you are eating the fruit green, before it has matured into anything you have earned.

What remaining performance obligations measures

Remaining performance obligations is the larger number. It counts every part of fruit set on every agreed branch: the prepaid deferred revenue, plus the agreed work the customer has not paid for yet. The day a contract is agreed, the whole term sets fruit, even the part that bills next year and the year after.

That is why auditors and mature buyers weigh it over ARR. ARR is a run rate, a snapshot of how fast you are harvesting ripe fruit right now. Remaining performance obligations is the forward count, the total value still maturing on the branch across the full term of your agreements. ARR shows this season’s harvest rate. RPO shows the standing crop you have already grown and agreed.

Most founders never report it. They lead with annual recurring revenue because it is known and it grows fast in a report. But a sophisticated investor reading your numbers for a raise, or a buyer running an audit before a sale, wants the forward count. They want to know how much future revenue is already set under agreements, not hoped for. That number is RPO.

RPO, not ARR, is the best measure of fruit you have already grown and agreed.

Backlog is the whole standing crop

Backlog is the widest of the three. It is the full list of work you have agreed to deliver across all your deals, including parts that may sit outside the strict accounting line of remaining performance obligations. Different companies draw that line in different places. Some treat backlog and RPO as nearly the same. Others use backlog for the entire standing crop, every contract’s worth of agreed delivery the team is still owing.

So the three line up like this. Deferred revenue is fruit you have been paid for. RPO is all the fruit set under agreements, paid or not. Backlog is the whole standing crop in your rows. Each one counts work owing, across a wider or smaller spread of it.

Why the direction of the line matters

A gardener who never walks the rows misses the deadwood. Same with these lines.

A large RPO against a flat ARR tells you long, durable agreements are set and maturing, fruit on the branches waiting to be picked. That is good news. But a falling RPO with steady ARR tells you the agreed work is draining faster than you are signing new deals. The branches are going bare. You are harvesting ripe fruit at a good rate while setting almost no new fruit behind it, and a single number will never show you that. It is the kind of decay you only catch by walking the rows.

One thing I hear founders say is that a growing deferred revenue line proves the business is healthy. It does not, on its own. I watched a seed-stage SaaS founder, call her Mara, lead every board update with a deferred revenue chart that rose all year. It looked great. But her RPO had gone flat in month four, because she was front-loading annual prepaid contracts from a smaller set of new customers. The fruit on the branch was not growing. She was collecting cash sooner on the same crop. The board caught it before she did.

The gap between these lines is the useful part, and most reporting buries it.

Frequently asked questions

Is deferred revenue an asset or a liability?

A liability. You collected cash for a service you have not delivered, so you are still owing the work. On the balance sheet it sits with your debts until the service lands and the revenue is recognized. The cash is real today, but you have not earned it yet. It is fruit you have been paid for but have not harvested.

What is the difference between remaining performance obligations and deferred revenue?

Deferred revenue is the prepaid part, the cash already collected for work not delivered. Remaining performance obligations counts all of it: every agreed, not yet delivered part of work, whether the customer has paid or not. RPO is the larger, more forward number, which is why auditors and mature buyers lean on it over the prepaid part alone.

How is RPO different from ARR?

ARR is a run rate, a snapshot of your recurring revenue right now, this season’s harvest rate. RPO is the total value still maturing over the full term of your agreements, including the multi year deals that ARR will smooth over. ARR shows where you are harvesting. RPO shows the standing crop you have already grown and agreed.

Should founders report RPO when raising or selling?

They should. Show only ARR and you are holding back your most durable number from the people setting your valuation. RPO shows how much future revenue is already set under your agreements. Lead with it, and a sophisticated investor reads you as a gardener who knows the rows, not a founder waving one green chart.

The stand

Stop reading deferred revenue as money you have earned. It is fruit you have been paid for and have not harvested, a service still owing, and handling it as profit is how scaling companies eat the crop green. Walk the rows and report RPO. It is the best measure of work you have already grown and agreed, the forward count your investors will weigh.

You should know where the money is going, and that includes the cash you have collected but have not yet earned. CX Cash counts deferred revenue, RPO, and backlog as what they are, work owing, so you read the gap between your lines before it reads you. Join CX Cash, grab the SaaS KPI dashboard and ARR growth tracker, and share this with the founder still pulling fruit off the branch before it is ripe.