Four metrics, not eleven. Everything beyond these is interesting rather than actionable — and an interesting metric is how a fifteen-minute review becomes an hour. Enter six figures you already have and get the number this whole book exists to move.
Nothing is sent anywhere. The calculation runs entirely in your browser.
Six inputs. Five come from tools you already use; one you have to log by hand, and it's the one everything turns on.
Hours worked is the only manual input, and it has to be — it's the number no system can observe and the number the whole book turns on. Log it weekly in your Sunday review, from your block adherence. Five seconds.
Revenue is not the number. Revenue per hour is. Enter what you were doing before you automated anything, and see the actual return.
| Number | The decision it drives |
|---|---|
| Revenue per hour | Whether any of this is working. Should climb even in flat-revenue months, because the machines keep absorbing work. |
| Contribution margin | Below about 70%, something structural is wrong — usually a fulfilment cost you didn't plan for. Above 90%, stop optimizing costs entirely. |
| Cost per subscriber | The floor you compare paid acquisition against. Never buy traffic more expensive than the traffic you already get free. |
| 90-day value | The number that authorizes spending. You cannot responsibly buy a customer until you know what one is worth. |
You'll be tempted by open rates, follower counts, impressions, time-on-page. Not because they're meaningless — because a metric you look at and don't act on is a small recurring tax on your attention, and at four hours a week attention is the actual scarce resource. The test for any candidate: what decision would a change in this number cause me to make? If you can't answer in one sentence, it's a quarterly glance, not a dashboard.
Forty-five minutes, with a timer, in this order. Tick as you go — the boxes reset when you reload, which is the point.
0 of 11
Stop when the timer rings, even mid-thought. A review that runs to ninety minutes stops being a review and becomes work, and within a month you'll start avoiding it.
Never build during the review. This is the one people break constantly — you'll spot a broken scenario, think that's a five-minute fix, and lose forty minutes. Log it. Saturday exists for exactly this. The only exception is a high-severity error, where a customer is currently affected.
And if you tick every box in nine minutes because nothing moved and nothing broke — that isn't a failed review. A quiet Sunday review is the product.
This page calculates once. The dashboard does it nightly, from data your machines already produce, and puts it on one screen you check on Sundays.
It's a base template and a blueprint file — tell me where to send them.
One email a week about building things that run without you. Unsubscribe link at the bottom of every one, and it works.
© 2026 Jeff Sheikowitz. All rights reserved.