Yes, for the workflows you actually plan to automate. AI works off what your firm has written down, not what your best bookkeeper does from memory. Undocumented process is the single biggest reason AI projects stall, so you document the target workflow first and then automate it. You do not need to document the whole firm to start.
Last updated: July 16, 2026
Do I really need documentation, or is that just consultant busywork?
You need it for anything you want a machine to run, and it is the opposite of busywork. Documentation is the only thing the AI can actually read. Everything else in your firm lives in people, and the model cannot see people.
I run into the pushback constantly. A firm owner says their team knows the work cold, so why write it down. That is true and it is exactly the problem. The knowledge being excellent and being trapped in someone’s head are the same fact, and the second half is what breaks an AI build. When your senior bookkeeper does month-end, she is running a hundred small decisions she has never made explicit: which accounts to reconcile in what order, when a variance is normal versus worth a call, which client always books their loan payment to the wrong account so she fixes it every month without thinking. Ask a machine to do that job and it inherits none of those decisions. It inherits a blank page.
Why does undocumented process break AI specifically?
Because the model has nothing accurate to imitate, so it invents. And an invented answer inside accounting looks exactly like a real one until someone catches it at review, if they catch it.
The failure data is blunt about where projects die. MIT’s Project NANDA studied the state of AI in business and found that 95% of enterprise generative AI pilots delivered no measurable return on the P&L (MIT Project NANDA, via Fortune). When you look for the reason, it is not the model. Informatica’s CDO Insights 2025 survey put data quality and readiness at the top of the obstacle list at 43%, and found only 12% of organizations said their data was actually of sufficient quality and accessibility for AI (Informatica CDO Insights 2025). Undocumented workflow is the human version of dirty data. Same story, told about people instead of records.
How do I know if a workflow is documented enough?
Use one test: could a competent person who has never done this job run the process from what is written down, without tapping your senior staff on the shoulder? If yes, it is documented. If they would get stuck and have to ask, it is not.
That “they would have to ask” moment is the whole thing. It is the undocumented “it depends” hiding inside a process that felt finished. In practice it shows up the second we try to write the workflow down with a client. We get three steps in and someone says “well, it depends on the client,” and now we are chasing a rule nobody ever made explicit. That gap is exactly where the AI would have guessed wrong, and we found it with a pen instead of a failed six-month build.
| Not documented | Documented |
|---|---|
| “Sarah just knows how this client’s books work” | The client’s coding rules and quirks are written down and followable |
| The close happens, but the steps live in memory | The close is a checklist someone new could execute |
| “It depends” with no rule behind it | The decision rule is explicit and on paper |
| Review catches errors because a specific person is careful | Review has defined checks anyone qualified could run |
So do I document everything before I touch AI?
No, and this is where firms overcorrect. You document the specific workflow you want to automate, prove it works, then move to the next one. Documenting your entire firm before you are allowed to try anything is its own kind of stall.
This is what the readiness step is for. The AI Readiness Audit tells you which workflows are already documented enough to automate now, which need to be written down first, and which should stay human for now. If the honest answer is that too much lives in heads, the next step is the Operational Foundations work, where we write the SOPs so there is finally something worth amplifying. This is the same logic as our pillar piece, AI only amplifies what it can read: amplify the documented workflow, not the guesswork.
Your next step
Start with the AI Readiness Audit. It is $750, it credits toward the build, and it tells you exactly which of your firm’s workflows are documented enough to automate and which are not.
If you are trying to decide where to point AI first, read where should a bookkeeping firm use AI first. If your bigger worry is the underlying data, start with how to clean up client data before using AI in your firm. And the broader case sits in the landing page, AI for accounting and bookkeeping firms.