Operations tool · Virtual COO · reads your Company Memory

SOP Writer

Describe how you actually do a recurring task — ramble, or paste a voice-note transcript, it's fine. Get back a clean numbered SOP with roles, tools, checkpoints, and the one "done when" test that says the job's finished.

🎙️

How you actually do it

ramble or a voice-note transcript

⚡

AI writes the SOP

sent once · nothing stored

📋

A numbered SOP

roles, tools, checkpoints, "done when"

The job that only works when you do it becomes a step-by-step anyone on your team can follow — because 'you just know how' is not a process, it's a bottleneck.

Watch the 90-second build

Describe the task — how it starts, what you do step by step, who does it, what you use, and how you know it's done. Messy is fine.

🔒 What this touches: your description plus your saved Company Memory (if you've built one) are sent once to an AI model to draft the SOP. The draft shows here; nothing is uploaded or stored on a server — no account, no database. Close the tab and it's gone.

Writing your SOP…

Draft — read it through and fix anything I guessed at

The SOP

Quick checklist

Anything I wasn't sure about is marked [confirm] — fill those in before you hand this to someone. This is a draft; you own the final version.

This is your Virtual COO compounding → Build your Company Memory once and every operations tool — SOPs, roles, onboarding — reads it, so your business runs the same way whether you're on the tools or on the beach. See the whole Run the Business path.

Why the SOP you never write is the one that costs you

The task lives in your head. You've done it a thousand times, so writing it down feels like busywork — until the day you're out sick, or you finally hire someone, and it turns out "you just know how" was the whole process. Then every job routes back through you, and you can't take a Tuesday off, let alone a vacation.

The reason it never gets written isn't that you don't know the steps — it's that turning a rambled explanation into a clean, numbered document is its own boring job. So this tool does that job. You talk it through the way you'd tell a new hire; it hands back the SOP, with a "done when" test so the work is actually finished, not just abandoned.

Talk, don't typeRamble it, or paste a voice-note transcript. You explain the job once in your own words; it becomes a document someone can follow.

Nothing inventedIt only writes down what you actually described. Anything it can't tell — a specific tool, a threshold, a name — is marked [confirm], never guessed.

"Done when," not "good luck"Every SOP ends with a clear finish test, so a helper knows the job's complete instead of leaving it half-done and calling you.