For directors and operations leads in advice firms and wealth managers.
Why does advice take so long to document? Because the fact find, the research and the suitability report are separate pieces of work.
Client data, provider information and review obligations sit across a client management system, provider portals and email. Outproduce installs the path from the fact find and provider information requests into a prepared review pack and a drafted suitability report, with annual review obligations tracked and client communication held for the adviser. Advice, recommendations and anything sent to a client wait for a named approver.
A paraplanner requests provider information by letter or portal and chases each one separately.
We build this
An information request path that issues the requests from the client record and tracks each to received.
What changes
Outstanding provider information is a visible list with an owner.
You do this by hand
The fact find is read and the key figures are retyped into a review pack.
We build this
A review pack preparation path that assembles the client position from the records and names anything missing.
What changes
Preparation starts from an assembled position rather than a blank document.
You do this by hand
The suitability report is written from scratch each time, reusing paragraphs from an old file.
We build this
A drafting path that prepares the report structure and factual sections from the confirmed client record.
What changes
The adviser spends the time on reasoning, not on restating facts.
You do this by hand
Annual review dates are tracked in a spreadsheet and worked through when capacity allows.
We build this
A review obligation register built from the client records, with each review tracked by what it is waiting on.
What changes
Service commitments are managed by cause rather than by date alone.
You do this by hand
Client correspondence and signed documents are filed manually after each meeting.
We build this
A filing and completeness path that places correspondence against the client and names gaps in the file.
What changes
The client file is complete without a manual tidy up before a review.
Advice capacity is limited by documentation, not by client demand. The adviser is the scarce resource, and much of the adviser day is spent assembling facts that already exist in the firm systems.
Regulatory expectations keep pushing towards evidenced, timely review of every client the firm has agreed to serve. Treating that as a register with causes, rather than a spreadsheet of dates, is what makes it survivable.
Lifecycle
Where the system runs and where a person decides.
Typical lifecycle in this sector
1Review or advice need arises
2Client position assembled from the recordsAutomated
3Provider information requested and trackedAutomated
4Gaps in the fact find raised for the adviserHuman approval
5Review pack preparedAutomated
6Adviser forms the recommendationHuman approvalAdvice is never produced without a named adviser.
7Suitability report drafted around the recommendationAutomated
8Report and client communication approved and releasedHuman approval
Workflows
The workflows we install first.
Each one names the manual version, the installed version, and the approval point that stays with a person. Figures show sample records, never client data.
01
Provider information request and tracking
Requests are issued from the client record and each response is matched back to its request. Outstanding items stay visible with an owner.
Expected impactExpected impact: less chasing by hand and fewer reviews delayed by missing data.
Illustrative ladder for outstanding informationIllustrative
Requests issuedA request per plan, recorded against the client.
Automated
Response matchedReceived data attached and the item closed.
Automated
Still outstandingA follow up is prepared for the administrator to release.
Human approval
Review date at riskRaised to the adviser with the missing plans named.
Escalated
02
Client position to review pack
Holdings, objectives, contributions and prior advice are assembled into a review pack, with anything unverified named rather than assumed.
Expected impactExpected impact: paraplanning time moves to analysis.
Illustrative review pack assembly · Illustrative
Section
Assembled from
When it is held
Current holdings
Platform and provider records
Valuation not received
Objectives and circumstances
Fact find and meeting notes
Material change not confirmed
Contributions and withdrawals
Plan records
Conflicting figures between sources
Prior advice
Previous suitability reports on file
Report missing from the file
03
Recommendation to drafted suitability report
Once the adviser has formed the recommendation, the report is drafted around it from the confirmed record. The adviser approves before anything reaches the client.
Expected impactExpected impact: report turnaround improves without weakening the adviser role.
Illustrative trace of a suitability reportIllustrative
01
Adviser records the recommendation
Rationale and client objective captured on the case.
Human approval
02
Factual sections drafted
Current position, costs and comparisons drawn from the record.
Automated
03
Inconsistency raised
A figure that disagrees with the source is held, not written.
Escalated
04
Adviser approves and releases
Named approval before the report goes to the client.
Human approval
04
Review obligation register
Every agreed service commitment sits on a register with its state and cause of delay, so the firm can see where capacity is actually blocked.
Expected impactExpected impact: service commitments are evidenced and visible firm wide.
Illustrative comparison of review tracking
Case
By hand today
Inside the installed path
Review due
Read from a spreadsheet of dates
Register entry with an owner and a state
Waiting on provider data
Invisible until chased
Shown as the blocking cause
Client not responding
Noted in an adviser inbox
Recorded contact attempts on the register entry
Go live
How it reaches production in your firm.
01
Fit Review with advisers and paraplanners
We follow a live case from review trigger to released report.
Free
02
Operating Map
The map names the client records, the information requests, the pack structure and every adviser approval point.
Paid, yours to keep
03
Production Install on a scoped client segment
A chosen segment or adviser book goes live first, with an agreed acceptance test on real cases.
Human approves
04
Managed operation or handover
We run the exception queue with your team, or hand over the documented system with an owner named.
Monitored
What we measure
Baseline first, then the delta.
We record each of these before anything switches on, so the result is measured against your numbers, not a benchmark.
Baseline in week one · higher is betterReviews starting with a complete information set
Baseline in week one · lower is betterProvider chases written by hand
Baseline in week one · lower is betterSuitability reports returned for factual correction
Baseline in week one · higher is betterAgreed reviews with a recorded state and cause
first builds: provider information request and tracking · client position to review pack · recommendation to drafted suitability report