A course gives you the starting point. Advisory is there when it has to be put to work: a few hours a week embedded with your teams, over a month or two, where the work actually happens.
A few hours a week, for a month or two
I join your teams, sit in on the meetings and spar with your product people about what they are actually working on. In, alongside, out again.
And just as often, I am the leader’s advisor. A standing hour with you, the person responsible for product development: how you use AI in your own leadership work, which experiments you start, and what you say no to. Most leaders use AI every day. Very few have anyone to spar with about it.
I go through your product development and write down where it stalls, and what I would do about it. You get it in writing, and you get it said out loud to your leadership. This is often where an engagement starts.
I sit next to your product people for a whole day, and we finish something real. Not a mockup. Something that still works after I have gone home.
Fixed price, agreed up front, so you know what it costs before we start. An engagement typically lands in the same range as a course, just spread into the workweek. Tell me what you are dealing with, and I will say what I would do, and what it comes to.
One day, at your place, with the whole team together. A shared base setup, workflows for discovery and PRDs, and at least one tool built on a problem of your own.