Loop Gain and the Data Stack

Deep Dive #3 of 5 -- How to actually measure whether your revenue system is compounding or decaying

Every CEO I talk to claims their revenue system is compounding. Almost none of them can give me the number that proves it. They can give me ARR. They can give me NRR. They can give me a growth rate. None of those numbers answer the question. The number is called Loop Gain, and the reason most CEOs cannot cite it is not because they have not heard of it. It is because the data stack underneath it was never built.

Loop Gain is not a metaphor. It is not a marketing concept. It is a ratio, and if your architecture is correct, you can calculate it on a Tuesday and recalculate it next Tuesday and watch it move. If your architecture is incorrect, you cannot calculate it at all, and what you have instead is a slide that says “we are compounding” because somebody wrote that sentence into the board deck two quarters ago and nobody has challenged it since.

Deep Dive #1 made the case that the feedback-loop moat behaves differently from every historical moat because it compounds instead of depreciating. This piece is the operator answer to the obvious next question: how do you measure compounding, as a number, on an ongoing basis, and how do you build the thing underneath it so the number actually means something.

I am going to try to make the technical content concrete. It has been over-gated long enough. Consultants have built careers on keeping this fuzzy. It is not that fuzzy.

What Loop Gain actually is

Jacco van der Kooij’s formulation is the cleanest I have seen. Loop Gain is the ratio of productive output that feeds back as input per cycle.

Break that apart.

Output is what your system produces in a cycle. A closed deal. A renewed contract. A resolved ticket. A campaign that ran. A submission approved. Something observable, with a result attached.

Input is what feeds the next cycle. Not the raw effort. The learning. The updated model, the refreshed scoring, the retrained agent, the playbook that now includes what last week taught you. Input is the part of the output that gets captured and becomes the starting condition for the next run.

A cycle is whatever the natural unit of repetition is for the workflow you are measuring. Outbound sequences run on a weekly cadence. Support tickets run on an hourly one. Pipeline reviews run on a two-week one. You do not have to normalize across the business. You do have to name the cycle for the workflow, because without a cycle there is no ratio.

Loop Gain greater than one means the system is compounding. Output exceeds input. Each cycle strengthens the next. The moat widens without defense.

Loop Gain less than one means the system is decaying. Output underperforms what the inputs would predict. You are spending more than you are getting back. No headcount addition fixes it. No budget increase fixes it. No CRO hire fixes it. The mechanics are mechanical. A decaying loop compounded by more resources is a decaying loop running at higher volume.

That last point is the one most CEOs flinch at. The instinct when growth stalls is to add. Add sellers, add marketers, add a head of demand gen. If the underlying Loop Gain is below one, you are paying linearly for output that decays geometrically. I have seen this at multiple companies. The board meeting where somebody says “we just need more pipeline” is almost always a meeting where nobody at the table can tell you the Loop Gain of the pipeline motion.

The ratio matters more than the absolute numbers. A small system with Loop Gain at 1.3 beats a large system with Loop Gain at 0.8 over any meaningful time horizon. Compounding is not about scale at t=0. It is about direction at every t thereafter.

Why most companies cannot measure it

A ratio requires three things. What feeds in. What comes out. What cycle you are measuring. Those are not abstract. Those are three pieces of infrastructure that either exist or do not.

Most companies cannot answer any of the three for their own growth system.

Feeds in: marketing counts MQLs, sales counts SQLs, CS counts NPS, product counts DAU, and nobody agrees on how the motion starts or where the boundaries are. There are four definitions of “lead” in the room, and three of them are hidden inside departmental spreadsheets that do not talk to each other.

Comes out: every team has its own output metric, tied to its own comp plan, defined at whatever granularity made it easiest to hit the number last year. The output of the sales motion is not the input to the CS motion in any automated sense. A human copies, pastes, reformats, summarizes. Signal leaks at every hand-off.

Cycle: the planning cycle is quarterly. The forecast cycle is monthly. The pipeline cycle is weekly. The agent cycle is real-time. Nobody has named which cycle Loop Gain is supposed to measure, so the number is unmeasurable by default.

That is the architecture problem showing up in the metric layer. You cannot measure what you have not built. The inability to cite Loop Gain is not a reporting failure. It is the stack revealing itself. If somebody on your team tells you they cannot calculate Loop Gain, they are not making excuses. They are diagnosing the real problem.

The five-layer stack that makes the number real, the three ways it quietly hollows out, what Loop Gain above one looks like on an actual Tuesday morning, a build I shipped one level deeper, and the five-question diagnostic you can run at your desk this week are the rest of this piece.