12 Week Year Examples: 5 Real Plans for Different Goals

Why examples matter more than templates

The 12 Week Year, based on the book by Brian P. Moran and Michael Lennington, is deceptively simple to describe: pick one to three goals, break each into weekly tactics, score every week, aim for 85% completion. But describing the structure and actually filling it in are different problems. The book's own examples lean heavily on sales contexts, and the most common question from people trying the system for the first time is some version of 'what does a real plan actually look like for my situation?'

Templates help with shape — and we have a free 12-week plan template if you need one — but shape is rarely the bottleneck. The bottleneck is writing goals that are specific enough to measure and tactics that are concrete enough to score. A worked example does something a blank template can't: it shows the reasoning behind each line, so you can translate the logic rather than copy the words.

The five plans below span deliberately different domains. None is a real person's confidential plan, but each is built from patterns we've seen work repeatedly. Read the one closest to your situation first, then scan the others — the structural similarities across all five are the real lesson, and we'll call them out explicitly in the section after.

Example 1: SaaS founder growing from $15k to $25k MRR

Vision: I run a profitable SaaS company where revenue growth comes from a repeatable acquisition channel, not founder heroics, and I have the financial runway to hire my first full-time marketer by Q3.

This founder has a product with decent retention but no predictable top-of-funnel. The 12-week cycle is about building that channel, not fixing the product. Two goals, each with a clear lag measure: (1) Reach $25k MRR by week 12 (current: $15k). (2) Publish 12 pieces of search-targeted content with at least 3 ranking on page one by week 12.

Goal 1 tactics, weekly: Run 3 new cold outreach sequences to ICP accounts (Mon/Wed/Fri). Respond to every trial signup within 4 hours on business days. Ship one product improvement tied to the top churn reason (due each Thursday). Hold one 30-minute demo with a qualified lead. Goal 2 tactics, weekly: Publish one blog post targeting a validated keyword (due Wednesday). Build 3 backlinks via guest posts or partnerships. Share 3 distribution posts across LinkedIn and relevant communities.

A good scoring week: 85%+ means you hit at least 5 of 6 tactic lines. The founder might miss the backlink target one week (hard to control timing) but nail everything else. That's a scoreable week, and the lag measure — MRR — will move over the twelve weeks if the lead measures stay consistent. If MRR stalls despite high execution scores, the tactics are wrong, not the effort, and that's exactly what the weekly scorecard is designed to surface.

Example 2: Sales rep targeting 120% of quarterly quota

Vision: I consistently exceed quota through a disciplined pipeline process rather than end-of-quarter scrambles, and I'm positioned for promotion to senior AE by year-end.

Sales is where the 12 Week Year was born — Moran and Lennington developed the system coaching sales teams — so this example should feel closest to the book's original intent. One goal: Close $480k in new business by week 12 (quota: $400k, stretch: $480k). The lag measure is closed revenue. The lead measures are pipeline-building activities the rep fully controls.

Weekly tactics: Make 50 prospecting touches (calls, emails, LinkedIn messages) — tracked daily, scored as a weekly total. Book 5 new discovery calls. Send 3 proposals to qualified opportunities. Follow up on every open proposal older than 5 days (Sunday evening prep). Spend 30 minutes on Thursday reviewing the pipeline and updating CRM stages. Attend one internal deal review or coaching session.

A good scoring week: the rep completes 5 of 6 tactics. The follow-up tactic might not apply every week (no aging proposals), and the system handles that cleanly — mark it complete if there was nothing to follow up on, or exclude it from the week's count. The sales rep template has a pre-built version of this plan with the scoring logic already set up. What matters most is that the prospecting touches and discovery calls happen every week without exception — those are the lead indicators that fill the pipeline that produces the revenue that is the lag measure.

Example 3: Runner training for a half-marathon in 12 weeks

Vision: I cross the finish line of the October half-marathon healthy, under 2 hours, having trained consistently enough that race day feels earned rather than survived.

Fitness goals translate unusually well to the 12 Week Year because the lag measure is concrete (finish time), the tactics are physical and unambiguous, and the 12-week timeline matches most training plans naturally. One goal: Complete the half-marathon in under 2:00:00 (current best pace projects to roughly 2:10). The lag measure is race-day finish time.

