The Quiet Cost Nobody Budgets For
Most organizations budget for the tool. They account for the license, the integration work, the consultant hours. What they do not budget for is the harder thing: getting their people to actually use it.
There is a rule of thumb in enterprise technology that for every dollar spent on an AI initiative, an organization needs three more dollars — sometimes more — for change management. That ratio does not show up in the vendor proposal. It rarely shows up in the internal business case either. And so it catches teams off guard, usually after the platform is live and the adoption numbers are quiet.
For credit unions and community financial institutions, this is not an abstract principle. It is a pattern that shows up again and again.
The tip of the iceberg
What Change Management Actually Means
The phrase carries a lot of baggage. It sounds like a workshop, a slide deck, a communications plan with a rollout timeline and a ribbon-cutting announcement. Those things can be part of it. What they are not is the substance of it.
Change management, in the context of AI, is the work of answering the questions your team is actually asking — out loud or not. Will this replace my job? Do I have to learn a new system on top of everything else? Who decided we were doing this, and why did no one ask me? What happens if I make a mistake using it?
Those are not HR questions. They are the questions that determine whether a six-figure platform gets used or sits idle.
Consider the typical pattern: a credit union invests in a marketing intelligence tool or a member analytics platform. The executive team is aligned. The vendor demo went well. Implementation takes longer than planned but the system eventually goes live. Then six months pass, and the staff is largely working around it, not with it. The data is there. The reports are available. The capability is real. But the workflow did not change, and the people were not brought along far enough or early enough to change it themselves.
The tool did not fail. The adoption did not happen.
A fork on the road
The Ratio and What It Is Telling You
The 3:1 figure is a signal worth sitting with. It is not prescriptive — not every initiative will need exactly three times the change investment — but it reflects something true about where AI projects actually break down.
They break down at the human layer.
The technology decision is often the easiest part. The harder decisions are about roles, workflows, accountability, and trust. Who now owns the insight that used to live in someone's head? How does a branch manager act on a recommendation the model generated? What do front-line staff say when a member asks how the credit union knew to offer them a loan product this month?
These are not implementation questions. They are organizational design questions, and they deserve the same rigor and budget as the technical work.
What the ratio is really saying is this: do not treat the human side as a cost to minimize. It is where the investment pays off or does not.
Why Community FIs Cannot Afford to Skip This
A larger bank can absorb a failed rollout. It has the bench to try again, the budget to re-engage, the organizational slack to let a stalled initiative sit while another team builds momentum elsewhere.
A community financial institution does not have that slack. A mid-sized credit union that spends eighteen months and a meaningful portion of its technology budget on a platform its staff does not adopt has not just lost money. It has lost the window. It has also confirmed, for the skeptics on the team, that AI initiatives are not worth the disruption.
That is a difficult position to recover from.
With that said, the 3:1 rule is not a reason to hesitate on AI investment. It is a reason to plan honestly. An initiative scoped with change management built in from the start, not added on at the end, looks different at every stage. The diagnostic work happens earlier. The people who will live with the system are in the room before the vendor is selected. The questions about workflow and accountability are answered before go-live, not after.
Furthermore, this kind of planning is available to resource-constrained organizations. It does not require a separate organizational effectiveness budget or a change management firm on retainer. It requires treating the human side of the initiative as a first-class design problem, from the first meeting.
Blueprint
Building It Once, Building It Right
The goal for any community financial institution is to make an AI investment that does not need to be made again next year. That means the platform works, the workflows adapt, and the staff trusts the output enough to act on it.
None of that happens by accident. It happens because someone asked, early and honestly, how this will change the way people work — and whether those people are ready for that change, and what it will take to get them there.
The technology question is worth asking. The change question is the one that decides whether the answer matters.
Elias Kruger, MBA, is the Managing Principal of Long-Range AI Consulting LLC, where he provides advanced analytics strategy and AI-powered business transformations tailored for midmarket sectors, including community banks, credit unions, and fintechs. His career spans over 22 years of continuous reinvention across finance, data science, and enterprise AI leadership, notably serving as a Vice President at Wells Fargo where he co-led an internal analytics consulting program of over 60 analysts. As a diagnostic-first practitioner, Elias designs customized human-empowering AI-enabled solutions ranging from multi-agent orchestration, RAG-powered workflows to predictive modeling that drives operational efficiency and valuation increases. He is a frequent speaker at major industry conferences like Finnovate.