Cost-to-serve in wealth management: measure effort before claiming savings
Measure the work behind client service. Separate active effort, waiting time, shared costs, released capacity, and realized expense reductions.
Cost-to-serve in wealth management is the cost of delivering a defined service to a client, household, or account over a defined period. A useful model connects staff effort, directly attributable expenses, and an explicit share of common costs to the work delivered. It does not treat AUM, elapsed processing time, or the number of software tools as a substitute for measured effort.
For operations and finance leaders, the question is specific. Which activities consume resources, and what would actually change if the workflow improved? Answer that before converting a demonstration of fewer clicks into a savings claim.
Define the service before calculating its cost
Start with a unit of work that has a recognizable beginning and end. A completed account-opening request, an annual review, or a client-record update can each be measured. A household's annual service cost combines those activities with the recurring relationship work.
Keep acquisition, initial onboarding, ongoing advice, and account servicing separate. Otherwise, a newly onboarded household can appear expensive relative to an established relationship simply because the measurement periods contain different work.
Choose the denominator deliberately. Cost per completed request answers a process question. Cost per household-year answers a relationship question. Cost per account may help compare servicing workflows, but it can obscure households with several accounts. State which one the analysis uses.
Michael Kitces' guidance on advisory-firm KPIs distinguishes direct expenses from overhead and discusses estimating client profitability using advisor and staff time. The principle remains useful; historical numerical benchmarks should not replace your own firm's cost data.
Separate active effort from waiting time
A request can take days to complete while consuming far less than a day of staff effort. Capture both measures, but do not price the entire interval as labor.
Track the work by role and activity:
- Advisor time spent gathering context, explaining options, or responding to a client.
- Service-team time spent preparing information and coordinating a request.
- Operations time spent processing, checking, or reconciling the outcome.
- Review time required by the firm's policies.
- Rework and status-chasing time after the first attempt.
Record waiting time separately, including client response, queue delay, and external processing. Delay can matter to the client without representing continuous staff labor. Follow-up calls during that delay do consume labor and belong in active effort.
Do not infer minutes worked from the gap between two activity timestamps. Sample representative cases, ask staff to record active effort, and check the sample against the workflow history. A task count without a time estimate is a volume measure, not a cost estimate.
Build a cost model that avoids double-counting
For a bounded workflow, estimate labor cost by multiplying active hours for each role by that role's loaded hourly cost, then adding the results. Add expenses attributable to the case. Show shared-cost allocations separately.
Ask finance to define the rate consistently. Compensation, employer costs, available working hours, and the treatment of training and leave all affect it. A rate based on total paid hours and a rate based on available service hours answer different questions. Do not switch denominators between the baseline and the comparison.
For shared technology, management, and support costs, document the allocation rule. ACCA's explanation of activity-based costing describes cost pools, cost drivers, and assigning costs according to resource consumption. Applying that principle to wealth operations means choosing a driver that reflects the activity rather than allocating every expense by AUM.
Avoid charging the same support cost through both the role's hourly rate and an overhead allocation. Reconcile the model to the firm's financial accounts. An internal workflow estimate can use different classifications from a financial statement, but the difference needs to be visible.
Compare similar service commitments
Group cases by factors that change the work, such as account structure, custodian, service commitment, or whether the relationship is new. Compare equivalent periods and include unsuccessful or abandoned requests in the workload view, even when the completed-case denominator excludes them.
A simple case log needs a service type, relationship identifier, start and completion dates, active effort by role, rework reason, and outcome. Use identifiers rather than unnecessary personal details, with access governed by the firm's policies.
Look at typical cases and the expensive exceptions separately. A single average can conceal a workflow that works well for ordinary requests but repeatedly requires specialist intervention.
Kitces Research's advisor-productivity analysis discusses team structure, client complexity, client face time, and pricing. Its survey analysis also found little relationship between technology investment and revenue productivity in that sample. This is not proof that software cannot help. It is a reason to measure the work and the service model rather than assume another application creates capacity.
Distinguish capacity from realized savings
When a changed process reduces active effort, describe the benefit accurately:
- Released capacity means staff have time available for other work.
- Avoided future cost means a documented hiring, overtime, or outsourcing requirement no longer arises under the same service assumptions.
- Realized expense savings means actual spending falls, net of the change's operating costs.
These are different outcomes. Removing an administrative task does not immediately remove a salary expense. Released advisor time does not become revenue unless it is used for work that produces revenue.
Include platform fees, implementation, training, support, and ongoing review in the comparison. Do not count the same benefit once as labor savings and again as additional capacity. Keep assumptions about future volume and adoption separate from observed results.
Schwab's 2026 RIA Benchmarking Study includes operating margin, time spent on client service and operations, and standardized workflows in its Firm Performance Index. Its data is self-reported by participating Schwab-custodied firms and was not independently validated by Schwab. Use industry research for context, not as proof of your firm's savings.
Keep service quality in the comparison
Lower cost is not an improvement if the service becomes incomplete or required review disappears. Compare effort alongside completion quality, reopened cases, outstanding work, and the client's experience of the process.
Specify which checks must remain before testing a change. If a workflow becomes faster only because work moves to advisors, clients, or a different department, include that transferred effort. If cases accumulate unresolved, the apparent saving may simply be unfinished work.
Review the cost estimate with the people who deliver the service. Their case history can explain whether rework comes from missing information, unclear ownership, unnecessary duplication, or a legitimate complex request. Each cause calls for a different response.
Use connected workflow evidence, not assumed outcomes
OneVest's Advisor Workspace brings client profiles, portfolio data, task queues, and cross-system workflows into one workspace. Client Management consolidates client records and activity context. Those capabilities are relevant when investigating where work happens and why a team repeats it.
The Operations Workspace centralizes workflows, approvals, and exceptions for home-office oversight. Evaluate that operating context against your selected service boundary and cost baseline. The product descriptions do not establish a native cost-accounting engine, measured labor minutes, or a guaranteed reduction in staffing expense.
Start with one service, keep its control requirements intact, and compare actual effort before and after the change. A defensible cost-to-serve model explains where the benefit comes from and whether it has reached the firm's expense base.
Explore OneVest Operations Workspace.