Teach it, or build it. Usually both.
Three ways to work together. A day in a room with your team, teaching that keeps going after it, or a standing seat where I find the work worth automating and then build it. Whichever you start with, everything that gets made is yours.
Half a day, your firm, your own work.
Your people come in with the work they actually do that week. By the end they have used AI on it themselves, and they know which parts of their job it is genuinely good at and which parts it should stay away from.
It is a room, not a webinar. No slides you could have read. Nobody leaves with a login they never open again.
One firm at a time, so the examples are yours rather than a stranger's industry.
What the day is
- On site, half a day, one firm
- Built around the work your team brought
- Hands on the keyboard, not watching me
- What not to automate, said out loud
- The material stays with you afterwards
Teaching that outlasts the room.
One good day changes what people think. It rarely changes what they do on the following Tuesday. Training runs over weeks instead, in shorter sessions, close enough together that the habit sets.
Your team keeps the written material, the examples and the prompts, in your own words and your own file names, so a new hire next year can be brought up to the same place without me.
I have taught and built training programs for about seven years, across three different settings, and supervised the people delivering them.
How it runs
- A series of sessions, not one hit
- Written for your firm, not a generic deck
- Materials handed over, yours to keep
- In person or remote, whichever suits
- One team, or the whole firm in groups
A standing seat, and the building that comes with it.
This is the main thing I do. A fractional Chief AI Officer, the same way a growing firm brings in a fractional CFO. A real seat at the table, sized to the work you actually have.
We start by finding the one opportunity with the highest return, fix the process underneath it, and then build the system inside the tools you already pay for. Month one ships something working. After that we keep going down the list, and each system makes the next one faster.
A consultant hands you a plan and leaves. I stay while it becomes a real thing, and you own every piece of it.
What you get
- A monthly fee, never an hourly rate
- Three or six months to start, then month to month
- Built inside your existing tools
- Your tools, your data, your IP, always
- It all keeps running if we part ways
Professional firms where knowledge is the product. Accounting, law, engineering, architecture. Usually somewhere between thirty and a hundred and fifty people, with someone other than the owner running operations, and client information you are obliged to look after properly.
There is no territory. I am based in Idaho and I work with firms across the United States. Where you are is not one of the things I screen on.
Pricing comes on the call. Nothing is quoted before I know what the problem is actually costing you, because a number without that behind it is just a guess with a dollar sign on it.
Not sure which one you need?
Take the call. Thirty minutes, and you will leave knowing the one move worth making first, whether or not you make it with me.