Fixed quote after a free call

Annual review automation so every client gets the review they pay for

We build a workflow that schedules each household's review from its service level, sends a pre-review questionnaire, chases updated details, drafts a preparation pack from the CRM and platform data for the adviser, and logs that the review was offered, held or declined. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why paid-for reviews slip

Ongoing advice fees are paid for an ongoing service, and the review is its centre. Scheduling dozens of reviews a month, chasing clients for updated circumstances and pulling together valuations and notes takes a great deal of administrator and paraplanner time.

Regulators look at whether reviews happen. In its review of ongoing advice services, the FCA found suitability reviews delivered in around 83% of cases where they had been promised, with clients declining or not responding in a further 15%, and said cases where no review was attempted must be put right. Evidence of every offer and outcome matters.

What we build

What our annual review automation includes

Review calendar per household

Reviews scheduled from each client's service level, with invitations sent ahead of the due month.

Pre-review questionnaire

A short update on circumstances, goals and contact details, chased politely.

Preparation pack draft

CRM notes, last review actions, questionnaire answers and platform valuations gathered into one draft pack.

Declined and unresponsive tracking

Offers, reminders and declines logged with dates, so the firm can show what was offered.

Post-review tasks

Actions agreed in the meeting turned into tasks for the paraplanner and administrator.

Service delivery report

A monthly view of reviews due, held, declined and overdue by adviser.

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

    Review due

    The service calendar marks a household as due for review.

  2. 02 Automated

    Invite and questionnaire

    The client is invited to book and asked to update their details.

  3. 03 Automated

    Pack drafted

    A preparation pack is drafted from the CRM, questionnaire and platform data.

  4. 04 Staff review

    Paraplanner checks

    The paraplanner checks the pack and adds analysis the adviser needs.

  5. 05 Adviser or compliance decides

    Review and advice

    The adviser holds the review and decides any changes to the advice.

How it behaves

How annual review preparation behaves

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

What the client sees

  • A timely invitation to book their review
  • A short questionnaire to update their details
  • A focused meeting with an adviser who is prepared

What staff see

  • Draft packs ready to check
  • Post-review tasks created automatically
  • A monthly service delivery report

What the automation does

  • Schedules, invites and chases on time
  • Drafts packs from existing data
  • Logs every offer and outcome

Edge cases and fallbacks

Client books outside the usual month
The review is matched and the calendar adjusts.
Questionnaire not returned
The pack is drafted from existing data and the gap is noted.
Client has died or left
Staff mark the record and the calendar stops.
Platform data unavailable
The pack marks valuations as pending rather than using stale figures.

Architecture

Annual review preparation 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.
Service calendar Reviews due n8n workflow Invite and chase Questionnaire Client updates CRM and platform Notes, valuations Prep pack draft For the adviser Paraplanner Check and add Delivery log Held or declined
  • Input
  • Logic and services
  • Output
  • AI step
  • People
  • Data

How it flows

  1. 1 The service calendar marks households due for review.
  2. 2 Clients are invited and asked to update their circumstances; CRM and platform data are gathered.
  3. 3 A preparation pack is drafted for the paraplanner to check and complete.
  4. 4 The adviser holds the review, and the offer and outcome are logged.

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.

Annual review scheduling, preparation & evidence project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Service levels, current review process, pack contents, platforms and reporting needs.

  2. 02

    Design

    2 to 3 days

    Invitation timing, questionnaire, pack template, decline rules and report layout.

  3. 03

    Build

    1 to 2 weeks

    Calendar triggers, questionnaire, pack drafting, logging and tasks.

  4. 04

    Shadow run

    About 1 week

    Packs drafted for a month of reviews while paraplanners compare with their own.

  5. 05

    Launch

    1 to 2 days

    Switch on for all advisers.

  6. 06

    Support

    Ongoing

    Pack and questionnaire changes.

What it runs on

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

n8n Wealthbox, Redtail, Salesforce Financial Services Cloud or Intelliflo Office Secure questionnaire form Platform or portfolio system data (route confirmed per project) Calendly API v2 or Microsoft 365 calendars Claude or OpenAI for pack drafting, under the firm's vendor terms

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

    Service levels, pack template and decline rules.

    $200 – $400

  • Build

    Triggers, questionnaire, pack drafting and logging.

    $500 – $1,300

  • Integrations

    CRM, calendar, forms and platform data.

    $150 – $400

  • Testing and shadow run

    Packs compared with paraplanners' own.

    $100 – $250

  • Launch and training

    Switch-on and team walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Platform valuations depend on what each platform exposes; where there is no route, the paraplanner adds them. Subscriptions are billed to you directly.

Monthly running costs you pay directly

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

  • AI model usage: Billed by the provider per use; usually a small monthly amount at practice volumes.
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

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.

UK: ongoing advice reviews

The FCA's multi-firm review found suitability reviews delivered in around 83% of promised cases and said redress is likely where no review was attempted; logging every offer supports the evidence.

Source: www.fca.org.uk

UK: Consumer Duty

The FCA's Consumer Duty sets high standards of protection for retail consumers; delivering the service clients pay for sits at its centre.

Source: www.fca.org.uk

US: records of advice

SEC Rule 204-2 requires keeping written communications relating to advice for at least five years, so review packs and notes are retained.

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

Annual review scheduling, preparation & evidence questions, answered.

Changes in circumstances and goals, contact and beneficiary details, last review actions, current valuations and performance, and anything the adviser wants to revisit. We build the questionnaire and pack template from your own checklist.

No. It gathers and summarises facts into a draft pack. The adviser decides whether the advice should change.

Every offer, reminder and decline is logged with dates. How you respond, such as reviewing the service or the fee, is the firm's decision.

Where the platform or portfolio system offers an API or export, yes. Otherwise the paraplanner adds them and the rest of the pack is still ready.

It gives you a dated log of reviews offered, held and declined for every client, which is the evidence firms were asked about.

Reviews due versus held, declined and overdue, days from invitation to meeting, and paraplanner time per pack.

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