For ops teams
SOPs your team writes once and your agents actually follow.
Most SOP software produces documents nobody opens. In Patina, an SOP is a playbook: it carries the steps, the inputs, and the context — and your agents run it, the way your best person runs it.
Start your 14-day free trial$149/mo after trial · Cancel any time
An SOP that runs
Write the procedure once — the steps your best person follows without having to think about them — and attach the context it depends on. From then on, any teammate or agent runs the same procedure and gets the same result. The know-how stops living in one person's head, and it doesn't leave when they do.
Exceptions update the SOP
The reason SOPs rot is that reality changes and the document doesn't. Here, when an agent working through a procedure hits a case the steps don't cover, it proposes an update — with the exception that prompted it attached. The operator approves, and the next run follows the new process. Your procedures stay current because keeping them current is part of running them.
Approved, versioned, current
Every SOP has a trust state: draft, approved, or deprecated. Approving a change is a recorded decision, and the old version stays in the history. A nightly sweep flags procedures that have gone stale or been superseded, so nobody discovers the outdated SOP by following it.
Built for teams going AI-native
No engineers required: your team writes procedures in plain language and reviews changes in one queue. If you're taking an ops or marketing team AI-native, here's what that looks like end to end — the SOPs are one part of a workspace where your voice, personas, and decisions live alongside them.
Your process, running without you in the room
SOPs live in the AI knowledge base your agents read, stay current through the AI memory, and change only through your team's review.
Start your 14-day free trial$149/mo after trial · Cancel any time