The Crash Course · $85,000
Two weeks. The whole company. A crash course in your own business.
When you already feel late, the last thing you need is another tool. You need someone independent to walk the whole operating floor — systems, data, process, people, and the AI your staff is already using quietly — and tell you the truth about all of it at once. That's two weeks, roughly sixty hours on the ground, me plus one senior operator I trust. Then I write you the map.
It's called the Crash Course because that's what it is — and you're the subject. By the end, your leadership team can read the map without me, which is how you know it worked.
The two weeks
- Week one — we read the company. Interviews across functions, systems and data review, the real workflows behind the official ones, and the shadow AI nobody put in a deck.
- Week two — I write the architecture. The full can / can't / shouldn't map by function, the never-lines drawn, the one-to-three-year trajectory, and the architecture of your options: build, buy, partner, or wait — for each opportunity, in order.
- The readout. The executive session where the decisions land — what to build first and why, what to wait on, what to stop, and the lines AI never crosses here. It ends with an ask, not a slide that says "thank you."
- Thirty days of bounded Q&A. Two calls and an open inbox while the decisions turn into motion. Bounded means bounded — it ends on day thirty, on purpose, because I told you I wouldn't become a monthly bill.
The objection, met at the door
"$85,000 and you don't build anything?"
Correct — and that's the part you're paying for. This decision aims the next half-million to five million dollars you spend, and it draws the boundary that keeps AI off the things that hold your company together. The big firms charge two to five times this for the same readout, and then sell you the build they just recommended. I can't do that even if I'm tempted, because there's nothing on my shelf to sell you. A wrong build costs more than $85,000. Quietly, a wrong "never" costs even more.
The fine print, in plain sight
- This works when I get decision-maker access, a look at the real systems, and your team's time for interviews. If you can't give those two weeks, wait until you can — I'd rather you wait than waste the money.
- What I don't do: build the systems, hire the team, run the rollout, or maintain anything. The map is mine; the road crew is yours to choose, and the map is written to be handed to them.
- $85,000, public, a floor. Larger orgs and more functions are priced as an addendum before we start. Paid by wire, half to book and half at the readout.
- Proof: one active engagement, under NDA. Here's what I can share about it, and exactly what I can't.