Planning Layer · Year-End Infrastructure · Brief 96
The Annual Review OS:
How Solo Consultants Should Actually End the Year.
Retrospective first, planning second. Most consultants open January with goals disconnected from reality because they skipped the review entirely. Seven-layer framework: financial retrospective (revenue by month, by client, by service type, effective hourly rate — the number almost always produces surprise), client portfolio review with five-dimension composite scoring, positioning and skills review, tool/system review, goal retrospective (the 'abandoned by default' pattern), energy retrospective, and a forward planning layer that converts findings into three strategic priorities. Distinct from the Annual Planning OS — this brief earns the right to plan by running the data first. Updated May 2026.
Updated: May 2026 · Pricing verifiedRetrospective first
Most consultants skip the review entirely and go straight to goal-setting in January. The result is goals that repeat last year's structural mistakes in new packaging — because they were never grounded in what the data actually shows.
Most consultants' intuitions about the year are anchored to the most recent months and the most emotionally salient events — the large win, the difficult client, the month revenue spiked. A data-driven retrospective corrects for recency bias and availability bias by requiring actual numbers for all 12 months. The subjective sense of "how the year went" is a notoriously poor predictor of what the data shows.
Distinct from the Annual Planning OS (Brief 60): that brief covers what to do once you have your retrospective findings — revenue modeling, capacity planning, quarterly review cadence. This brief is about getting the findings right first. The planning layer runs on the model the review produces; without the review, the model stays stale and every downstream decision degrades accordingly. See also the Tech Stack Audit OS for the tooling layer of this review.
Layer 1 — Financial retrospective
Revenue by month, by client, by service type — and the effective hourly rate calculation that almost always produces surprise.
Revenue by month
Monthly totals for all 12 months. How many months were above/below the annual monthly average? Flag any month distorted by timing (large invoice paid in one month for work done across several).
Revenue by client — concentration risk flag
Total billed per client. What % of total revenue came from each? If one client represents >35% of annual revenue, that is a structural risk regardless of how good the relationship is.
Effective hourly rate by client and service type
Total billed ÷ total hours (including scoping, admin, revisions, and communications — not just delivery hours). Most consultants are shocked by this number. See Time Tracking OS for accurate data. Use estimates if not tracked, but note that time tracking is worth implementing in the next year. Key question: which clients and service types generated the most revenue per hour of total effort invested?
Layer 2 — Client portfolio review
Rate every client from the year on five dimensions. The composite scoring frequently surfaces a high-revenue client with a low composite score that you have been unconsciously tolerating.
| Dimension | What to assess | Scale |
|---|---|---|
| Outcome quality | Did the work produce measurable results? | 1–5 |
| Relationship quality | Communicative, respectful of process, easy to work with? | 1–5 |
| Scope discipline | Did engagement stay within defined scope? | 1–5 |
| Referral potential | Has referred, would refer, well-networked in target market? | 1–5 |
| Renewal likelihood | Is there a realistic path to future work? | 1–5 |
Composite score range: 5–25. High revenue + high score = ideal archetype to replicate. High revenue + low score = dangerous dependency on a difficult client. Low revenue + high score = good relationship with growth potential. Low revenue + low score = exit or don't renew. From this data: write 2–3 sentences describing the ideal client profile to pursue next year and 1–2 sentences describing the profile to screen out. These become inputs to forward planning. CRM data from the CRM OS can pre-populate some of these ratings.
Layers 3–6 — The remaining four lenses
Positioning, tools, goals, and energy — each with a specific key question that determines whether next year's priorities are obvious by the end of the review.
Layer 3 — Positioning and skills review
Write your positioning at the start of the year and now. Did they converge (sharper) or diverge (drift)? Run the "turned down" audit: every type of work or inquiry declined, and why. Which do you wish you had said yes to? Which are you glad you turned down? Skills inventory: deployed, developed, requested but unavailable. Key question: did the year sharpen or blur my positioning?
Layer 4 — Tool and system review
Five categories: client-facing (proposals, contracts, onboarding), delivery (project management, files), financial (invoicing, accounting), business development (CRM, outreach, referral), time and capacity (tracking, utilization). For each: did it work reliably? Did you actually use it consistently? What did it cost to maintain? Keep / improve / replace / eliminate. See Tech Stack Audit OS for the full methodology. Key question: which systems paid off their overhead?
Layer 5 — Goal retrospective
Retrieve or reconstruct last year's goals. Classify each: Achieved · Partially achieved · Abandoned (intentional) · Abandoned (default) · Changed. The most revealing finding is usually "abandoned by default" — goals that faded without a conscious decision. Note the absence of written goals as a finding. Key question: what patterns in how I set and tracked goals explain the gap between intention and outcome?
Layer 6 — Energy and capacity retrospective
Which months felt genuinely sustainable vs. depleted? Which client or project types drained energy disproportionate to revenue? Was there adequate recovery time? If the year included a burnout episode, see the Burnout OS for the recovery and prevention framework. Key question: is this operating model sustainable and enjoyable for another year?
Layer 7 — Forward planning layer
Convert retrospective findings into three priorities (not goals) for next year. If the retrospective was thorough, the priorities tend to surface from the data without much deliberation.
Step 1: Extract the top five signals from layers 1–6. These are the facts, patterns, and surprises that should drive next year's decisions. Examples: "My retainer clients generated 3× the effective hourly rate of project clients." "Two clients represented 61% of revenue with uncertain renewal likelihood." "My CRM wasn't used consistently after March and I have no reliable pipeline data."
Step 2: Set three business priorities (not goals) for next year. Each priority is a strategic direction, not a specific target. Limit to three — more than three signals an inability to prioritize from the data. Examples: "Shift revenue mix to ≥60% retainer by Q3." "Reduce client concentration risk by adding two new named clients." "Establish credibility in [adjacent niche] through visible deliverables by mid-year."
Step 3: Set quarterly milestones per priority and monthly targets for Q1. Q2–Q4 targets are placeholders refined in quarterly reviews. See the Annual Planning OS for the full forward planning methodology — revenue modeling, capacity planning, and quarterly review cadence. That brief covers what to do once you have your retrospective findings; this brief is about getting the findings right.
Recommended timing
Run retrospective layers (1–6) in mid-to-late November with 10-month actuals plus estimates for November–December — accurate enough for directional decisions. Run the forward planning layer (7) in early January once December numbers are closed. Two short sessions rather than one large block is easier to protect from client work encroachment. Minimum viable version (2 hours): Revenue by client (30 min) · Client quick-score on relationship quality + renewal likelihood only (30 min) · Three things that worked and three that didn't (20 min) · Three priorities (20 min) · Q1 revenue target and one system to fix (20 min). This is the floor, not the standard.
Get the Solo Consultant OS Blueprint
Five-layer OS architecture, tool selection by practice stage, and automation wiring — free for subscribers.
- Five-layer OS framework
- Tool selection by practice stage
- Make automation scenarios
- Weekly OS Review template
Free for subscribers
No spam. Unsubscribe any time.
Related reading