← Engagements
Category comparison
Lock vs. AI-generated policy templates
An AI tool can draft a policy document in seconds, but it does not know your company’s context or how that policy connects to the processes around it. Lock designs the fit and the connections; it does not templatize.
Comparison table
| Dimension | Lock | Alternative |
|---|---|---|
| What you get | A process fitted to your specific business model, constraints, and existing systems. | A generic, plausible-sounding document generated from a prompt. |
| Who runs it afterwards | The client’s own team, or Lock through a defined engagement. | The client, with no verification that the output fits or connects to anything. |
| Whether seams are connected | Yes — explicitly designed interfaces to upstream and downstream processes. | No — a single generated document has no awareness of adjacent processes. |
| Measures | Defined measures shipped with the process, reviewed on a cadence. | None, unless a person adds them afterward. |
| Price model | Published starting prices by scope (see /pricing). | Free or near-free per generation, with no accountability for fit. |
When not to use Lock
This comparison is not always in Lock's favor.
- You need a quick draft to react to, not an accountable operating process.
- The stakes of getting the process wrong are low enough that fit does not matter yet.
- You already have the process designed and just need document formatting.