In 2 days every leader gets a digital twin. In 3 months it does 90% of the department's work
For a company's leadership team
A group of 6–12 leaders, with the CEO in the group. Everyone brings their own work: what eats their evenings and what they never get around to.
Who it is not for. Anyone expecting turnkey development. A simple test: if the owner of the task goes on holiday and nobody is blocked, it is a job for the twin. If ten people are blocked, it is a system, and that takes development.
Sound familiar?
“It works as long as I'm here, right now.”
“We wrote the procedure, and a few weeks later it was buried.”
“People ask a chatbot, and the work gets done the old way.”
Everyone goes through training and nothing changes: they listen and go back to the old way of working. Here everyone leaves with a working agent by the very first Monday, and nobody is left alone with it afterwards.
An agent you trust with your work
The twin does not answer questions; it gets things done: it sorts the inbox, prepares materials, runs tasks, reminds and reports. It takes the work you have trusted it with and asks where the decision is yours. It follows four rules:
1State lives in documents and a task base, not in conversations
Test: close every window — tomorrow the work picks up where it left off.2The twin changes nothing without a declared task
Test: every change has a ticket.3Minor matters arrive as a batch
Three times a day: what is urgent, what is not, which decisions it recommends and will make unless you object.
Test: in a day you answered three batches, not thirty messages.4Trust grows one task at a time
The twin takes the next task once the previous one works.
Test: you can name what it already does on its own and what it takes next.Two parts
Day 1 · why, and what changes
What agents can do today and how an agent differs from a chat. A six-step ladder from “I ask” to “it runs without me for a week” — everyone sees where they stand. Which work to hand over first and what changes for the leader and for the company.
Day 2 · everyone builds their twin
Working with agents, each leader designs a twin around their own work, connects it to where their tasks live and hands over the first tasks. Each leader writes down the list of their department's work and how long it takes today — this is the baseline we compare against later.
After two days: every participant has a working digital twin.
So the twin doesn't fall over in a week
The twin enters day-to-day work one task at a time: first run, corrections, watchdogs — how you learn something broke and what the twin may not do without a human — then a week when it runs without you. Once a month we check how much work it has already taken over. By the end of month three the twin does 90% of the department's work.
A personal engineer for every leader
From the Monday after the bootcamp every participant has their own engineer — a person who works with agents every day. They tune the twin, clear blockers right away rather than at the next meeting, and suggest which work to hand over next. It all runs continuously, with no gaps between meetings.
In three months the twin does the work without you
On day two of the bootcamp each leader writes down the list of their department's work. After three months the twin does 90% of the work on that list. If not, the personal engineer keeps working for free until the twin gets to 90%.
We do not promise a savings figure in advance: we measure what actually happens, against the day-two list.
After three months
- The twin does 90% of the department's work while the leader is busy with other things.
- A before / after record for every task.
- Leaders know what they can demand — from agents and from people — because they have seen it with their own eyes.
- A list of tasks the twin did not take, written so it can be handed to development.
Two cohorts, about a hundred participants
Same programme, same materials, same lead. 70% of participants opened their workspace where someone was asking “what's done?” and “how can I help?”, and 36% where nobody was. That is why every leader gets their own engineer.
Honestly, about the second cohort
The goal was strict: for five participants out of six, the process frees up at least 15 hours a month, confirmed by the participant and their manager. Two out of six were confirmed by evidence. The “before” measurement was not taken back then — now it is part of day two of the bootcamp.
Conditions
| what | why |
|---|---|
| Two weekend days in person, the whole group | the twin is built in those two days; it does not get built in pieces |
| 3–4 hours a week on rollout for three months | people drop out because of workload, not difficulty |
| Your own real work | a training exercise doesn't show what is achievable |
| Five one-off things from IT | without them the twin hits a wall at the first command |
We work in what you already have: Claude Code, Codex, Notion or your own environment. A CyberBrain workspace is optional, priced separately.
Bootcamp and three months
| what | price |
|---|---|
| Bootcamp · 2 weekend days, a group of up to 12 leaders | €4,500 per group |
| Rollout · 3 months with a personal engineer | €500 a month per leader |
Example: a group of 8 leaders — €4,500 for the bootcamp and €4,000 a month for three months. A CyberBrain workspace is not included. In roubles: 450,000 ₽ and 50,000 ₽ a month.
What people ask first
Where is the line between the twin and development?
The line is drawn by who uses the result. The twin takes what lives inside the work of a leader and their closest colleagues: the inbox, materials, tasks, summaries from several exports. Development starts where people who did not build the result depend on it: access rights, integration with your ERP or CRM, a service that must run at night without its author.
Do we need a platform?
No. The twin is built in Claude Code, Codex, Notion or your own environment. CyberBrain is an optional workspace you can add later.
What do we need from our IT team?
Five things, all one-off: a folder for the tools outside corporate folders and sync · installation into the user profile without admin rights · excluding that folder from script and antivirus policies · outbound access to the required addresses, and if you go out through a proxy, its certificate in the system · local ports on the machine itself. Best done before the bootcamp, so day two isn't spent on installation.
What if the twin breaks?
Message your personal engineer — they sort it out right away. Every task gets watchdogs, so you hear about a failure from the twin, not from a client.
And if it hasn't worked in three months?
Then the personal engineer keeps working for free until the twin does 90% of the work on the day-two list. A second bootcamp is not part of the guarantee — it isn't needed.
Tell me about your team
Who these leaders are and what work keeps repeating for them. I'll tell you whether the format fits and when the next bootcamp is.