The workshop

What the workshop actually is

Four sessions that turn AI from a talking point into something your team uses on Monday morning. Read the full outline below, then book a free call if it fits.

Book a free call

The four sessions

Nothing generic. Every session is built around your business, your systems, and the work your team is actually doing.

Session 1: Blueprint

We map how your business runs, where the hours go and which jobs Claude should take on first. You leave with a clear plan for the next three sessions.

Session 2: Set up and first builds

We set Claude up securely on your team's computers, connect the tools you already use, and your team builds its first working assistants on real tasks.

Session 3: Build and embed

We build out the next workflows, fix what isn't working yet and make sure everyone on the team is using it day to day.

Session 4: Review and refine

Two to four weeks later we check what stuck, sort out anything that didn't, and set your next steps. Included, not an upsell.

What each person walks out with

Different roles, different starting points, same expectation: everyone leaves with something working.

Beginners leave with a working AI setup for one recurring job they already own, with the prompts and the checks saved so they can run it again on Monday morning without guessing.
Intermediate users leave with two or three connected workflows running end to end, plus a shared workspace where the rest of the team can see what has been built and pick it up.
Power users leave with a working prototype of an AI-driven internal tool that saves the team hours a week, and enough understanding to extend it themselves as the tools keep changing.

How mixed skill levels are handled in one room

Every person in the room works on a task that fits their level, on their own real work. Beginners are given a well-scoped workflow they can finish inside the session, so they leave with a win rather than a page of notes. Power users are pushed onto something ambitious, usually a workflow that wires AI into a system the team already relies on. Toby moves between them across the day. Nobody is left behind waiting for the group to catch up, and nobody is bored waiting for the group to catch up either.

What the review session covers

Two to four weeks after session three, we come back online and walk through what actually happened. Which workflows the team is still running daily. Which ones quietly got dropped and why. What people extended on their own without being asked. Any open questions that need a fresh answer now that the team has used the tools in anger. If adoption is slipping in one corner of the business, this is where we catch it and adjust, before it becomes the story leadership tells about the whole investment.

What you need ready before we start

Short list. Nothing painful.

A primary contact on your side who can answer questions between sessions.
A list of the tools your team actually uses day to day (CRM, docs, email, project software, whatever it is).
A short list of the workflows you want to test in the workshop — the jobs that eat time or trip people up.
Any internal policy or compliance document your team must work inside (privacy, data handling, financial services rules, contractor rules). We build the workshop around them.

Ready to see if it fits?

A free call is the fastest way to know. No slides, no pitch — just a conversation about your business.