Your team already has the quarterly-planning and board-narrative playbooks — the worked recipes for running one planning cycle and prepping one board meeting, step by step. Each is the orchestration playbook that pulls every earlier foundation together, run once. This module is the layer that turns them into a recurring discipline: a plan whose cut list actually holds, and a board narrative built before the slides so the hour in the room goes to decisions, not to surviving an ambush.
It’s Module 5 of the certifiable Founders & PMs track, and it inherits everything you built across the track — product-context.md and market-landscape.md from Module 1 directly, and ideally a roadmap signal from Module 3. M1–M4 mastered the inputs and the moves; M5 is where they get assembled into the two highest-stakes recurring moments a founder runs — and assesses whether the cut list and the narrative hold up under real scrutiny, not whether the slides looked clean.
A plan that commits to everything has prioritized nothing, and a board deck built before the story is settled is forty polished slides with no spine. Both failures share a root cause: skipping the hard, explicit “no” — the cut nobody wants to write down, the uncomfortable number nobody wants to lead with. This module is where that discipline becomes the standard your company’s two highest-stakes meetings meet every single cycle.
The system, not the one-good-quarter
Most founders treat quarterly planning as a meeting to survive and board prep as a weekend of slide-polishing. Neither is a system — the plan ends up shaped by whoever argued hardest in the room, and the deck gets built before anyone has settled what story the numbers actually tell, so a board member fixes on one figure and an hour of careful work turns into a confidence problem.
A planning-and-board engine is two named systems that run the same disciplined way every cycle:
- Plan — lock the frame before generating any candidates, surface initiatives from real evidence grouped into themes, score them with visible reasoning rather than a verdict, then draft the plan and the cut list, and pressure-test the whole thing against real capacity.
- Board — establish the narrative arc before any slide exists, build a metrics-backed outline where every claim ties to a number you supplied, write the one-page pre-read, generate the hard-questions prep, then run a final consistency pass before anything ships.
Each system has one job: the plan turns strategy and evidence into a committed, bounded quarter; the board system turns the quarter’s real story into something you can defend in the room. Run both the same way every cycle and a founder stops re-deriving judgment from scratch every three months.
You run both in the chat. Open your strategy, market, and feedback docs, plus your verified metrics, in Claude Desktop, and work one system at a time — no terminal needed on the main path.
Quarterly planning — the cut list is the artifact
The playbook gives you the steps: set the frame, generate candidates, score them, draft the plan and the cut list, pressure-test against capacity. Mastery is protecting the part everyone is tempted to skip.
- A wrong frame is the most expensive mistake in the whole exercise. Before any initiative gets proposed, make Claude restate your strategy and name the one thing the quarter must move. A plan aimed at the wrong target is worse than no plan — catch the wrong frame here, while it costs one prompt, not a quarter.
- Scores need visible reasoning, not a ranked verdict. A table that shows why each score was given is something you can interrogate; a number Claude hands down is theater. Watch the confidence column hardest — a high-impact, low-confidence bet isn’t a “do it,” it’s a “de-risk it first.”
- The cut list is the most valuable artifact in the plan, and it’s the one founders are tempted to drop. A plan that commits to everything has prioritized nothing. Writing down what you’re explicitly not doing, with a one-line reason for each, is what you point to in week three when a stakeholder asks why their feature isn’t in — protect it, don’t quietly skip it because saying no is uncomfortable.
- Capacity is a reality check, not a formality. A committed list that ignores how many real engineering-weeks you have is fiction with a deadline. Pressure-test the commitments against real capacity before you call the plan final.
A plan that clears this bar reads as one page: 3-4 themes, the committed initiatives under each with a single success metric apiece, an explicit cut list naming what’s deliberately excluded and why, and an honest capacity check with the single biggest risk to the plan named alongside it.
Board narrative — numbers first, slides second
The single biggest board-prep mistake is building slides before the story is settled. The discipline that prevents it is sequencing: arc, then numbers, then slides — never the reverse.
- Lock the arc in three or four sentences before anything else exists. Everything downstream — every slide, the pre-read, the Q&A — inherits this arc. A narrative that isn’t crisp in four sentences will not get crisper at forty slides; it gets buried.
- You supply every number; Claude only structures the story around it. The
[NEED: …]flag for a missing figure is a feature, not a gap to paper over with an estimate — if Claude ever fills in a number you didn’t give it, that’s the most expensive kind of error this discipline exists to prevent. - The hardest questions get rehearsed before the room asks them, not improvised in it. Having Claude play a sharp, skeptical board member and surface the uncomfortable questions — about burn, about a missed target — turns a flinch into a steady answer. The honest answer beats the spun one every time; directors have seen the spin before.
- If the data tells a worse story than you wanted, the story changes — never the numbers. A board sees through an unsupported narrative faster than almost anything else, and the credibility cost is the same as a wrong figure.
A board package that clears this bar produces a locked 3-4 sentence arc, a metrics-backed outline where every slide names its evidence, a genuinely one-page pre-read, 8-10 rehearsed hard questions with honest answers, and a final consistency pass that caught every internal contradiction before the package left your hands.
A note on Arabic boards
If your board, family office, or local investors read in Arabic, this module inherits Module 1’s standard directly: the pre-read and the hard-question answers are authored in Arabic from the same verified numbers, adapted not translated — localized framing and examples so the document reads native, with numbers and financial terms staying consistent across both languages. A pre-read that reads natively in Arabic lands with a Gulf board in a way a translated one never does; the same discipline applies if you reuse this system for a fundraising deck aimed at Arabic-speaking investors.
Your assignment
Run both systems — one quarterly plan and one board (or investor) narrative — for your own company (recommended: the output is the actual cycle you run this quarter) or the sample brand Mizan, the GCC bookkeeping SaaS whose co-founder, Dana Al-Qassimi, runs throughout this track. Open product-context.md, market-landscape.md, your roadmap signal, and your verified metrics in Claude Desktop — no terminal needed.
Module 5 deliverable — planning & the board
Inherits from M1: product-context.md, market-landscape.md
(ideally also M3's feedback-signal.md / decision-memo.md)
1. quarterly-plan.md (the quarterly-planning output)
- the locked frame: north star, who you serve, the ONE thing this
quarter must move
- candidate initiatives grouped into 3-4 themes, each tied to real
evidence
- a scored comparison (impact/effort/confidence) with visible
reasoning per cell
- the committed initiatives, each with one success metric
- an explicit CUT LIST, each item with a one-line reason
- a capacity check and the single biggest risk to the plan
2. board-package/ (the board-narrative output)
- the locked 3-4 sentence arc
- a metrics-backed deck outline, each slide tied to a real number,
[NEED: …] flagged for anything not yet supplied
- a one-page pre-read
- 8-10 hard questions with honest, numbers-grounded answers
- a final consistency pass — every mismatch and unsupported claim
listed and resolved
Confidentiality: every number used is your own verified figure, never
invented; raw financials, the cap table, and customer PII stay in your
approved workspace, not in this draft.The Foundation toolkit holds the product-context.md and market-landscape.md this module’s plan and narrative both inherit directly.
How it’s graded — the rubric
This is the part the free playbooks don’t have, and the part that makes the credential mean something. Your two deliverables are scored against five criteria. Each is meets / nearly / not yet, and a “nearly” on any one is a revise, not a pass.
Planning & board rubric
1. The frame is locked before candidates exist
The "one thing this quarter must move" is named first, and every
theme and initiative traces back to it.
2. The cut list is real
Every excluded candidate has a one-line reason. A plan with no cut
list, or a token one, does not pass.
3. Every board claim ties to a real number
No invented figures anywhere in the outline, the pre-read, or the
Q&A. Missing numbers are flagged [NEED: …], not estimated.
4. The hard questions are genuinely hard
The 8-10 questions include the uncomfortable ones — a missed
target, rising burn, a real risk — not softballs.
5. The consistency pass actually caught something, or confirmed none
The cross-check between the arc, the outline, the pre-read, and the
Q&A is shown, with any mismatch resolved before submission.The discipline is deliberately what a skeptical board member would demand: a plan with no real cut, or a deck built before the story was settled, fails quietly — three weeks into the quarter, or live in the meeting — so it has to be caught here.
The bar, shown — a worked model answer (Mizan)
You don’t have to guess what “meets” looks like. Here’s a passing excerpt for the sample brand — your own doesn’t need to look like this, it needs to clear the same bar. These are Dana Al-Qassimi’s documents, built for Mizan’s Q2 2026 planning cycle and the board meeting covering the May close.
quarterly-plan.md — Mizan, Q2 2026 (excerpt)
Frame: north star is Active Customers (9,460 in May); the one thing
this quarter must move is billing trust — the March incident dented
CSAT from 4.7 to 4.2, and market-landscape.md's wedge depends on being
the GCC bookkeeping product customers trust completely with money.
Themes: (1) Billing Trust — flag-a-charge safeguard, renewal-email
clarity; (2) GCC Compliance Depth — native VAT export; (3) Retention —
Q2 save-flow, informed by Module 3's churn signal.
Committed initiatives: flag-a-charge safeguard (success metric: CSAT
back above 4.5 by end of Q2); native VAT export (success metric: the
7-customer ask resolved, measured by support-ticket volume on the
theme dropping to zero); Q2 save-flow (success metric: logo churn
holds under 1.5%).
CUT LIST: enterprise SSO — real but isolated demand (2 accounts),
product-context.md already excludes enterprise this phase. Custom
invoice branding — one loud account, large effort, doesn't serve the
quarter's one thing. Mobile app — no evidence it's the active blocker
for anyone; revisit if it surfaces in Module 3's next synthesis round.
Capacity check: committed work is ~9 eng-weeks against ~10 available
after support overhead — fits, with little slack. Biggest risk: if the
flag-a-charge build uncovers more billing-pipeline issues once eng is
inside the code, VAT export is the initiative that slips first.board-package — Mizan, May 2026 close (excerpt)
Arc (locked, 4 sentences): We closed May at AED 512,000 revenue against
472,000 spend — net +40,000 — with ARR at 6.1M and 9,460 active
customers. The quarter's defining event was a March billing incident
that dented CSAT from 4.7 to 4.2; we've fixed the root cause and are
shipping a customer-facing safeguard this quarter. The market shifted
toward stricter GCC VAT requirements, which is exactly the wedge we're
positioned to own. We're asking the board for an intro to a
compliance-focused investor and a read on raise timing.
Outline (excerpt): Slide 4 — "Billing trust, addressed" → 11 affected
customers, root cause confirmed and fixed (ties to the engineering
postmortem), CSAT trend 4.7→4.2→[NEED: June CSAT, not yet available].
Slide 6 — "The compliance wedge" → market-landscape.md's wedge
rationale, tied to ARR 6.1M and the Q2 VAT-export commitment.
Hard question rehearsed: "CSAT dropped six weeks in a row — why should
we trust the fix holds?" Honest answer: the root cause was a renewal
job firing twice on a specific date boundary, confirmed independently
by two teams using different methods; the fix changes the renewal
job's idempotency, not just a symptom, and the flag-a-charge safeguard
gives customers a way to surface the next issue immediately instead of
escalating to a ticket. We don't have June CSAT data yet — flagged as
[NEED] rather than guessed.
Consistency pass: confirmed the CSAT figure (4.7→4.2) matches across
the arc, the outline, and the pre-read. Flagged one gap: the outline
referenced "11 affected customers" but the pre-read said "a dozen" —
corrected to the verified 11 in both.What you’ve proven — and what’s next
Clear the rubric and you’ve proven something the free playbooks alone can’t certify: that you can run a quarterly cycle whose cut list survives scrutiny, and walk into a board meeting having already stress-tested the narrative and rehearsed the hard questions. That’s the Planning & Board stage of “Certified Founders & PMs with Claude.”
You’ve now worked all five modules. The capstone — Roadmap-in-a-Box — is where they stop being five separate systems and become one product organization you can prove you can run end to end.
If you’re rolling this across a team, the operating guide is the decision-and-data-safety layer that goes underneath the whole system — and the 30/60/90 rollout plan there is exactly the cadence Modules 1-5 are built to support.