SOP Software
Executable SOPs
The procedure is in a doc. The work happens somewhere else. A new hire follows the doc, an old hand follows memory, and the two of them do the same job differently until a customer notices. SOP software is supposed to close that gap. Most of it just stores a better copy of the doc.
The SOP Nobody Follows
A standard operating procedure fails in a quiet way. It was true the week it was written. Then the warehouse changed who packs an order, the payment check moved, and the doc stayed. People stop trusting it, so they stop opening it. The file is still named "the process." It is a relic.
A new hire follows the doc, then spends the first week learning the exceptions the doc missed. Support answers from the file. The warehouse answers from the floor. An audit is assembled from chat logs, because the procedure has no record of what changed. A clearer sentence does not close any of those gaps. The written steps and the work are updated on different days, and a change to one does not reach the other.
A Real Operating Model
This is order fulfillment at BrightBox Commerce, compiled from that company's genome. Each step names who is accountable. The rule is in the step it governs, not a footnote someone might remember.
Order fulfillment
Owner Operations director
Placement through delivery confirmation, across catalog, inventory, and fulfillment.
SOP Software for Small Business
A small team does not need a suite. It needs one place where the way the work happens is the way the work is described. Google Docs is a fine place to draft that. It is a bad place to run it. A doc has no owner per step, no rule that blocks the next step, and no way to tell you the doc and the checkout flow have drifted apart.
At ten people you can still shout the correction across the room. At twenty you are forwarding the doc and hoping. SOP software for a small business earns its place when the correction lands in the procedure the team actually runs, including the agent that packs, refunds, or answers the ticket.
DNA
DNA Codes is the operating model those procedures live in. You describe the roles, the steps, and the rules once. The doc, the workflow, and the agent read that description. If you're interested, join the waitlist.