Make your team fluent
in Claude.

We work with one team at a time — your marketers, your ops group, your leadership — and teach them Claude and Claude Code from the ground up, on their own work. They leave running it in everyday work. We're here to help afterwards, and work on retainer for larger projects when you need us.

A hands-on education that takes your team from zero to one with Claude

This is an education, not a training catalogue. We sit down with one team — no prior experience needed — teach them everything they need on their own work, and take them from never having used Claude to running it independently. Then we stay reachable for the projects they'd rather hand off.

01

We get to know the team

A short call to understand the function, the work, and what good would look like in three months. We tell you honestly whether a workshop is the right move, and if it isn't we say so.

Free
02

Your team learns Claude end-to-end

One to two days on-site, working on the team's real material. Claude, Claude Code, prompting, agents, workflows — taught from the ground up. They leave fluent enough to use it in their day-to-day work the morning after.

1–2 days
03

We build the bigger projects

When the team identifies work they'd rather have built for them — a custom agent, an integration, a multi-team rollout — you commission it on retainer. They brief us; we deliver. No babysitting, no padded hours.

On retainer · as needed

Things we're opinionated about

Capability you keep — not dependency on us.

The workshop is the product. By the end your team owns the skills, the workflows, and the judgement to keep going without us. We'd rather make ourselves optional and earn the bigger projects than meter you for advice.

Built around your team, not a curriculum.

We don't run public cohorts. Every workshop is shaped around your team's real work, your tools, and your sector. You bring the material; we shape the days around it.

One function at a time, on their work.

We focus on a single team — typically 6–12 people — and teach them on the actual work they do every week. Org-wide rollouts built on hypothetical use cases tend to fail; functional fluency compounds.

Starting points, not menus

Every engagement is tailored, but these are the shapes that work repeatedly. The names are descriptive — the actual workshop is shaped around your team.

0→1 Claude Code for a marketing function

8–12 people, marketing or content

The team leaves with three working Claude Code skills owned by named individuals — typically a brief-to-multi-channel-content workflow, a campaign reporting workflow, and a research workflow.

What the team leaves with

  • Three production skills running on their tools
  • Named workflow owners per skill
  • A 90-day adoption plan signed off by the head of function

AI strategy for the leadership team

3–6 senior leaders

A focused half-day for the C-suite or partner group. By the end you have a ranked use-case shortlist, a build/buy/partner call on each, and an owner for the pilot.

What the team leaves with

  • Ranked shortlist of 3–5 use cases
  • Do / delay / don't call on each
  • Named owner and 90-day pilot scope

Process automation for ops & finance

6–10 people, back-office teams

Inbox triage, document extraction, expense and onboarding workflows. The 0→1 engagement is shaped around the team's actual volume — we measure before and after, not vibes.

What the team leaves with

  • Time-study baseline and post-build measurement
  • Two live workflows with mandatory human review
  • A reliability runbook the team can act on themselves

Sector workshops for professional services

6–12 fee-earners or partners

Document drafting, precedent management, lease/contract abstraction, time-recording assist. Tuned to the firm's regulator, voice, and risk posture.

What the team leaves with

  • Workflow for one billable activity, measured against current hours
  • Partner-review interface and approval rate baseline
  • Eval set the firm owns and can extend

Common questions

The questions we hear most often. Don't see yours? Just ask.

What actually happens in the training?

One or two days on-site with a single team, working on your real material, not slides or demos. We teach prompting, agents, and Claude Code from the ground up. By the end the team is using it in their day-to-day, with a 90-day plan they own.

Do we need any technical background?

No. We work with marketers, ops teams, and leaders who've never written a line of code. Everything is taught on the work you already do.

What happens after the training?

The skills are yours to keep. Plenty of teams run with them and never need us again. When a bigger build comes up that you'd rather hand off, like a custom agent or an integration, you can bring us back on retainer, briefed by the team we trained.

What does it cost?

Training is a fixed fee, agreed up front and scoped to the team and the days involved. Larger builds on retainer are quoted per project, with a clear scope and price before we start. No open-ended meters.

Is our data safe?

Yes. We work on your material under NDA, use enterprise-grade security, and never train models on your data. Anything we build can run in your own infrastructure or a compliant cloud.

Where are you based?

Rugby, Warwickshire, right in the heart of the Midlands. We run training on-site across Birmingham, Coventry, Oxford, Milton Keynes and beyond, and work remotely where that's easier.

Tell us about your team

A short call, no pitch. We'll come back within a working day with whether a workshop is the right move for the function and what it would look like in practice.