DeepWork OS — Weekly Operating System

What it does & who it's for

DeepWork OS is a complete weekly operating system for founders and operators whose calendars keep eating the work that actually matters. It runs on plain markdown files — in Obsidian, Notion (import instructions included), or any text editor — so there's no app to learn, no subscription, and nothing that stops working when a startup pivots or a tool dies. Your planning system lives in files you own. The system is a closed loop of five parts. Monday, the weekly plan turns a quarter-level objective into three priorities with checkable "done means" statements, runs a capacity check so you stop planning weeks that don't mathematically fit, books the deep blocks, and audits every meeting. Each day, a three-minute log tracks the blocks, catches interruptions in a pattern log, and closes with a shutdown ritual so open loops stop following you home. Friday, the weekly review scores the week out of 25 against a strict five-dimension rubric — deep-work volume, priority completion, plan fidelity, meeting discipline, energy — and tells you the single change to make next week. Everything traces up to a quarterly goals tree, and the meeting-cost calculator prices your recurring calendar in dollars per year (the sample calendar for a six-to-eight-person startup comes out at A$213,190 — a number that makes the audit conversations very short). What makes this different from a free template you could sketch yourself is the operational detail: anchored 1–5 scoring rubrics rather than vague reflection prompts, a capacity check that forces the cut before the week starts, tripwire tables in the goals tree that define "off track" in advance, and honest loaded-cost rules for the calculator. It's the difference between a blank page and a system with opinions. It also ships with the part most template packs skip: a 14-day adoption guide that installs the system in layers — daily habit first, weekly loop second, quarterly spine last — with a specific, small job for each day and counters for the four standard ways these systems die (over-templating, skipped shutdowns, priority creep, and treating a low score as failure). Try the live demo first: it's a full sample week, written into these exact templates by a believable founder.

Version history

1. v1.0Latest28 July 2026

Licence & terms

These terms are snapshotted at purchase — what you see here is what applies to your order.

Reviews