The weekly review that replaces your status meetings
If your team has fewer than fifteen people and you still run a Monday standup, a Wednesday sales sync and a Friday "where are we" call, you are paying three times for the same information. Most of it is spoken aloud, half-remembered and never written down. A single 60-minute founder weekly operating review, run from one page of numbers, does that job better and gives your team back hours of calendar.
One meeting, one page, fixed agenda
The review works because it's boring in a good way. Same day, same time, same order, same document. For a solo founder it's a meeting with yourself, and it still matters: you are the person most likely to skip the uncomfortable parts.
Pick a slot early in the week, when there's still time to act on what you find. Monday morning or Tuesday morning works for most teams. Invite whoever owns a number. At five people that's everyone. At fifteen it's you and the three or four leads, and everyone else reads the notes.
The page is prepared before the meeting, not during it. Each owner updates their numbers by the evening before. If a number isn't on the page when the meeting starts, it gets marked as missing and the meeting moves on. That one rule removes most of the "let me pull that up" time.
The 60-minute agenda
Adjust the minutes, keep the order.
- Numbers (10 minutes). Five to eight metrics, each with this week, last week and target.
- Pipeline (15 minutes). Sales pipeline and, if you're raising, the investor pipeline.
- Cash (10 minutes). Balance, burn, runway, and anything owed to or by you.
- Decisions (15 minutes). Open questions that need an answer this week.
- Next week's three bets (10 minutes). What the company will push hardest on, and who owns each.
Numbers go first. If revenue is flat three weeks running, that should colour everything that follows.
What to look at in each block
For numbers, choose metrics that move weekly and that someone can change. Revenue or bookings, new qualified leads, activation or usage for your core action, and one quality signal like churned accounts or support tickets. Leave out vanity numbers. Look at the direction and the gap to target, and ask one question per number: is this moving the way we expected, and if not, do we know why?
For pipeline, don't review every deal. Look at what changed since last week: deals that advanced, deals that stalled for more than two weeks, and deals expected to close this month. A stalled deal needs one of three actions: a specific next step with a date, a downgrade in probability, or removal. If you're fundraising, run the investor pipeline the same way. Who moved to a second meeting, who went quiet, which follow-ups are due. Treat investors like a sales pipeline because that's what it is during a raise.
For cash, write down the bank balance, last month's net burn and runway in months. Then check receivables (who owes you money and how late they are) and any large payments coming in the next 30 days. Founders at this stage rarely die from a bad month. They die from not noticing runway shrinking by a few weeks every month. Seeing the number every Monday makes that hard to miss.
Decisions are the point of the meeting
Status updates are what you read on the page. The meeting exists for decisions. Before the review, anyone can add a decision request with three lines: the question, the options, and their recommendation. In the meeting you decide, defer with a date, or kill it.
Write each decision down with an owner and the reasoning. Six months from now you'll want to know why you dropped the enterprise tier or delayed the Android app, and "we talked about it once" isn't an answer. If a decision needs more than five minutes of discussion, it's probably not ready. Send it back to the owner for more homework and put it on next week's page.
Three bets, not a to-do list
The last block is where teams usually slip back into listing tasks. Resist it. A bet is an outcome the company will push hardest on this week, with a named owner and a way to tell whether it worked. "Close two of the four pilots in negotiation" is a bet. "Work on sales" is not.
Three is a deliberate limit. With a team of eight, three bets means everyone knows what matters more than their inbox. At the next review, each bet gets a plain verdict: hit, missed, or partly. Missed bets aren't a disaster, but a pattern of missing them tells you your estimates or your focus are off.
What you can cancel once this is running
Give the review four weeks before you judge it. Once it's stable, look at your calendar and cut the meetings whose only job was sharing status. Keep short daily check-ins if your engineers find them useful for unblocking each other, but stop using them for updates that already live on the weekly page. Keep one-on-ones, because those are about people, not numbers.
The prep is what makes this sustainable. If pulling the numbers takes each owner an hour, the habit will die by week six. Put your metrics, pipeline, cash and decision log somewhere they update as work happens, so the page is mostly assembled before anyone opens it. Nautis keeps your CRM, investor pipeline, financials and tasks in one workspace, which makes that page easier to build, but a well-kept spreadsheet works too.
Start this week: create the one-page template, pick a slot, and run the first review even if half the numbers are marked missing. The gaps will tell you what to fix before the second one.