Yes, you need documented workflows before adding AI to your RIA. AI works off what your firm has written down, not what your advisors carry in their heads. Undocumented workflows are the single biggest reason AI projects fail, and at an advisory firm those same gaps are where your compliance and data problems hide. Document first, then point AI at the parts that are actually ready.
Last updated: July 16, 2026
Why can’t I just add AI to how we already work?
Because “how you already work” mostly is not written down anywhere a model can read it, and AI can only work from what it can read. Your firm runs on judgment built over years, a hundred small decisions your senior people make automatically. The AI does not inherit that. It inherits whatever you have actually documented, and for most firms that is a fraction of how the place really runs.
The consequences show up in the numbers. 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). That is almost everyone, and when you look at why, you do not find a story about weak models. You find a story about the process and data underneath. Informatica’s research put data quality and readiness at the top of the obstacle list at 43%, with only 12% of organizations saying their data was actually of sufficient quality for AI (Informatica CDO Insights 2025). Read those together. Almost nobody gets a return, and almost nobody has the documented, clean foundation that would produce one. Same story, told twice.
What actually breaks when the workflow isn’t documented?
The build breaks at the “it depends.” Here is how these engagements really go. We sit down to write the process the firm wants to automate, say the review-meeting prep or the onboarding sequence, and nine times out of ten we cannot finish, because halfway through someone says “well, it depends,” and now we are chasing a decision rule nobody ever made explicit. That moment is the whole point. That gap is exactly where the AI would have failed, filling the hole with a confident, plausible, wrong answer, and we found it on a whiteboard instead of in a failed six-month project.
At an RIA the gap is worse than a productivity problem, because the undocumented workflow is usually also where your compliance and data hygiene are weakest. The step nobody wrote down is the step where client data moves without a rule, where a record does not get filed consistently, where the marketing language never got substantiated. Documenting the workflow does not just make AI possible. It closes those gaps at the same time. You pay once and fix two problems.
Isn’t our data mostly in the CRM already? Doesn’t that count?
Having a CRM is not the same as having clean, structured, trustworthy data in it, and AI is brutally sensitive to the difference. Billion-dollar RIAs, the most sophisticated firms in the industry, name improving data visibility and usage as a top challenge at 35% (Cerulli Associates, U.S. RIA Marketplace 2025). If the biggest firms with the biggest budgets are still fighting their data, the half-filled fields and inconsistent notes in a smaller firm’s Redtail or Wealthbox are not going to feed a reliable AI build.
This is the thesis, and it is not complicated: AI only amplifies what it can read. Point it at a documented workflow feeding clean CRM data and it amplifies a tight operation. Point it at an undocumented process feeding messy data and it amplifies your guesswork, faster and with more confidence than a human would ever dare.
What does “document first” actually look like?
It is the unglamorous work, and it is the part that makes everything after it succeed. You write down how the firm actually handles the workflow you want to automate: the steps, the decision rules including the ones that currently live as “it depends,” where the data comes from, and where the output goes. That is the Operational Foundations work, and it exists precisely because so many firms are not ready to build yet. It is not a consolation prize. It is the thing that turns a coin-flip AI project into one that works.
Documenting first is also cheaper than the alternative. A failed AI build costs you the money, the time, and the trust of a team that now believes “AI doesn’t work here.” Writing the workflow down first costs a fraction of that and tells you the truth before you spend. That is why the AI Readiness Audit is step one: it finds the gaps for a few hundred dollars instead of letting a build find them for six figures.
Your next step
If you are wondering whether your firm is ready to build, that question has a cheap, honest answer. The AI Readiness Audit tries to document your target workflow, shows you exactly where it breaks, and tells you whether to build now or do the Foundations work first. It is $750 and credits toward the build.
For the low-risk starting points once you are ready, read where should a financial advisor use AI first. For the full picture, the RIA landing page. And for the idea under all of it, AI only amplifies what it can read.