Advisers spend around 15 hours per client on onboarding, and more than half of that time has nothing to do with the client sitting in front of them. It goes on chasing documents, re-keying data, drafting follow-up emails, and waiting for systems that don’t talk to each other. That is not relationship-building — it is administration wearing a relationship’s clothes. And it’s not a capacity problem you solve by working harder; it’s a process problem you solve by redesigning the process.
This playbook walks through how to do that, step by step, in a way that holds up under FCA scrutiny and doesn’t require a large technology budget or an IT department.
Where the time goes
Before touching any software, it’s worth being precise about where the hours go. Most onboarding processes have four distinct stages, and the inefficiency is rarely spread evenly across them.
The stages are: initial data collection (fact-find, ID verification, source of wealth documentation), internal processing (keying information into back-office systems, compliance checks, file assembly), suitability assessment and documentation (research, drafting, review), and client communication (welcome correspondence, progress updates, next-step confirmations). In most firms I look at, stages two and three are where the majority of non-client-facing time accumulates. Stage one is slow because it depends on clients returning information at their own pace. Stage four is slow because it’s done manually and repeatedly for each client.
The cost is easy to underestimate. For a firm onboarding 50 new clients a year, half of 15 hours per client is roughly 375 hours of non-client-facing work — at a conservative £50 per hour for adviser or paraplanner time, £18,750 a year in pure process overhead, before you account for the opportunity cost of growth. That diagnosis matters because automation works differently at each stage, and targeting the wrong stage first wastes effort.
What level of help do you need
Not every firm needs the same solution, and not every problem needs engineering. Before specifying any tool, place each bottleneck at the right level.
- Level 1 — education. Problems you can solve with a better prompt, a smarter template, or a fifteen-minute configuration in a tool you already pay for. If your CRM has a workflow builder you’re not using, or your back-office platform has a document request feature sitting unused, that’s a Level 1 fix. Free. Available today.
- Level 2 — integration. Two or three systems need to be connected so data flows automatically between them rather than being re-keyed by hand. This is the most common genuine need for IFA onboarding automation. Tools like Make, n8n, or Zapier handle this configuration work — expect days to a few weeks and a cost in the low hundreds to low thousands of pounds.
- Level 3 — custom build. Real engineering: bespoke pipelines, complex logic, orchestrated AI. Most IFA onboarding processes don’t need this. If a vendor is suggesting you do, push back and ask them to explain why Level 2 won’t work.
The discipline is to solve at Level 1 first, then Level 2 if you genuinely need it. Most firms that come to me thinking they need a custom build actually need a two-hour configuration session and a better template library.
Map the process before you automate it
Automating a broken process produces a faster broken process. The mapping step is not optional — and it is the first step regardless of which technology you end up using. Not a technology decision, not a procurement exercise: a simple audit.
Spend two to three hours tracing one recent onboarding end to end, from first contact to file completion. For each step, note: who does it, how long it takes, what triggers it, what system it lives in, and what can go wrong. You are looking for three things: steps that are purely mechanical (copying data from one place to another), steps where the same communication gets written from scratch each time, and handoff points where work sits waiting for someone else to pick it up.
Those three categories are your automation candidates. Decision-intensive steps, anything involving regulated judgement, and any step where a human needs to apply discretion or professional knowledge are not candidates. Keep those human, because they need to be. The goal isn’t to remove people from onboarding — it’s to remove the mechanical work that stops people from doing the parts only they can do.
What to automate, and in what order
- Document collection. A secure digital portal, even a simple one, that sends automated reminders and tracks document status will recover more time faster than almost any other single change. Clients who receive a clear, professional request with a simple upload mechanism return documents faster; the adviser spends less time chasing. Most modern back-office platforms include this — if yours does and you’re not using it, that’s a Level 1 fix.
- Data transfer between systems. The most common source of re-keying is the gap between a fact-find tool and a back-office platform. A Level 2 integration using Make or n8n can typically move structured data between these systems automatically once a fact-find is marked complete, reducing manual entry to an exception-handling task rather than a default step.
- Templated communications. A library of well-written, compliance-reviewed templates for routine onboarding communications — acknowledgement of first meeting, document request, progress update, welcome to service — reduces drafting time and produces a more consistent client experience. A Level 1 change in most cases. AI tools can help draft the templates, but a human reviews them for regulatory accuracy and firm tone before they go into use.
- Meeting capture. Technology that records a conversation and drafts a follow-up note or fact-find summary can recover meaningful time in the post-meeting stage — but the output must be reviewed and confirmed by the adviser before it enters any client file or informs any recommendation.
A workflow built on these four targets can send a document request, track whether it has been completed, chase it after 48 hours, and flag it to the adviser if it is still outstanding after five days. The adviser does not need to be involved until there is something that requires their judgement.
Keep the touchpoints human where it counts
Automation does not hollow out a relationship unless you let it. The risk comes from applying it indiscriminately to every touchpoint, including the ones where a human presence actually matters. The test is not whether a step can be automated — it is whether automating it removes something the client would notice and value.
A firm I have seen do this well has a simple rule: any touchpoint that is informational gets automated; any touchpoint that is decisional stays human.
| Automate it — informational | Keep it human — decisional |
|---|---|
| Document requests and upload chasing | The first conversation |
| Status updates and progress tracking | The risk discussion |
| Appointment and deadline reminders | The recommendation discussion |
| Data transfer between systems | The welcome call after the fact-find |
| ID verification workflows | Any moment of genuine client concern |
One principle from a16z’s “barbell” model for AI in client services is worth taking seriously here: use automation for high-volume, low-value interactions so you can concentrate genuine human time on the interactions that matter most. A progress-chasing email? Automate it — the client wants to know where things stand and doesn’t particularly want to call your office to find out. The welcome call after the initial fact-find? Do not automate it. That is the moment a client decides whether they trust you.
Start at the new-client boundary
New clients have no existing habits with your firm. They have not yet formed an expectation of how you do things — which makes onboarding the ideal place to introduce digital tools, because there is no friction of re-learning an old process. Existing clients who have always received a paper pack and a phone call will notice if you change that; new clients will simply experience whatever you set up as normal. This principle — set a digital-first expectation from the very first interaction and you rarely have to reset it later — is well-established in fintech adoption practice.
Practically: introduce automated document collection, digital ID verification, and progress-tracking portals as standard for new clients, even before you roll them out to your existing book. It also gives you a clean data point on how clients respond.
Transparency and data handling
There is a trust dimension worth being explicit about. Clients interacting with automated communications should always know they can reach a person, and any automated system that resembles a conversational interface should make clear that it is not a human agent. In practice: automated emails signed clearly by the firm (not mimicking a personal adviser email), a visible route to the adviser or their support team, and no ambiguity about when a client is dealing with an automated step versus a person. Done well, this transparency builds confidence — clients see an efficient, well-organised process that knows when their situation needs a real conversation.
Any automated system collecting or processing client personal data needs to operate within your existing GDPR framework. The EDPB has published guidance noting that vague or over-broad consent in professional services contexts can create ambiguity and compliance risk [1]. Make sure your digital onboarding captures specific, purposeful consent — not a blanket agreement buried in a welcome email.
What the FCA expects when you automate client-facing processes
The FCA’s expectations around Consumer Duty are directly relevant here. The duty requires firms to deliver good outcomes for clients — including that the onboarding process itself is clear, fair, and not misleading, that clients understand what they’re being asked for and why, and that the firm can demonstrate genuine engagement and informed consent at each stage [2].
Automation supports all of this, done correctly: consistent communications reduce misunderstanding, a documented workflow is easier to audit than one that depends on individual memory, and automated reminders stop clients falling through the cracks. But automation can also work against Consumer Duty: a process that routes every client through an identical journey regardless of complexity or vulnerability fails the individualisation requirement; a system that chases documents with no way for a client to flag difficulty creates exactly the friction the duty is designed to remove; and any automated communication a client might reasonably read as advice, rather than administration, carries regulatory risk.
If you’re implementing onboarding automation, five things keep it defensible:
- Document your process map — before and after. The FCA expects firms to demonstrate that their processes produce good client outcomes; a written process map is the foundation of that demonstration.
- Review every automated communication against Consumer Duty standards. Every templated email or message is a regulated communication. Have your compliance officer or a suitably qualified person review them before they go live.
- Build in vulnerability identification. Your intake process should give clients a clear, easy way to indicate they need additional support — and surface it to a human promptly. An automated system that doesn’t is a Consumer Duty gap.
- Keep human review explicit at regulated decision points. Any AI-assisted output that informs a suitability assessment, a recommendation, or a regulated document must pass through a logged human review step. “The system drafted it and I checked it” is a legitimate workflow. “The system handled it” is not.
- Audit the process periodically. Review how the workflow is performing every six months: are clients completing onboarding faster, and where do things stall? Consumer Duty requires ongoing monitoring of outcomes, not a one-time design review.
On AI tools specifically
Several AI-assisted tools now exist for specific onboarding tasks: summarising meeting notes, generating first drafts of suitability-adjacent documents, and extracting structured data from uploaded documents. Used well, these can considerably reduce the time cost of the processing and documentation stages. Used carelessly, they create compliance risk — any AI system produces outputs that require human review before use in a regulated context. This isn’t a precaution worth skipping when you’re busy; it’s the step that keeps the process defensible.
There’s also a vendor-selection consideration. Gartner has noted that a significant proportion of tools marketed as AI agents in 2026 are rebranded legacy automation with a new label. Before building an onboarding workflow around any specific AI tool, satisfy yourself that the vendor has genuine substance behind the capability claim, that the contract covers your data rights clearly, and that your workflow can survive if the tool is discontinued or pivoted. Vendor dependency is a business continuity risk for any firm in a regulated environment.
The realistic outcome
Intelliflo’s data from firms using integrations like wealthLink and zeroKey shows around a 20% increase in average clients per adviser as a result of efficiency gains. That’s not a number to take as a guarantee for your firm — it’s a direction of travel, and it makes sense: if an adviser currently spends seven or eight hours of each fifteen-hour onboarding on mechanical tasks, and you recover most of that, you’ve meaningfully changed their capacity.
There is also a more interesting version of the outcome than cost and capacity. Dunbar’s number — the anthropological principle that humans can maintain roughly 150 stable relationships — matters here: an adviser managing 75 or more clients is already at the edge of what is cognitively manageable for genuine relationship work. When six or seven hours per new client come back from automation, that time goes into the conversations that actually build the relationship: longer discovery sessions, more proactive annual reviews, better preparation before meetings. The relationship does not get worse when you automate the administration. It gets better, because the adviser’s attention is no longer being consumed by process.
The firms that get there are the ones that start with the honest process map, fix the Level 1 things first, and build the Level 2 integrations carefully rather than chasing a system that promises to do everything. If you want to work through what this looks like for your specific firm, a discovery call with Cordrey Consulting is a good place to start.
This article is for informational purposes only and does not constitute regulated financial advice or a compliance opinion. Consult a qualified compliance professional for advice specific to your firm.
Sources
[1] EDPB, ‘Guidelines 1/2026 on processing personal data for scientific research purposes under Article 89 GDPR’, European Data Protection Board, 2026. Available at: https://www.edpb.europa.eu/our-work-tools/documents/public-consultations/2026/guidelines-12026-processing-personal-data_en [Note: public consultation document; the guidance on consent specificity cited here reflects the draft position. Firms should monitor for the finalised version before treating it as settled regulatory requirement.]
[2] Financial Conduct Authority, Consumer Duty (PS22/9), final rules and guidance (July 2022), https://www.fca.org.uk/publications/policy-statements/ps22-9-new-consumer-duty