Explain the job once. Get back a procedure somebody else can run without asking you a single question. SOP Builder works from a screen recording, a voice note, a call transcript, or you just talking through the task. It writes the procedure, catches the steps you skipped because they felt obvious, and closes with a check anyone can verify. Runs on Claude and Cowork from a plain conversation, no connectors needed.
You know the job so well you cannot see it anymore. That is the trap. You explain it to the new hire in four minutes, they nod, and then they interrupt you nine times over the next two weeks because the four-minute version left out everything you stopped noticing years ago.
The usual fix fails for a reason. Somebody sits down to write the procedure and produces the theory. "Review the submission." A new person reads that, has no idea what reviewing means or what disqualifies a submission, and comes straight back to you. Vague documentation is worse than none, because now everyone believes the process is written down.
So it stays in your head, and your head stays in the loop. Every hire ramps at your speed instead of theirs. Every absence turns into a queue. Modeled at three interruptions a day at ten minutes each, that is roughly three weeks of an owner's year spent re-explaining work that was already explained.
The fix is not disciplining yourself into writing more. It is removing the writing step.
| Category | What it captures |
|---|---|
| Objective and Trigger | What the task achieves, and the event that means it is time to run it |
| Tools and Owner | Every system, file, and credential involved, plus who runs it, who approves, and who they escalate to |
| Numbered steps | Concrete actions with exact paths and labels, written for a person who has never touched this, with every fork stated in the open |
| The skipped steps | The parts you left out because they felt too obvious to say, surfaced by three questions a recording cannot answer |
| Definition of Done | A check someone can open and verify, not a feeling that the work looks finished |
| Missing-value flags | Anything you did not supply is marked REQUIRED - MISSING in the body rather than guessed or quietly dropped |
Hand over whatever you have. A screen recording transcript, a voice note, a call where you explained it to somebody, rough bullets, or nothing at all. Out of order is expected. Tangents are expected.
It maps before it writes. It reads the whole input first and works out the sequence, the forks, the approvals, and what has to be in hand before step one.
Three questions a recording never answers. One at a time, never a wall. What you would point at to prove the job was done right. What has to be sitting in front of the person before they can start. And the version of this that only turns up a few times a year, which is the version that generates the phone call.
It writes it concrete. Exact menu paths, exact field labels, exact button names. One action to a step. Forks written out loud instead of assumed.
It reads it back. You get asked whether that is the order you actually work it or the order it is supposed to go in, and what you left out because it felt too obvious to mention. That second question earns its keep every time.
Pick your format. Markdown, PDF, Word, or straight in the chat. You see the procedure in the chat either way.
SOP: Onboard a New Client
| Field | Value |
|---|---|
| Objective | Get a signed client fully set up so the delivery team can start work without chasing the account manager for missing information |
| Trigger | The agreement is countersigned and the deposit clears |
| Tools | CRM, billing system, shared drive, REQUIRED - MISSING: your kickoff email template |
| Owner | Runs: account manager. Approves: operations lead. Escalates to finance when the deposit does not clear within five business days. |
Steps (excerpt)