Most RIA leaders know what their firms spend. They know their payroll, technology costs, vendor relationships, and other major operating expenses. But ask a more specific question: “What does it actually cost your firm to rebalance one account?” and the answer becomes much harder to produce. The expenses are visible. The cost of the work itself often is not.
I think that distinction matters more as firms grow. We talk frequently about improving efficiency, increasing advisor capacity, automating workflows, and using AI to reduce manual work. But it is difficult to know whether any of those efforts are improving the operating model if there was never a baseline in the first place. Before we decide what to automate, replace, integrate, or hire around, we need to understand what the current process actually costs.
The principle is simple: measure before you manage.
We Measure the Inputs, Not the Work
Most firms are reasonably good at measuring inputs. Compensation is recorded. Technology contracts have a price. Vendor invoices arrive every month. These numbers make their way into budgets and financial statements, giving leadership a clear picture of what the organization spends. But those expenses do not necessarily tell us how efficiently resources are being converted into work.
Rebalancing is a useful example. The process is not simply the moment when a trade is generated. Depending on the firm, it can involve identifying accounts requiring attention, reviewing portfolios, preparing data, handling restrictions, resolving exceptions, approving recommendations, executing trades, reconciling activity, and providing oversight. Different people and systems may participate at different stages. A few minutes of manual work can appear insignificant until it is repeated across hundreds or thousands of accounts.
This is where expense visibility and operational visibility begin to diverge. A firm may know exactly what it pays for its portfolio technology and exactly what its investment operations team earns, yet still have no reliable answer for what completing the rebalancing process costs per account. Knowing what you spend is not the same as knowing what your operations cost.
The Costs You Don’t Measure Become Growth Assumptions
When firms cannot measure the economics of a process, they tend to manage it through proxies. Teams feel overloaded. Turnaround times increase. Advisors spend more time on operational work. Exceptions accumulate. Eventually, leadership concludes that more capacity is required. The obvious response may be another hire, another application, or another layer of automation.
Any of those decisions could be correct. The problem is that without a baseline, it becomes difficult to prove what actually improved. Suppose a firm adds operations staff as account volume grows. Did the organization successfully scale, or did it simply add people at roughly the same rate that operational complexity increased? Suppose it introduces a new platform. Did the cost of servicing each account decline, or did the technology simply shift work from one team or system to another? Activity changed, but the economics may not have.
This is one reason growth can become progressively heavier. Costs that were insignificant at one level of scale become structural when repeated across a larger account base. Manual reviews, data movement, approvals, reconciliations, and exceptions can quietly absorb capacity without appearing as distinct line items on a financial statement. If we do not measure those costs, we risk treating their consequences as unavoidable features of growth rather than characteristics of the operating model.
Start With Cost Per Account
I believe a better conversation starts by changing the unit of analysis. Instead of looking only at broad technology spend or total operations headcount, take a defined workflow and ask what it costs to complete that work for an account. Rebalancing is a logical place to begin because it touches people, technology, data, controls, and investment processes.
At a high level, the framework does not need to be complicated. Start with the people involved in the process and the time they contribute. Add the relevant technology and infrastructure supporting that work. Then account for process overhead—the handoffs, approvals, checks, data movement, and administrative steps required to get from the beginning of the workflow to the end. Finally, examine exception handling, because the standard workflow rarely tells the complete story. Together, those elements begin to reveal the total operational cost of rebalancing. Divide that cost across the accounts processed, and the firm begins to establish a meaningful cost-per-account baseline.
The arithmetic is the easy part. The harder part is deciding what belongs in the calculation. A process that appears automated may still depend on substantial human oversight. An integration may move data automatically but still require someone to validate it. An exception may take only a few minutes but occur frequently enough to matter. That is why cost-per-account should not be treated as another accounting metric. It is a way of exposing how the operating model actually works.
Measurement Changes the Technology Conversation
Once a firm has that visibility, the technology conversation changes. Instead of asking whether a new platform offers more automation, leadership can ask whether it reduces the resources required to complete the process. Instead of measuring success by implementation, feature adoption, or the number of tasks automated, the firm can examine whether the economics and capacity of the workflow actually changed.
The same discipline should apply to AI. There will be no shortage of opportunities to automate reviews, analyze data, generate recommendations, summarize information, or assist employees. But automating an activity is not automatically the same as improving the operating model. If AI saves time in one step while the workflow still requires manual intervention somewhere else, the overall economic improvement may be smaller than it appears. Measurement gives firms a way to separate visible automation from meaningful operational change.
This does not mean every technology investment needs to reduce cost. Some investments improve control, client experience, investment capability, or risk management. Those outcomes matter. But when the objective is efficiency or scalability, firms should be able to demonstrate that the operating economics changed. Technology should not merely add capability. At scale, it should change the economics of the work it was intended to improve.
Measure Before You Manage
As RIAs become larger and their operating environments become more complex, I believe unit-level operational visibility will become increasingly important. Leadership cannot rely indefinitely on aggregate technology budgets, headcount ratios, or a general sense of whether teams are busy. Those measures describe the organization from the top down. Cost per account begins to show what is happening from the workflow up.
The objective is not simply to find places to cut costs. It is to make better structural decisions. Once you understand what a process costs, you can begin asking better questions about what should be automated, integrated, redesigned, consolidated, or supported with additional people. You can also establish a baseline against which future investments can be judged. Without that baseline, efficiency remains largely an impression.
So before deciding that a process needs more people, more technology, or more AI, measure the process you already have. Understand where the resources go, where manual work remains, and where exceptions consume capacity. Measure before you manage. Because you cannot improve the economics of an operation you have never taken the time to see.
