Tutorial 11 · Beginner
Run a Weekly Founder Review
Turn a bounded week of reviewed business evidence into an owner-reviewed one-page internal review, a small set of founder decisions, and reproducible next-week commitments without hiding uncertainty or taking external action.
You will build
An internal one-page weekly founder review with reconciled numbers, visible gaps and conflicts, decisions, risks, up to three owned commitments, explicit non-priorities, and a complete run receipt
You will strengthen
Reviewing a week honestly, separating facts from interpretations, making bounded founder decisions, and maintaining an owner-approved operating memory
Learning map
Tools and capabilities
Tools
Capabilities
Before you begin
What you need
- Codex in the ChatGPT desktop app or another Codex surface
- The extracted Founder Operating Workspace
- Reviewed files from your real business, or the separately linked complete Sample Venture fallback
Practice assets
Download what you need
Step-one preview
Define the review window
Objective
Set the review dates, owner, questions, and internal-only completion boundary before collecting evidence.
Try it now · In the extracted Founder Operating Workspace and a new Codex conversation
- Open AGENTS.md, ROUTING.md, workflows/weekly-review/METHOD.md, workflows/weekly-review/CHECKLIST.md, and the weekly founder review template.
- Record an exact review start date, end date, review date, owner, and the prior review path or `none`.
- Choose at most three business questions this review must support, such as what changed, which risk needs judgment, and what deserves commitment next week.
- Use your real business by default when the bounded inputs are reviewed and safe to use; otherwise choose The Sample Venture as the complete fictional path.
- State that completion is one founder-reviewed internal page and a run receipt: do not publish, share, send, purchase, recruit, change an external system, or perform any other external action.
Visible result
You can see a dated review window, one owner, no more than three questions, one complete real or fictional route, and an internal-only boundary with external actions set to none.
Completion check
I defined the review start date, end date, review date, owner, questions, route, and internal-only completion state.
If you get stuck
Stop, choose one exact week and owner, reduce the questions to three, and restate the output and external-action boundary.
I’m stuck on this step