Observation is Never Neutral

The most practical thing I can offer a business leader who wants to understand what’s actually happening inside their own company.

I’ve been working on a framework for revenue operations observability for the better part of a year now, and this one idea is the anchor.

Observation is never neutral.

You can’t measure a business before you’ve decided where you’re standing and what you’re looking at. The place you stand and the direction you look are what produces the observation. If you skip that step, your data is ungrounded. Numbers without a model behind them won’t tell you anything relevant about the business.

This is where I see most reporting in most companies fail. Someone asks for a report and someone else obliges but nobody pauses to ask which lever of the business the report will measure, what time horizon it should speak to, or which level of the organization needs to see it. The report gets built but then nobody quite knows what to do with it. The numbers are accurate but the observation behind them is unclear.

Observability doesn’t start with measurement. It starts with defining the model you’re going to use to observe the business.

The rest of this piece is about that model. The framework is a 3x3x3 matrix that combines three revenue levers, three time horizons, and three levels of the organization. That gives you 27 combinations. Every meaningful report you build will be in one of those 27 cells.

The three levers

Every business has three principal levers that produce revenue. The levers are volume, conversion, and value. Another way to describe them is inputs, throughputs, and outputs.

Volume is how many revenue opportunities are entering the system. Without sufficient volume, you don’t produce growth. Quantity alone is misleading though, so volume has to be observed alongside source, quality, timing, and fit. A thousand bad leads in the door is a completely different business from a hundred good ones. The metrics that live under volume include total lead count, marketing-qualified and sales-qualified leads, source attribution, channel mix, event-driven inflows, and the cost to acquire each one.

Conversion is how efficiently the system transforms an opportunity into revenue. The thing most people miss about conversion is that it includes velocity. Speed matters as much as the rate, sometimes more. A 30% close rate at 60 days is a completely different business from a 30% close rate at 6 months. Both numbers look fine on a slide, but they describe very different operations. Conversion metrics include stage conversion rates, overall win rate, sales cycle length, time in stage, and pipeline velocity.

Value is how much revenue a single opportunity produces. Value can show up as ACV, MRR, LTV, contract size, or expansion revenue, depending on how you account for it. Value must always be bound to a time window, whether that window is one year, two years, or the full customer lifetime. Value also gets measured very differently depending on the business model, which means the first question to ask about any business is how it thinks about value. A SaaS subscription is a completely different beast from a consumption contract, and consumption is going to keep growing as a model because of AI. Conversations about value have to start with the business model.

Each metric that matters comes back to one of these three levers, or to the interaction between them. If you can’t ground a number in volume, conversion, or value, you won’t know what that number relates to.

The three horizons

The next coordinate is time. There are three horizons of observation, and each one answers a different question.

Horizon 1 is operational. It operates in real time, minute by minute. The question this horizon answers is whether the system is running right now. Operational observability is like the temperature gauge on your car. The gauge has one job, which is to tell you when the engine is about to seize. Operational observability does the same thing for a revenue system. It tells you whether the lead form is firing, whether the routing logic is putting leads where they should go, and whether the integrations between your tools are syncing. When the temperature spikes, you want to know fast. Operational reports look like alerts, error logs, sync status pages, and form-submission counters that should be ticking up but suddenly aren’t.

Horizon 2 is directional. It tracks leading indicators on a time frame of hours to weeks. The question this horizon answers is where the vectors are pointing right now. At Innovation Refunds we ran the business in 4-hour windows. By noon every day we could predict how many deals would close before close of business. We could do that because we had built directional observability into the rhythm of the day. We watched whether volume was steady or climbing, whether qualified pipeline was moving, whether stage conversion was holding, and whether average deal size was sitting where we expected it. If the leading indicators were pointing in the wrong direction, we knew before the day was over. Directional reports look like daily pacing dashboards, week-over-week conversion trends, and pipeline-by-stage views with movement velocity built in.

Horizon 3 is strategic. It covers months, quarters, and years. The question this horizon answers is whether the system is producing the outcomes it was designed to produce. This is the horizon that executives default to, and it is the easiest to measure but the slowest to give you signal. By the time horizon 3 says something is broken, horizon 1 and horizon 2 said so weeks or months earlier. A lot of companies build horizon 3 reports because the board asks for them and then they wonder why every quarter end is a fire drill. Strategic reports look like annual revenue trajectories, retention cohorts, LTV-to-CAC ratios, and progress against multi-quarter goals.

The three levels

The last coordinate is who is looking. The three levels are executive, team, and individual or process.

Executive reporting maps to the strategic horizon. The question is what a CEO or board needs to see to know the business is on track. Team reporting breaks the business into functional units. Marketing, sales, and customer success each need a view that shows their part of the system performing or not. Individual and process reporting goes one level lower. The question becomes how a specific rep’s activities and meetings and win rate are feeding into the system, or how a specific campaign is performing, or how an automated routing flow is doing its job when no human is touching it.

That last level is the one most companies forget. We automate things now so the system runs without a person involved in a lot of the steps, but you still have to observe what the system is doing, or you’ll be the last to know when it stops doing it.

The matrix

The matrix combines the three levers, three horizons, and three levels. That gives you 27 combinations. Every report you build should answer three questions at the outset. The first question asks which revenue lever the report is measuring. The second question asks over what time horizon. The third question asks at what level of the organization the answer needs to land.

If you can answer all three, the report will be meaningful.

Take a concrete example: a founder needs to raise $4.6M in 60 days, with a $200K minimum check size. The math says 23 investors, which works out to one investor every 3 days. That number is useful, but it doesn’t tell the founder how to pace the work. Most fundraises are back-loaded, with more closes in the second half of the window. The realistic expectation might be 4 commits in the first 3 weeks and 19 in the last 5. Once that description is on paper, the next question becomes how many investor conversations need to be in flight each week to produce that pace, which is the directional horizon at the individual level. Then the daily question becomes whether the right meetings are landing on the calendar at all, which is the operational horizon at the individual level. The strategic horizon was the $4.6M target.

The whole exercise describes the same business pursuing the same goal. It produces three completely different reports. Each one answers a different question, and each one matters at a different cadence.

From observation to control

The next piece of work after observability is controllability. The term observability isn’t mine, by the way. It comes from control theory, a branch of applied math that Rudolf Kalman developed in the late 1950s and early 1960s as computer systems were getting complex enough that engineers couldn’t see what was happening inside them anymore. Kalman’s question was whether, if you put a known input into a system, you could predict the output. If the answer was yes, the system was observable. Once a system was observable, it would be controllable.

A revenue system works the same way. Once you can observe the system across three levers, three horizons, and three levels, you can start designing controls. A control is an action with a predicted outcome. Most actions inside a sales or marketing org are taken without a predicted outcome attached. That is the gap controllability closes.

Controllability is the next article. For now, the test is just this: before you build any report, ask which lever, which horizon, and which level. If you can name all three, the report will be useful. If you can’t name them, you have a different job to do first. That job is defining what is being observed and why.

That is where revenue operations actually starts.