Before anything else
Give me something to build.
Shout one out. Anything you'd want on a screen. I'll start it now and it runs while we talk.
Running
It's going. We'll come back to it at the end.
If it falls over, you'll see that too. That's the point of doing it live.
Quickly, so you know why to listen
Everything I do goes through Claude.
on AI tooling since May. Claude, OpenAI, Anthropic.
on a PC built to run it faster.
tokens through the API in five weeks.
automated calls I never watched.
a day, every day, since March.
Some of what came out of it
Nobody wrote any code. Me included.






Your ideas
Here's what you told me you wanted.
Tom
Pulling receipts and paid invoices for bookkeeping. About an hour a month. Adobe hides them somewhere in the back end.
Already running
It watches Gmail for invoices, converts them to GBP and adds them to the tracker, every evening. Once a month a browser script collects the ones that never email a receipt. I haven't typed a transaction by hand since July.
Happy to tailor this to your workflow. About thirty minutes on a call, sometime this week.
Tom
The sales spreadsheet, pulling from Attio. I spent a lot of time and credits and it didn’t deliver anything useful.
Already running
This is the Superco tracker. A live sheet, fed on a schedule from the campaign system, that people actually open. The same shape pulls from Attio.
Happy to tailor this to your workflow. About thirty minutes on a call, sometime this week.
Lisa
Some of the solutioning is quite poor. Sometimes absolute gibberish. I think its sources are out of date.
You're right
It's answering from memory. Every tool I use has a folder, and the learnings file sits on top. It reads the docs, adds what it discovers, and updates the file itself.
Start here
Take your Shopify call transcripts, hand them over, and let it write them into a learnings file. It stops guessing the moment it has something to read.
Happy to tailor this to your workflow. About thirty minutes on a call, sometime this week.
Sophie
The first draft usually sounds very robotic. I want it to ask me the questions rather than the other way round.
Proof it's buildable
That's the output of a voice skill built from 128 real posts, measured rather than described. The tone is deliberately a joke. The method is the point: Superco has years of published work, and a skill that interviews you before it writes is a day's build.
Happy to tailor this to your workflow. About thirty minutes on a call, sometime this week.
Rachel
Find the out-of-office replies from people who’ve left and see if they name someone else. And sense-check anything going out, without writing it for me.
Out of office
That's a sequencer feature and the one you're moving to has it built in. I'm setting it up anyway, so it'll just be on.
Sense-check
The copy gate reads a draft against a written standard and tells you what's wrong. The writing stays yours, and your boundary stays where you put it.
Happy to tailor this to your workflow. About thirty minutes on a call, sometime this week.
Farah
A pitch deck that doesn’t eat credits. A proposal from a template with the exact services.
Already running
After a discovery call, the proposal writes itself from the recording and emails itself. One spec file makes the review copy and the branded document, so they can't drift. The deck is the same idea in a different shape.

Happy to tailor this to your workflow. About thirty minutes on a call, sometime this week.
How I've set up Claude
Five files. All of it runs in Claude Code.
- how to reply to me, and in which English
- what to do every time, without being asked: give an ETA, sample the output, render before handing over
- the hard rules it may never break
- where everything lives
How I work with it
Three habits that make the files work.
The parts I'd show a friend
Things that run without me.
Make whatever you want
Four steps, and none of them needs a terminal.
CLAUDE.md in the project folder. It gets read first, every time.Or send me the thing you want built, and I'll run mine on it.
Step four is the part people skip. My build loop does it: the rubric gets written before the build exists, so the check can't be bent to fit what got made. You get it back with the score, and the transcript of this session plus a starter repo if you want to run it yourself.
Back to the start
So. Did it work?
That's it
Ask me anything.
This page was made the same way. It's yours to keep, and it reads on its own.