1:1 Claude coaching

See what you could build.

There is a version of your work where the tedious parts run themselves and the ideas you keep parking actually get built. These sessions show you that version — live, one to one, with your own work on the screen.

90 min
Working session, screen shared, your files
1 to 1
No cohort, no curriculum you sit through
Day one
You leave with something that runs, not notes
01 — The imagination gap

The barrier isn't the technology.

You already know what Claude is. You've read the threads, you've watched someone demo it, you have an account open in a tab. And still, nothing has moved.

That's not a knowledge problem. Desire follows awareness — you can't want a thing you've never seen work. Before you watch an app materialise from a paragraph of plain English, before you watch a messy pile of thinking turn into structured output, the whole category of things I could build is a missing category, not an empty list.

Everything before that moment is persuasion. Everything after it is momentum. The work of these sessions is to get you to the moment.

02 — Coaching paths

Four ways in.

Pick the one that matches where you're stuck. Most people start with the first and don't stay there long.

PATH 01

The first jaw drop

One session. You bring a real piece of your work — a spreadsheet, a process, a document nobody wants to write. We build the thing live. You watch the blank space fill in.

Best for: never got past the chat box
PATH 02

Build your first thing

Four sessions across a month. We take one idea from a paragraph to something you actually use on a Tuesday — and you drive, while I sit next to you.

Best for: an idea you keep not starting
PATH 03

Into the ecosystem

Projects, artifacts, connectors, the API, agents that run without you. The parts past the chat window, taught against your own workflow rather than a demo dataset.

Best for: fluent in chat, stuck at the edges
PATH 04

Bring your team

You've had the moment and now you have to give it to eleven other people. We work on what to show them, in what order, and what to stop them from doing.

Best for: the person who has to lead this
03 — How a session runs

Ninety minutes, your screen.

BEFORE

You send me the friction

Two or three sentences about the part of your week you dislike most. No prep, no reading list, nothing to install.

DURING

We build it, not discuss it

Your hands on the keyboard from the first ten minutes. I narrate what I'd try and why, and you watch the thing take shape in front of you.

AFTER

You keep the working thing

The artifact, the prompts behind it, and a short list of the next three you could build. Most people build one before we speak again.

Who this is for

Business professionals who already believe the thing works. You don't need convincing that AI matters — you need to stop reading about it and put an hour against your own work with someone who has been inside the tool.

No engineering background assumed, and none required. Plain English is the interface.

The moment your jaw drops and you think “wait, it can do that?” — everything after it is momentum.

04 — Get started

Start with one session and see what happens.

Tell me roughly where you are and what you'd like to stop doing by hand. I'll come back with a time and what to have open.

Request a session
I reply personally, usually within a day.