Four episodes for the founder running on the operator treadmill, doing 65-hour weeks, and noticing that the business doesn't actually scale further by adding hours. Why working harder is a strategy that maps to a specific stage and stops working at the next one. The structural moves that buy time back without dropping output: delegation (the version that works versus the version that produces hand-back loops), elimination (more important than delegation; harder), the calendar architecture that protects the work that compounds. Built for the founder ready to do the harder work of building a business that doesn't require their hourly attention.

The book that treats founder time as a strategic resource rather than an unlimited input. Covers the structural framework: the time audit (the unflattering version), the delegation hierarchy (which work goes first, in what order), the elimination question that most operators skip (because admitting work shouldn't have been done is harder than delegating it), and the calendar architecture that protects the strategic work most founders sacrifice first. Worked examples in services, ecommerce, and software businesses. Built for the founder running a 1-50 person business and starting to notice that they're the bottleneck on every meaningful decision.

The starter list of systems most operators should automate first, in priority order. Customer onboarding email sequence (so the first impression is consistent regardless of when the lead comes in). Invoice and payment reminder cadence (so chasing money stops being a discretionary task). Recurring report generation (so the weekly numbers don't depend on someone remembering to pull them). Customer support FAQ deflection (so easy questions stop eating expensive time). Internal status updates (so meetings stop being status meetings). Each gets the rough effort estimate and the ROI math. Most operators get 8-15 hours a week back from the first three alone.

The structural protocol for protecting the daily strategic hour most founders intend to keep and end up sacrificing first. Walks through the placement decision (not first thing in the morning if that's when calls hit; not after lunch if energy crashes), the calendar enforcement (default-decline rules, the assistant override conditions), the focus environment setup, and the recovery protocol when it gets hijacked anyway. Run weekly for the first month; the protected hour starts to feel structural rather than aspirational. The compounding effect across a year is what most founders don't internalise until they've lost twelve months without it.

The structured guide to recovering meaningful weekly time without becoming a productivity zealot. Covers the time audit (the unflattering version that surfaces where the hours actually go), the elimination question (which work shouldn't have been done at all), the delegation hierarchy (which work goes to which person, in what order), and the calendar redesign that makes the new pattern stick. Worked example tracks 15+ hours recovered for a hypothetical operator. Built for the founder doing 60+ hour weeks and wanting the hours back without dropping output.

Twelve specific time-recovery tactics with the implementation note for each. Batched email response (twice a day, not continuously). Meeting elimination (the third of meetings that should have been a Slack message). The 'no-meeting Friday' policy that protects deep work. Default-decline calendar rule. Inbox triage rules that prevent re-reading. Structured handoff documents that prevent the same conversation from happening three times. Read in twelve minutes. Most operators recognise at least four they could deploy this week. Pair with the 15-hour guide for the structural framework.

Seven recurring patterns that consistently bleed hours out of a working week — most invisible to operators who haven't named them. The unstructured 'quick check' on Slack that costs 23 minutes of refocus. The reactive calendar (filled by other people's priorities, not yours). The handoff that never quite finished, so the work returns to you. The status meeting that's also a planning meeting that's also a working session. Each gets the structural fix. Read time about ten minutes. The recognition is usually the first step; the bundle's other resources handle the implementation.

Eight email lessons that walk an overworked founder through the operator-to-owner transition. By session three the recipient has done the time audit and identified the highest-leverage delegations. Sessions four through six work the harder elimination decisions and the systematisation that makes recovery durable. Sessions seven and eight handle the longer game — what to build after the basic time recovery works. Built for the founder running on hours, ready to do the structural work that lets the business not require those hours.