Facebook tracking pixel Skip to main content

Daily operations

Know where every target stands.

Reads every row of your numbers log and builds a scorecard for one month or quarter: each metric from baseline to current to target, judged apart on position, pace and freshness. Then it explains what moved in each area and why, names three wins tied to evidence and what stalled, and sets three next moves, each with a metric, a target and a skill to run. Its narrative puts what is behind first.

Request access Have us build it
  • Never writes to your log
  • Narrative leads with what is behind
  • Stale is not behind

At a glance

Group
Daily operations
Command
/business-review
Uses
Your numbers log and strategy
Writes
A review, a snapshot, a Daily line
Sends
Nothing. Drafts only.

01When to use it

Use it when a month or quarter closes.

  • A month or a quarter has ended, or someone asks how you are tracking against your targets.
  • A planning session, a board update or a strategy refresh needs one honest read on progress.
  • You run it on a regular rhythm, so your numbers stay traced and the next review has a fresh snapshot to compare against.

Not for

  • Closing out a single week. Use /weekly-review
  • A one-page HTML view of the numbers right now. Use /exec-dashboard
  • Pipeline coverage, deal aging and the forecast. Use /pipeline-review

02What it needs

A period, your log and your targets.

  • The period: a month such as 2026-05, or a quarter such as 2026-Q2. If you do not name one, it confirms the period before reading anything.
  • Your whole numbers log, every row of it.
  • Your strategy file, for the priorities and targets each metric is judged against. Pace needs a dated goal there; without one, pace reads n/a.
  • Recent decision records, which explain why numbers moved, and the baseline snapshot each piece of work saved in your projects and content folders.
  • The last review's snapshot, if one exists, so the new report can open with the trend.

03What it writes

A report, its snapshot, a line in Daily.

{date}-business-review.md
The review, saved in Operations/reviews/{date}-business-review/ and marked generated. On a re-run it opens with the trend since last time, then the scorecard, movement by area (acquisition, conversion, retention, content and pipeline), the narrative and the three next moves.
data/baseline.json
A snapshot of the period, kept beside the report for the next review to diff against.
Daily note
One line in today's note saying the review was generated, with its headline read.
Signals rows
When an input was missing or stale, or two sources disagreed, a row in your signals queue names it and the source it went with. With clean inputs, the report says so instead.

04Limits

What it never does.

  • Write to your numbers log. It reads every row and changes none.
  • Put a figure in the scorecard that no row supports. A metric it cannot trace is marked stale, and its current value is never filled in from the target, the trend or memory.
  • Call a metric behind when the truth is that nobody has measured it lately. That is stale, and the fix is a measurement.
  • Hide a slipping metric under the wins. A regression leads the narrative.
  • Patch a generated report by hand. A re-run writes it fresh.

What stays with you.

  • Sharing the review. It stays a draft file until a person does.
  • Running the three next moves, and measuring any metric marked stale.

05Sample output

Four metrics, four different reads.

Rows from the 2026-Q3 scorecard of a made-up florist, verdict columns only. A real scorecard also gives each metric its baseline, current value, target and change.

2026-Q3-business-review.md Illustrative, not a client result.
Wedding inquiries 2026-09-26
vs targetBehind
vs paceAhead
Newsletter sign-ups 2026-09-19
vs targetHit
vs paceAhead
Repeat customers 2026-09-24
vs targetBehind
vs paceBehind
Corporate orders Stale, 2026-07-02
vs targetBehind
vs paceOn pace

How the narrative opens

  • Repeat customers regressed: the gap to target is wider than at the baseline.
  • Wedding inquiries trail the target but run ahead of pace, so they need no push yet.
  • Corporate orders have no recent row. The fix is a fresh measurement, not a push.

06Related skills

Often run beside it.

07Questions

Before you run it.

How can a metric be behind and ahead at once?

Behind target describes where the number sits against its target, as of its latest row in your log. Pace compares how much of the gap has closed with how much of the goal window had passed by that metric's latest row. A number can trail its target and still be ahead of schedule.

Does it change my numbers log?

No. It reads every row and writes none. Its own writes are the report, the snapshot beside it and one line in your Daily note, plus a signals row when an input was missing, stale or contradicted.

Does it need Python?

No, though it uses it when it can. With Python 3, a bundled script computes the scorecard, so the same log always gives the same result. Without it the scorecard is built by hand, the report says which way it was made, and a pace verdict is treated as a judgement call.

Have us build it

We can build it for you.

Start with the free plan. A person names the first fix.

Get your free plan Or run it yourself with the toolkit.