All articles

Commercial Analysis

Wealth Technology Demand: Accounts, Adviser Workflows and Platform Change

Connect wealth-management growth to technology demand through asset composition, account workloads, budget ownership and replacement triggers.

Nerish MarakContent Writer2025 edition · Evidence through Published 11 min readIntermediate
  • Wealth Management
  • AUM
  • Wealth Technology
  • Platform Economics

Market appreciation can raise a wealth manager's assets without adding an account or a transaction. New client households can increase onboarding, reporting and service work even when asset prices are flat. Technology demand is more closely tied to those operating changes and to platform constraints than to one asset headline.

This analysis separates asset growth from account workload, then follows the budget and replacement decision. It uses disclosures and measurement guidance available through December 2025. The final comparison is illustrative and does not estimate a wealth-technology market.

AUM composition and the fee relationship

AUM is not a universal accounting field. The SEC Form ADV General Instructions define regulatory assets under management around securities portfolios for which an adviser provides continuous and regular supervisory or management services. The instructions address portfolio value, private funds, accounts with no compensation, and assets managed by another person. A firm’s investor presentation may use a broader “assets,” “assets under advisement,” or “platform assets” measure.

Record the legal entity, valuation date, mandate, custody relationship, discretionary status, currency, and whether the number is ending or average AUM. The SEC’s Form ADV FAQ also distinguishes regulatory AUM from an adviser’s own balance-sheet assets. A clean definition is the first control against treating a client-asset measure as a budget or revenue measure.

Separate market appreciation, flows, and acquisitions

AUM growth can have different operational consequences. Market appreciation may increase reported asset value while adding no households or advisor work. Net inflows can add accounts, onboarding, suitability checks, and service requests. An acquisition can bring a new book, a new custodian, data conversion, duplicate systems, and contractual integration work. Outflows can shrink the asset base while leaving the platform footprint and licenses in place.

Ask management for the bridge from opening AUM to closing AUM: market movement, net flows, transfers, acquisitions, divestitures, and foreign-exchange effects. If only a year-end percentage is supplied, preserve the causal gap. Growth caused by prices is evidence about asset value; it is not evidence about seats, transactions, or replacement timing.

Translate AUM into fee revenue carefully

AUM can influence fee revenue when a contract prices advice, administration, custody, or processing as a percentage of assets. It does not make the relationship one-to-one. Fee schedules can tier down at higher balances, exclude certain products, apply to average rather than ending assets, or be shared with a broker, platform, or sub-adviser. Some wealth-tech vendors charge per account, user, household, transaction, module, or fixed subscription instead.

BlackRock’s 2024 Form 10-K illustrates the separation: investment-management fees are generally tied to AUM, while Aladdin technology-services revenue is tied to positions, users, implementation, and support. The same company can therefore have an asset-sensitive business and a usage or contract-sensitive technology business. Model the fee rate and the technology price as separate variables.

The adviser, account and platform workload

AUM can sit in several value-chain reports. An adviser may make investment decisions; a broker-dealer may hold the account; a custodian may provide statements and data; a turnkey asset-management platform may supply models and trading; a software vendor may provide CRM, planning, portfolio accounting, or compliance workflows. A provider’s “platform assets” may therefore include client assets that it does not own or manage.

Charles Schwab’s 2024 filing reports client assets, brokerage accounts, workplace participants, and bank accounts as different operating measures. That mix shows why a client-asset total cannot substitute for advisor count, account complexity, or software usage. Start the buyer map with the operating role, data rights, billing owner, and workflow owner for each number.

Distinguish advisor capacity from asset scale

Technology demand often follows the work required to serve clients, not the market value of their portfolios. A firm with more AUM from appreciation may have the same advisors, households, plans, and service events. A firm that adds smaller accounts may have lower AUM per household but substantially more onboarding, rebalancing, reporting, and support work.

Track advisors, households, accounts, plans, service interactions, trades, managed sleeves, and exceptions beside AUM. LPL Financial’s 2024 filing connects continued technology investment to integrations, advisor-platform experience, and institutional onboarding. That is evidence that implementation and workflow can trigger spend independently of a simple AUM change.

Measure workflow and account complexity

