You built your expertise over a decade. AI changed the operating system. I'll help you REBOOT yours.

REBOOT. PRACTICE. COMPOUND.

REBOOT is a live cohort for business consultants, analysts, and subject matter experts who are done prompting and ready to build. You leave with a Work OS running in your actual job: Claude handles your research, your drafts, and your recurring tasks automatically. One full day back every week. And the system compounds from there.

8 seats $3,500 Applications open

THE PROBLEM

You're already using AI. That's not the problem.

You use Claude or ChatGPT every day. Your emails are sharper. Summaries take seconds. You're faster than most people in your field. In your own mind, you're ahead of the curve.

Here's what's harder to see from where you're standing: that edge is now the floor. Close to 90% of knowledge workers use AI regularly. Most of them are doing exactly what you're doing: open a chat, type a question, get an answer, close it. Every session starts from zero. No memory of the client. No context from last week. No understanding of how you think or write.

The output looks polished. The system hasn't grown.

Your expertise took a decade to build. Watching it become table stakes is a specific kind of professional fear. Most people feel it. Very few address it directly.

Somewhere in your firm, someone has been doing something different. They went slower at first. Built one workflow. Then another on top of it. Taught their AI about their clients, their recurring tasks, their voice. Every session made the next one faster. Every correction became a permanent rule. That work has been compounding for months.

That person, same role, same tools as yours, is running ahead. Their system is growing. Yours is standing still.

Using AI and building a system that runs on AI are not the same thing. Most professionals never make the jump.

REBOOT is how you make it.

THE WORK OS

Claude Cowork, briefed like a colleague.

Think of Claude Cowork as the most knowledgeable colleague you've ever worked with. Instantly capable. No onboarding required. But it knows nothing about you: your clients, how you write, what you do every Monday morning. Every session, you brief it from scratch. It does good work. Next session, you start over.

The Work OS is what you teach it once, permanently.

That system has five parts. You build all five in REBOOT.

Your Work OS · Built on Claude Cowork — Diagram — coming soon

My Voice

Every output sounds like me. My structure, my tone, my vocabulary. Reports, emails, proposals: first draft ready to review.

My Work Knowledge

Claude Cowork knows my clients, my projects, my context. Brief it once. It remembers everything.

My Tools

Connected to the apps I use every day at work. Claude Cowork acts. Work gets done.

Auto-pilot

My recurring tasks run without me. My morning briefing is ready before I open my laptop. The work that used to take hours runs overnight.

Always Learning

My Work OS gets smarter every week. Every correction I make becomes a permanent rule. The system compounds.

These five components are what make it a Work OS.

BEFORE / AFTER

Same job. Same tools. Different Monday.

Joe and Jane are both subject matter experts at a boutique consulting firm. Same role, same Claude Cowork subscription. Here's what separates them.

Joe's Monday starts the way it always does. Inbox. Calendar. Catch up. By the time he's processed everything, it's past noon.

Jane's Monday started last Friday. She didn't work over the weekend: she built a system that works when she doesn't.

JOE · No Work OS JANE · Work OS running
Monday morning Opens five apps to figure out what today looks like. Hours pass before the work can start. One briefing, ready before she opens her laptop. In deep work by 9AM.
Client context Re-explains the client name, project goals, and reference docs. Every session. One command. Context already loaded. Structured summary in seconds.
Research Searches Drive, digs through Slack, pastes into AI. Starts from zero next time. Research space current and queryable. Brief generated automatically.
Writing Edits AI output until it sounds like him. Hopes the AI tells don't show. First draft already sounds like her: her structure, her tone, her vocabulary.
Recurring tasks Same work, manually, every time. Automated routines run in the background. A full day back every week.
Six months later Output is better. System is standing still. System is compounding. The gap widens every week.

Joe and Jane have the same tools. What Jane has is a Work OS.

SIX WEEKS FROM NOW · BY GRADUATION DAY

One full day back every week. Your Work OS running. Then it compounds.

One full day back every week. Here's what it looks like.

Your voice is in the system.

Every report, email, and proposal starts as a first draft in your structure and vocabulary. One skill, running with eight characters. You review; you don't write from scratch.

