Fixed quote after a free call

Financial advisor client onboarding with fact-finds and KYC evidence built in

We build an onboarding workflow that starts when a client agrees to proceed: it sends your fact-find and risk questionnaire, chases what is missing, gathers identity and ownership evidence through your verification provider, sends client agreements for e-signature and tracks account opening paperwork until everything is complete, with a file ready for the adviser and compliance. A typical build costs $1,000 to $2,500 per workflow and takes about four to five weeks.

The problem

Why financial advisor client onboarding stalls

Onboarding a new household involves a fact-find, a risk questionnaire, identity documents, a client agreement, fee disclosures and account opening forms, often across several systems. Clients start keen and then stall at the paperwork, and the administrator spends weeks chasing.

The rules expect diligence. FINRA Rule 2090 requires broker-dealers to use reasonable diligence to know the essential facts about each customer, and in the UK many firms apply the Money Laundering Regulations' customer due diligence. Whatever applies, the evidence has to be complete, consistent and easy for compliance to check.

What we build

What our financial advisor client onboarding includes

Onboarding triggered by a yes

A won opportunity in the CRM starts the right onboarding path for an individual, couple, trust or business.

Fact-find and risk questionnaire

Your own forms sent through a secure portal, pre-filled from what the CRM already holds, with reminders.

Identity and ownership evidence

Requests through your verification provider, with results filed to the client record.

Agreements for e-signature

Client agreement and disclosures sent through DocuSign and filed on completion.

Account paperwork tracker

Custodian or platform forms tracked item by item, with the route to each provider confirmed per project.

File ready for review

A checklist view showing what is complete, missing or flagged, for the adviser and compliance.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Client says yes

    A won opportunity starts onboarding for that client type.

  2. 02 Automated

    Forms and requests sent

    Fact-find, risk questionnaire, ID requests and agreements go out.

  3. 03 Automated

    Evidence filed

    Completed items are filed and gaps chased on schedule.

  4. 04 Staff review

    Administrator checks

    The administrator resolves gaps and confirms the file is complete.

  5. 05 Adviser or compliance decides

    Adviser and compliance

    The adviser reviews the fact-find and compliance signs off the file where your procedures require.

How it behaves

How onboarding and KYC behave

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

What the client sees

  • One secure place for the fact-find, questionnaire and documents
  • Agreements to sign online
  • Reminders that stop once each item is done

What staff see

  • A checklist per client showing complete, missing and flagged items
  • Evidence filed to the right record
  • Fewer chasing emails

What the automation does

  • Starts the right path per client type
  • Pre-fills, sends, files and chases
  • Never assesses risk or approves a client

Edge cases and fallbacks

Joint clients complete forms at different times
Each person's items are tracked separately within the household.
Verification result needs review
Flagged to compliance; nothing proceeds automatically.
Client prefers paper
Staff upload completed forms and the checklist clears.
E-signature or portal outage
Requests queue and retry, and the administrator is alerted.

Architecture

Client onboarding for an advice firm at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
CRM opportunity Won n8n workflow By client type Fact-find Secure portal ID evidence Verification Agreements DocuSign Completeness check Gaps and flags Administrator Chase and confirm Client file CRM and storage
  • Input
  • Logic and services
  • Output
  • AI step
  • People
  • Data

How it flows

  1. 1 A won opportunity in the CRM starts the onboarding path for that client type.
  2. 2 The fact-find, identity requests and agreements go out together through secure channels.
  3. 3 Completed items are checked for gaps and inconsistencies, and reminders chase the rest.
  4. 4 The administrator confirms the file, the adviser and compliance review it, and it is saved to the client record.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Client onboarding, fact-find & KYC evidence project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Client types, forms, verification provider, custodians or platforms and compliance checklist.

  2. 02

    Design

    About 1 week

    Paths per client type, pre-fill rules, reminder timing, completeness checks and retention.

  3. 03

    Build

    1 to 2 weeks

    Portal forms, verification requests, e-signature, tracker and checklist view.

  4. 04

    Shadow run

    About 1 week

    New clients onboard both ways while compliance compares the files.

  5. 05

    Launch

    1 to 2 days

    Switch on for all new clients.

  6. 06

    Support

    Ongoing

    Form changes, new client types and provider updates.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Wealthbox, Salesforce Financial Services Cloud, Redtail or Intelliflo Office DocuSign eSignature REST API Your identity verification provider Secure client portal or form tool Companies House public data API for UK business clients

Cost estimate

What it costs, line by line.

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

    Client types, forms, checklist and retention.

    $250 – $550

  • Build

    Portal forms, requests, tracker and checklist view.

    $450 – $1,150

  • Integrations

    CRM, e-signature, verification provider and storage.

    $150 – $450

  • Testing and shadow run

    Parallel onboarding compared by compliance.

    $100 – $250

  • Launch and training

    Switch-on and administrator training.

    $50 – $100

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. E-signature, verification and portal subscriptions are billed to you by each vendor. Direct custodian integrations depend on each provider and may be quoted separately.

Monthly running costs you pay directly

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

  • E-signature and verification: DocuSign and your verification provider at their own pricing.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually) or €50 (Pro).

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

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: know your customer

FINRA Rule 2090 requires member firms to use reasonable diligence to know the essential facts about every customer and anyone acting for them. The workflow collects; the firm decides.

Source: www.finra.org

UK: customer due diligence

Regulation 28 of the Money Laundering Regulations 2017 requires identifying and verifying the customer and beneficial owners and understanding the purpose of the relationship, scaled to risk.

Source: www.legislation.gov.uk

US: safeguarding customer information

Regulation S-P requires an incident response program, customer notice within 30 days of becoming aware of certain incidents and oversight of service providers, which applies to every onboarding vendor.

Source: www.law.cornell.edu

US: electronic agreements

Under the E-SIGN Act a contract cannot be denied effect solely because it is electronic; consumer disclosures delivered electronically need prior consent.

Source: www.law.cornell.edu

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.

FAQ

Client onboarding, fact-find & KYC evidence questions, answered.

Typically a fact-find, risk questionnaire, identity and address evidence, ownership details for trusts or businesses, a signed client agreement and fee disclosure, and account opening forms. We build your checklist per client type so nothing is missed.

No. It sends your questionnaire and files the answers. The adviser interprets them with the client and decides what they mean for the advice.

They depend on your registration and jurisdiction. Broker-dealers follow FINRA Rule 2090, UK firms often apply the Money Laundering Regulations, and firms set further requirements in their own procedures. We build to the checklist your compliance lead sets.

It tracks the paperwork and pre-fills what it can. Direct integration with a custodian or platform depends on what that provider offers advisers, so it is confirmed per project.

Yes. Forms work on a phone, save progress and pre-fill from the CRM. A meeting route stays for clients who prefer it.

Days from yes to complete file, share of files complete first time and how often onboarding stalls waiting on the client.

Free 20-minute call

Want this 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