Most setups fail quietly. That is the expensive one.
A crash gets fixed on Tuesday. A job that finishes quietly having done nothing gets found in March. The difference is whether anything was written down.
Three standards sit under every build on this site, whichever package it came from. Below them are the checklists, so you can see what is needed from you before you spend anything.
It is built around your work
We start from a job you already repeat, not from a demo. Your agent is configured to your tools, your accounts and the way you actually work, so the first thing it does is something useful to you.
It stops before it matters
Anything outward waits for you: a send, a delete, a charge. Everything else just runs. That gate is the difference between useful and frightening.
It leaves a receipt
Every run says what it did, what it skipped and why. You can tell success from silence, and I set up the health checks that tell you when something has quietly stopped.
Whether this is for you.
I would rather you worked this out here than on a call. The right hand column is the honest half: if you are in it, say so on the form and I will tell you so instead of selling you something.
This fits you.
- You have a job you repeat every week and resent, and you can describe it out loud.
- You want the thing to live in your own accounts, under your own billing, and to still be yours after I leave.
- You would rather learn to run it than rent it from somebody forever.
- You are one person, or a team of up to about twenty five.
- You can get a decision made without a committee, or you are the committee.
- You want to be told which jobs are not worth handing over, not just the ones that are.
This is not for you.
- You want somebody to run it for you indefinitely. I build it with you and then the engagement ends.
- You want an hourly arrangement or a block of hours to draw down. Every package here is a fixed fee with a finish line.
- You need single sign on, directory sync or custom security engineering. That is a different kind of firm.
- You want certainty about the outcome before anything is built. I will tell you what I will do, and what I cannot, in writing, before you pay anything.
- You want me to hold your card, your keys or your passwords. I never do, on any engagement.
- You are hoping AI will replace a person this quarter. That is not what this is, and I would rather say so now.
What is needed from you.
A fixed price on a fixed window only survives if both sides turn up. Every package publishes its own list of what it needs from you, what the fee assumes, and what happens if a prerequisite is not in place. None of it is discovered in week two.
The team install carries the longest list, because a team has an administrator, a seat count and an IT review in it. A one to one build needs three things: a machine you can install on, an account in your own name, and one job you already repeat.
- Read the team install list before you book it: seven items, all of them things only you can do. Claude for Business.
- Read what the Readiness Assessment needs and what arrives at the end of it. AI Readiness Assessment.
- Read everything that can be booked and what each one is for. Claude Setup.
- Read the terms in full, before you pay anything and before you give me access to anything. Terms.
Those lists live on each package page rather than being restated here, so there is only ever one version of what I have asked of you.
What a written roadmap actually contains.
The Readiness Assessment is the one package whose whole deliverable is a document, so here is its table of contents. You are reading what you would get, not a description of it.
- What you do todayIn your words, written back to you so you can correct it before anything is built on it.
- The jobs worth handing overRanked, each with what it would need and roughly what it takes.
- The jobs not worth handing overAnd why. Naming these is most of the value and almost nobody does it.
- Where your data can actually goPer tool, and what leaves your building.
- What has to ask you firstThe outward actions that must never run unattended.
- What a quiet failure looks likeIn each job, and the check that would catch it.
- Readiness per systemWhat you already have, what is missing, what blocks.
- The order to do it inAnd what each step is worth.
- Both costsWhat it would cost to have me do it, and what it would cost you to do it yourself.
- The honest no action baselineWhat happens if you do nothing. Sometimes that is the answer.
Fifteen to twenty five pages, then an hour together walking through it. Yours whether or not you hire me to do any of it.
Start with the free call.
Twenty minutes, by video or phone. You describe the work, I ask enough to understand it properly, and we look at whether an agent fits it at all, including when it does not.
You leave with a short written plan: the first job worth handing over, what it needs, and roughly what it takes. That is yours whether or not we work together. Nothing is charged and nothing is installed on the call.
Clients in unrelated trades, each with a name and a date, are on the home page.