Confident about last quarter, blind about next
You can answer detailed questions about what happened. Revenue by month, projects delivered, clients gained and lost, hours spent. The historical record is genuinely good.
Now ask what next quarter looks like, and the answer changes register entirely. It becomes a feeling, hedged, with a couple of specific deals attached. Not because you are careless — because there is nothing in the business to consult.
The starkest version: every serious problem you have had in the last three years announced itself in the numbers only after it had fully happened. The client who left showed up as churn. The quiet quarter showed up as revenue. In every case the data confirmed the thing after it was too late to act on, and you experienced that as bad luck rather than as a property of what you measure.
Transactions leave receipts, behaviours leave nothing
Trace where a lagging metric comes from. An invoice exists because money had to move, and moving money requires a record. A signed contract exists because agreement requires an artifact. Churn exists because ending a subscription requires an action in a system. Every one of these is recorded as a byproduct of the business functioning — nobody built the capture, the capture is the transaction.
Now trace a leading indicator. A conversation that did not happen. A follow-up nobody sent. A client whose replies have slowed from a day to a week. A project whose next step has not been scheduled. None of these involve a transaction, so none of them generate a record, so none of them are visible to any tool you own.
That is the whole mechanism, and it explains why the effort you would spend is so lopsided. Lagging metrics are free and arrive whether you want them or not. Leading metrics require somebody to define a behaviour, decide how it will be captured, and maintain the capture — for a number whose only value is that it might save you from something that has not happened yet.
It also explains why the usual advice fails. Being told to track leading indicators is unhelpful when the reason you do not have them is not that you did not think of it. It is that they cost something and the lagging ones did not.
This is distinct from finding out about problems too late, which is a latency problem — the signal exists and reaches you slowly. Here the signal does not exist at all. Speeding up your reporting would not help, because there is nothing upstream to report.
What a purely backward-looking business costs
The first cost is that every intervention happens at the most expensive possible moment. A drifting client is a phone call in month four and a lost account in month seven, and lagging metrics only ever show you month seven. Same problem, different price, decided entirely by when you found out.
The second cost is that you cannot steer, only react. Planning against outcomes means adjusting after results arrive, which in a service business is a lag of one to two quarters. The business is being driven by looking in the mirror, and the mirror is honest.
The third is that it makes forecasting a personality trait rather than a process. Without leading indicators, the only forecast available is the founder's intuition, which means it cannot be checked, cannot be delegated, and cannot be improved — and when it is wrong, nobody can say why.
The fourth is what it does to the team's behaviour. If only outcomes are measured, only outcomes get attention, and the behaviours that produce outcomes — the follow-up, the check-in, the early conversation — become invisible work that nobody is credited for. They then stop happening, which shows up as an outcome, two quarters later.
Pick four behaviours and build the capture
You do not need a system of leading indicators. You need three or four, and they should be behaviours you can already name because you already know what predicts trouble in your business.
For most founder-led service businesses the same four keep working. Net new conversations started this week, which leads revenue by about a quarter. Open opportunities with no scheduled next step, which is the pipeline's decay rate made visible. Days since a client last heard from a human, which leads churn. And work items past their promised date, which leads the delivery problems you will hear about in a month.
Then confront the capture honestly, because that is the actual work and it is where this dies. Days since last contact requires that contact is logged. Next step scheduled requires that next steps live somewhere structured rather than in someone's head. Past promised date requires that a promised date was recorded at all. Each of these is a small change to how work is done, and each will be resisted, correctly, if it is imposed as reporting overhead.
So make the capture a byproduct of the work rather than an addition to it. If logging a client conversation requires a separate act, it will not happen; if the conversation happens in a system that records it, it is free. This is the whole design constraint — build the systems as you do the work, not instead of the work. Every leading indicator that survives in a real business is one where the capture rides along with something people were doing anyway.
Start with one. Pick the behaviour that most reliably preceded your worst surprise of the last two years, instrument only that, and run it for a quarter. One leading indicator that fires is worth more than four you designed and never captured.
Telemetry, and the honest offer
This is Telemetry, and it is the pillar's actual purpose rather than its accessories. Stop reacting, start recognizing — recognition means seeing the pattern while it is forming, and a business measuring only transactions has, by construction, forfeited that.
The three layers make the gap concrete. The scoreboard is what is working over time, and most businesses have some version of it. The pulse is what is happening right now — and a pulse assembled from invoices is not a pulse, it is a slow history. What is missing in almost every founder-led business is not the scoreboard, it is the pulse, and the pulse is exactly the layer that requires deliberate capture.
The honest offer: pick the single behaviour that preceded your worst surprise in the last two years and start counting it by hand this week. A tally in a notebook is a valid leading indicator, and doing it manually for a month will teach you whether it is the right one before you build anything.
The build is the capture — making the record a byproduct of the work rather than a task on top of it. The OPERATE Report is a $1,997 diagnostic across all seven pillars, for the founder who knows what they should be watching and has nowhere for it to come from.
Outcomes record themselves because a system had to process them. Behaviours record nothing, so leading indicators only exist if you build the capture — and the capture has to ride along with work people already do.