Method
How the 12 weeks work.
By week 12 you present one AI pilot, built from your own agenda, and defend it unscripted when the questions come. The room turns to you on AI, because you earned it in the work, not the slide. Here is exactly what happens between now and then. No curriculum, no other people's examples. Your calendar is the material.
- Phase 1 · Weeks 1 to 4
The diagnostic block
We start with your actual workflows: the reading pile, the board prep, the decisions that eat your evenings. You build working AI workflows on those, with Marian, in the room. In parallel, we scope the pilot: one problem from your own agenda worth twelve weeks.
Week 4 is the Scope Gate, and it is a feature, not fine print. You either hold a working workflow plus a pilot scope you would sign, or we stop and you pay for the diagnostic block alone. Nobody drifts into month three hoping it gets better.
- Phase 2 · Weeks 5 to 8
The build
The concierge expert team builds the pilot between sessions. Your weekly session stays hands-on and stays on your workflows, not on demo material. You make the calls the pilot needs: scope cuts, data boundaries, what good looks like. The team turns those calls into a working pilot before you meet again.
- Phase 3 · Weeks 9 to 11
Hardening and the message
The pilot gets hardened: edge cases, failure modes, the follow-up questions a board or a journalist will actually ask. In parallel, the communication gets drafted on what you did, not on talking points. Town hall, internal memo, board note. In your words, because the work underneath them is yours.
- Phase 4 · Week 12
You present
You present the pilot as yours, because it is. You defend it unscripted, since you made every decision inside it. From here, when AI comes up, the company looks to you, because you are the one who actually did it. Then the handover: your team gets the pilot, documented, and takes it from there.
Cadence
What a week looks like.
One half-day session, in person, Prague. Marian across the table, working on your real agenda.
Between sessions, the concierge team builds: the workflows and pilot pieces you agreed on, ready for you to test next time.
From you, about an hour of async across the week. Reviewing what the team built, answering scoping questions, making the small decisions that keep the build moving. All in: about 5 hours a week.
Compliance
The two modes.
Sanctioned-stack
We work inside your approved tools and your IT and compliance rules. Nothing enters the workflow that your security team has not already signed off. For a bank executive that means no new vendor review, no exception requests, nothing to explain to compliance afterwards. The trade-off is honest: approved stacks usually run a step behind the frontier.
Sandbox
Frontier tools, on realistic but non-sensitive material. Nothing sensitive leaves the room, because nothing sensitive enters it. You see what the current best models do at full strength, then decide what to take inside and how.
Who picks: you do, before week one. If you want your CISO's view first, bring them to the intro call.
Guarantees
Three, plainly.
Under 7, free. You rate every session. Anything below 7 out of 10, you do not pay for.
The Scope Gate. Week 4: a working workflow and a pilot scope you would sign, or we stop and you pay for the diagnostic block alone.
Discretion. Nothing about the engagement exists publicly unless you activate public mode. Who knows inside your company is your call too.
Half a day a week. Twelve weeks. One pilot, so that what you say about AI is true. The intro call is 30 minutes, with Marian, private.
Book an intro call