AUM does not describe the number of tax lots, account registrations, model portfolios, alternative investments, beneficiaries, restrictions, or custodial feeds that a platform must process. Complexity can rise when assets move into private markets, separately managed accounts, direct indexing, or multi-custodian arrangements. It can also fall after standardization or a book consolidation.

Build a workload inventory with the unit that drives effort: accounts, households, advisors, positions, orders, documents, feeds, or exceptions. Note whether the metric is an average, a peak, or an end-period count. A platform budget should be tied to the workload it automates and the control it provides, not to an unlabeled asset headline.

Technology budget and purchasing authority

A firm’s operating expense includes people, occupancy, compensation, compliance, data, marketing, servicing, and technology. A technology budget may include licenses, cloud infrastructure, implementation, integration, cybersecurity, support, and internal engineering. Public filings rarely expose a clean “wealth-tech budget” line, so do not infer it from total expenses or from AUM growth.

SEI’s 2024 Form 10-K is a useful comparison point: it reports technology and operations outsourcing revenue separately from asset-management fees and describes investment-processing services priced through contracted fees or asset-linked measures. The distinction works both ways. A vendor’s asset-sensitive revenue does not reveal a client’s internal software allocation, and a client’s rising expense does not reveal which vendor captured it.

Identify the budget owner and buying unit

The budget owner may be a chief investment officer, wealth-platform leader, operations executive, chief information officer, compliance officer, or business-line president. The buying unit may be an enterprise, an acquired practice, a broker-dealer, an RIA network, or an advisor team. AUM can be reported centrally while the purchase decision remains local.

Ask who approves the business case, who owns implementation risk, whose budget pays the recurring fee, and whether the spend is capitalized or expensed. Envestnet’s filing describes technology, data, and wealth solutions serving firms, advisors, and enterprises; that multi-sided structure means platform assets and contract ownership must be tested rather than assumed.

Replacement, contract and resilience requirements

Replacement spending is usually triggered by a change in the operating stack: a core-system sunset, an acquisition, a custody change, a regulatory requirement, a security incident, poor adoption, service-level failure, or a material workflow redesign. AUM growth can make the trigger more urgent if the existing platform cannot scale, but growth alone is not the trigger.

Separate three cases: expansion of the existing platform, integration of a new book, and replacement of a core system. Each has different implementation hours, data conversion, parallel-run, training, and switching costs. LPL’s discussion of technology investment for integrations and advisor experience supports this distinction; the filing does not establish a universal spending rate.

Read contract, seat, and usage economics

Record the pricing unit and the commitment. A contract may charge by advisor seat, account, household, asset band, transaction, module, API call, implementation phase, or minimum annual fee. It may have volume tiers, step-downs, pass-through data costs, renewal uplifts, or a separate professional-services statement of work.

AUM matters only when it is the contract’s defined billing base. If the license is per advisor, rising AUM with flat advisor count may not change recurring price. If the contract is per account, an acquisition of many small accounts may matter more than market appreciation. If pricing is asset-based, test the rate card, exclusions, average-versus-ending balance, and revenue share before modelling vendor capture.

Account for compliance, security, and resilience work

Compliance and resilience can create technology demand without any AUM change. The SEC Regulation S-P final rule requires covered financial institutions, including registered investment advisers, to maintain written incident-response policies for unauthorized access to customer information and to notify affected individuals in specified circumstances. That makes data lineage, access controls, retention, and incident response part of a buying case when the relevant obligations apply.

FINRA’s Regulatory Notice 21-29 reminds member firms that outsourcing does not remove supervisory responsibility and highlights vendor due diligence, contracts, records, and controls. Treat those obligations as procurement requirements and implementation work. Do not convert a rule into a universal budget number; identify the firm, jurisdiction, role, and effective requirement.

Deployment, retention and vendor economics

A vendor can report assets processed, administered, advised, or managed while recognizing revenue from subscriptions, processing fees, implementation, custody, or asset-based fees. The denominator may be client assets; the numerator may be a contract fee. Those measures should not be divided together unless the scope and period match.

SEI describes investment-processing fees as contracted services or a percentage of market value, while information-processing and software-servicing fees are reported separately from asset-management, administration, and distribution fees. Morgan Stanley’s 2024 filing likewise presents wealth-management revenue across fee-based asset management, transactional activity, net interest, and other categories. Use each issuer’s definitions and reconcile only comparable lines.

