Playbook · Operations Layer · Brief 21
The Weekly OS Review
for Solo Consultants.
Tools without a review cadence are dead weight. The CRM accumulates stale deals nobody follows up on. Invoices go unsent because the manual step never fired. Clients feel unseen because nobody checked in. The Weekly OS Review is the operations layer that keeps every other layer of your Consultant OS alive — not by doing the work, but by surfacing what needs doing and ensuring nothing falls between the systems.
Updated: May 2026 · Seven passes · 60–90 minutes · Copy-paste template includedWhy operations is the missing layer
Three signs you need this before anything else.
Most consultants reach for a new tool when the real problem is the absence of a review cadence. None of these are tool failures — they are operations failures. No CRM, scheduling tool, or invoicing system resolves them independently.
The "what was I doing?" moment
Monday morning, opening the laptop, no clear sense of what's next. The tools have data — the CRM has deals, the inbox has messages, the calendar has gaps — but there's no orientation layer that synthesizes them into "this week matters because of these three things."
The buried deal
A real opportunity from three weeks ago resurfaces in an email thread and you realize you never followed up. The deal is still in "Proposal Sent" in your CRM. The prospect assumed you moved on. The deal is probably dead — not because of the proposal, but because of the silence.
The invoice you forgot to send
Work delivered, work billable in the contract, work unbilled because the manual step — open the invoicing tool, create the invoice, send it — never fired. Revenue earned but uncollected is the most expensive operations failure in solo consulting.
The seven passes
60–90 minutes. Each pass tied to a layer of the OS.
Default cadence: Friday afternoon. Context is warm, the week's loops can be closed, and Monday starts clean. Monday morning works if you prefer orientation over closure. Pick one, lock it to a recurring calendar block, and treat it with the same protection as a client meeting.
The review surfaces work — it doesn't do it. When a pass reveals something that needs doing, add it to next week's task list and move on. The review that takes 3 hours is one where you stopped reviewing and started working.
Pipeline Review
Tool: Your CRM (Pipedrive, HubSpot, or Notion CRM). For every active deal not in Won or Lost, answer one question: what is the next step, and is it scheduled? If a deal has no next-step date, assign one now — even if the step is "wait until X, then check in." Stale deals (no movement in 14+ days) move to a Stuck view: revive, dormant, or lost. Update notes on anything that's moved since last week.
Delivery Review
Tool: Client portal or project workspace (Notion, SuperOkay, SuiteDash). For every active engagement, answer: are they getting what they paid for this week? Check status of in-flight deliverables — anything blocked, overdue, or underdocumented? Identify the one client most likely to feel "I'm not getting enough value" and reach out proactively before they do. Note any scope changes that were discussed but not documented.
Billing Review
Tool: Wave, FreshBooks, or your all-in-one billing layer. Any work delivered this week that's billable but unbilled? Send those invoices now, before anything else. Any invoices outstanding more than 14 days? Send a polite follow-up. Reconcile any payments received this week — match them to the right deals in the CRM.
Acquisition Review
Tool: Newsletter platform + LinkedIn + Calendly/Cal.com. How many new contacts entered the funnel this week? How many discovery calls completed? Newsletter sent this week — yes or no? Any inbound message left unreplied? Reply now or schedule it. Cross-post last week's newsletter issue to LinkedIn if you haven't already.
Stack Health Check
Tool: Make or Zapier automation logs. Quick glance at the last 7 days of automation runs. Any scenarios failed? Any triggers that should have fired but didn't? Any tool subscription notifications, price changes, or platform updates requiring action? Any manual step you repeated more than twice this week that should be automated?
Energy and Capacity Read
Tool: Your calendar + a piece of paper. Look at next week's calendar. Is it full of low-leverage meetings or high-leverage deep work? Rate your energy now (1–10) and identify what you need before Monday. What commitments are you carrying that you'd decline if asked today? Identify the single most important thing next week — the one that moves the business — and block time for it before anything else.
Surface Wins, Patterns, and Newsletter Material
Tool: A "weekly capture" Notion page. One thing that worked this week and why. One thing that didn't and the pattern it reveals. One observation from client work that could become newsletter content (sanitized). One open question you're sitting with. This is the pass most operators skip. It is the pass that compounds most over 12 months.
The template — copy this now
Drop into Notion, a Google Doc, or your notes app.
This is the primary deliverable of this article. The template is minimal by design — the review should take under 5 minutes to open and start. Complexity in the template is friction against doing the review at all.
Where the review fits
Layer 5 of the Consultant OS. The maintenance layer that makes 1–4 compound.
The Consultant OS has five layers. The first four — Acquisition, CRM, Delivery, Billing — are the operating machinery. The fifth is the operations layer that maintains them. Without it, every system accumulates entropy on the same predictable schedule.
Adaptations
Adjust the weight, not the passes.
Lean harder on Pass 2 (Delivery)
Your pipeline is stable. The delivery risk is higher. Spend 20–25 minutes on Pass 2 instead of 15. Pass 1 can be lighter — fewer active deals to track.
Lean harder on Passes 1 and 4
Your pipeline is your livelihood. Passes 1 and 4 deserve 20 minutes each. Pass 2 is leaner — projects close faster and delivery windows are shorter.
Triple time on Pass 7 (Capture)
The patterns from year one become the content, frameworks, and positioning of year two. 30 minutes on capture in year one pays compounding dividends from year two onward.
Lock to first day after disruption
Don't lock to a weekday if your schedule is genuinely irregular. Lock the review to "first morning after travel ends" or "first Monday of each week regardless of what happened." The anchor is what matters.
Failure mode diagnostic
When the review is breaking down.
| Failure mode | Cause | Fix |
|---|---|---|
| "I skipped it last week." | No locked calendar time | Recurring calendar block, protected like a client meeting. If a client asks for that slot, you're booked. |
| "It takes me three hours." | Doing work during the review | The review surfaces; it doesn't execute. When something comes up, add it to next week's list and move on. Immediately. |
| "I'm not finding patterns." | Not enough weeks of data | Patterns emerge at weeks 8–12. Trust the process. The capture pass builds the dataset that makes patterns visible. |
| "It feels like overhead." | Reframing problem | The review is the work. The other work is the byproduct. A practice without an operations layer is just a collection of open tabs. |
Get the Weekly OS Review Template Pack
The Notion-ready review template, the annual retrospective template, and the stack health checklist — free for subscribers.
- Weekly OS Review — Notion-ready template
- Annual retrospective template (Q1–Q4)
- Stack health checklist — 15 signals to check quarterly
- Capture database — pattern-tracking over 52 weeks
Free for subscribers
No spam. Unsubscribe any time.
Related resources