Note: The following is a composite case study drawn from patterns common among founders and solo product builders who use AI-assisted time blocking. It represents a realistic rather than idealized application of the Themed Block Method.
Marcus runs two early-stage products. One is a B2B SaaS tool for customer success teams with 40 paying customers. The other is a consumer app in private beta with 800 users and two part-time contractors. He does most of the writing, product thinking, and strategic work himself.
His week, before he built a time-blocking system: 50-60 hours of undifferentiated busyness. He was always working. He could never clearly say what had moved forward. Every Friday felt like he’d been spinning plates rather than building anything.
Six months in, his calendar looks different. Not perfect — founders’ calendars never are — but structured in a way that produces consistent output on what matters most.
Here’s how it works.
The Starting Problem
Marcus’s problem wasn’t that he lacked time. It was that his time had no architecture.
A typical day started with email, slid into a customer call, detoured through Slack, surfaced in a product decision meeting at 2pm, and ended somewhere around 7pm with the actual writing he’d planned to do still untouched. The writing — strategy memos, investor updates, product specs — kept getting pushed. Because it was always pushable. Unlike a customer call, a writing block doesn’t have external accountability.
His task list was long and accurate. His problem was execution, not planning — or so he thought. The real problem was that he had planning without structure. He knew what needed doing. He had no reliable system for when.
The First Attempt (And Why It Failed)
Marcus tried standard time blocking first. He bought a premium calendar app, spent a Sunday afternoon building a detailed weekly schedule, and ran it for nine days before abandoning it.
The failure was predictable in retrospect. He had blocked every hour, left no buffers, and underestimated almost every task. By Wednesday of week one, the plan was already fiction. He kept looking at a calendar full of blocks he hadn’t executed and feeling worse rather than better.
He also had no protocol for recovery. When the plan broke, he had nothing to do except improvise — which is what he was doing before, except now he had the added friction of a schedule that was telling him he was failing.
The Redesign
Three changes made the system work.
First: he cut his weekly ambition in half. Instead of blocking every hour, he identified three anchor outcomes per week — the three things that would matter if he looked back on the week on Friday. Everything else was “if time permits.” This forced real prioritization and created a clear signal for success.
Second: he built a theme structure around his actual constraints. His investor calls tended to cluster on Tuesdays and Thursdays. Customer calls were on his terms, so he batched them on Wednesday afternoons. That left Monday mornings and Tuesday/Wednesday mornings as his primary deep work windows.
His themes:
- Monday: Strategic and planning. Weekly setup, product decisions, strategic writing.
- Tuesday morning: Deep work (protected anchor block). Product specs, strategy memos, long-form writing.
- Tuesday afternoon: Investor and partnership calls (already where they were clustering).
- Wednesday morning: Deep work. Second anchor block for the week.
- Wednesday afternoon: Customer calls (batched, not scattered).
- Thursday: Collaborative. Team syncs, contractor check-ins, feedback cycles.
- Friday: Administrative and review. Email, bookkeeping, contractor payments, week reflection.
The theme structure didn’t require renegotiating every meeting. Most meetings were already clustering this way. He just made the structure explicit and started defending it.
Third: he built AI into the daily allocation and re-blocking steps, not the planning itself. The weekly structure was his to design. The AI’s job was the daily execution layer.
The Daily Routine in Practice
Sunday evening (20 minutes): Marcus reviews his three anchor outcomes for the coming week. He pastes his task list into Beyond Time and asks it to:
Given these three anchor outcomes and my theme structure,
allocate outcomes to specific days and suggest a realistic effort estimate
for each one. Flag anything I've likely underestimated.He adjusts the output, puts the anchor blocks into his calendar, and that’s the week’s skeleton.
Each morning (5 minutes): He runs a daily allocation. He pastes the day’s task list and his calendar into an AI conversation and asks it to assign specific tasks to his blocks. The prompt is simple:
Today is [day/theme]. My blocks are [anchor block time, secondary block time, buffers].
My fixed commitments are [any meetings].
Here are my tasks in priority order: [list].
Assign tasks to blocks. For the anchor block, give me exactly one task.
Tell me what I'm probably underestimating.The five-minute conversation produces a concrete daily plan. He reviews it, adjusts it if needed (the AI doesn’t always get the priority weighting right on complex strategic questions), and begins.
Mid-day re-block (when needed, ~2 minutes): Marcus’s investor relationships mean surprise calls happen. A founder he’s considering partnering with calls on Wednesday morning. The anchor block is gone.
Instead of abandoning the afternoon plan, he runs a re-block:
It's 11:30am. A surprise call took my anchor block.
My remaining task list: [paste].
My afternoon: one customer call at 3pm, otherwise free until 6pm.
Rebuild my afternoon. Move the most important anchor block task to the best available window.
Tell me what won't happen today.The AI moves his product spec writing to a 12:30-2:00pm slot (he’s found he can write well after a morning of conversations — the contrast works for him) and defers two lower-priority tasks to Thursday or Friday. Wednesday is not what he planned. But the product spec moves forward.
The Numbers After Six Months
Marcus tracks his weekly outputs loosely — not a detailed time log, but a Friday note about which of his three anchor outcomes were completed. Six months in:
- Weeks where all three anchor outcomes were completed: roughly 60% (up from about 20% before the system)
- Weeks where at least two were completed: roughly 85%
- Average number of “lost” days per month (days where no anchor block work happened): reduced from 8-10 to 2-3
The improvement isn’t magic — it’s structural. He has a clear signal (three outcomes), a protected time window (two morning anchor blocks per week), and a recovery mechanism (the re-block) that prevents single disruptions from cascading into lost days.
He also reports a qualitative change he didn’t expect: less decision fatigue during the day. When something comes in that competes for attention, the theme structure gives him a default answer. “That’s a Thursday thing” is a real response to a real request, not a deflection.
What Still Breaks
Honest accounting requires noting what doesn’t work.
Investor crunch weeks. When fundraising conversations intensify, the theme structure collapses. Three investor calls on a Tuesday morning means no anchor block. Marcus has accepted this as a season, not a failure — he runs a looser version of the system during fundraising sprints and returns to full structure when the sprint ends.
The Friday problem. Administrative Fridays have a tendency to become half-days by early afternoon, especially after a heavy week. He’s moved his weekly review to Friday morning rather than evening, which helps anchor the day but doesn’t fully solve the Friday drift.
Effort estimation for ambiguous tasks. AI is genuinely helpful for tasks with clear scope. For open-ended strategic thinking — “figure out the monetization model for Product 2” — it tends to underestimate wildly, because the task has no fixed ceiling. Marcus has learned to treat these as three-session problems regardless of what the AI suggests.
The Transferable Lessons
A few principles from Marcus’s experience that apply regardless of your role:
Three anchor outcomes per week is enough. More creates the illusion of productivity. Three creates real accountability.
The anchor block is the non-negotiable. Everything else in the system serves the anchor block. If you protect one 90-minute morning block and nothing else, you’ve captured most of the system’s value.
The re-block is more important than the morning allocation. The morning plan is easy to make. The recovery from disruption is where most people fail. Practice the re-block prompt until it’s a reflex.
AI doesn’t make you plan better; it makes re-planning cheap. That cost reduction is the real value. Re-planning under pressure without AI support is cognitively expensive enough that most people don’t do it. With AI support, it takes two minutes, which means you actually do it.
Your action: Before this week ends, write down your three anchor outcomes. Don’t block any time yet. Just identify what three things completing would make the week a success. That’s the foundation the whole system rests on.
The full framework is in the Themed Block Method article. The step-by-step implementation is at how to time block with AI.
Tags: time blocking, AI planning, founder productivity, case study, deep work
Frequently Asked Questions
-
How does a founder realistically protect deep work time?
The key is treating the anchor block as a non-negotiable calendar commitment — visible to everyone, blocked in advance, and defended as actively as you'd defend a board meeting. Most founders who successfully protect deep work do it by scheduling it first, before the day can fill around it, and communicating the block to anyone who might request their time during it. The blocking itself is less important than the social commitment to protect it.
-
How much does AI actually speed up planning for a busy founder?
In practice, AI primarily eliminates the decision-making overhead of replanning — not the planning itself. The biggest time savings come from the re-blocking moments: instead of spending 15-20 minutes figuring out how to restructure a disrupted afternoon, you spend two minutes in a conversation and get a concrete revised plan. Across a week with typical disruptions, this saves 30-45 minutes of planning overhead and reduces the friction that causes people to abandon planning entirely.