Weekly tactics: Complete 3 weekday runs per the progressive training schedule (Tuesday, Wednesday, Friday — distance increases weekly per the plan taped to the fridge). Complete 1 long run on Saturday (distance per schedule). Do 2 strength/mobility sessions (20 minutes minimum — bodyweight or gym). Log every run in the tracking app within 1 hour of finishing. Take 1 full rest day (Sunday) — yes, rest is a tactic, because skipping it leads to injury that destroys the whole cycle.

A good scoring week: 5 of 5 tactics completed. This plan is unusual because every tactic is genuinely weekly and binary — you either did the Saturday long run or you didn't. A runner scoring 80% most weeks (missing one run per week) will still finish the race but probably won't hit the time goal. The 85% rule is especially visible here: consistent 85%+ weeks compound into fitness; sporadic 60% weeks don't, even if the total mileage somehow matches. Rest as a scored tactic is worth emphasizing — it reframes recovery from laziness to discipline.

Example 4: Writer finishing a first draft in 12 weeks

Vision: I hold a complete 60,000-word first draft of my novel by week 12 — not a perfect draft, but a draft that exists, which is more than I've managed in three years of 'working on my book.'

Creative projects are the hardest to fit into any execution system because the work resists decomposition — you can't always predict whether Tuesday's writing session will produce 500 words or 50. The trick is making the tactics about the controllable input (sitting down, for a defined duration, on the scheduled days) rather than the unpredictable output (word count per session). One goal: Complete a 60,000-word first draft by week 12 (current: 8,000 words — roughly 4,350 words per week needed).

Weekly tactics: Write for 90 minutes before checking email on Monday, Wednesday, Thursday, and Friday (4 sessions). Hit a weekly word-count floor of 4,000 words (scored Saturday — this is the one output metric, deliberately set below the pace target to account for hard weeks). Outline the next chapter before starting it (one outline per week, due Sunday evening). Read for 30 minutes on Tuesday and Saturday (craft input — not optional, not a luxury). Review the week's draft for 20 minutes on Saturday and note what's working (the writing equivalent of the weekly review).

A good scoring week: 4 of 5 tactics completed. The word-count floor is the tactic most likely to be missed, and a miss there is diagnostic: was it because you skipped sessions (execution problem) or because the sessions were unproductive (creative problem, different fix). The four writing sessions are the real lead measure — track those relentlessly, and the word count follows over twelve weeks. Writers who try to score on daily word count alone burn out or game the metric; scoring on sessions-completed plus a weekly floor is more honest and more sustainable.

Example 5: Freelancer escaping feast-or-famine

Vision: I have a sustainable freelance practice with a 3-month pipeline of booked work, steady monthly income above $8k, and I never again spend a panicked week scrambling for the next project because I stopped marketing the moment I got busy.

The feast-or-famine cycle is a perfect example of a problem the 12 Week Year is built to solve: the freelancer knows exactly what to do (keep marketing even during busy periods), knows why they don't do it (client work fills every available hour), and has failed repeatedly not from ignorance but from inconsistent execution. Two goals: (1) Maintain a rolling 3-month pipeline of $24k+ in booked or near-signed work by week 12. (2) Raise effective hourly rate to $125/hr by eliminating or repricing sub-$100/hr engagements.

Weekly tactics: Send 5 warm outreach messages to past clients, referral sources, or new prospects (Monday batch). Publish 1 portfolio piece, case study, or LinkedIn post showcasing recent work. Spend 1 hour on Friday reviewing the pipeline spreadsheet — total booked, total pending, total needed. Submit 2 proposals for new work (even during busy weeks — this is the tactic that breaks the cycle). Track hours per project and flag any engagement running below $100/hr effective rate. Block 2 hours on Wednesday morning as non-client strategic time (time blocking is what protects this from getting eaten by deadlines).

A good scoring week: 5 of 6 tactics. The one most likely to slip is the 2-proposals tactic during a busy delivery week, and that's precisely the one that matters most — the common failure modes chapter calls this 'the urgency trap,' where important-but-not-urgent work (pipeline building) loses every fight with urgent-but-not-important work (this week's client fire). Scoring this tactic weekly, visibly, is the mechanism that breaks the pattern. If you're a freelancer considering this approach, the action plan template can help you structure the tactic breakdown.

What all five examples share: the structural patterns

Read across the five plans and several patterns emerge that aren't accidental — they're what separates 12 Week Year plans that work from plans that look good on paper and collapse by week four.

