Fifteen minutes. Three things.
Give the transcript of this session to Claude afterwards and it sets all of it up for you.
Everything I do goes through Claude.
on AI tooling since May.
on a PC to run the automations.
tokens through the API in five weeks.
automated calls I never watched.
a day, every day, since March.
Some of what it made.




The file structure
One folder. This is the whole thing.
The rule that makes it work
Nothing lives in a chat. If it mattered, it went into a file, and the file is where the next session reads it. That's why it never asks you the same thing twice.
Per client, per tool
A client folder holds everything about that client. A tool folder holds how to use that tool, with a learnings file on top that it updates itself.
The file structure
Three things that sit alongside it.
Skills, one each
You told me the problem. Here's the skill.
Sophie
The first draft usually sounds very robotic.
How it was built
Pulled 128 of my own posts with Apify, measured how they're actually written, and turned that into a skill. It sounds like a person because it was made from one. The tone is a joke on purpose; the method is the point. Superco has years of published work to do the same with.
Happy to tailor this to your workflow. About thirty minutes on a call, sometime this week.
Tom
Pulling receipts and paid invoices for bookkeeping. About an hour a month. Adobe hides them somewhere in the back end.
FinanceInbox
It watches Gmail for invoices, converts them to GBP and adds them to the tracker, every evening at 19:00. I haven't typed a transaction by hand since July.
Browser harness
For the ones that never email a receipt. It logs in once, then once a month opens each portal and collects them itself.
Happy to tailor this to your workflow. About thirty minutes on a call, sometime this week.
Lisa and Sophie
I have to be very specific about the use case to get the answer right. I want it to ask me the questions rather than the other way round.
grill-me
Before it builds anything, it interrogates you: the edge cases, the things you'd assumed, the bits you'd forgotten to say. You answer questions instead of writing a brief. It's the single most useful skill I have and it's about a page long.
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.
The integrations process
Every tool gets a folder. It pulls the API docs in, and a learnings file sits on top that it updates every time it discovers something. It stops guessing the moment it has something to read.
Your Shopify knowledge, in a file
The call-transcript puller takes your Shopify calls and writes what you know into that same learnings file. Then it answers from your knowledge, in your words.
Happy to tailor this to your workflow. About thirty minutes on a call, sometime this week.
Juliet
Just being able to pick up the phone when I want to.
A .env file and one sentence
With Deepline or FullEnrich keys in the .env, you say enrich this list with phone numbers and it does. No tool to learn.
Offer
Send me a list this week and I'll run it, so you can see the numbers come back before you set anything up yourself.
Happy to tailor this to your workflow. About thirty minutes on a call, sometime this week.
Skills, for everyone
Six worth copying on day one.
Plus slop-text-removal.md: thirty-four named AI tells, checked before anything leaves. This page went through it.
Tips
Eight things I wish someone had told me.
For inspiration
Things I built that show what's possible.
Give the transcript of this to Claude and it sets it up. Ask me anything.