Most companies do not need a full-time AI hire yet. They need an expert they can reach a few times a month: someone who knows their systems, has met their teams, and can be booked when a person is stuck rather than when a project gets funded.
That is what this is, for two audiences at once. Leadership uses me to work out what to do next and to keep the plan moving between sessions. Anyone on your team books time with me whenever they need it: we screen-share, and I either help them build it, point them to a tool that already does it, or tell them it is not worth doing. You still own it. You are no longer doing it alone.
Who this is for
- You want ongoing help rather than a project, for leadership deciding what to do and for the team doing it.
- You have paid for seats in a tool and are not seeing the value, and you would rather fix that than buy another one.
- You are not ready to hire for this, and you may never need to.
Before any of this starts
Every engagement starts the same way, whichever one you pick. It takes a few conversations, on purpose: you are choosing someone your teams will work with directly, and the scope comes out of those conversations.
- 1
Intro call
You
Thirty minutes to hear where your company is with AI, what leadership is asking you for, and what you are trying to get done. It is enough to tell whether a longer conversation is worth having, and that is all it needs to do.
- 2
Discovery sessions
You first, then your leadership team
Usually two or three, each about an hour. The first is with you: your issues, priorities, and concerns, properly, often with some hands-on work so you can see how I operate. Then a level-set with the people who will have to approve this, on a call or in person: my approach, what I expect from your side, and what the engagement would look like. This is where the scoping starts.
- 3
Proposal and statement of work
You and leadership
Based on what came out of discovery, I send a short proposal: what we would do, in what order, and what it costs. Once everyone is comfortable with it, it becomes a signed statement of work.
- 4
The work starts
Everyone
Sessions get scheduled around your priorities and your team's availability. Everything I produce lives in your systems, and you own it whether or not we work together again.
How it runs
Once the scope is agreed, this is the work.
- 1
Department workshops in the first month
Each department, one at a time
Before anyone books time with me, I need to know how they work. In the first few weeks I get set up in whatever your team uses to talk to each other and run a short workshop with each department to see what fills their day, what they get stuck on, and where a tool or an automation would help. This is also where people meet me, which is what makes them comfortable booking time later.
- 2
The booking link goes out
Everyone
Every person on the team gets my contact details and a booking link. From then on, they book time whenever they are stuck. A report they build by hand every week, a tool the company bought that nobody uses, a process that should be automated, a question about what data is safe to put where. Sessions are screen-share and we work on the real thing, not a demo of it.
- 3
Small group sessions when a pattern shows up
Whoever shares the problem
When three people from the same team book about the same thing, I pull them into one session instead of solving it three times. That is often how a department's playbook gets written: one problem at a time, by the people who have it.
- 4
A monthly note to you
You, or whoever sponsors this
Once a month you get a short written summary: who booked time, what we worked on, what got built or fixed, and what I think is worth doing next. It is the page that lets you show leadership what the flat fee is buying without asking anyone.
What you get
- A department workshop with each team in the first month
- A booking link for everyone on your team, used as often as they need
- Screen-share sessions: build it, fix it, or find the tool that already does it
- Training, building, and integrating the tools your team already uses
- Straight answers on what is not worth doing
- A monthly summary for leadership of what was worked on
- Month to month, pause or cancel whenever
What it takes from your team
An hour or two per department in the first month, then whatever your people choose to book. Sessions are usually thirty to sixty minutes. You get a monthly note and otherwise hear from me only when something needs a decision.
What it does not include
Large builds. Sessions are for getting people unstuck and building small things with them. A multi-system integration, a production agent against your ERP, or anything that takes days of build time gets scoped and priced separately, so the monthly fee stays honest for both of us. Session availability is subject to my calendar, and I keep the roster small enough that people can usually get time within a day or two.
Is it a fit?
Thirty minutes, no pitch deck. Tell me where your company is with AI and what leadership is asking you for, and I'll tell you honestly whether this is the right shape, or whether one of the other two fits better.