Workflow intelligence · SOPs
Turning tribal knowledge into a system your whole team can use.
Ask an owner how the business runs and they can walk you through every step. Ask three employees the same question and you'll usually get three different answers. That gap is what a written SOP is supposed to close, and what most written SOPs fail to close in practice.
The problem
Static documents are read once, then forgotten
A procedure written down but never opened isn't really a procedure. It's a file.
Most small businesses have some SOPs, usually in a shared drive folder nobody revisits after onboarding. When a process changes, the document rarely gets updated to match. When an experienced employee is out or leaves, the business slows down, because the exact steps and judgment calls they used never made it into anything the rest of the team can rely on.
The fix isn't writing a better manual. It's putting the procedure somewhere your team will actually use it while they're doing the work, not before or after.
The difference
A written SOP vs. one built into your workspace
| Written SOP | SOP built into an AI workspace |
|---|---|
| Filed away; found only if someone remembers to look | Answered on request, in the workspace your team already has open |
| Goes stale until someone remembers to revise it | Updated once, in one place, and used from there on |
| Read, then applied by hand from memory | Applied directly: drafts a record, a quote, or a message that follows the rule |
The goal isn't a longer document. It's fewer situations where someone has to guess or ask around.
How we build one
Four steps, starting from how the work is actually done today
Capture it as it really happens
An experienced team member walks through the task out loud, or dictates it, rather than trying to write a polished procedure from scratch.
Structure it
The raw walkthrough is organized into a standard shape: what the task is for, what's needed before starting, the steps in order, and the exceptions that come up.
Load it into the workspace
The structured procedure goes into your company's knowledge base, and where it's a task done often enough, we build a tool for it.
Keep a person reviewing customer-facing output
Any draft that reaches a customer, an invoice, or a record still gets a human check before it goes out. The SOP removes the retyping, not the judgment.
Where this applies
A few examples across different businesses
Service businesses
A follow-up procedure for open quotes: when to reach out, what to reference, and when to flag a quote as lost instead of following up again.
Real estate
A listing-consultation procedure that turns a walkthrough into a structured property feature sheet ready for an agent to finish and post.
Professional services
An intake procedure that organizes consultation notes into a consistent case summary for staff review, without offering advice on its own.
Keep reading
Related
Method
How We Work
The seven-step Theory of Operation we use to diagnose a workflow before building anything.
Flagship
AI Concierge
Where knowledge bases and SOPs like these get built, session by session.
Guide
How HVAC companies use Claude
A worked example of a company knowledge base in a trade business.
Questions
FAQ
What tool do you build these in?
We build these inside a Claude workspace: a company knowledge base plus tools for specific recurring tasks, connected to what you already use.
Will our team actually use it, or will it sit unused like the old SOPs?
The difference is that it's built into the tool people are already using to draft the work, not a separate document to remember to check. That's what makes it get used.
How long does it take to turn one process into a working SOP?
A single, well-understood process is usually one session: capture it, structure it, and load it in. Larger or messier processes take longer, and we'll tell you honestly which kind yours is.
Next step
Let's find the knowledge that only lives in one person's head
A short call to talk through the processes your business depends on that aren't written down anywhere your whole team can reach.