How much of your business is you remembering things?
01
Tasks in three different tools, and the real list in your head.
02
The diet that keeps starting next Monday.
03
A workout plan you’ve restarted four times this year.
04
The weekly review you’ve been meaning to start since January.
05
A content calendar you set up in March and haven’t opened since April.
06
Revenue that’s doubled while the way you run your week hasn’t changed at all.
There’s a name for these: open loops. Anything unfinished stays active in the back of your mind and keeps taking a little attention, whether you’re working on it or not. One or two is nothing. A few dozen is why you’re tired by 4pm with the important work still not started.
02The Philosophy
The method is named after Kanso — 簡素 — the Japanese principle of simplicity: clarity that comes from removing what doesn’t serve you. Most systems fail because things only ever get added. Half of this work is taking things away.
03The Process
A week. A system. Running by Friday.
01
Days 1–2
Audit
We spend two days on how you actually operate — tools, calendar, energy, everything you’ve started or keep postponing — and put all of it on one list. Most people have never seen theirs written down.
You leave with: every open loop, on one page
02
Days 3–4
Design & Build
Then I build: capture, planning, execution, review, set up in your own tools around how you actually think. Anything on the list that isn’t worth building gets crossed off instead — decided, out loud, so you can stop pretending you’ll get to it.
You leave with: your system, live in your own tools
03
Day 5
Handover
On the last day we walk through the system together until you can run it without me. Everything is documented, and everything from Monday’s list is accounted for — built, or crossed off.
You leave with: full documentation + two weeks of support
Most productivity advice is a book. This is an installed system.
04What Makes This Different
01
The whole operation, end to end
How you capture, plan, execute, and review — plus everything else that decides your output. If training eats three hours a day, we build a routine that fits the schedule you actually have. If breakfast is why your afternoons disappear, that gets fixed too.
02
Built for execution
A beautiful Notion workspace that takes half of Sunday to maintain is procrastination, nicely dressed up. I build the opposite: fewer moving parts, in software you already use, judged on whether the work moves.
03
Half the work is subtraction
Some open loops close because the thing finally gets built. Others close because you look at them properly and decide they’re not worth doing. Nobody offers that second part, and it does about half the good.
04
Implementation, not advice
You don’t get a framework and a wish of luck. You get the thing built, in your own tools, working before it’s handed over.
05
Why a week
Because you already know what you should be doing, and it still hasn’t happened — this kind of project loses to client work every time it’s spread across a month. A week is short enough to actually protect and long enough to finish.
05Who This Is For
Built for people who run everything themselves.
You have real clients and real revenue, and nobody behind you handling operations. The business has grown. The way you run it is still whatever you improvised in year one.
This is for you if
There’s no ops person and no assistant — everything routes through you.
You’ve bought the tools and read the books, and it didn’t stick.
You’d rather pay once to have it done properly than keep tinkering.
You can clear six to eight hours across one week.
This is not for you if
You’re after a template or a quick fix.
You want a report you can read and set aside.
You mostly enjoy trying new productivity apps.
06The First Step
Begin with a conversation.
Every engagement starts with a complimentary thirty-minute consultation. We talk through how you currently operate, what’s been sitting open, and what I’d do about it — whether or not we ever work together.
Thirty minutes
We go through how you work now and where it’s breaking down. The main problems are usually visible within the first twenty minutes.
Real recommendations
You leave with two or three specific changes you can make immediately. Yours to keep, with or without me.
No pitch
If I can help, I’ll say exactly how. If I can’t, I’ll tell you that too — and point you somewhere better.
Engagements are scoped individually. Investment is discussed on the call, once I understand the shape of your work.
07Who Does This
Built by someone who needed it first.
For years I’ve been building, breaking, and rebuilding personal systems — first for myself, then for the people around me who kept asking how I stay on top of more than seems reasonable.
Most of the job is judgment: looking at everything on your plate — the tools, the calendar, the training schedule, what you eat at your desk — and being honest about which parts need a system and which parts just need to go. Most people are two or three decisions away from a much simpler week.
I also build quickly. AI does a lot of the mechanical work now, which is most of the reason one week is enough.
— Adam · Cape Town
08Questions
What people ask before they book.
Every engagement is scoped to the person — the shape of your work, the tools involved, and how much needs to be built. Investment is discussed openly on your consultation, once I understand what you actually need. The consultation itself is free, and you’ll leave with value from it either way.
Around six to eight focused hours across the five days. The deepest involvement is early, during the audit. Mid-week, I build while you work. On Friday, we walk the system together until it’s yours.
Almost never. The system is built in the tools you already use wherever possible — the problem is rarely the tool, it’s that nothing connects. If a change is genuinely warranted, I’ll make the case and you decide.
No. Anything that affects your output is in scope — sleep, training, what you eat, how you plan the day. I’ve built workout routines and meal-prep plans into these systems where they were the real bottleneck. If it decides how much you get done, it belongs on the map.
The systems that failed were templates — someone else’s idea of how you should work. This one is built around how you already work, and everything you were never going to do gets cut rather than built. You also get two weeks of support after handover, because week two is where systems usually die.
Yes. The full engagement runs remotely. I’m based in Cape Town (SAST), which pairs comfortably with Europe, the Middle East, and the US East Coast.
A running personal operating system: capture, planning, execution, and review, wired together and tested against your real week. Full documentation, so the system is yours and not dependent on me. And two weeks of direct support.
09Get Started
Find out what a week would fix.
The first step is a free thirty-minute consultation. Worst case, you leave with two or three useful recommendations and a clearer idea of where your time goes.