Your Work OS knows your clients.

One command surfaces a structured brief: client background, open threads, last decisions. Context stacks across every session. No re-explaining from scratch, ever again.

Your morning briefing runs on schedule.

The job ran on Anthropic's cloud while you slept. Inbox triaged. Calendar priorities clear. In deep work by 9AM, before the first Slack message arrives.

Claude owns your recurring tasks.

Research summaries, status updates, weekly reports: documented, automated, not coming back to you. For most consultants and analysts, those tasks add up to roughly one full day a week. That's the day you get back.

Your AI Practitioner Plan is rewritten.

You arrived with a diagnostic. You leave with a roadmap.

When Claude owns the research, the drafts, and the recurring logistics, you stop switching between thinking and administration. The work that requires your judgment gets more of you. That's where expertise compounds.

Six weeks is ignition.
The year after is when it builds.

Every REBOOT graduate gets ongoing access to the AI practitioner community. When Anthropic ships something new, I test it, assess it, and tell you what's worth adopting and what isn't. Best practices from practitioners working across industries. My call on what actually moves the needle — so you're not starting from zero every time the field shifts.

Course updates are free for alumni. The architecture is durable; what runs on it keeps improving.

When you hit a wall — a workflow that isn't working, a system decision you're unsure about — the community and my expertise are there.

The AI Practitioner Plan you graduate with is the roadmap. The community is where you keep building it.

HOW IT'S DELIVERED

Maximum 8 students. 80+ hours of total practice. I review every weekly assignment.

Pre-work: two weeks before the cohort starts.

The first two weeks are yours: no live sessions, no group calls.

You complete three Claude certifications, onboard into the community, and build the first version of your AI Practitioner Plan. Plan for 10 or more hours across those two weeks. You arrive on Day 1 knowing the tools, knowing the platform, and knowing yourself. The course starts building immediately.

For the next four weeks: a 3-hour live group session every week.

Each weekly session is a working session. Students present their work to the cohort, and because every exercise maps to each student's actual job, no two presentations look the same. A consultant's Work OS looks different from an analyst's or a functional consultant's.

I show exactly how my own Work OS is set up at each stage: no secrets, full access. Every decision I made is on the table and explained.

Your AI Practitioner Plan: the thread through the whole course.

You build it before Day 1 as a diagnostic: how you work today, where AI should take over, what you want different in 30 days. Every week it evolves as exercises map to your actual workflow.

By graduation, it's a different document from the one you arrived with: documented automations, reclaimed time, and a roadmap for what you build next.

How the weeks work: practice, submit, get feedback, build the next layer.

Every week you submit your assignments. Expect 15 or more hours across practice, assignments, and exercises. Block a 2-hour slot every workday, plus a couple of deep work sessions on top of that.

I review each submission personally, with feedback specific to your system, your workflow, your decisions. I'm in the community 7 days a week, Pacific time, usually within hours.

One more thing. The Work OS doesn't clock out. Most of my students are parents. Outside of the job, there's a second operation running in parallel: school pickups, shopping lists, the invisible logistics that keep a family moving. The same principles apply. Reclaim a day at home, and you'll feel it more than any salary bump. My wife took the course. Her co-ed soccer team thanks me for it.

Why trust me.

I came to this through a decade of building products at Salesforce, then running a food tech business where execution was everything and overhead was mine to own. That was the Work OS in practice, before it had a name or a course built around it. Full story on the About page →

I eat my own dog food, visibly. The page you're reading right now was built using my Marketing Work OS: drafted in my AI voice, structured with guidance from Donald Miller, Seth Godin, and April Dunford, refined by me. Student intake, course content, quizzes, exercises, community management — all of it runs on the same Work OS principles I teach in REBOOT. My entire business runs on a Work OS. I cancelled my QuickBooks subscription. The accounting runs itself.

Fabrice Talbot

Fabrice Talbot. Founder, AI Practitioner Circle. Engineer, MBA, 10 years product management at Salesforce.

BEFORE YOU COMMIT

This is our first cohort. Here's what you're evaluating instead.

I don't have a wall of testimonials yet. This is the first time REBOOT runs as a public cohort, and I'm telling you that directly because I'd rather show you what I can actually stand behind.

