A day in the life of a wealth manager, with and without agents

An adviser managing a book of clients does two jobs at once. One is the job they were hired for: understanding what a family is trying to do with its money and helping them do it. The other is assembling the material that makes the first job possible, and it eats the day.

This is a description of that day, before and after. The names are invented and the pattern is not.

Without agents: Tuesday

Eight fifteen. Overnight market movement has touched four portfolios in ways worth mentioning. Finding out which four means opening each one.

Nine. First meeting. The adviser has prepared for it, which meant an hour last night pulling holdings, recent correspondence, the note from the tax specialist and the change of circumstance the client mentioned in passing six weeks ago. Most of that hour was retrieval, not thinking.

Eleven. A client emails asking whether a change in their situation affects their plan. Answering properly means checking a policy document, a suitability record and a previous recommendation. Answering quickly means guessing. The email sits open until Thursday.

Two. Compliance asks for the rationale behind a recommendation made in March. It exists, spread across a meeting note, an email and somebody's memory.

Six. The actual work of the day begins: thinking about three families whose circumstances have changed.

With agents: the same Tuesday

Eight fifteen. A briefing is already assembled. Four portfolios flagged, each with the movement, the affected holdings, and the specific sentence from the last review that the movement bears on. The adviser reads it in six minutes and disagrees with one of the four, which is the point.

Nine. The meeting pack was drafted overnight, drawing on holdings, correspondence, specialist notes and that remark from six weeks ago, which the agent found because it was in the record even though nobody had tagged it. The adviser edited it for ten minutes rather than assembling it for sixty.

Eleven. The client email is answered the same morning. The agent retrieves the policy language, the suitability record and the prior recommendation, and drafts a response that cites all three. The adviser reads the citations, rewrites two sentences, and sends it.

Two. Compliance asks about March. The rationale, the sources it drew on and every agent action taken in the process are in an audit trail that exports in one click.

Six. The adviser goes home. The thinking happened at three in the afternoon, when they were awake.

The parts that deliberately do not change

The adviser still makes every recommendation. The agent does not decide suitability, does not contact a client unprompted, and does not act on an account. It prepares, retrieves, drafts and flags, and a qualified person decides.

This boundary is not a limitation we are apologising for. It is the design. In a regulated business the question is never only "was this correct" but "who is accountable and can you show your reasoning". An agent that acts without a named human behind it fails the second question regardless of how well it answers the first.

What makes it safe enough to run

None of the above works on trust alone. It works because of what sits underneath:

• Policy enforced at the moment of action, so an agent that should never touch a trading system cannot, no matter what its plan says.
• Credentials resolved at runtime from an org-level vault, so no secret lives in an agent's configuration.
• An audit trail covering every action, exportable when a regulator or an internal reviewer asks.
• Evals on every run, so quality is scored continuously rather than sampled after a complaint.
• Spend attributed per agent, so the firm knows what this capability costs per adviser rather than as one opaque line.

The honest version of the benefit

The productivity claim usually attached to this is some percentage of time saved. We would put it differently. The time is not saved, it is moved: out of assembling material and into the conversations that assembling material was always in service of.

That is a smaller claim than the industry tends to make and a more durable one, because it survives contact with an actual Tuesday.

Next

The financial services pages cover deployment patterns, including running entirely inside your own infrastructure where client data cannot leave it. If you would rather see it against your own systems, book a demo and bring your constraints.