Case Study

Case Study: Financial Adviser Onboarding & Annual Reviews

We built a connected set of automations for an independent advice firm with several advisers and paraplanners: a CRM pipeline and household service calendar, onboarding with fact-finds and KYC evidence, annual review preparation with delivery logging, suitability report drafting and CPD and marketing approval tracking. Advisers now walk into reviews prepared, and compliance can show what was offered and delivered for every client.

Firm type
Independent financial advice firm with ongoing service clients
Team involved
Advisers, paraplanners, administrators, compliance lead
Systems connected
Adviser CRM, e-signature, identity verification, meeting calendars, document storage, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Prospects arrived through client referrals, introducers and seminars, and only the adviser who met them knew where each stood.

Onboarding ran on emailed forms. Fact-finds, identity evidence and agreements came back piecemeal, and administrators spent weeks chasing.

Reviews were scheduled by memory, preparation packs were rebuilt each time and nobody could quickly show which clients had been offered a review and declined.

Paraplanners rebuilt every report from scratch, and CPD and marketing approvals lived in spreadsheets and email threads.

Goals

What the project had to change

  • Every prospect sits in one pipeline, and every client has a service calendar.
  • New clients complete onboarding through one secure route with a checklist compliance can trust.
  • Every paid-for review is offered on time and logged, held or declined.
  • Report drafts start from facts already filled, with the adviser's rationale untouched.
  • CPD and marketing approvals are tracked in one place.

What we built

What we built, as one connected system.

01

CRM pipeline and service calendar

We connected referral, introducer and seminar sources to one pipeline, booked discovery meetings and gave every household a service calendar that creates team tasks.

Service details
02

Client onboarding

A won opportunity now sends the fact-find, risk questionnaire, identity requests and agreements together, chases gaps and shows a checklist per client.

Service details
03

Annual reviews

Reviews are invited from each service level, pre-review questionnaires are chased, preparation packs are drafted and every offer and outcome is logged.

Service details
04

Suitability report drafting

Fact-find data and the adviser's recommendation notes fill the firm's templates, gaps are flagged and drafts go through paraplanner checking and adviser sign-off.

Service details
05

CPD and marketing approvals

Advisers log CPD against their configured requirement, marketing pieces go through a compliance queue and a monthly summary is ready for audits.

Service details

Architecture

How the firm's workflows connect

Referrals, events Prospects Adviser CRM Households Client forms Fact-find, reviews n8n Five workflows AI drafting Packs and reports E-sign and ID Onboarding Compliance log CPD and approvals Paraplanners Check and edit Advisers Advise and sign off Reports Service and audit
  • Input
  • Logic and services
  • AI step
  • Output
  • Data
  • People

How it flows

  1. 1 Prospects, CRM households and client forms feed one n8n instance.
  2. 2 Five workflows send onboarding requests, draft review packs and reports, and keep the compliance log.
  3. 3 Paraplanners check drafts; advisers advise and sign off; compliance approves where required.
  4. 4 Service delivery and audit reports come from the same records.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What clients see

  • A prompt reply and easy meeting booking
  • One secure route for the fact-find, documents and agreements
  • A timely review invitation and short questionnaire
  • A clear report soon after their meeting

What staff see

  • One pipeline and a task list driven by the service calendar
  • Onboarding checklists and draft review packs
  • Report drafts with facts filled and gaps flagged
  • A compliance queue and monthly summary

What the automation does

  • Captures, sends, chases, drafts and logs on schedule
  • Applies consent, opt-outs and records rules everywhere
  • Alerts the practice manager if anything fails

Edge cases and fallbacks

A prospect asks an investment question by email
Routed to an adviser; no automated reply addresses it.
A verification result needs review
Flagged to compliance before onboarding continues.
A client declines their review
The decline is logged with the date for the adviser and compliance.
Adviser notes are thin
The report draft marks the rationale incomplete and returns it to the adviser.
n8n or the CRM has an outage
Events queue and retry, staff work as before and the practice manager gets an alert.

Integrations

What we connected

All integrations

Wealthbox

Adviser CRM

Contacts, households, tasks, events, opportunities, notes and workflows.

Wealthbox REST API with OAuth 2.0 (application registered through Wealthbox support).

DocuSign

E-signature

Client agreements and disclosures sent and filed on completion.

DocuSign eSignature REST API and Connect webhooks.

Zoom

Meetings

Recordings and transcripts for AI meeting notes, with consent.

Zoom Cloud Recording API and webhooks; transcript access confirmed per project.

Microsoft 365 and Teams

Email, calendars and meetings

