The 6 Numbers to See Every Week

You can tell me last month's revenue. You probably can't tell me whether this month is good.

That's not a knock — it's a structural fact about the number you're watching. Revenue is a trailing indicator. It's the echo of decisions you made a season ago: the outreach you did or didn't do in March, the follow-ups that happened on a Thursday you had energy, the client you meant to call in week six. By the time revenue tells you something is wrong, the cause is four months cold and unfixable.

Watching revenue weekly is like driving by watching the road behind you. It's real information. It's just about a place you've already been.

The six numbers below lead. They move before revenue does — in some cases by a full quarter. Which means when they move, you can still do something.

First, the trap this list has to avoid

The instinct after reading a list like this is to go build a dashboard with everything on it. Don't. That's how you end up with a dashboard nobody opens — twenty-eight metrics, no signal, quietly abandoned by week three.

The goal isn't to watch everything… it's to know the right things to watch.

Six is the number because six is what a human will actually look at every week for a year. And there's a frame that makes them cohere rather than pile up. The Telemetry pillar has three layers:

• The pulse — is the business alive right now? The leading, operational signals. Numbers 1 through 4 below.
• The scoreboard — are we winning? The outcomes. Revenue lives here, and it belongs here — it's a scoring mechanism, not a steering wheel.
• The soul — how does it feel to be a client of this business, or an employee inside it? The thing no chart contains and every good founder can sense.

When you combine the pulse, the scoreboard, and the soul, you stop reacting and start recognizing. You stop guessing and start seeing.

1. Net new conversations started

What it is: How many new qualified people entered a real conversation with your business this week. Not impressions. Not followers. Conversations.

Why it leads: It moves an entire sales cycle ahead of revenue. If your cycle is 60 days, this number is telling you about September in July. It's also the number that goes to zero the month you get busy — exactly the month you won't be looking at it.

That's the whole cruelty of the Outreach pillar: if you only market when you need clients, you'll never have clients when you need them. This number catches that in week one instead of month four, when you're wondering why marketing stopped when the work started.

Where it lives: Your CRM — GoHighLevel, or wherever new contacts land. Count things that crossed into a two-way exchange.

What you do when it moves: Down for two consecutive weeks is a fire, not a blip, and the response is not "post more." It's structural: your visibility is running on your mood again. A cold outreach engine or a queued content engine is what makes this number survive a busy quarter.

2. Warm deals with no scheduled next step

What it is: Of every open opportunity, how many have a specific next action with a date? Track the ones that don't. This number should be near zero, and in most founder-led businesses it's the majority of the pipeline.

Why it leads: Because this is the number that predicts the deals that will die of nothing. Not rejection — neglect. Momentum fades the same way it does in relationships, and a deal with no next step is not "in the pipeline." It's a memory.

I learned this the expensive way, collecting business cards at networking events and feeling great about it. I was mistaking interest for intention. Enthusiasm today doesn't equal action tomorrow. Without a system in between, tomorrow never comes.

Where it lives: The Pipeline pillar, and mechanically, a filtered view of your CRM. If your CRM can't tell you this in one click, that's the finding.

What you do when it moves: Every deal on that list gets a next step assigned now — not a follow-up, a next step. Then fix the upstream cause, because this number rising means your pipeline is running on your recall and leads are going cold in your inbox.

3. Stage age vs. your average

What it is: For each open deal, how long has it been sitting in its current stage compared to your typical? Watch the outliers, not the average.

Why it leads: Deals don't announce that they're dying. They just stop moving, and the stopping is measurable weeks before the loss becomes obvious. A proposal that normally converts in nine days and has been out for twenty-six is not "still deciding." It's already gone, and you're the last to know. This is the number that catches deals stalling after the first call while there's still a conversation to have.

Where it lives: Your CRM's stage timestamps, which you already have and are almost certainly not looking at.

What you do when it moves: An outlier is a signal to change the approach, not to send another nudge. A stalled deal usually means an unspoken objection or a stakeholder you haven't met. The fourth "just checking in" doesn't surface either. Structurally, this is what a real lead-to-close pipeline is for: designing moments that invite the next step rather than applying pressure.

4. Days since a client last heard from a human

What it is: Per account, the number of days since a real person sent them something real. Automated sequences do not reset this clock. That's not a technicality — that's the point.

