The weekly operating cadence. What kept a $7M company honest.

Leading indicators move fast — watch them weekly

The most useful numbers are the leading ones — the early signals that predict the outcomes you actually care about, long before those outcomes show up in revenue. Feature adoption, activation, support's first response time, ticket volume, account-level engagement — these move on a weekly or even daily rhythm, and they're where you can still intervene. A new customer stalling in onboarding, a feature's adoption sliding, a spike in tickets that means you shipped something broken: catch those this week, and you can act. Find them in a monthly report and you're reacting to damage already done.

The discipline is to put the fast-moving, actionable signals in front of the team every week, where someone can do something about them — not bury them in a quarterly review where they're just history.

Lagging indicators move slowly — read them quarterly

The financial and company-level numbers — LTV, LTV:CAC, Rule of 40, runway — move on the order of quarters, and reading them weekly invites false precision. A Rule of 40 that wobbles two points week to week tells you nothing; pulling it every Monday just creates noise you'll be tempted to react to. These are board-level health checks. Read them quarterly, against the trend, and let the weekly work be what actually moves them. You manage the leading inputs; the lagging outputs follow.

The trap is doing it backwards — obsessing over the lagging financial number in every meeting while the leading signals that drive it go unwatched. By the time churn shows up in your revenue, the engagement signal that predicted it was sitting there, unread, two quarters earlier.

Consistency beats intensity

The cadence only works if it's actually a cadence — the same review, the same numbers, every week, without fail. A heroic quarterly deep-dive that happens when someone remembers is worth less than a boring weekly scorecard the whole leadership team looks at together. Consistency is what lets you see trends: a number is just a number, but the same number watched week over week becomes a direction, and direction is what you act on. The widening burn, the creeping ticket volume, the sliding adoption — all of those are invisible in a snapshot and obvious in a trend.

Get it out of the founder's head

Here's the part that doesn't scale: for years, a lot of this lived in my head. I knew the survival number, I knew which accounts felt shaky, I knew which feature support was complaining about — but it was mine, not the team's. That's a single point of failure, and it's the opposite of an operating discipline. The whole point of a scorecard is to make the rhythm a shared, durable habit — so the leadership team is reading the same leading signals every week, acting on the same trends, and the health of the business doesn't depend on one person paying attention. That shared weekly cadence is the operating system of a healthy company, and it's exactly the thing most small SaaS companies never build.