Three of them, in detail
What I do
Three things. Every one of them starts the same way: a conversation, and one real piece of your work. The smallest is one person, one task, one afternoon. The other two grow with the size of the company.
- An afternoon
- A day
- The build
An afternoon
You pick one task you do by hand today and show me how you do it now. We build it together, in whichever account your IT allows, and by the end of the afternoon the task runs end to end on your real inputs, with you driving. If it does not, you do not pay the second half.
Before it: twenty minutes on a call to pick the task, a sample of the input, the systems it touches and the access I will have. Your NDA, signed before I see any of your work.
The afternoon rests on the sample and the access being in place. If either is missing on the day, we move the date rather than run it short.
It is the smallest thing I do, the one I suggest first, and the one that fits a person working alone. If there is no team to roll anything out to, start here. If it goes well and other people would want the same thing, the day is the next size up.
A day with the people who do the work
One day with a group from your company. The morning is built on their own work rather than a generic course: everyone brings one real piece of what they do. The afternoon is a hands-on build. Everyone leaves with something their own team can switch on the next day.
Before it: an hour with each person, so they arrive with real work. That is the whole ask of your people for the day itself, the hour and the day.
After it: we read what was built, what it changed in the work, and whether it is still in use, at thirty, sixty and ninety days. If nothing has moved at thirty, we stop there.
Then one team at a time. Where the day moved something, one session with each team on the work that team does every week, across the ninety days, with the same reads. You choose how many teams and in which order.
Then the whole company. Every team, plus a half-day with the leadership team and one-to-ones where they are wanted. I do not put a number on the whole company before one team session has run. Within a week of that first session you have it in writing, element by element, with the start, the finish and the point at which we would stop written beside each one.
The build
Sometimes the right answer is not a session but the thing itself.
What I build is a store of what your company already knows, in a form your AI tools can read from, and the first real job running on it end to end, with a person accountable for every word. Not a demonstration but the working version. I have built the store reMarkable's engineering team adopted, and the running job Hesketh & Son works from. Both are described on the home page.
It lives in your systems, under your control, and what I build there is yours to keep and to change after I leave. Whether I stay alongside you afterwards depends on the size of it. It does not run your work on its own, and I will not build you one that does.
What happens, step by step
The same terms, every time
Each has a fixed fee, agreed in writing before it starts, half on booking and half at the end, and you have the number before you say yes.
Nothing recurring unless you ask for it. Your NDA, signed before I see any of your work.
What I will not do
A generic course. A demonstration of what AI can do. A promise about time saved or money made. Anything that runs with nobody accountable for it.
Start with an email
Write to me about whatever brought you here, and say which of these sounds nearest, or say it is bigger than any of them. If none of them fits, say that instead, and say what you were hoping to find. I read them myself and I answer properly, including when the honest answer is that I am not the right person for it.