HIVE80lab — Ops notes

Quarterly business review template: one page, one hour

Most small-company QBRs are status theater: a deck assembled over two evenings, presented to the four people who already knew everything in it, ending with the phrase "so, anything else?" and no decisions. The deck is not the problem — it is the symptom. A deck exists to be presented, so the meeting becomes a presentation. A review exists to change what next quarter looks like, so the meeting should be a decision machine with a sixty-minute clock. The template below is the second kind: one page read in advance, one hour in the room, and at least five decisions written down before anyone stands up.

This is the template: the read-first memo that kills the deck, the timed agenda, the five-number scorecard with the amber/red rules, the stop list (the highest-paid ten minutes of the quarter), the one-table money view, decision-log discipline written in the room, and three bets with kill conditions.

1. The read-first memo (replaces the deck)

Circulated at least 24 hours before the meeting, one page, written in about 45 minutes using data you already have. Five parts:

The memo is the meeting. If it does not go out 24 hours ahead, the meeting cancels itself — a QBR without pre-reading is a status meeting wearing a suit.

2. The 60-minute agenda (timed, printed on the memo)

MinutesSegmentThe rule that keeps it short
0–10Scorecard walkAmber gets a question, red gets an owner and a date — today, in the room. Green gets nothing.
10–25What worked / what brokeTwo minutes each, from the memo. Debate goes in the parking lot, not the clock.
25–35The stop listEvery proposed stop needs a name and a date to die. Defending a stop is the same ten seconds as proposing one.
35–50The three betsEach: countable outcome, owner, date, cost. A bet without a number is a wish and leaves the room.
50–55Money tableOne minute per row. Growth faster than revenue is the only red flag that matters here.
55–60Decision readbackThe scribe reads every decision aloud. Undecided items go to the decision log with an owner and a date — never into the air.

3. The scorecard: five numbers, not fifty

Pick the five numbers a buyer of your company would look at first. For most small teams that is: revenue (or billable utilization), cash runway in months, customer churn (or top-client retention), delivery on-time rate, and one number unique to your trade — support first-response, defect escapes, pipeline coverage. Every number gets a target and an actual, computed from data you already keep. The color rules are the whole point:

If a scorecard number cannot be computed from data you already collect, that is the finding: either build the counter (see the daily operations checklist) or admit the number does not run your business.

4. The stop list: capacity is won by subtraction

A five-person team cannot add a priority; it can only replace one. The stop list is the section that pays for the meeting. Rules for it:

The honest measure of a QBR is not what was decided; it is what died.

5. The money table (one table, four rows)

6. Decision-log discipline: write it in the room

Every decision made in the hour gets a line in the decision log before the meeting ends: what was decided, by whom, when, and what it kills. The scribe reads them back at 55:00 — the readback is where "I thought we agreed the opposite" dies, at the cheapest possible moment. Items not decided get an owner and a decision date in the log, which is the difference between a parked item and a hope.

7. The three bets for next quarter

Three, not seven — a small team that is betting on seven things is betting on nothing. Each bet is one sentence with four fields: the countable outcome (a number, not a vibe), the owner (one name), the date (inside the quarter), and the kill condition ("if X has not happened by Y, we stop and say so in the next QBR"). The kill condition is what makes it a bet instead of a hope: it pre-agrees the exit, which is the single hardest thing for an owner to grant and the cheapest thing to grant in advance.

8. Rules that keep it to one hour

9. Five review numbers

Where this fits

The QBR is the top of a ladder that starts daily: the daily operations checklist feeds the numbers, the decision log keeps the decisions from evaporating between quarters, the annual ops budget template is where the money table rolls up to, and once a year the annual security review takes the security slot the QBR deliberately does not cover. If you want an outside pair to run the review and hand back a prioritized fix plan, that is the Small-Team Ops Audit; and when the scorecard's red numbers are operational rather than commercial, the Custom Incident Runbook turns them into procedure.

From the HIVE80lab kit