Check adoption, retention, and implementation success

Signed contract value is not deployed value. Measure implementation milestones, data-conversion completion, advisor activation, active-user rate, account coverage, workflow completion, exception rate, support volume, renewal, expansion, and termination. A growing AUM book can mask weak adoption if new assets remain on a legacy system or if the acquired advisors use only a small part of the platform.

Define the cohort and time window. “Users” could mean provisioned seats, monthly active advisors, or one login. “Assets on platform” could mean accounts connected, assets reconciled, or assets billed. Keep adoption and retention measures separate from AUM so a buyer can see whether technology is actually embedded in the operating model.

Use a wealth-tech taxonomy without double counting.

Assign each opportunity one primary workflow and one economic owner. Do not add advisor-desktop software, custody technology, portfolio accounting, and asset-management fees into a single “wealth-tech market” total unless the boundary explicitly supports it. A clean taxonomy prevents a broad AUM narrative from counting the same platform relationship more than once.

Build an AUM-to-spend buyer filter

The buyer should be able to follow the signal from assets to a specific operational change and then to a contract. Require the AUM definition and bridge, advisor and account workload, fee and margin base, budget owner, pricing unit, replacement trigger, implementation plan, compliance scope, adoption measures, and vendor-recognition rule. If one link is unavailable, keep the spending implication unavailable.

Scroll horizontally to compare all columns.

AUM signalWhat it can establishWhat it cannot establishRequired follow-up
Ending regulatory AUMAsset value within the stated mandate and dateAdvisor capacity, accounts, budget, or software revenueConfirm Form ADV scope, valuation date, and discretionary basis
AUM growth rateChange between comparable asset observationsCause of growth or technology workloadSplit market movement, flows, transfers, acquisitions, and FX
Net inflowsAdditional assets entering the stated relationshipNew account count, implementation effort, or vendor captureReconcile households, accounts, custodians, and onboarding work
Advisor countPotential service capacity and seat populationProductivity, adoption, or spend per advisorMeasure active advisors, roles, workflows, and license assignment
Account or household countRelationship and servicing volumeAsset value, complexity, or fee revenueSegment registrations, balances, tax lots, and service events
Platform assets or positionsPotential processing scale for the named platformClient ownership, contract value, or recognized revenueDefine custody, usage, billing base, and reconciliation rules
Technology expense or vendor revenueA reported spend or revenue line for the named entityIncremental spend caused by AUM growthRead accounting policy, contract unit, period, and shared costs

Two different growth paths for the same asset base

Imagine two hypothetical firms starting with $1 billion of AUM and 10,000 accounts. Firm A's assets appreciate 10%, while its account count and workflows are unchanged. Firm B also reaches $1.1 billion, but through 1,000 new accounts with onboarding and reporting work. Both finish with the same AUM and a different technology workload.

If an invented platform contract charges $20 per active account per year, Firm A's account-based fee stays at $200,000; Firm B's becomes $220,000. A contract based on average AUM, a fixed licence or transaction volume would produce a different result. These assumptions explain contract sensitivity, not prevailing prices.

The research should then test whether existing capacity can handle the extra accounts, whether integration or service costs increase, and whether a renewal or replacement event is approaching. Additional workload may be absorbed by a current platform rather than create an open vendor opportunity.

Prioritise the account, workflow or platform change that the buyer must fund. Match it to the contract basis and approving entity, then test implementation capacity. Asset growth supplies context; the operating constraint and procurement window establish the technology opportunity.

Discuss the evidence you need

Define the market, geography and questions your research must answer.

Sources

  1. SEC Form ADV General Instructions
  2. SEC Form ADV and IARD frequently asked questions
  3. BlackRock 2024 Form 10-K
  4. Charles Schwab 2024 Form 10-K
  5. LPL Financial 2024 Form 10-K
  6. SEI Investments 2024 Form 10-K
  7. Envestnet 2023 Form 10-K
  8. Morgan Stanley 2024 Form 10-K
  9. SEC Regulation S-P final rule
  10. FINRA Regulatory Notice 21-29: Vendor Management and Outsourcing

Continue your research