Bring me the thing your team built.
An hour on the workflow, agent, or AI plan you've already got. You'll leave knowing what's solid, what's going to break, and what I'd do next. No pitch and no rebuild proposal. If it's fine, I'll say it's fine.
$175 an hour, booked one session at a time. Free 30-min intro first if you want to check the fit.
Pick the right format
Cohort
You build your first one, with a group. Best if you haven't shipped an AI tool yet and want fixed dates and shared momentum.
See the cohort →Coaching you're here
You build it, I help you build it. Best if something already exists and you want a second opinion, or you're the one doing the work and want help doing it well.
Book a 30-min intro ↓Consulting
I scope and build it for you. Best if you want the workflow or prototype handed to your team finished, on a project timeline.
Start a project conversation →A second opinion from someone who's shipped a lot of these.
This is not a tool tour. Send me what you've got beforehand and I'll spend the hour on the three questions people actually bring me.
Is this any good?
Your team built something and it demos well. I'll tell you whether it holds up outside the demo, where the risk actually sits, and whether it's worth putting in front of more people.
Why does it keep breaking?
It worked last week and today it doesn't. That's usually missing context, scope that crept, or nothing checking the output before a human sees it. We find which one, and fix the cause instead of the symptom.
What should we do next?
You've got a goal, a team, and a budget conversation coming. We turn that into a shortlist you can defend: what to build, what to buy, and what to leave alone for now.
Hands-on yourself? We can go straight at the agent loop, the context files, Skills, and the first real eval. Plenty of the people I work with are operators who've gotten technical, and the vocabulary isn't a prerequisite either way.
A few quick details
Once you submit this, you'll pick a 30-min slot on the next screen. No payment, no spam. These notes tell me what you've built and what you're deciding, so the intro isn't spent on background.
Pick a 30-min slot
I'll see your prep notes before the call. If nothing here works, email [email protected] and we'll find a time.
Who this is for
You own the outcome, not the code
Your team built something and you're the one who has to decide whether it ships, scales, or gets quietly retired. You want a read you can trust before you spend more on it.
You're about to defend a plan
There's a rollout, a budget ask, or a leadership conversation coming. You want the holes found by me first, in private, instead of by your CFO in the meeting.
You're doing the building yourself
You're an operator who got hands-on, and now you're past the tutorials and into the parts nobody wrote down. You want someone who's hit those parts already.
Start with one. Book more only if they're worth it.
Plenty of people take the first hour and leave with enough to run on their own. That's a good outcome, not a lost sale.
Hour 1: the teardown
You send it over ahead of time. I come with a read: what's solid, what breaks under real use, what I'd change first, and what I'd ignore. You leave with that written down.
Next hours: fix what we found
You do the work between sessions. We review what changed, argue about the calls worth arguing about, and get the thing steady enough to put in front of people.
After that: as you need it
Some people book an hour a week while a build is live. Some come back once a quarter when the next decision lands. There's nothing to keep paying for in between.
FAQ
Is the intro call really free?
Yes. 30 minutes, no obligation, no payment. The intro is here so we can both decide if 1:1 coaching is the right fit before anyone commits.
What happens after the intro?
Most people book a one-hour teardown: you send me what you've got beforehand, I spend the hour telling you what's solid, what's going to break, and what I'd do next. You're billed $175 for that hour. If we're not a fit, no charge and I'll point you at someone (or something) that fits better.
What if my team built it and I didn't?
That's the common case and it's fine. You don't need to be the one who wrote it. Bring what you can share (a demo, a doc, a repo, or just an honest description of what it does and where it disappoints you) and bring the decision you're trying to make. Pulling in the person who built it for part of the hour usually helps, but it isn't required.
How is coaching different from consulting?
Consulting is me scoping and building it for your team on a project timeline. Coaching is you building it, with me alongside for an hour at a time: reviewing what you've got, telling you what I'd change, and unblocking you when it stalls. If you want it handed to you finished, that's consulting. If your team is doing the work and needs a second set of eyes, that's this.
How is coaching different from the cohort?
The cohort is for people who haven't built one yet and want a group, fixed dates, and one shipped tool at the end. Coaching assumes you already have something running, or a real goal and a team, and want focused help on that specific thing. Pick the cohort to build your first one; pick coaching when the thing already exists and you need it to hold up.
Do I have to commit to a package?
No. Coaching is $175 an hour, booked one session at a time. Most people run a weekly hour while a build is active and then stop for a while. There's no retainer, no minimum, and nothing to cancel.
How many hours will I need?
Most builds take four to six hours spread over a month: one to scope and set up the harness, two or three on build and diff review, one to add the first eval and write down what the workflow now knows. You book the next hour only when you want it.