Founder operations · Business fundamentals
A Weekly Operating System for a Small Founder-Led Business
The point of a weekly review is not more reporting. It is to notice a constraint early enough to make a cheaper decision.
- Originally published
- September 5, 2026 by Matt Herrera
- Reviewed and updated
- September 5, 2026 by Matt Herrera
Keep one operating record
Use one current page or dashboard for the few numbers that govern the business: cash available, cash due, qualified pipeline, work promised, work delivered, and unresolved customer issues. Each figure needs an owner and a source. A number nobody can reproduce is not yet an operating metric.
Keep the financial records required for the business separately and accurately. The weekly view is a decision layer, not a substitute for bookkeeping, tax records, or professional advice.
Review in the order risk arrives
Begin with cash and obligations, then customer commitments, delivery capacity, and pipeline. This order prevents an exciting sales update from hiding a payroll, fulfillment, or service problem. Mark exceptions that require a decision rather than narrating every normal activity.
- What changed since last week?
- Which promise is at risk?
- What is the single binding constraint?
- Which decision has an owner and due date?
- What will we stop doing to create capacity?
Close the loop
End with a short decision log. Record the decision, the evidence used, the expected result, the owner, and the date for review. At the next meeting, compare the result with the expectation. That habit turns ordinary operating work into company-specific knowledge instead of repeating the same debate.