One system, and every
person makes it their own

Everyone on your team shapes the same system to their role, their life and how they work, planning with their whole self. Claude holds it, so the week gets lighter instead of fuller.

Book a call

For managers at founder-led companies whose people already have Claude.

Not your typical AI training

Everyone has Claude open
Almost nobody is better for it

Where it is now

Claude arrived as one more thing to keep on top of. People use it because they are supposed to, on a plate that was already full, and Friday lands exactly as heavy as it did before.

What we teach instead

Every session starts from a person's own week rather than from the software. Each one learns how their own work goes, builds something that holds it, and sees the week back in front of them. Claude carries what used to live in their head, and the overwhelm comes down with it.

Five sessions, two hours each

Everyone starts with the Four Languages scan, a short look at where their week goes now, done before the first session. Then the four, in this order, because by the fourth one there is a real week to look at rather than an empty template. The fifth comes only with all five together, and puts the team's best templates in one place for everyone to take.

Each session installs the skills and templates that run it, on their own machine, rather than slides to remember. They keep them and keep using them after the run.

🧠 Your Root File

The system everyone shares, written in their own words.

Everyone gets handed the same blank chat window and is expected to know what to do with it. This is where each person writes down how they work, once.

Their role, their standards, and what a good day looks like for them. Written in the session, by them.
Claude reads it at the start of every session after that, so nobody explains themselves twice to something that begins from nothing.
The training: what to hand over, what to keep, and how to tell when an answer is wrong.

✨ Your Memory

What a person knows about their own work stops living in their head. It sits in one place, and Claude reads it before anyone starts.

A workspace of their own, holding the files their work runs on, so the context is there before they ask for it.
Decisions kept as files, rather than lost at the bottom of a thread nobody can find again in March.
The training: what belongs in memory, and how to ask for something written six weeks ago and get it back.

❤️ Your Rhythm

The routines that hold a day together, including the ones that run on a schedule without anyone starting them.

A morning that sets the day up and an evening that closes it, shaped around how that person works.
The weekly review, and anything that should not depend on somebody remembering, put on a schedule so it arrives already done.
The training: how to change a routine that stopped fitting, instead of quietly abandoning it three weeks later.

The day gets a shape, so it stops being decided by whoever emails first.

💪 Your Dashboard

Where the week actually went, on one screen, by kind of work. This is the loop that makes the next week different from this one.

On their own machine, with no account and nothing leaving it. It is theirs to look at, which is what keeps it honest.
The time tracker is installed in this session too, on their own machine, so the hours on the dashboard are the hours they worked.
The training: reading it without grading yourself, and what to change when it shows you something you did not expect.

Your Marketplace

The templates the team built, in one place for everyone to take.

Four sessions in, each person has templates shaped around their own work, and some of those templates would help a colleague too. In this session the team hands their best templates to each other.

Everyone brings the template they use most, and shows the others how they use it.
The Marketplace opens in the team's own Team Garden, a shared space everyone reaches in the browser, with the shared templates already in it. Anyone can take a colleague's template and install it in their own Claude.
We host the Team Garden for the first month, then move it to the company's own setup with everything in it, theirs to keep.
The training: for one person on the team, how to run the Marketplace, what goes in, when a template comes out, and how to keep it worth opening.

A kick-off, the sessions, and a close

Each session ends with something running that was being done by hand before.

Kick-offWith the management team

What these teams do all day, what is already working, and which people we start with.

The sessionsTwo hours each

Weekly, or on back-to-back days in one week. Up to 10 people, because above that nobody gets looked at.

The closeOne session after

What stuck, what did not, and what to build next. Held once people have used it for real.

A channel open from the kick-off to the close, running under the whole thing, so the question that comes up on day three gets answered on day three.

Cowork or Claude Code, chosen person by person at the kick-off. Same app, same seat, so switching later costs nothing. The full run adds a strategy conversation with the management team, on the company's own voice and the files everyone shares.

What people build with it

Sophie trains emotional intelligence inside companies. The companies she works in will not let her record the sessions, so anyone who missed one was left out. She built the companion that fixes it. She built her live quiz from the root system template too, with a host view and a participant view, and ran it with a corporate team in place of Mentimeter. The dashboard she opens every morning holds the day's plan, who to reach out to, her content pipeline, her funnel, her CRM, and how much she has worked.

"I feel like it takes care of the basis and I can just focus on making it better and bringing in my creativity."

See what Sophie built →

Lavinia runs Livit Hub Bali, Remote Skills Academy and Livit International. A personal site migrated off Squarespace in two hours, a voice guide made from her own writing so Claude writes the way she writes, an assessment for her readers, and a 20 slide framework deck filled in from her real financial statements.

See what Lavinia built →

Everyone in a workshop leaves with the same thing, on their own machine.

Built around your team

Your Root FileWhere the basics get installed. Two hours, one file each, and the training to use it. Always first.

Each session after itMemory, rhythm or the dashboard, taken singly or in any order, on top of the Root File.

All five togetherKick-off, the five sessions, the close, Slack throughout, the strategy conversation, a Team Garden with the team's best templates in it, and one person trained to run the Marketplace.

What it comes to depends on your team, how many sessions you take, and whether you meet online or in person. We work that out together on a call.

Everything each person builds is theirs, along with the skills and templates installed in the sessions. There is no licence and nothing to renew, and running it afterwards costs nothing beyond the Claude seats you already pay for. One session fits a wellbeing budget or a training budget on its own, and the full run is usually split across both.

Start with a call

We work out which sessions your team needs and how to run them, and you decide from there. Nothing is booked on that call.