A suitability report generator that drafts from your templates, never your advice
Writing advice documentation is one of the biggest time costs in a practice. We build a workflow that takes the fact-find, objectives, attitude to risk and the adviser's own recommendation notes, assembles them into your approved report template as a first draft, flags missing sections and routes it through paraplanner checking and adviser sign-off, then files the final version. A typical build costs $1,000 to $2,500 per workflow and takes about four to five weeks.
The problem
Why advice documentation eats paraplanning time
A suitability report, or recommendation letter outside the UK, has to explain the client's circumstances and objectives, what is recommended and why, and the risks and costs involved. Paraplanners rebuild much of it from scratch for every client, copying facts from the fact-find and adjusting boilerplate.
The risk in automating it is obvious: a report that reads well but says something the adviser did not decide. The answer is to automate the assembly of facts and approved wording, and keep the recommendation and its reasoning firmly with the adviser.
What we build
What our suitability report generator includes
Your template, structured
Your approved report broken into sections with rules for which apply to which advice type.
Facts filled from the fact-find
Circumstances, objectives, attitude to risk and capacity for loss pulled from the CRM or fact-find.
Adviser rationale, in their words
The adviser's recommendation notes placed where they belong and tidied for readability, not invented.
Gap and consistency checks
Missing sections, mismatched figures and objectives without a matching recommendation flagged.
Paraplanner and adviser sign-off
A clear review route with changes tracked and sign-off recorded.
Filing and retention
The signed report filed to the client record and kept according to your records policy.
Who does what
Automation does the chasing, people make the calls.
-
01
Staff review
Advice agreed
The adviser records the recommendation and reasons after the meeting.
-
02
Automated
Draft assembled
Facts, approved wording and the adviser's rationale fill the template.
-
03
Automated
Checks run
Gaps and inconsistencies are flagged in the draft.
-
04
Staff review
Paraplanner edits
The paraplanner completes and corrects the draft.
-
05
Adviser or compliance decides
Adviser signs off
The adviser approves the final report before it is sent to the client.
How it behaves
How report drafting behaves
What the client sees
- A clear, consistent report soon after their meeting
- Their own circumstances and objectives reflected accurately
What staff see
- Drafts with facts already filled
- Gaps and inconsistencies flagged
- A tracked review and sign-off route
What the automation does
- Fills templates from fact-find data
- Places the adviser's rationale without inventing it
- Files the signed final report
Edge cases and fallbacks
- Adviser notes are thin
- The draft marks the rationale section incomplete and returns it to the adviser.
- Fact-find figures conflict
- Flagged for the paraplanner; no figure is chosen automatically.
- New advice type with no template
- Routed to the paraplanner to draft manually.
- AI provider outage
- The template is filled with facts only and the paraplanner completes the rest.
Architecture
Suitability report drafting at a glance.
- Input
- Logic and services
- AI step
- People
- Data
How it flows
- 1 Fact-find data and the adviser's recommendation notes feed the workflow.
- 2 The right template sections are filled and gaps and inconsistencies flagged.
- 3 The paraplanner edits and checks the draft.
- 4 The adviser signs off, and the final report is filed and retained.
Project planner
How the project runs, phase by phase.
Suitability report drafting & advice documentation project plan
Typical time to launch: about 4 weeks, then support
-
01
Discovery
2 to 3 days
Report templates, advice types, where fact-find data lives and how reports are checked.
-
02
Design
About 1 week
Section rules, field mapping, check rules, review route and retention.
-
03
Build
1 to 2 weeks
Template assembly, checks, review route and filing.
-
04
Shadow run
About 1 week
Drafts produced alongside paraplanners' own reports and compared.
-
05
Launch
1 to 2 days
Switch on for agreed advice types.
-
06
Support
Ongoing
Template updates and new advice types.
What it runs on
Real products only, connected through the access each vendor provides. See all integrations
Cost estimate
What it costs, line by line.
-
Discovery and design
Templates, section rules and checks.
$250 – $500
-
Build
Assembly, checks, review route and filing.
$500 – $1,300
-
Integrations
CRM, Word templates and storage.
$125 – $400
-
Testing and shadow run
Drafts compared with paraplanners' reports.
$100 – $200
-
Launch and training
Switch-on and paraplanner walkthrough.
$25 – $100
-
Total project estimate
$1,000 – $2,500
Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Several report templates or advice types may need a second workflow. AI usage is 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; report drafting uses more than short steps but is usually modest 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
Privacy and consent
Rules we design for, with the sources.
The recommendation is the adviser's
The workflow assembles facts and approved wording. It never chooses products or writes reasons the adviser did not give.
US: advice records
SEC Rule 204-2 requires keeping written communications relating to advice and recommendations for at least five years from the end of the fiscal year of the last entry.
Source: www.law.cornell.eduUK: Consumer Duty
The FCA's Consumer Duty expects firms to put good outcomes for retail customers at the centre; reports must be understandable as well as complete.
Source: www.fca.org.ukEU and UK: processor contracts
Any AI or automation vendor handling client data needs an Article 28 GDPR contract.
Source: gdpr-info.euFree tools
Try these first, free.
Guides to read first
How we deliver
Agile delivery, in 1 to 2 week sprints.
Every sprint
- 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 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 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 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
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
- Input
- Logic and services
- People
- Output
- Data
How it flows
- 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
- 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
- 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
- 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.
FAQ
Suitability report drafting & advice documentation questions, answered.
A tool that assembles client facts, objectives and the adviser's recommendation into your report template as a first draft. Ours flags gaps and routes the draft through paraplanner checking and adviser sign-off.
It drafts the factual sections and tidies the adviser's own rationale. It never decides what to recommend or invents reasons, and every report is checked and signed off by people.
Yes. We structure your existing templates rather than imposing ours, so the output looks like your firm's reports.
Yes. Section rules decide what applies to pensions, investments, protection or other advice types you offer.
In effect, but built around your CRM and templates rather than as a separate product to learn.
Paraplanner time per report, share of drafts needing major rework and days from meeting to report sent.
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.
More for financial advisers
All servicesCRM for financial advisors: pipeline & service calendar
Prospects from referrals, seminars, your website and centres of influence in one CRM pipeline, plus a service calendar that schedules reviews, birthdays and required milestones for every household.
From $1,000 · About 4 weeks Details
Client onboarding, fact-find & KYC evidence
Turn a yes into a complete client file: fact-find and risk questionnaire sent and chased, identity and ownership evidence gathered, agreements out for e-signature and account paperwork tracked to completion.
From $1,000 · About 4 to 5 weeks Details
Annual review scheduling, preparation & evidence
Every paid-for review scheduled on time, a pre-review questionnaire chased, a preparation pack drafted for the adviser and evidence of delivery logged, including clients who decline.
From $1,000 · About 4 weeks Details