Usually yes. AI reads your written procedures, not the judgment in your team’s heads, so if the workflow you want to automate has no SOP, the model is guessing. You do not need a binder for the whole agency. You need documented rules for the specific process you are about to hand a machine, and that is a much smaller job than it sounds.
Last updated: July 16, 2026
Do I really need an SOP before I add AI, or is that overkill?
You need one for the workflow you are automating, not for everything. AI cannot inherit the judgment your team carries around unwritten. It can only read what is on paper, so the process you hand it has to exist on paper first.
Here is the thing people miss. The reason AI feels magical in a demo and disappointing in your agency is that the demo runs on a clean, defined task and your agency runs on a hundred undocumented ones. MIT’s Project NANDA found that 95% of enterprise generative AI pilots delivered no measurable return on the P&L (MIT Project NANDA, via Fortune). When you dig into why, it is almost never the model. It is that the business pointed the model at a process nobody had written down. Informatica’s CDO Insights 2025 survey put data quality and readiness at the top of the obstacle list at 43% (Informatica CDO Insights 2025). The SOP is how you fix the readiness half of that before you spend a dime on the model.
What happens if I skip the SOP and just turn the AI on?
It works right up until it hits the part of the process that only lives in someone’s head, and then it guesses. The output looks polished and confident, which is exactly what makes a wrong guess dangerous in an agency.
Think about a renewal. Your service lead knows this carrier has been non-renewing older roofs, so she pulls the account early. She knows to check three things before she touches the account. None of that is written anywhere, so when you drop an automation on top of the renewal workflow, it does not know any of it. It processes the renewal the way the blank page tells it to, which is to say incorrectly, and it does so to your client. That is not a technology failure. It is a documentation failure wearing a technology costume. It is a people business, and when the people’s knowledge never made it onto paper, the machine is working blind.
Which SOPs actually matter before an AI build?
Only the ones covering the workflow you are about to automate, written to the level of detail where the decision rules are explicit instead of assumed. Here is what “documented enough for AI” looks like versus what most agencies actually have.
| What most agencies have | What AI actually needs |
|---|---|
| “Sarah handles renewals, she knows what to do” | A written renewal process another person could follow start to finish |
| “It depends on the account” | The decision rule spelled out: if X, then Y, escalate when Z |
| Notes scattered across email, sticky notes, and memory | One source that says how the workflow runs today |
| Success is whatever Sarah decides looks right | A defined outcome you can check the AI’s work against |
The good news is you are not late for needing to do this. Only about 6% of agency principals have actually implemented an AI solution (Agent for the Future, Liberty Mutual). You are not behind the field. You are ahead of the ones who skipped this step and are now quietly walking their projects back.
Do I have to document the whole agency before I can start?
No, and you should not try. Documenting everything at once is how the project dies before it produces anything. Pick the one workflow you most want AI to handle, write that process down to the point where the rules are explicit, and start there.
This is where simplicity is king. One documented workflow that AI can run correctly beats a half-finished automation strategy spread across your whole operation. Get one process onto paper, prove the AI can run it, then move to the next. If writing the process turns into a fight because nobody can agree on how it actually works, that is not a reason to quit. That disagreement is the exact gap the AI would have failed on, and you just found it for free.
Your next step
If you are not sure which of your workflows are documented enough to automate and which are still living in someone’s head, that is precisely what the AI Readiness Audit is for. It reads your agency the way an AI would, tells you what is ready and what needs an SOP first, and costs $750 that credits toward the build.
For the thinking behind all of this, read AI only amplifies what it can read. If you are ready to pick a starting workflow, read where an independent agency should actually use AI first. And if you are weighing the liability side, read whether AI increases your agency’s E&O exposure.