Academy · Founder OS

The operating system behind the founder.

Brand strategy says who BXS is to the market. This says what BXS is for. Three strategies and a personal operating system, built before the next phase of the business gets priced and staffed.

Sessions

Weeks

~21

Focused hrs

Vault docs

The case

Why this matters right now

You're at an inflection point where the personal context is changing fast. New son. Marriage later this year. Cape Town move. The business is at a pricing and positioning crossover point.

The brand strategy you've already locked describes BXS to the market. It does not describe what BXS is supposed to do for you.

"Brand strategy says who BXS is to the market. Operating Strategy says how the studio runs. Financial Strategy says what it has to produce. The Life and Vision Brief sits above all three and tells them what they're for."

Skip the vision work and go straight to Founder Definition, and you'd be making operational decisions without the criteria to make them against. Should I delegate X depends entirely on what you want your life to look like in three years.

The arc

Three strategies, one personal OS

Fourteen sessions across roughly five weeks. Each is 90 minutes and ends with a written artifact that goes into the vault. Cooling days sit between the heavy blocks. The rhythm app architecture sits in the middle so strategy and personal OS co-design.

🔒

The closure rule

Every session closes on one written artifact. If you can write the document, the session is done. If you can't, you haven't finished it. Hours spent don't count. Mark a session done only when its output exists in the vault.

Reference

Reading, mapped to the work

Documents lock decisions. Books rewire how you think about them. One at a time, roughly a book a fortnight, read across the year not in a sprint. Around 25 listed; the goal is compounding, not completion.

When	Focus	Books
Pre-Sunday	Frame setter	The E-Myth Revisited · Gerber
Weeks 1–3	Systems & operating	Thinking in Systems · Meadows, Buy Back Your Time · Martell, Profit First · Michalowicz
Week 4	Knowledge & rhythm	How to Take Smart Notes · Ahrens (before Session A), Deep Work · Newport (before Session B), skim Building a Second Brain
Q3 long read	Systems applied	The Fifth Discipline · Senge
Q3 quick wins	Variety	Die With Zero, The Systems Bible, The Goal, The Psychology of Money
Q4	Strategic depth	Designing Your Life, Company of One, Play Bigger, 7 Powers, Obviously Awesome, Simple Numbers, An Elegant Puzzle
Slow burn	Reread, fragments	The Almanack of Naval Ravikant, Atomic Habits, Range, The Extended Mind
After Op. Strategy	Tactical ops	The Great CEO Within, Working Backwards

Outputs

What the vault holds by Week 5

01Life and Vision Brief

02Operating Strategy v1 (Sessions 1–5)

03Financial Strategy v1 (Sessions 6–9)

04Integration document (Session 10)

05Rhythm App Architecture (Interlude)

06Information Architecture Map (Session A)

07Personal Workflow Playbook (Session B)

08Personal Financial OS (Session C)

How it runs

Working principles

01All sessions happen inside this Claude project. The project memory compounds across the fourteen sessions. The vault holds the documents.

02Each session ends with a written artifact. No session ends without one.

03Cooling days are not optional. They're where the thinking settles and the contradictions surface.

04Pushback is invited. If anything feels rushed, vague, or aspirational, name it and slow down. The point is a document that holds, not a finished exercise.

05Strategy informs the rhythm app architecture. The architecture informs the personal OS. The personal OS feeds back into Phase 2 of the build.