Wealth manager: from first meeting to a complete client file

The first meeting is where the work starts, not where it ends

Direct answer: between the first meeting and a complete client file, an independent wealth manager can let the follow-up tasks run on their own (acknowledging receipt, listing expected documents, reminders, filing, completeness checks) and keep the decisions: accepting the client, judging a doubtful document, signing off the file. What runs alone prepares and reminds. What commits you stays a human decision.

The meeting goes well and the client agrees in principle. Then comes the part nobody bills for: asking for documents, noticing two are missing, chasing, receiving an unreadable scan, retyping details from an email into a record. For a firm of one to three people, this phase stretches over weeks, at the pace of the client’s forgetfulness and your own.

This article covers work organisation only: who prepares what, in what order, with what check. It says nothing about what your profession requires in a file, or about the rules that apply. That list belongs to you and your advisers. Our general approach is described on the page about what the studio automates. A neighbouring article covers the next stage, client reports without losing your evenings.

The seven steps between the meeting and a complete file

Before automating anything, break the phase into steps. In most firms the same seven appear.

1. Confirm. Send the follow-up message: a summary of what was said and the next steps.
2. List. Draw up the list of documents and information expected from this particular client.
3. Collect. Receive the documents by email, messaging or upload, in very varied forms.
4. Chase. Remind the client of what is missing, without nagging, until the file is complete.
5. File and enter. Name each document, store it in the right place, copy the details into the client record.
6. Check. Verify that everything is there, legible, correctly named and consistent from one document to the next.
7. Sign off. Decide that the file is complete and that the relationship can move forward.

Steps 1, 4 and 5 are mechanical. Steps 2, 3 and 6 largely are. Step 7 is a decision and nothing else. The useful work is to draw that line in your own practice rather than discover it after an incident.

What can run alone, and what stays with you

The last row is deliberate. No tool should declare a file complete on your behalf. It can tell you “all twelve items on the list have arrived”, which is a fact. Deciding that this is enough is a judgement that binds you.

The completeness table, the centrepiece of the process

Definition: a completeness table is a single view, per client, showing for each expected document its status (not received, received, to verify, validated), the date of the last reminder and who holds it. This table, more than any AI, is what saves time: it replaces memory and email threads.

Once it exists, everything else hangs off it. The acknowledgement updates the status of a row. The reminder fires on rows still “not received” after a delay you set. Filing names each file after the row it fills. Your morning view shrinks to the list of files that are moving or stuck, the kind of overview described in the daily summary.

For reading the documents received, the principle is simple: the AI reads the document, proposes what it is and which file it belongs to, and flags anything it is unsure about. You only review the flagged cases.

The follow-up message, the one moment the client really commits

The message sent after the meeting sets the rhythm of everything that follows. A good one has four elements: what was agreed, the list of expected documents, a requested return date, and who to reply to. When those four are clear, later reminders only need to repeat them, and the client cannot say they did not know.

It is also the simplest task to prepare: from your meeting notes and the master list, a draft is ready before you have closed the door. You read it, adjust a sentence, send it. The gain per message is modest, but it removes the week-long gap that often separates the meeting from the first email, and that gap is what cools a new client.

A worked example with your own numbers

We do not publish an average gain, because it depends on your clients and habits. Here instead is how to compute yours, with purely illustrative figures.

Suppose six new files per quarter. If, once timed, following up one file (confirming, chasing, filing, entering, checking) costs you 4 hours spread over three weeks, that is 6 × 4 = 24 hours a quarter. If the process brings those steps down to 1.5 hours of review and decisions per file, the total falls to 9 hours. The theoretical gain is 15 hours a quarter, roughly two working days. These are your assumptions, not a promise: replace 6, 4 and 1.5 with your own measurements.

The calculation serves two purposes. It tells you whether the subject deserves a project, and it gives you a baseline for judging the result after three months. The most visible gain is sometimes not time but elapsed duration: a file chased on fixed dates is completed faster than one chased when you remember. Measure that delay too, from the meeting to sign-off.

Setting up the process, step by step

1. Write your master list. The documents and information you ask for, by client type. One page, approved by you and, if you wish, by your advisers.
2. Pick a single drop point. One address or folder where everything arrives, with a simple naming rule (client, document type, date).
3. Create the completeness table. One row per expected document, four statuses, one reminder date.
4. Set the reminder rhythm. For example one reminder after a few days, a second later, then a call from you. The number and the delays are yours.
5. Connect reading and filing. Documents received are read, named and stored, and the table updates itself.
6. Keep human sign-off. The file moves from “complete against the list” to “validated” by your decision, never automatically.

All of it plugs into your current tools (email, storage, client record), under your control. If you want to size up a first task, the studio’s automation catalogue shows what is already built.

When this approach is not the right choice

• You open very few files. With one or two new clients a quarter, a master list and a spreadsheet are enough. The calculation above will show it.
• Every file is completely different. If no list ever repeats, there is little routine to prepare. The tool will mainly help with filing.
• Your clients only answer by phone. If collection happens through spoken exchanges, you first need a way to record what was said. Automation comes after.
• Your master list does not exist yet. Automating a fuzzy list produces fuzzy reminders. Write it first.

Finally, a tool like this does not replace advice on what your business must contain or retain. That question is outside its scope.

Pitfalls to avoid

• Mixing up two clients. The most serious risk is a document landing in the wrong file. The process handles each client separately and checks the name at every step.
• Chasing too hard. A badly tuned automatic sequence makes a firm look pushy. Test the tone on one file before rolling it out.
• Letting the tool conclude. “Everything has arrived” is not “the file is good”. Keep the decision.
• Not measuring. Without timing before and after, you will not know whether the process works.

Where to start this week

Take your most recent open file. Note every step between the meeting and sign-off, with the date and the time spent. Mark the mechanical ones in green. If more than half the time is green, you have a serious candidate, and the first thing to write is the master list.