What Does ACAT Follow-Up Automation Cost?
See what ACAT follow-up automation may cost, how to measure staff time spent on status checks, and when the investment makes sense.
ACAT transfers can look straightforward when they’re opened. Then the paperwork goes in, the client asks for an update, and someone on the team starts checking whether the delivering or receiving firm has moved the transfer along.
That work is easy to underestimate. A client service associate may spend a few minutes logging into a custodian portal, checking a status, recording what they found, and deciding whether to follow up. Repeat that across open transfers, multiple custodians, and several weeks, and status checking becomes a regular operational task.
The cost to automate ACAT follow-up depends on more than the software. It depends on how many transfers the firm handles, how many systems staff must check, what information can be accessed safely, and how exceptions are routed to a person. The right comparison is the cost of that setup against the staff time and client service capacity currently tied up in checking and chasing.
What ACAT follow-up work actually includes
Automating follow-up doesn’t mean submitting every transfer automatically or letting software make decisions about account movement. The practical target is the repeatable work around an active transfer.
A typical manual process might look like this:
- A staff member records the transfer request and its key details in the CRM or a spreadsheet.
- They check a custodian portal or another approved source for the latest status.
- They note the status, date, and any outstanding requirement.
- They decide whether to contact the client, the custodian, or the receiving team.
- They record the contact and set a reminder to check again.
Each action is small. The difficulty is keeping the process consistent across open cases. A transfer may sit without a clear next step, a status update may not make it into the CRM, or two team members may check the same case.
An ACAT follow-up agent can organize this cycle. It can identify transfers due for review, gather status information from approved sources, update the record, draft a client message for review, and route exceptions to a staff member. It shouldn’t invent a status, send a message without authorization, or treat an unclear update as a completed transfer.
For a broader look at the workflow itself, see how to automate ACAT transfers at your firm. This article focuses on what it can cost to automate the follow-up work and how to judge the return.
How much staff time do status checks take?
Start with the activity, not an industry benchmark. Count the open transfers your firm handles in a typical month, how often staff check each one, and how long a check takes from login through documentation.
For an initial estimate, a firm handling 25 to 50 transfers a month might review each case three to five times, with each review taking five to eight minutes. That works out to roughly 6 to 33 hours a month on status checks alone. It’s a planning range, not a claim about every advisory firm. Your own transfer volume and process may be very different.
That estimate can miss other work around the check. Staff may need to locate the right account, reconcile a portal status with CRM notes, ask a colleague what happened last time, or contact a client when an update is unclear. Track those activities separately rather than padding the time estimate without evidence.
A simple monthly calculation is:
Monthly status-check hours = transfers reviewed × reviews per transfer × minutes per review ÷ 60
Then multiply those hours by the firm’s loaded hourly cost for the people doing the work. For illustration, 40 transfers with four reviews each, taking seven minutes per review, comes to about 19 hours a month. At an assumed loaded cost of $45 per hour, that’s approximately $840 per month in staff capacity spent on checks.
That figure does not mean the firm will save $840 in cash each month. Staff are usually still employed, and the time may be redirected to other work. The useful question is whether that capacity can reduce overtime, support more client work, shorten internal delays, or prevent the firm from adding administrative headcount sooner than planned.
Also measure the experience around the task. How often do clients ask for updates before the team contacts them? How many cases are missing a clear next action? How long does it take to spot an incomplete requirement? Those measures help show whether automation improves service and process control, not just minutes on a timesheet.
What automation may cost
There isn’t one fixed price for ACAT follow-up automation. A workflow connected to one well-documented system is different from a multi-custodian process that relies on manual portal checks and several disconnected records.
For a first-pass budget, these illustrative planning bands can help frame a conversation. They’re not market averages or a vendor quote.
- A scoped pilot, roughly $5,000 to $15,000 to set up: One defined workflow, a limited group of users, basic status tracking, and a staff review step. This is a sensible way to test whether the process can be automated safely before expanding it.
- A connected workflow, roughly $15,000 to $40,000 to set up: More CRM or document-system connections, defined exception handling, audit logging, and several transfer paths. More integration and testing usually mean more setup work.
- A broader multi-custodian operation, roughly $40,000 to $80,000 or more to set up: Multiple systems, more varied transfer scenarios, deeper controls, and a larger set of operational requirements. This isn’t the right starting point for every firm.
There may also be recurring costs for software, hosting, monitoring, and ongoing support. As an early budgeting assumption, some firms may model roughly $500 to $3,000 a month for operating a connected workflow. The amount depends on what services are already in place and how much ongoing maintenance the firm expects. Ask vendors to separate one-time implementation from recurring costs, and confirm what’s included in each.
The main cost drivers are usually:
- Number of systems and custodians. More handoffs mean more testing and more variations to manage.
- Access to status information. A supported integration may be more reliable than an attended portal process. Any portal access needs to follow the custodian’s terms and the firm’s security policies. Automation shouldn’t bypass authentication or access controls.
- CRM and record quality. If transfer details are incomplete or inconsistent, the project may need data cleanup and clearer intake steps before automation can work well.
- Exception handling. Transfers don’t all follow the same path. Incomplete paperwork, mismatched details, and unclear status updates need a reliable route to a person.
- Controls and review. The firm needs to define what the agent can update, what it can draft, what requires approval, and what must remain a human decision.
For a wider view of implementation budgets, read about AI automation costs for advisory firms. It’s useful to compare ACAT follow-up with other work your firm might automate, but keep the scope and economics of each workflow separate.
What an end-to-end ACAT agent does
A useful workflow starts when the firm records a transfer request. The agent checks that required fields are present, such as the client, account, custodian, request date, and any agreed follow-up instructions. If important details are missing, it flags the case instead of trying to fill gaps by guesswork.
Next, it places the transfer on a follow-up schedule the firm has approved. On the scheduled review, it checks the relevant approved source, such as an available system integration or a staff-authorized workflow. It records the date and the status it found, with a link or reference to the source where possible.
If the status is clear and the next step is routine, the agent updates the CRM and sets the next review date. It may prepare a client update for staff to approve. If the status is unclear, a requirement is outstanding, or the case has stopped progressing, it places the case in an exception queue with a short explanation and the information already gathered.
The staff member sees a prioritized list rather than a collection of reminders. They can review the source, decide what to do, and approve or edit any client communication. The agent records the final action so another team member can understand the case without repeating the same checks.
That workflow needs clear boundaries. For example, the agent can report that a source shows a pending requirement, but a person should verify what the firm needs to do next. It can draft a message, but the firm decides whether the message is accurate and appropriate to send. It can flag a transfer that appears inactive, but it shouldn’t promise a completion date.
The team should also agree on basic measures before launch: time spent on checks, cases awaiting action, cases with no next step, time to respond to client status requests, and the share of updates that need correction. After launch, compare the same measures. If the agent saves minutes but creates a steady stream of corrections, the workflow needs more work.
How to decide if the investment makes sense
Compare the full cost with the value the firm can reasonably expect to recover. Don’t treat broader operational leakage as if all of it comes from ACAT follow-up or as a guaranteed return from one workflow.
Use a narrower calculation:
- Measure the firm’s monthly ACAT volume and the time spent checking each case.
- Include time spent documenting updates, contacting clients, and correcting missed or duplicated work.
- Estimate the share of that time the proposed workflow can realistically remove.
- Add setup and recurring costs over the period you’ll use to evaluate the project.
- Decide what the firm will do with the freed capacity.
If the calculation shows only a small amount of staff time, a large custom build may not pay back on labor alone. A small pilot, a clearer follow-up process, or better use of existing CRM reminders may be a better first move. If the team is checking many transfers across several systems and struggles to keep ownership clear, a broader workflow may be justified by more than minutes saved. It may also reduce avoidable client chasing and make the process easier to supervise.
The important distinction is between time removed and capacity recovered. Time removed is the estimate from the activity log. Capacity recovered is the work the team can now complete with that time. Be specific. It might mean fewer hours spent on repetitive status reviews, or more time for client requests that currently wait in a queue.
An ACAT paperwork workflow guide can help you identify where document handling fits into the process. If staffing is part of the decision, compare the workflow with the full cost of adding capacity in CSA hiring versus automation. Neither comparison replaces measuring your current process.
If you want to map the process and costs with someone, Book a 60-min Omni Audit. Book a conversation to discuss your team’s work, handoffs, and whether an agent may be a sensible fit. You can also see Omni for financial advisory firms before booking.
The wider operations picture
ACAT follow-up often sits alongside other repeatable tasks that compete for the same people’s attention. Meeting preparation and notes can take time that competes with other operational work. Compliance documentation can also consume paraplanner time, depending on the work involved. Those figures are useful context for prioritizing operational work, but they shouldn’t be used to inflate the business case for ACAT automation.
For example, a meeting-preparation workflow could organize information for an adviser to review before a meeting. A client-onboarding workflow could help organize information and documents for adviser review. These are separate workflows, with their own controls and economics. They may belong in the same operational plan, but each should have its own baseline and success measures.
That’s one reason a firm-wide assessment can be more useful than pricing a single task in isolation. A focused ACAT pilot may answer whether status checks are a worthwhile target. An operations review can help determine whether that work should come before onboarding, meeting preparation, or another bottleneck.
What happens in an Omni Audit
An Omni Audit is a focused review of your process. We map the process, understand the systems and staff involved, and identify where a workflow could be automated safely. The aim is to identify a potential opportunity, workflow considerations, and assumptions that may affect cost.
Bring a rough count of monthly transfers, the systems your staff check, and a few examples of cases that required extra follow-up. You don’t need a polished process map. The goal is to understand what happens in practice, including the exceptions that don’t show up in a written procedure.
For ACAT follow-up, the audit should establish whether status information is accessible through approved routes, what needs staff approval, and how the agent should handle unclear or stalled cases. It should also identify the measures you can use to judge the pilot. If the time saved is too small to justify a build, that’s a useful answer too.
Book a 60-min Omni Audit or see the AI audit for financial advisory firms. The aim is a grounded decision based on your transfer volume, staff time, systems, and controls, not a generic promise that automation will pay for itself.
Your guide is ready
Check your downloads folder. If it did not open automatically, use the button below.
Download the GuideYour guide is ready
Check your downloads folder. If it did not open automatically, use the button below.
Download the GuideTalk it through
Talk it through with Sam
30 minutes on what a Command Centre would look like for your business.
Book a call