The graduation standard is observable.

You either leave with a Work OS running in your actual job or you don't. The proof is concrete: Claude Cowork owns named, documented tasks. Your voice file is in active use. Your morning briefing runs automatically. Your AI Practitioner Plan is rewritten. Every one is verifiable on graduation day.

If you arrive on graduation day without a Work OS running in your actual job, we'll talk.

The course is built around real knowledge worker workflows.

Every workflow taught maps directly to something a consultant, analyst, or subject matter expert actually does: researching a client, drafting a deliverable, managing recurring communications. I built this architecture on a decade of living that work myself at Salesforce, from the inside.

Built for business users, not developers.

Everything you build is built in Claude Cowork, in plain language: workflows, automations, the full system. No Claude Code, no APIs. That's a deliberate choice: Cowork gives you everything you need, and I designed the course entirely around it. If you've never done anything technical, you're exactly who I built this for.

High-touch by design.

I review every submission weekly against your actual job: your AI Practitioner Plan, your workflow, your goals. The feedback is specific to what you're building, not a generic rubric. I track each student's progress across the whole cohort. That level of attention doesn't scale. Eight students is where it holds.

Before you apply.

$3,500. One full day reclaimed every week, permanently — that math resolves fast. Beyond the numbers: 8 students, three hours of live sessions a week, individual feedback from me on every submission, and ongoing access to the AI practitioner community after you graduate. This isn't a course you finish. It's the start of how you keep building.

You could. It would take considerably longer without structure, accountability, or someone who has already built what you're trying to build. I've compressed that into six weeks of structured practice. Then the community takes over for the year after. Self-directing through this without a structured path is how most people stay at Prompt 101 for months and wonder why the gap isn't closing.

They will. I review new tools myself, share what's worth adopting in the community, and update the course curriculum for active students. The Work OS architecture is durable: the five components don't change because a new model launched. What runs on top of it keeps improving.

REBOOT is built entirely on Claude Cowork. The Work OS we build together — the automations, the voice file, the morning briefing, the connections to your real tools — is native to that platform. If you're committed to ChatGPT, Gemini, or Microsoft Copilot, the course won't translate. Come back if that changes.

REBOOT isn't for engineers or developers. You have the technical path to build this yourself. If you need to learn at your own pace, it won't fit: the course has structure, deadlines, and weekly accountability. YouTube and the Anthropic docs are genuinely useful if that's your mode. The cognitive load is high from Day 1. Every session is an implementation session, and the hours add up fast. It requires 15+ hours a week across six weeks. If work is unusually demanding right now, the next cohort will be there.

Not the right time for August?

There are three ways to stay connected, depending on where you are.

August works, but you need to think first.

Apply anyway. The form takes 5 minutes, and the 15-minute fit call is the right place to ask questions. No commitment until after that conversation.

Next cohort is right, August isn't.

Select "Future cohort" in the application form below. You'll be first in line when the next cohort opens.

Not sure yet.

I write about practical AI for business professionals every week on Substack: practitioner-first, no hype. Worth reading if you want to stay current before you're ready to apply. Read it here →

AUGUST 2026 COHORT · 8 SEATS

Ready to apply?

I review every application personally and respond within 24 hours. If there's a fit, you'll get a link to book a 15-minute call. The seat offer comes after that conversation, reserved for 48 hours.

Fit starts with one question: can this person reach the graduation standard? Real job, real recurring work, time to commit, and the freedom to adopt Claude Cowork as their work OS. Every student in the room affects every other student's experience. That's what I'm protecting.

REBOOT makes one promise: six weeks from now, how you work has changed. Getting there takes work. You build your system in your actual job, session by session, correction by correction. Motivated people who put in the reps leave with a Work OS that compounds. If the timing isn't right, the next cohort will be there.

This field is required.
Please enter a valid email address.
This field is required.
This field is required.

Which cohort are you applying for?

Please select an option.
This field is required.

Are you currently on Claude Cowork?

Please select an option.

No payment now. I'll respond within 24 hours. If there's a fit, you'll get a link to book a 15-minute call. The seat offer comes after that conversation, reserved for 48 hours.