The deferred revenue you accidentally spent

At one company I worked with, a customer prepaid $480,000 for a year in January, dropped straight into a business burning $80,000 a month. On paper that single contract looked like half a year of runway, so the founder pushed the hiring pace and approved three roles in February against the cushion. By July the cash was gone, burn was higher, and at that point the balance sheet still carried $240,000 of deferred revenue, against a customer now asking to renegotiate.

The renegotiation included a partial refund for the unused part of the year. At that point the company owed $180,000 back and didn't have $180,000 in free cash. The founder found the gap during a late-night review and spent six weeks managing a small but sharp liquidity event that should have been impossible for a business that had recently taken in nearly half a million dollars from one customer.

The gap was deferred revenue. Of the $480,000, most had not yet been earned. Each month one-twelfth of it converted from deferred revenue into recognized revenue, and the rest stayed a liability. In cash terms the company had been spending as if all of it was theirs. In cash terms it was right, until the customer wanted some of it back.

This is one of the most consistently underweighted dynamics in early SaaS. Deferred revenue feels like cash because it's cash, sitting in the account. The treatment that recognizes it over the contract term is technical and easy to ignore day to day. Teams plan against the bank balance. That balance misleads. It folds in obligations that haven't been earned. Then the obligation comes due, through refund, dispute, or churn inside the prepaid window. The cash that should have covered it is gone, spent on payroll in the months between collection and claim.

The trap gets worse at companies with high annual-prepay attach. A business that closes most contracts on annual prepay is borrowing a year of cash from every customer. The borrow is interest-free in dollars but obligation-bearing in operations. Stack enough of it and the total deferred balance runs to a real share of the cash position. Operate against the full balance and you're operating against money you owe. It's the illusion behind annual contracts booked as monthly revenue: the calendar and the cash don't move together.

The discipline is to keep two cash numbers. Gross cash is the bank balance, the one most companies report. Net cash is gross cash minus the unearned deferred revenue. That's what you'd owe back if every prepaid customer canceled tomorrow. Net cash is the conservative figure, and it's the one to plan runway against. At companies with heavy annual prepay, the gap between the two can be a real chunk of the runway.

Most companies skip this because gross cash tells a nicer story. Runway on gross cash is longer than runway on net cash. The longer number is the one the founder wants to believe and the board takes at face value. The shorter number is the one that survives a hard customer event. Founders prefer the longer number right up until the hard event lands, at which point the shorter number is the only one that matters. It's the runway version of a runway figure that lied by six months.

The next round's investor will compute net runway in diligence, almost without exception. The founder running on gross cash gets surprised. The founder running on net cash doesn't. Diligence surfaces the deferred balance, the refund exposure, and the runway recut against the conservative number. The valuation adjusts to match. Do the analysis first and you walk in with the answer. Skip it and you absorb the recut live, across the table.

The cleaner framing is to treat deferred revenue as a customer loan. The customer prepaid for delivery. The company took the prepayment. Now it owes either the product or a refund of the unearned part. Under that framing the cash in the bank is not the company's to spend freely; it's the customer's, held against a delivery obligation the company accepted.

The framing is uncomfortable because it tightens spending, which is the intent. The same balance looks different as "cash we earned" versus "cash we're holding against future delivery." The second reading spends more slowly, and the slower spend is what keeps the company able to honor a refund if the customer churns inside the window.

A matching discipline is to size the operating reserve against the deferred balance. Say a company carries $1M of deferred revenue; the reserve should be at least the unearned part of it. That reserve buys the ability to honor refunds without triggering a liquidity event. It costs some flexibility and returns real resilience.

Deferred revenue is cash you have that you owe. The cash is real. The obligation is real. Spend the cash without booking the obligation and you're borrowing against a balance sheet that doesn't show the loan.

Before the next burn discussion, ask:

• What is the current deferred revenue balance, split by customer and by months of remaining obligation?
• What is net cash, gross minus unearned deferred, and how does it compare to the runway you've been quoting?
• If the largest prepaid customer asked for a refund of the unused portion tomorrow, could you pay it without a liquidity event?
• Is the operating reserve at least the unearned portion of deferred revenue?

Run the numbers before you need them. Most teams find they've been spending against gross cash while the obligation sat quietly on the balance sheet. Keep both numbers, live off the conservative one, and the discomfort of the smaller figure is the price of not getting caught.