Executive & founder coaching
One-to-one work with senior people who don't have time for a syllabus. We start where you actually spend your week and build prompts and habits from there.
Boffin Hub · Senior Claude trainer
Most teams meet Claude through a demo and a clever prompt. Senior teams need more: real fluency in prompt design, judgement about what to delegate, and workflows that survive contact with a real working week. That's what the training builds.
Engagements rarely fit a neat box, but most lean on one of these three. Programmes are bespoke; the underlying craft is the same.
One-to-one work with senior people who don't have time for a syllabus. We start where you actually spend your week and build prompts and habits from there.
The unglamorous middle layer: sharpening intent into prompts, building a sense of when Claude is the right tool, and when the human brain in the room still wins.
Programmes shaped around the team you have: your tools, your tone, your constraints. Workshops, cohort coaching, and follow-through that actually sticks.
Two versions of the same request, before and after one session. Drag the slider to see what changes.
You're writing as our COO — dry wit, plain English, no hashtags.voice, named
Draft a LinkedIn post announcing our new scheduling tool for operations leads who are tired of AI hype.a real audience
Lead with the problem it removes, not the features. About 120 words. End on a question.shape & length
Two past posts in our voice are pasted below — match them.
The interesting work isn't the model.— On training senior teams to use Claude well
It's the moment a team stops asking
and starts using.
Most engagements are with founders, executive teams, and the functional leaders they bring with them. The brief varies. The need for something practical doesn't.
Every team follows a version of this line. My job is the slope, and getting you through the dip in the middle. Scroll and it draws itself.
Shaped around your team rather than a fixed syllabus. Most engagements move through these four steps.
We start with a call: what your team does, where Claude might earn its keep, and where it almost certainly shouldn't.
Sessions designed around the team you have: live workshops, small-group coaching, async materials, or some combination.
We work with Claude on real material from your team. Prompts, workflows, edge cases. Nothing rehearsed.
The bit most training skips. We come back to the workflows after they meet real life, refine what's working, and quietly retire what isn't.
Five session themes, dealt in whatever order your team needs. Every programme uses them differently.
What Claude actually is, what it isn't, and the three habits that outlast any cheat-sheet.
How to ask for what you mean. Voice, context, shape, and why they change what comes back.
No toy examples. We bring your real documents into the room and build the workflows there.
When to delegate, when to double-check, and when to do it yourself.
A check-in once the training has met a few real weeks. What stuck, what didn't, what needs another pass.
A few numbers worth knowing before you get in touch.
Hello,
If your team already gets solid work out of Claude every day, you don't need me. Close the tab, no hard feelings.
Most teams I meet aren't there yet. The licences are paid for, two or three people are keen, and the results are patchy. Nobody says this out loud. That gap is where I spend my working week, on your documents and your deadlines rather than generic exercises.
If you're weighing it up, send a short note about the problem sitting in front of you. I'll tell you straight whether training will move it. If it won't, I'll say so and point you at something that will.
Warmly,
P.S. You'll get a reply from me, not an assistant.
A short note is plenty. I'll come back to you within a couple of working days with whether I can help. If I can't, I'll suggest someone who can.
Your note is on its way. I'll come back to you within a couple of working days.