Follow-ups, review booking, Word templates and Teams meetings.

Microsoft Graph APIs.

Calendly

Scheduling

Discovery and review meeting booking.

Calendly API v2; webhooks need a paid Calendly plan.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We sat with advisers, paraplanners, administrators and the compliance lead, mapped prospect-to-review steps and agreed data and records rules.

  2. 02

    Design and access

    Week 2

    Service levels, onboarding paths, review pack and report templates, CPD rules from the compliance lead, CRM API access.

  3. 03

    Sprint 1: CRM pipeline

    Week 3

    Built and shadow-ran the pipeline and service calendar; demo and sign-off.

  4. 04

    Sprint 2: onboarding

    Week 4

    The pipeline went live. Built fact-find, identity and agreement requests with the checklist view.

  5. 05

    Sprint 3: reviews

    Week 5

    Onboarding went live. Built review invitations, questionnaires, pack drafting and delivery logging.

  6. 06

    Sprint 4: reports

    Week 6

    Reviews went live for one adviser. Built report drafting; paraplanners compared drafts with their own.

  7. 07

    Sprint 5: CPD and approvals

    Week 7

    Report drafting went live for two advice types. Built the CPD log and marketing review queue.

  8. 08

    UAT and handover

    Week 8

    The team ran user acceptance testing on every workflow, then we switched everything on and handed over the run book.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Captures prospects and schedules household service
  • Sends and chases onboarding forms, ID requests and agreements
  • Invites clients to reviews and drafts preparation packs
  • Fills report templates with facts and flags gaps
  • Logs CPD and routes marketing for approval

The team does

  • Resolve onboarding gaps and confirm files
  • Check and complete review packs
  • Edit and check report drafts
  • Keep the service calendar accurate

Adviser or compliance decides

  • Make every recommendation and confirm every report
  • Hold reviews and decide changes to advice
  • Approve client files, CPD and marketing where compliance must
  • Decide how to respond to declined reviews

Compliance handled

Privacy, consent and safety, built in.

No advice from automation

Automated messages use approved wording; recommendations are always the adviser's.

Records of advice kept

Reports, notes and communications relating to advice are retained under the firm's policy, in line with SEC Rule 204-2 for US clients.

Source: www.law.cornell.edu

Service providers assessed

Every vendor was assessed for incident notification and safeguards in line with Regulation S-P.

Source: www.law.cornell.edu

Ongoing reviews evidenced

Every review offer, hold and decline is logged, the evidence the FCA asked firms about in its ongoing advice review.

Source: www.fca.org.uk

Marketing approvals recorded

Marketing goes through a compliance queue with versions and approvals recorded, reflecting the SEC marketing rule.

Source: www.sec.gov

Processor contracts

AI and automation vendors are covered by processor terms for EU and UK personal data.

Source: gdpr-info.eu

Outcomes

What changed for the practice

  • Every prospect now sits in one pipeline, and every household has a service calendar that drives tasks.
  • New clients complete onboarding through one secure route, and compliance works from a checklist.
  • Reviews are offered on time and every outcome is logged.
  • Paraplanners start reports from drafts with the facts already filled.
  • CPD and marketing approvals are tracked in one place, ready for audits.

What we track

The measures the practice watches.

Onboarding time

Days from a client saying yes to a complete file.

Review delivery

Reviews due versus offered, held and declined each month.

Report turnaround

Days from meeting to report sent and paraplanner time per report.

CPD on track

Share of advisers on track against their requirement each month.

Approval turnaround

Days from marketing submission to compliance decision.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, records rules, templates and the backlog for all five workflows.

    $950 – $2,000

  • CRM and service calendar module

    Source capture, booking, service calendar and tasks.

    $700 – $1,700

  • Onboarding module

    Fact-find, ID requests, agreements and checklist.

    $800 – $1,900

  • Annual review module

    Invitations, questionnaires, pack drafting and logging.

    $750 – $1,900

  • Report drafting module

    Template assembly, checks and sign-off route.

    $800 – $2,000

  • CPD and approvals module

    CPD log, reminders, review queue and summary.

    $500 – $1,300

  • Integrations

    CRM, e-signature, verification, calendars and storage.

    $200 – $500

  • Testing, UAT and launch

    QA, user acceptance testing, launch and training.

    $300 – $1,200

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every firm gets its own fixed quote after a free call.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • n8n: Free self-hosted Community edition on the firm's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • Vendor plans: CRM, e-signature, verification and storage subscriptions at each vendor's own pricing.
  • AI usage: Pay-per-use model fees for pack and report drafting, usually modest at practice volumes.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built for your financial adviser?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call