Every goal has a number and a deadline. Not 'grow revenue' but '$25k MRR by week 12.' Not 'finish the book' but '60,000-word draft by week 12.' The number makes the goal measurable; the deadline makes it urgent. Together they produce the lag measure — the thing you'll check at the end to know whether the quarter worked. The goal-setting template enforces this format if you're struggling to nail it down.

Every tactic is scoreable as yes/no or count-based. 'Do marketing' is not a tactic. 'Send 5 warm outreach messages by Monday EOD' is a tactic. The test from writing tactics is simple: on Friday, can you answer 'did I do it?' without judgment or interpretation? If the answer requires a paragraph of context, the tactic is too vague. Every example above passes this test, and that's not a coincidence — it's the single most important quality of a 12-week plan.

Lead measures dominate, lag measures are checked but not scored weekly. The SaaS founder scores outreach touches and content published (lead), not MRR (lag). The runner scores sessions completed (lead), not pace improvement (lag). This distinction, covered thoroughly in lead vs. lag indicators, is the structural insight that makes the system work: you can control whether you make 50 prospecting calls this week; you cannot control whether any of them close this week. Score what you control.

The plans are small. No example has more than two goals or more than six weekly tactics. This feels like not enough — surely a SaaS founder has more than two priorities? — but that's the book's core bet: depth of execution on fewer things beats shallow execution on many things. An execution score of 85% across five tactics means you're doing roughly four things consistently, every week, for twelve weeks. That's 48+ completed actions. Plans with twelve tactics produce scores of 50%, which produce nothing.

What makes a bad example (and how to fix it)

The most common bad plans share three features, and recognizing them is as useful as seeing good examples. First: vague goals disguised as specific ones. 'Improve my marketing' sounds directional but has no lag measure — improved compared to what, measured how, by when? The fix is always a number: '$25k MRR,' '60,000 words,' '3-month pipeline.' If you can't attach a number, you may not have a goal yet — you have a direction, and you need to spend more time in the goal-setting process before building the plan.

Second: unmeasurable tactics. 'Work on business development' appears in more failed 12-week plans than any other phrase. You cannot score it — did you 'work on' it for five minutes or five hours? Did you think about it while jogging? The fix is always the same: make it binary or countable. 'Send 5 outreach messages' is measurable. 'Have 2 sales conversations' is measurable. 'Work on sales' is a wish wearing a tactic's clothing. The writing tactics chapter has a complete diagnostic for this.

Third: too many goals. The person who writes five goals for a 12-week cycle is telling you they haven't made a decision about what matters most. The 12 Week Year isn't a productivity system for doing more things — it's a focus system for doing fewer things completely. If you genuinely have five priorities, stack-rank them, pick the top two, and put the others on a 'not this quarter' list. The discipline of saying no to good goals so you can say yes to the most important ones is the hardest part of planning, and the strategic planning template can help you work through the tradeoffs.

A useful self-test before starting your cycle: hand your plan to someone unfamiliar with your work and ask them to score a hypothetical week. If they can't tell whether each tactic was done without asking you clarifying questions, the plan isn't ready. Rewrite until a stranger could score it. Use the free 12-week plan generator to pressure-test your draft — it will flag vague language and missing measures.

Building your own plan from these examples

Start by picking the example closest to your situation and rewriting it in your own words. Don't copy the tactics literally — the SaaS founder's '3 outreach sequences' means nothing if your business runs on inbound content — but copy the structure: a vision sentence that makes the work feel worth it, one or two goals with numbers, and three to five tactics per goal that you can score on Friday without ambiguity.

Then run the plan through the tests from the previous section. Is every goal numbered and deadlined? Is every tactic binary or countable? Can a stranger score your week? If yes, you have a working plan. If no, you have a draft, and drafts are normal — most good plans take two or three revisions before they're tight enough to execute. The 12-week plan template gives you the structure, and the quarterly planning template helps if you want to set the plan in a broader context.

The plan is the easy part. Execution is the hard part, and execution means scoring every single week for twelve weeks — not perfectly, but consistently. The weekly scorecard chapter covers how to read your scores as diagnostic data rather than grades, the model week chapter shows how to build a weekly rhythm that protects tactic time, and the execution score calculator lets you compute your score right now if you've already started.

If you want to go from example to live plan in a few minutes, the 12-week plan generator will take your goal and draft a scored tactic structure you can refine. And if you want the scoring, reminders, and accountability built in rather than bolted on, Pilot runs the entire weekly loop for you — so you can focus on the tactics instead of the tracking.