RIA Director of Operations: What the Role Actually Owns in 2026
A working guide for the person in the seat: the six domains a director of operations at a wealth management firm owns, how the job changes with firm size, the metrics worth reporting, and what to do in the first 90 days.
A director of operations at an RIA owns everything that has to happen between an advisor's recommendation and a correct client statement: opening and transferring accounts, keeping client data in the CRM accurate, running billing, reconciling and reporting, supporting the compliance program alongside the CCO, and running the tech stack and its vendors. At smaller firms the director does much of that work personally. At larger firms the job is designing the processes, leading the specialists who run them, and reporting a small set of operating metrics to the COO or CEO.
Job postings describe the role as a list of duties. This guide describes it the way it feels from inside: as a set of domains that each have recurring work, a predictable way of breaking, and a number that tells you whether they are healthy. If you are new to the seat, or you just inherited it after the last person left, start here.
The six domains a director of operations owns
Every RIA divides the work a little differently, but the same six domains show up at almost every firm, plus a seventh that arrives with growth. For each one, the useful questions are the same: what recurs, how it fails, and what you would measure to know it is fine without checking by hand.
1. Account lifecycle and custodian paperwork
The recurring work: new account applications, transfers of assets, beneficiary updates, address and account maintenance, standing instructions, and closing accounts. Most of it starts in the CRM household record and ends as a PDF packet at the custodian. The forms themselves are documented in our custodian account opening forms, ACAT transfer and account maintenance forms guides.
The failure mode: not in good order (NIGO). A missing signature, a mismatched account title, an outdated form version or a beneficiary percentage that does not add to 100 sends the packet back, and the client waits another week. NIGO is rarely a people problem; it is usually a data problem upstream in the CRM.
The health metric: NIGO rate and account-opening cycle time, both defined in the KPI section below.
2. Client data and the CRM
The recurring work: keeping household, contact, account and relationship records complete and current in Salesforce, Wealthbox, Practifi or Redtail; making sure the portfolio system and the CRM agree; and keeping workflows and task templates in the CRM matched to how the team actually works. See the best CRM for financial advisors for how the main CRMs differ.
The failure mode: drift. The same client has three different addresses across the CRM, the portfolio system and the custodian, and nobody knows which is right. Every downstream form, bill and report inherits the error.
The health metric: CRM data completeness on the fields your paperwork and billing actually depend on.
3. Billing and fees
The recurring work: running the billing cycle in the portfolio system (Orion, Black Diamond, Tamarac, Addepar or similar), applying fee schedules, householding, and exclusions, reviewing the output, and sending fee files to the custodian.
The failure mode: a fee schedule in the system that no longer matches the signed advisory agreement. That is an operations error with a compliance consequence, because it means clients were billed differently from what they agreed to.
The health metric: billing exceptions per cycle, and how many of them trace back to setup data rather than a one-off client request.
4. Reporting and reconciliation
The recurring work: daily reconciliation of positions and transactions between custodian feeds and the portfolio system, quarterly performance reports, client-meeting packets, and the internal reports leadership asks for.
The failure mode: breaks that age. One unresolved break is a task; a hundred breaks older than two weeks is a quarter-end crisis, and a reporting package nobody fully trusts.
The health metric: open reconciliation breaks by age, and the share of quarterly reports that go out without a manual correction.
5. Compliance operations, alongside the CCO
The recurring work: the CCO owns the compliance program. Operations owns much of the evidence it depends on: records kept and retrievable under Advisers Act Rule 204-2 (books and records), client paperwork on file, advisory agreements and fee schedules matching what is billed, and data handled in line with Regulation S-P. Under Rule 206(4)-7, the firm reviews its policies and procedures no less frequently than annually, and the CCO will ask operations to show how the procedures actually run. See RIA compliance automation for how firms structure that evidence.
The failure mode: procedures that describe how work should happen, while the team does something slightly different. The gap only shows up during the annual review or an exam.
The health metric: how quickly you can produce the record behind any client action, and how many annual-review findings land on operations. Where a question is a judgment call, it belongs to your CCO or counsel, not to the ops team.
6. The tech stack and vendors
The recurring work: owning the CRM, portfolio system, e-signature, document storage, planning software and the integrations between them; running vendor renewals and due diligence; onboarding and offboarding user access. Our RIA tech stack guide maps the common combinations and where the handoffs between systems break.
The failure mode: the stack grows by purchase, not by design. Each tool is fine; the work between them is still done by people copying data from one screen to another.
The health metric: the count of manual handoffs between systems in your top ten workflows, and whether it goes down each quarter.
Plus: M&A and transition integration
When a firm starts acquiring practices or recruiting breakaway teams, integration becomes its own domain. It combines every domain above at volume and under a deadline: moving households into your CRM, mapping fee schedules, repapering clients and running transfers in waves. Advisory contracts cannot be assigned without client consent under Section 205(a)(2) of the Advisers Act, which is why repapering is so much of the work; how consent is obtained in a given deal is a question for your CCO and counsel. See the RIA acquisition integration checklist, the client repapering guide and the breakaway advisor transition checklist.
How the role changes by firm size
There is no standard org chart for RIA operations, and team sizes vary more with service model, custodian mix and acquisition pace than with assets alone. The patterns below are typical shapes, not benchmarks.
| Firm stage | Who leads operations | Team shape | Where the director's time goes | The main risk |
|---|---|---|---|---|
| Under about $1B | A director or operations manager, often also acting COO | Player-coach plus a few generalists who each cover everything | Doing the work: paperwork, billing runs, CRM cleanup, vendor calls | Key-person risk: processes live in one or two heads |
| About $1B to $5B | Director or VP of operations, reporting to a COO or managing partner | Specialists: new accounts and transfers, billing and reporting, CRM and data | Designing processes, hiring, handling escalations, owning the stack | Specialists drift into silos, with handoffs between them done by hand |
| $5B+ and aggregators | Operations leaders per function, with a COO above | Functional teams, a technology or data group, often a dedicated integration team | Standards across offices, metrics, vendor strategy, M&A integration | Every acquired firm brings its own way of working and its own stack |
The transition that catches people is the middle one. The skills that made you excellent at doing the work (knowing every form, remembering every exception) are not the skills that make a team of specialists work: writing the process down, measuring it and removing the manual steps between people. For stage-specific tooling, see our guides for small, midsize and large RIAs.
Director of operations vs COO vs CCO vs operations manager
Titles overlap, and at a smaller firm one person may hold two of these roles. What matters is that every row below has one clear owner.
| Area | Operations manager | Director of operations | COO | CCO |
|---|---|---|---|---|
| Daily paperwork, transfers, maintenance | Runs it | Designs it, handles escalations | Informed | Sets review requirements |
| CRM data quality | Enters and fixes | Owns standards and required fields | Sponsors | Uses for oversight |
| Billing | Runs the cycle | Owns setup and review | Owns the revenue view | Tests against agreements |
| Reconciliation and reporting | Clears breaks | Owns process and deadlines | Consumes reporting | Reviews client communications rules |
| Compliance program | Follows procedures | Supplies evidence, runs procedures | Supports resourcing | Owns the program |
| Tech stack and vendors | Power user | Owns systems and integrations | Approves strategy and budget | Reviews vendor due diligence |
| M&A integration | Executes waves | Runs the integration plan | Owns the deal and timeline | Owns regulatory questions |
| Headcount and structure | Input | Proposes team design | Decides | Owns compliance staffing |
The COO question ("is the COO of an RIA the same as the director of operations?") usually has a simple answer: the COO owns the business, the director owns the service engine inside it. For how a COO should think about AI across the whole firm, see the wealth advisory COO's guide to AI.
The first 90 days in the role
- Inventory the work (weeks 1 to 4). List every recurring task the team does, who does it, how often, how long it takes and which systems it touches. Sit with each person for a day. The inventory you build will be wrong in places, which is fine; it is the first version anyone has written down.
- Map the stack. Draw every system and every handoff between them: CRM to portfolio system, CRM to custodian paperwork, e-signature to document storage, portfolio system to billing. Mark each handoff as automated or manual. The manual ones are your backlog.
- Fix NIGO first (weeks 5 to 8). Pull the last quarter of returned paperwork, group it by reason, and trace the top reasons back to the source field. It is usually a handful of CRM fields and form versions. Fixing those is the fastest visible win with clients and advisors. Our guide to auto-filling custodian forms covers the mechanics.
- Pick the first automations (weeks 9 to 12). Choose two or three workflows that are frequent, rule-based and painful, with one named owner each. Good first candidates are in RIA back-office automation workflows. Avoid starting with the most complex exception-heavy process.
- Set the metrics. Agree the five or six numbers you will report every month, measure the baseline now, and put them in front of the COO or CEO on a fixed schedule. A trend line after two quarters is worth more than any single month.
For a wider view of what tends to be broken when you arrive, see the most common RIA operations challenges.
The KPIs to report upward
These are the metrics that tie operations to client experience and risk. Define them precisely before you report them, and keep the definition fixed; changing the definition mid-year makes the trend meaningless. We do not quote industry averages here, because the published ones rarely use the same definitions; your own baseline is the comparison that matters.
| KPI | Definition | What it tells you |
|---|---|---|
| NIGO rate | Paperwork packets returned by the custodian as not in good order, divided by packets submitted, per month | Quality of upstream data and form preparation |
| Account-opening cycle time | Median business days from the client's signed paperwork to the account open at the custodian | How fast clients get started; where the queue is |
| Transfer cycle time | Median business days from transfer request submitted to assets received in the new account | Client experience during onboarding and transitions |
| CRM data completeness | Share of active households with every required field populated and validated (your list, e.g. DOB, address, beneficiaries, risk profile, advisory agreement date) | Whether downstream forms, billing and reports can be trusted |
| Billing exceptions | Accounts needing a manual adjustment or correction per billing cycle, split by root cause | Setup quality and revenue leakage |
| Reconciliation break age | Open breaks older than a set number of business days, at month end | Reporting reliability |
| Operations hours per household | Total operations team hours in the period divided by households serviced | Capacity: whether the team scales with growth |
| Manual handoffs in top workflows | Count of steps in your ten most frequent workflows where a person moves data between systems | Where automation will pay back first |
Hours per household is the one leadership will care about most as the firm grows, because it shows whether each new household makes the team bigger. It is also the hardest to measure honestly: you need the task inventory from your first 90 days to have a denominator you trust.
How AI changes the role in 2026
The practical change is a shift from doing the work to designing and supervising it. Tasks that follow rules, such as filling a transfer form from the household record, sending it for signature, filing the signed copy and updating the CRM, move to automation. What stays with people is the judgment: exceptions, unusual client situations, vendor choices and reviewing what the automation did.
That changes what the director is accountable for:
- Process design becomes the core skill. An automation is only as good as the written process behind it, so the inventory and handoff map stop being one-off projects and become living documents.
- Supervision replaces spot checks. Your CCO will want to know what ran, on which records, with what result. Prefer systems where every run is logged and reviewable, and where the steps are deterministic and repeatable rather than improvised each time.
- Ownership matters more than features. If only the vendor can change an automation, every process change becomes a ticket. Operations teams that can change their own automations keep up with the work.
The meeting side of the firm is changing too: note takers such as Jump and Zocks now draft notes and tasks into the CRM, which creates more structured data for operations to act on. For the firm-wide picture, read the wealth advisory COO's guide to AI and our overview of AI use cases for financial advisors.
Where Caddi fits
Caddi is built for the operations team, not the advisor. It has three parts. Discover finds the repetitive work in the tools your team already uses, which gives you a head start on the work inventory above. Caddi Automate builds the automation: someone on your team screen-shares the process or describes it in chat, and they change it in plain English as the work changes. Govern gives firm-wide visibility into the work done by AI and by people, with every run logged, which is the evidence your CCO asks for. AI builds it, verified code runs it, and any model step inside a run is scoped, logged, and reviewable.
For the account lifecycle domain, Caddi fills custodian paperwork (new account applications, transfer forms and similar PDFs) from the CRM household record, sends it for signature through DocuSign and logs it back to the CRM. It connects to Salesforce, Wealthbox, Practifi, Orion, Black Diamond, Tamarac, Addepar and Box, among others. Discover and Automate are on the free Individual plan; Govern starts on the paid team plan.
Where Caddi does not fit: it does not integrate with custodian platforms such as Schwab, Fidelity or Pershing, so work inside the custodian portal stays with your team. It does not take meeting notes; it connects to Jump and Zocks for that.
Matt Mercer, COO of The Planning Center, an independent RIA, put it this way: "We thought our processes were finely tuned, but every one still pointed back to a human. Caddi got the systems we already have to talk to each other, and gave my team back an hour a day." Read the Planning Center case study, or see how Caddi works for wealth management and RIA firms and for client onboarding.
More for RIA operations leaders
- The Wealth Advisory COO's Guide to AI
- The RIA operations tech stack, by workflow
- RIA acquisition integration checklist
- Client repapering without the NIGO
- Onboarding a breakaway advisor team
Caddi connects to the systems an RIA back office runs on: Salesforce, Wealthbox, Practifi, Orion, Black Diamond, Tamarac, Addepar, DocuSign, Jump, Zocks. See how it runs client onboarding and the operational side of RIA compliance, or the RIA operations overview.
Caddi
See how Caddi AI Agents can take the manual handoffs out of your operations team's week and cut NIGO paperwork and account-opening cycle time
Frequently asked questions
What does a director of operations at an RIA do?
A director of operations at an RIA owns the work between the advisor's promise and the client's statement: opening and transferring accounts, keeping CRM data accurate, running billing, reconciling and reporting, supporting the compliance program, and managing the tech stack and vendors. At smaller firms the director does much of this personally. At larger firms the job is designing the processes, leading specialists and reporting operating metrics to the COO or CEO.
What is the difference between a COO and a director of operations at an RIA?
The COO usually owns the whole business operation: operations, technology, often finance, HR and sometimes compliance reporting lines, plus strategy and M&A. The director of operations owns the service engine inside it: paperwork, data, billing, reporting and the team that runs them. At many firms under a billion dollars in assets, one person holds both titles in practice. The split tends to appear as the firm adds offices, acquisitions or a second custodian.
What KPIs should an RIA operations team track?
Start with the ones that tie directly to client experience and risk: NIGO rate on custodian paperwork, account-opening cycle time, transfer cycle time, CRM data completeness on required household fields, billing exceptions per cycle, and operations hours per household serviced. Define each one precisely, measure a baseline for a quarter, and report the trend rather than a single number. Avoid comparing to industry averages you cannot source.
How is an RIA operations team usually structured?
Smaller firms often have a player-coach director and one or two generalists who handle everything. As assets grow, teams split into specialists: new accounts and transfers, billing and reporting, CRM and data, and technology. Large firms and aggregators tend to have an operations leader per function, a COO above them, and a dedicated integration team for acquisitions. The right structure depends on custodians, service model and growth plans more than on assets alone.
What should a new RIA director of operations do in the first 90 days?
Spend the first month inventorying the work and mapping the stack: every recurring task, who does it, how often, and which systems it touches. In the second month, fix the biggest source of not-in-good-order paperwork and clean the CRM fields that drive it. In the third, pick two or three automations with clear owners, and set the handful of metrics you will report upward every month from then on.
Will AI replace RIA operations jobs?
In 2026, AI is changing the operations job more than removing it. Repetitive steps such as keying household data into forms, chasing signatures and copying data between systems are the first to move to automation. The work that stays human is judgment: exceptions, client situations, vendor decisions and supervising what the automations do. Directors who design and review that work become more valuable, not less.