How It Works

We don't run a workshop and leave. We sit on the bench and build.

Every engagement follows the same arc — assess, embed, compound — run by a Forward-Deployed Operator on your executive's real work. No generic curriculum, no sandbox exercises, no slide deck that gets filed and forgotten.

01

Assess & map

Week one

We begin by watching how the executive actually works — not how an org chart says they do. We sit in on the recurring meetings, read the recurring documents, and find the three-to-five tasks where better AI fluency would change the most.

A usage audit

Where they are today: what they reach for, what they avoid, where they're the bottleneck.

A tailored 30-day plan

The exact workflows we'll build, in priority order, mapped to their week.

A curated path

Only the materials, examples, and outside resources worth a senior leader's time. Nothing padded.

02

Embed & build

Weeks two onward

This is the difference. We coach on the real work as it happens — research, writing, analysis, synthesis, automation, agents — and we build the systems with them. Claude Projects, custom Skills, scheduled tasks, integrations, custom agents. Your executive is left with working systems, not assignments.

Because our operators write the code and wire the integrations themselves, there is no engineer in the loop and no waiting. And because they're available daily — in meetings, over Slack, on-site, in writing — the new way of working has somewhere to go the moment a question comes up.

A typical first 30 days
Week 1Assessment complete · first workflow live
Week 2Two recurring tasks replaced
Week 3Custom Skills + scheduled tasks running
Week 4A daily routine that holds without us
03

Compound

Ongoing

Every workflow we build becomes a documented playbook. What works for one leader is handed to the next — across the leadership team, then the wider organisation. Fluency moves from the top down, office hours and workshops keep it sticky, and each engagement sharpens the playbook library that powers the one after it.

The result is not a one-time training event. It is a capability that keeps growing after we've stepped back.

What we make them fluent in

Use cases

Research at depth, faster

Writing — memos, briefs, board prep

Analysis & synthesis of large material

Workflow automation

Agent-assisted work across systems

Surfaces

Claude & Claude Projects

Claude Skills

Claude Code

Cowork — scheduled tasks & connected apps

MCP integrations & the API

See what this does to a leader's week.