The Hidden Cost of Unpredictable Revenue

# The Hidden Cost of Unpredictable Revenue

Unpredictable revenue costs more than the quarters it misses. We call the full bill Revenue Debt: every hire delayed, every investment shrunk and every plan hedged because nobody trusts next quarter's number. The debt accrues quietly, compounds monthly, and gets paid whether or not you ever measure it. Here's where it hides.

"Sales is lumpy." Every founder says it, usually with a shrug, usually while deferring something that mattered: the hire held back a quarter, the campaign sized down, the plan built around the miss that might come. One seller on r/sales put the lived version plainly: "Only 20% of org hit their number and has historically been a feast or famine role, especially in new logo territories." [1] Feast or famine sounds like weather. It's the output of a system nobody designed, and the costs it generates don't show up anywhere your dashboards look, because they get paid in decisions rather than in pounds. Decisions don't have a ledger. They should.

The costs that never appear on a dashboard

The hire you made four months late. When you can't trust next quarter's number, you wait for it to land before committing to headcount. The role you finally fill in June was needed in February. Now add the arithmetic nobody runs: four months of vacancy plus three months of ramp means the pipeline that person would have built starts arriving three quarters after the need was real, and the deals that would have filled it went to someone else in the meantime. Nobody books that loss anywhere, which is why it never gets fixed.

The investment you sized for the bad quarter. Unpredictability breeds permanent conservatism. Marketing gets budgeted against the worst recent quarter rather than the median one, because reserves have to cover the miss that might come. Run three years like that and you've compounded it: every year's engine was funded as if the famine was the truth and the feast was the anomaly, which guarantees the engine stays small enough to keep the famine plausible. The caution creates the thing it fears.

The multiple you gave away. A buyer who can't model your revenue prices the risk in, because from their side of the table, growth nobody can model might be luck, and luck doesn't survive due diligence. If you're raising, the volatility in your revenue history becomes a line in someone else's spreadsheet, and you pay it in dilution without it ever being named in the meeting.

The pattern across all three: unpredictability taxes the decisions around revenue long before it touches revenue itself. That's why we call it debt. It charges interest, and the interest gets paid in decisions.

Where the unpredictability actually comes from

The comfortable story is that deals are inherently random. The arithmetic says otherwise. Our Revenue Debt whitepaper works it through a five-gate engine where every gate converts at a healthy-looking 70%. Multiply it out: 70% of 70% of 70% of 70% of 70% delivers 17% end to end. [2] Every gate looks fine in isolation. Every team defends its own number in the QBR, truthfully. The engine as a whole leaks five-sixths of what enters it, at the seams between the gates, and because nobody owns the seams, the leak reads as randomness.

That's the useful reframe: a "lumpy" quarter is usually five small, stable leaks arriving in an unstable order. The deals that vanish at the marketing-to-sales handoff. The trials that stall in week two. The proposals that end in no decision. Those are three different gates leaking: the handoff is Position work, the trial is Activate, the proposal is Capture. Each needs its own fix, and none of them is a morale problem. Each is a designable, fixable failure at one of the five gates a buyer moves through, and The $100k Inflection Point carries the post-PMF version of this arithmetic. Randomness is what a system's leaks look like from above.

The same seller community has the counter-receipt too: "So many times you hear 'Feast or Famine', but since breaking down my numbers and sticking to the activity metrics, there has been very little famine." [3] One seller, one territory, and the principle scales: break the system into measurable parts and the weather turns out to be plumbing.

Paying the debt down, gate by gate

You don't fix unpredictability by forecasting harder. A better forecast of an unstable system is a more precise guess, and the sibling piece on why pipeline metrics lie shows how much guessing is already baked in. The sequence that works runs upstream, and it's deliberately boring: find which gate leaks most, price what that leak costs per quarter, fix that one gate's definitions and handoffs, then move to the next. Stability is a property of the system, and it arrives one gate at a time.

Two rules make the sequence work. Fix conversion before volume, always: more pipeline through a leaking system produces bigger leaks and the same unpredictability, at higher cost. And price the leak before you fix it, because a sentence like we lose roughly £180k a quarter at the sales-to-onboarding handoff turns an operations job into a board decision. The pricing step converts "sales is lumpy" from a shrug into a number someone is accountable for.

Worked small, the sequence looks like this. A team whose biggest leak is proposals dying to no decision doesn't need more leads, a new tool or a pep talk. It needs stage gates that stop unfunded deals reaching proposal, which is a definitions fix, finished in weeks, that removes the largest single source of variance from every quarter that follows. Then the next-largest leak gets the same treatment. Three gates in, the forecast starts behaving, and nobody improved at predicting anything. The system just stopped generating surprises.

A forecast model built on a stabilised system comes last, and by then it's barely a model at all: stable gates produce stable outputs, and the forecast becomes arithmetic instead of hope. That's the end state we aim at, and it looks like a forecast meeting with nothing to argue about.

If you want the leak located before you spend anything fixing it, the free PACED diagnostic scores each gate of your engine against your own numbers and tells you which one is generating the famine.

Frequently asked questions

What is revenue debt?

Revenue debt is our term for the accumulated cost of running revenue on an undesigned system: the delayed hires, shrunken investments, discounted valuations and rescue work that unpredictability forces. Like technical debt, it's invisible on any single day and expensive over every quarter, and it compounds until the system underneath is rebuilt.

Is unpredictable revenue just part of B2B sales?

Deal-level variance is. System-level unpredictability isn't. Individual deals will always wobble, but a five-gate engine with owned handoffs and one qualification standard produces stable output from wobbly inputs. Teams that break their engine into measured gates usually find the "lumpiness" was a small number of repeat leaks arriving in different orders.

How do I make revenue more predictable without more pipeline?

Fix conversion before volume. More pipeline through a leaking system produces bigger leaks and the same unpredictability. Trace last quarter's deals backwards, find the gate where signal dies, price what that leak costs per quarter, and rebuild that gate's definitions and handoffs first. Volume amplifies whatever system it enters.

Sources

1. r/sales, Negotiating territory, March 2024. https://www.reddit.com/r/sales/comments/1b5enc4/negotiating_territory/
2. PacedRevenue, The Revenue Debt You Cannot See (whitepaper): the five-gate yield model
3. r/sales, It's a numbers game, May 2024. https://www.reddit.com/r/sales/comments/1cy215g/its_a_numbers_game/