Why it leads: Because this is the closest thing to a churn prediction you'll ever get for free. Clients rarely leave over a failure; they leave after a gap. And your attention is currently allocated by noise, which means the accounts drifting quietly toward the exit are structurally invisible to you.

I've killed enough houseplants to know you can't just give one deep watering after weeks of neglect. You need rhythm — a little attention, consistently applied. This number is the rhythm made visible.

Where it lives: The Retention pillar. Practically, a last-touch field on the account record, or a renewal and retention system that maintains it for you.

What you do when it moves: Anything over your threshold gets a human message this week — and per the rule, automate the reminder but write the message like a friend. If the same accounts keep crossing the line, you don't have a discipline problem. Connection doesn't happen by chance; it happens by calendar. Put it on one. This is how you stop clients churning without warning — the warning was always there.

5. Work items past their promised date

What it is: How many delivery commitments are currently late, by any amount, to anyone. Internal or client-facing.

Why it leads: Because your delivery is your marketing, and this number is the leading indicator of your reputation — which is the leading indicator of referrals, renewals, and every deal you'll close two years from now on the strength of someone's word.

It also leads you. A rising number here is the earliest hard evidence that you're back to being the person who rescues delivery at midnight instead of the person who designed how it gets done. That's the Execution pillar: it's not about removing yourself, it's about removing your dependency.

Where it lives: Wherever work actually lives. Notion, your project tool, the project delivery system. One filtered view.

What you do when it moves: Resist the urge to personally rescue it — that's the reflex that got you here, and there's a moment where hustle stops being heroic and starts being harmful. Ask instead what needed to exist so this would have finished without you. If work is falling through the cracks repeatedly at the same step, that step is a design flaw, not a people flaw.

6. Decisions that routed through you unnecessarily

What it is: A count. Every week, how many times did someone ask you to approve or decide something they were fully qualified to handle?

Why it leads: It's the only number here that measures your ceiling directly, and it leads everything — because it determines how much of the other five you have capacity to respond to. A founder answering thirty unnecessary questions a week has none left to architect anything, so all five numbers above drift, and nobody notices, because the one person who could notice is answering questions.

It's also the honest measure of the Enablement pillar. We love the comforting lie that only we can do things "the right way," but "the right way" is really just "the way we've always done it." It's ego disguised as responsibility and control dressed up as quality assurance.

Where it lives: Nowhere. You have to count it, by hand, for a week. That's the exercise, and it's worth every minute of the mild annoyance.

What you do when it moves: Each instance is one of three holes — they didn't have authority (empowerment), didn't have knowledge (education), or didn't have a system that supported acting (environment). Write down the answer where it belongs, in the SOP library or the boundary doc, and stop answering it live. Nobody hired a low-agency person; the system taught a high-agency person that checking first is the cheapest way to be right. When your team waits on your approval, that's the design working as built.

Where these six should live

Not in a dashboard you visit. That requires you to remember to look, and you won't — and the whole point is to stop making your attention the load-bearing element.

Push them. One weekly digest, one place, same time every week. A Slack message is genuinely better than a beautiful dashboard, because it arrives. Add an alarm layer for the two or three conditions where waiting a week is too long: a trigger that failed, a deal past double your stage average, a client silent longer than they've ever been.

A great system doesn't just execute: it communicates. It tells you when it's thriving and when it's gasping.

That's the standard for a founder dashboard, and it's a higher one than most reporting clears. Most reporting requires a human to assemble it, which is why reporting takes all day and why it stops the month you get busy. If your telemetry depends on you, it's not telemetry. It's another chore.

The reflection you're skipping

One last thing, because there's a version of this where you build all six and still don't get the benefit.

The numbers arriving isn't the practice. Looking at them is.

Every high-performance field treats reflection as part of the job, not an optional extra. Musicians tune their instruments before every show. Athletes watch game film every Monday. Pilots do the pre-flight checklist before every single flight — not the experienced ones less often. Every flight. Every time. None of them consider it overhead. It is the work.

Founders are the only high-performance operators who treat reflection as a luxury for slower weeks. Thirty minutes, same time weekly, six numbers, one question each: what does this tell me about a month from now? That's the whole practice. It's shorter than the meeting you're about to sit in that you didn't need to attend.

And it's the difference between running a business you can feel and running one you can only remember. If you have no idea whether this month is good, you're not missing data. You're missing instruments — and thirty minutes.