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.

45–60 minutesNo coding8 guided stepsIncluded in Founder-Operator Program and Premium Pack

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

CodexFounder Operating WorkspaceLocal Markdown files

Capabilities

Weekly reviewCombined file analysisNumber reconciliationFounder decisionsPriority settingApproved memoryWorkflow reproducibility

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

Weekly founder review templateThe one-page internal review structure for commitments, learning, business signals, decisions, risks, assumptions, next-week focus, and approvals.Download →Founder workflow run receiptA reusable record of exact inputs, method, checks, missing or conflicting evidence, founder approval, memory decisions, and external-action boundaries.Download →Founder Operating Workspace starterThe portable generic workspace with routing, weekly-review method and checklist, review storage, and reproducibility support; the fictional Sample Venture inputs are linked separately below.Download →Sample Venture guideThe fictional-data boundary and map for the complete Sample Venture practice path.Download →Sample Venture company contextReviewed fictional company facts, assumptions, stage, constraints, and decisions. Copy to `context/company.md` in the extracted workspace.Download →Sample Venture customer contextReviewed fictional customer observations, patterns, contradictions, and unknowns. Copy to `context/customers.md` in the extracted workspace.Download →Sample Venture offer contextReviewed fictional offer scope, assumptions, exclusions, capacity, and evidence limits. Copy to `context/offer.md` in the extracted workspace.Download →Sample Venture research-source indexA dated index of five fictional public-signal records and their limitations.Download →Sample Venture source logFive dated fictional public-signal records with limitations and no claim of real evidence. Copy to `evidence/source-log.md` in the extracted workspace.Download →Sample Venture interview indexA complete index of five dated fictional customer conversations.Download →Sample Venture interview SV-INT-001The first dated fictional customer note. Copy to `evidence/interviews/SV-INT-001.md` in the extracted workspace.Download →Sample Venture interview SV-INT-002The second dated fictional customer note. Copy to `evidence/interviews/SV-INT-002.md` in the extracted workspace.Download →Sample Venture interview SV-INT-003The third dated fictional customer note. Copy to `evidence/interviews/SV-INT-003.md` in the extracted workspace.Download →Sample Venture interview SV-INT-004The fourth dated fictional customer note. Copy to `evidence/interviews/SV-INT-004.md` in the extracted workspace.Download →Sample Venture interview SV-INT-005The fifth dated fictional customer note. Copy to `evidence/interviews/SV-INT-005.md` in the extracted workspace.Download →Sample Venture pricing notesThe fictional pricing decision context, assumptions, capacity constraints, and workbook map. Copy to `workflows/weekly-review/inputs/pricing-notes.md` in the extracted workspace.Download →Sample Venture pricing assumptions workbookThe binary fictional pricing workbook with three reviewable scenarios. Copy to `workflows/weekly-review/inputs/pricing-assumptions.xlsx` in the extracted workspace without converting it to text.Download →Sample Venture canonical lead recordsTen fictional lead states with dated follow-up signals, holds, owners, and next actions but no real contact data. Copy to `workflows/weekly-review/inputs/leads.csv` in the extracted workspace.Download →

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

  1. Open AGENTS.md, ROUTING.md, workflows/weekly-review/METHOD.md, workflows/weekly-review/CHECKLIST.md, and the weekly founder review template.
  2. Record an exact review start date, end date, review date, owner, and the prior review path or `none`.
  3. Choose at most three business questions this review must support, such as what changed, which risk needs judgment, and what deserves commitment next week.
  4. 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.
  5. 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