Back to library
Founder OpsOperator Vault

Founder Weekly Operating Review Pack

A deeper founder review system for decisions, revenue, product, customers, and bottlenecks.

Runtime
45-60 minutes
Difficulty
Intermediate
Format
Founder operating cadence

Example run

The artifact is the proof.

Tested 2026-07-12 · Claude (Fable 5)

Scenario: A $79/mo Shopify bookkeeping tool at $1,027 MRR: one churn this week, a $790 annual upsell waiting nine days on an unsent export sample, and a feature merged but hidden behind a flag.

Sample artifact

From the example run
CONSTRAINT MAP — Time: TIGHT — 15 hrs/wk consulting, but the CSV fix still shipped. Cash: OK — ASSUMPTION: no cash pressure in inputs; confirm runway. Energy: OK. Technical: OK. Customer access: BOTTLENECK — the only live revenue conversation ($790 Beacon annual) has waited 9 days on a sample I never sent. Tiebreak vs time: the sample is a one-hour task, so time didn't block it — sending it moves revenue soonest. MONDAY CARD: build the Xero sample from Beacon's June data and email Priya — done by 10:30, artifact: the sent email with the .xlsx attached, seen by: Priya.

Before

A week that felt productive — two deploys, days of feature work — with no way to see that the only live deal had been waiting nine days on a one-hour task.

After

A memo naming customer access as the single bottleneck, a decision log that killed a VA hire deferred three weeks running, a merged-but-flagged feature correctly scored as not shipped, and a Monday 10:30 card: send the sample.

Run it like this

  1. 01Fill the six inputs, including the one you'd rather skip — personal bottlenecks
  2. 02Paste the run prompt with your inputs into your AI tool and run it in one session
  3. 03Make or kill any decision the log shows deferred two weeks running
  4. 04Confirm exactly one BOTTLENECK survived and all three actions carry its trace clause
  5. 05Copy the Monday action card into your calendar before closing the doc

What you leave with

Useful output, not another chat.

01

Founder memo naming one binding constraint

02

Decision log with a two-week make-or-kill rule

03

Monday action card you can finish by noon

Contents

The working parts.

Best for Solo operators running multiple projects who need focus and visible progress.

Founder memo template
Decision log
Constraint map
Priority stack
Monday action card

Useful for

Weekly founder reviewProject triageAccountability memo