01
§ The Job — Defined
When someone says they need “help with AI,” that is a category, not a job. Categories do not get hired; jobs do. This page exists to name the actual job — in sentences specific enough that you can tell whether it is yours.
The distinction matters because the category — AI — is full of solutions looking for problems. The job is specific to you. When we run Discovery, the first fifteen minutes are usually about finding out, precisely, what job you are trying to hire us for. Most engagements begin their real life in the moment that question gets answered well.
What actually moves a decision.
Hiring anything is a four-force equation. People usually notice the first two and miss the second two. Below is all four, applied to the decision of hiring work like this. We describe them openly because we would rather you decide with the balance visible.
What is wrong with today.
Most clients arrive because they can feel a specific motion they should be making and aren’t. Their own slowness on this has become visible to themselves. The push is real before they open any tab.
What draws them toward one answer.
For this work, the pull is usually a precise sentence: One named leverage area. Ninety minutes. Refundable. Not a promise to transform. Specificity is what pulls serious people.
What worries them about hiring anyone.
Usually: another consultant who sounds smart and delivers slides. We address this directly by making the Discovery session bounded in time, fixed in price, and guaranteed in outcome.
The gravity of continuing what they already do.
For most of this market: muddling with ChatGPT alone, or waiting another quarter. The offer is deliberately shaped to be lighter than the habit — ninety minutes, one session, no commitment beyond it.
Push + Pull > Anxiety + Habit = a hire happens.
Customers don't buy products; they pull them into their life to make progress.
Every functional job proceeds through some or all of eight steps. The alternatives cover a handful. The engagement described here is designed to run the full loop.
Courses teach the first two steps. Developers start near Execute. Coaches usually stop at Confirm. The engagement described here is built to run the full loop on one platform — which is why a single session can start it and a single person can carry it through.