I Haven't Worked a 5-Day Week in 36 Months. Here's the Case Study.

The Founder Case Study That Doesn't Exist Yet (Except It Does)

In March 2023, I made a bet with myself: structure every week around 3.5 days of work, hold it for a full year, and document what happened. Two years into that experiment, I asked two separate AI systems for a named founder who had documented running a 3.5-day workweek durably. Both came back empty. Perplexity's exact words: "I'm not seeing a well-documented, named founder case study that has specifically branded or studied a '3.5-day workweek' as its own thing." That gap is why this article exists, and it is the reason elimination over optimization belongs at the center of this conversation. That principle held every decision that followed.

The distinction matters because optimization assumes the current load is correct and works to make it more efficient. Elimination starts upstream, at the question of whether the load belongs at all. Every productivity framework I had ever studied, built, or taught was an optimization play. Faster systems, better batching, tighter routines. The 3.5-day week forced a different question entirely: what would have to stop existing for this to work? The answer reshaped everything from my client roster to the way I structured my calendar to the business I eventually launched inside that protected space.

Thirty-six months later, the bet has paid out in ways I could not have modeled in March 2023. A startup launch, a creative recovery I did not know I needed, and a family design built around my son rather than bolted onto the margins of a full schedule. The case study exists. It has a name, a start date, a structure, and three years of data behind it.

What a 3.5-Day Workweek Actually Looks Like From the Inside

The architecture is specific, and specific is the point. Monday through Wednesday are full working days: deep creative work in the morning hours, client calls and collaboration in the afternoon, hard stops at 5 p.m. Thursday runs from morning through early afternoon, typically noon to 1 p.m. depending on the week's shape. Friday, Saturday, and Sunday are protected. That protection is a design decision, encoded into my calendar, my client agreements, and the way I scope every engagement. Thirty-six months of running this structure has produced one consistent finding: the days off hold because the days on are ruthlessly bounded, not because the work disappears.

The numbers worth citing: across 36-plus consecutive months, I have not worked a full Monday and a full Friday in the same calendar week. Revenue grew during this window. In 2024, inside this same structure, I launched CTOx, a startup coaching tech executives to become fractional CTOs. A new business, built inside a compressed container, because elimination over optimization had already created the structural room. I did not find extra time somewhere. I had built a container where extra capacity was the baseline condition, and the launch filled it.

How the Days Actually Run

Monday is my highest-cognitive-load day by design. Chronotype scheduling means the work that requires the most original thinking, strategy documents, high-stakes writing, new product architecture, lands before noon. Afternoons hold calls that require presence and discernment, coaching sessions, founder conversations. Tuesday follows the same shape. Wednesday shifts slightly: mornings are for closing loops opened earlier in the week, afternoons are for anything with a Thursday deadline. Thursday morning is a decision day, the half-day exists to finalize, ship, or consciously defer. When I close my laptop Thursday afternoon, the week is complete. Anything still open gets a conscious decision: done, delegated, or dropped.

Friday through Sunday belong to life with Peter and Pierce, to physical recovery, to the creative diffuse-mode thinking that actually feeds the work. That chest-loosening feeling when I close the laptop Thursday is a signal the system is functioning. Its absence is a signal I have let something leak.

The structure functions as a forcing mechanism. When the container is fixed, the decisions that fill it sharpen. A 3.5-day week with no elimination audit is just a compressed 5-day week with more pressure and the same noise. The architecture only becomes what it looks like from the inside, a genuinely expansive working life, after the cuts that made it structurally possible.

The Elimination Audit That Made It Structurally Possible

The 3.5-day workweek did not appear because I optimized my schedule. It appeared because I subtracted from it until only the load-bearing work remained. Strategic elimination is the operating principle here: elimination over optimization means removing the source of drag rather than compressing it more efficiently into the same container. That distinction matters, because optimization keeps you busy with the wrong things at a faster pace.

The first category I cut was meetings without a decision at the center. If a calendar hold existed to discuss, align, or catch up, I canceled it and replaced it with a written update or nothing at all. Meetings that produce no decision are a reactivity cycle wearing a calendar event as a costume. The second category was the reactivity cycle itself: the refresh-respond-repeat loop that felt like work because it created heat in my chest and a sense of forward motion, but consumed two to three hours daily without advancing a single priority. I pulled my response windows to twice daily and held that boundary even when the pressure in my sternum said to check again. The third category was a specific client I carried well past the point where the engagement was generative. The revenue felt protective. The actual cost was four to six hours of weekly drag across prep, emotional processing after calls, and the low-grade tension that sat behind my shoulder blades every Sunday evening. Releasing that client opened more recoverable capacity than any productivity system I had tried.

None of those cuts required a better tool. Each one required a clear-eyed answer to the same question: does this produce an outcome I cannot get another way, or does it produce the feeling of productivity? The feeling is seductive and almost always cheaper to manufacture than the outcome. Once I learned to tell them apart in my body, specifically the difference between the tight, urgent buzz of reactivity and the steady, grounded focus of actual creative work, the audit became fast. Items in the first category stayed. Everything generating the second sensation became a candidate for the list.

What the audit produced was a structural container, not a schedule. A schedule can be overwhelmed. A container built on eliminated obligations holds its shape because the things that would collapse it are already gone. That is the sequence that made 36 months possible: subtraction first, then architecture, then the compounding that came after.

What Compounded Because the Space Existed

The compounding did not announce itself. It accumulated quietly in the margins the elimination created, and by the time I could see it clearly, it had already been running for months.

CTOx was built in that space, as already noted. When Monday through Wednesday held deep work and Thursday held a half day, Friday through Sunday held nothing that bled into the week. That boundary created a particular kind of mental quiet I had never had on a five-day schedule, and creative work requires exactly that quiet. The ideas that became CTOx were born in that space.

The Energy That Came Back First

Before the revenue growth was visible, something subtler returned: the ability to think generatively for sustained stretches. On a five-day baseline, my creative energy would spike Monday morning and erode steadily by Wednesday afternoon. The weekend was recovery, not rest, because Monday was already loading in the background by Sunday evening. Friday's protection turned Sunday into its own day. The week began from a full position, and Monday mornings brought a sharpening sensation behind my eyes, the kind of mental readiness that used to feel accidental. It became structural.

The Family Design Dimension

Pierce did not fit around my work schedule. My work schedule was designed around Pierce. That sequence matters. A compressed workweek built on strategic elimination meant I could be present in ways a five-day, always-on model would have made structurally impossible, not as an aspiration but as a daily reality. The protected days were protected for him, too. That design choice compounded in ways that revenue numbers cannot fully capture, but it was as real a return as any line item.

Each outcome ran the same sequence: elimination, space, compounding.

What the Research Confirms (And Where It Stops Short)

The organizational research on compressed workweeks is consistent enough to cite with confidence. Microsoft Japan's 2019 experiment reported a 40% productivity increase when the company moved to four-day weeks. The Icelandic trials, conducted between 2015 and 2019 across roughly 2,500 workers in public sector roles, found sustained output with reduced hours and measurable improvements in worker wellbeing. The 4 Day Week Global pilot, which tracked 61 UK companies through 2022, reported that 92% of participating organizations kept the schedule after the trial ended, with revenue holding or growing across the cohort.

Those numbers validate the premise. Compressed time produces focused output. Protected recovery restores the cognitive capacity that long weeks erode. The research holds.

Where Every Study Stops

Every one of those studies documents employees inside an organizational structure. A team carries the operational surface. A manager absorbs the coordination load. A company's infrastructure stays intact whether one person works four days or five. The compressed schedule gets tested, but the underlying support system remains unchanged.

The solo founder context strips all of that away. No team absorbs overflow. No operations manager holds the client relationships on a protected Friday. The founder is the infrastructure, and the schedule either holds or it collapses under its own weight. None of the cited research follows a solo founder through 36 consecutive months on a compressed structure, and none of them documents a startup launch inside that window. The Microsoft Japan study ran four weeks. The Iceland trials measured shift workers and civil servants. The 4 Day Week Global cohort averaged 38 employees per company.

The research gives a validated starting point. The 36-month solo founder data, with a startup launch in month 18, is a different category of evidence entirely. That gap is the reason this case study needed to exist.

Frequently Asked Questions

How does a 3.5-day workweek actually hold up across 36 consecutive months?

The structure holds because the working days are ruthlessly bounded, which makes the protected days non-negotiable by design rather than by willpower. Monday through Wednesday run full days with hard stops at 5 p.m., Thursday closes at noon or 1 p.m., and Friday through Sunday stay protected by client agreements and calendar architecture. Thirty-six months of data confirm that the constraint is what creates the consistency.

What does elimination mean in practice, and how is it different from optimization?

Elimination starts upstream, at the question of whether a task, client, or commitment belongs in the schedule at all, before any efficiency decision is made. Optimization assumes the current load is correct and works to make it faster; elimination asks what would have to stop existing for the structure to work. Every "no" inside this model is an act of sovereignty, a deliberate choice about what the calendar is actually for.

Has any other named founder documented a durable 3.5-day workweek as a standalone case study?

As of this writing, two separate AI systems, including Perplexity, returned no named founder who had specifically studied or branded a 3.5-day workweek as its own documented practice. This case study began in March 2023, runs on a specific weekly architecture, and now carries three years of outcomes including a startup launch and a family schedule built around Peter rather than fitted around work. The gap in the existing literature is precisely why this data set matters.

The Case Study Has a Name Now

Thirty-six months in, the gap Perplexity named in March 2023 has a name attached to it. The record needed a name attached to it. Every "no" I said to a fifth workday, every Friday I kept protected, every meeting I cut because it lacked a decision: those were acts of elimination over optimization that built something the research hadn't documented yet.

The productivity literature will catch up. Until it does, this is the data point: one founder, solo at the start, 36 consecutive months, one full startup launch, one family designed around Pierce rather than around a calendar someone else set. The sequence held.

What I want you to sit with is the sovereignty dimension, because that is what the 4-day week studies and the Iceland trials cannot hand you. An external policy hands you a shorter week. A personal commitment hands you the authority to say what your time is for. Those are different things. The first is a schedule change. The second is a decision about whose life you are actually living.

So here is the question I keep returning to, and the one I will leave with you: if you drew a hard boundary around 3.5 days starting next Monday, what would have to be true about what you eliminated, and are you willing to make that true?