Ask a financial adviser what they want from software and you will usually get a shrug and something about wanting to find things faster. Ask them what their week actually looks like and a different problem appears entirely.
It is worth walking through that week, because the mismatch between it and the software normally sold to them explains why so many advisers end up running their business out of a notebook, a phone and a spreadsheet they do not show anyone.
The shape of the week
An established adviser holds somewhere between two hundred and a thousand relationships. Not leads — relationships. People they have met, whose families they know, some of whom they last spoke to in 2019.
In any given week, perhaps five of those matter. Someone's policy is up for review. Someone mentioned a baby due in March. Someone went quiet after a promising second meeting and it has been three weeks. Someone's friend was mentioned as an introduction and nothing was ever done about it.
The rest are dormant, and correctly so. Contacting all of them would be both impossible and unwelcome.
So the real work of the week is not the meetings. It is the sorting. It is the twenty minutes on a Monday morning — or more often, the twenty minutes that never happens — of scrolling through names trying to remember who is due for something. That job is invisible, it is unpaid, and it is the single largest determinant of how the month goes.
The adviser's constraint is attention, not information. They have all the information. They cannot hold all of it at once.
Why the standard CRM fits badly
Most CRMs are descendants of business-to-business sales software. They assume a deal: an opportunity with a value, a close date, and stages it moves through until it is won or lost. Everything in the interface serves that assumption — the pipeline view, the forecast, the reporting.
Advisory work does not have that shape, in three specific ways.
Nothing closes
A first policy is not the end of anything. It is the beginning of a relationship that will produce more later — at a marriage, a birth, a house purchase, a job change, a retirement. Software that marks a record "Closed Won" and moves it out of view is actively working against the adviser, because the record it just filed away is the most valuable one they own.
Dormancy is normal
In a B2B pipeline, a deal untouched for six months is dead and should be cleared out. For an adviser, a client untouched for six months is simply a client who did not need anything. The same silence means opposite things, and a system that treats all silence as failure will bury the adviser in warnings they learn to ignore within a fortnight.
Relationships reactivate years later
The person who politely declined in 2021 is a genuinely good prospect in 2026, because their circumstances changed. Standard pipeline software has no concept of this. Once something is lost it stays lost, and the adviser's most quietly reliable source of new business — people they already know — is the part the software helps with least.
Reviews and renewals are events, not deals
A large part of an adviser's calendar is recurring by nature. Annual reviews. Policies reaching a date that changes something. Anniversaries worth acknowledging. Commitments made in a meeting — "I'll look into that and come back to you."
These are all the same kind of thing: an obligation with a date attached, which will arrive whether or not anyone remembers it. And they are the easiest thing in the business to get wrong, because forgetting one produces no immediate consequence. The client does not call to complain that their review did not happen. They just quietly stop thinking of you as their adviser.
The software job here is unglamorous and entirely mechanical. A recurring event needs to reappear on a list at the right time, survive being postponed, and not vanish because someone marked something else complete. That is it. There is no cleverness required — but almost no generic CRM does it well, because it was designed for deals that happen once.
Two minutes before a meeting, not twenty
Here is the moment where a system either earns its keep or does not.
An adviser is in a lift, or a car park, or a coffee shop ten minutes early. They are about to see someone they last met fourteen months ago. What they need, in the time it takes to walk to the table:
- ✓What we hold together now, in plain terms.
- ✓What we discussed last time, and what I said I would do.
- ✓What has changed since — a new child, a new job, something they mentioned in passing.
- ✓What is coming up in the next few months that they should know about.
Four things. In a normal CRM, getting them means opening a record, scrolling a timeline, reading five notes of varying quality, and reconstructing the story from fragments. Twenty minutes if done properly, which means it is usually not done properly. The adviser walks in and improvises, and the client can tell.
A system that produces those four things on one screen, without being asked, changes the quality of the meeting. Not because it is intelligent, but because it did the reading. This is the clearest example of the general principle: the system's job is to hand something back, not to collect.
The compliance constraint sits on top of all of it
Advisers work under conduct rules about how advice is given and recorded, and under data-protection rules about what may be held and how it may be used. This article is not the place for specifics, and anyone who needs specifics should be asking their compliance function rather than a website.
But the shape of the constraint matters for how a system should be built, and it is straightforward enough:
- ✓Records need to be durable and honest. What was discussed and what was recommended may need to be evidenced long after everyone has forgotten. A system where notes are optional and easily overwritten is storing up a problem.
- ✓Marketing is not a free action. What may be sent, to whom, and on what basis is constrained. A system that makes it easy to blast a list to two hundred people is offering the adviser a way to get into trouble quickly.
- ✓Personal data has limits. Advisers hold unusually sensitive information — health, income, family circumstances. Who inside the firm can see it, and what happens to it when an adviser leaves, are design questions, not afterthoughts.
The practical consequence: a good system for an adviser is slightly more careful and slightly less enthusiastic than a general sales tool. It should make the right thing easy and the risky thing deliberate. That is a design choice, and it is one general-purpose software has no reason to make.
Where a system stops helping
It would be dishonest to write all of the above and not say the obvious thing: plenty of advisers do perfectly well with a diary and a spreadsheet, and some of the best do.
A few situations where the honest answer is to leave it alone:
- ✓A small book, well held. If someone has eighty clients and knows all of them, a system adds admin and removes nothing. The sorting problem only becomes real at a few hundred relationships.
- ✓The discipline is not there. This is the important one. A system surfaces what it has been told. If meetings are not written up, nothing appears — and the adviser now has two problems, the original one plus a system that quietly lies to them. Software does not create a habit that does not exist. It amplifies one that does.
- ✓Nobody owns it. A system that is not adjusted as the practice changes drifts away from the work. Within a year it describes a business nobody is running.
- ✓What you have already works. If the diary genuinely holds it together, that is the answer. Nothing here is worth disrupting something that works.
The case for building is strongest when the book is large enough that names fall through, the person cares enough to keep it accurate, and the cost of a forgotten review is real money.
None of this is about financial advice
Advisory work is a useful example because the pain is unusually visible — the relationships are long, the dormant periods are obvious, and the cost of forgetting someone is easy to name. But nothing above is specific to it.
Swap the words and it is the same shape anywhere the constraint is attention rather than information:
- ✓A recruitment desk holds hundreds of candidates and clients, most dormant, a few live this week. Placements are events, not closes. A candidate placed two years ago is the best lead in the database.
- ✓An agency holds past clients who reactivate when they rebrand or hire someone new. Retainers renew on dates. The account manager needs the four-line briefing before a call as much as any adviser.
- ✓A B2B sales team with long cycles has the same dormancy problem dressed as a pipeline — most accounts are quiet, and knowing which three are worth a Tuesday is the actual skill.
The common test is simple. Does your team already know more than they can hold in their heads at once? If yes, the problem is not storage. It is the daily act of deciding what to look at — and that is a job a system can genuinely take off someone, in any industry you like.
The short version
An adviser does not need a better place to put things. They need something that reads their own records back to them: five names on a Monday, four lines before a meeting, and a review that reappears on the right week without being remembered.
That is not a feature list. It is a change of direction — from a system that asks to one that tells. And it applies to everyone whose work is holding more relationships than one person can keep in mind.
Common questions
Often yes, and it is the sensible first move. Configuration bends a fixed shape as far as it will go, which is frequently far enough. The limit shows up around the assumptions — deals that close, silence that means failure, records that disappear once won. Those are baked in, and no amount of renaming fields changes what the software believes about your work.
Mostly by noticing dates and gaps, which is less clever than it sounds. A review coming up, a promise made and not kept, a life event mentioned in a note, a long-standing client who has gone unusually quiet. None of that is prediction. It is bookkeeping done continuously, so nobody has to do it on a Monday morning.
They will if the system treats every silence as a problem. Most dormant relationships are dormant for good reason and should stay quiet. A list that is short and mostly right gets used; a list of forty things gets dismissed by the second week, and then the system is worse than nothing because it looks like it is working.
Both, depending on how it is built. Durable records and clear visibility of who can see what generally help. Anything that makes mass contact effortless adds risk, because the constraints on advisers about marketing and record-keeping are real. What the specific requirements are is a question for your compliance function, not a piece of software.
No, and framing it that way would be a mistake. The same pattern appears on recruitment desks, in agencies, and in any B2B team with long sales cycles. The test is whether your people hold more relationships than they can keep in mind at once. If they do, the problem is attention, and the shape of the answer is the same.
That is worth deciding before it happens rather than during. Who owns the record, who can see it afterwards, and what the client is told are business and compliance questions, and a system should be able to enforce whatever you decide. If nobody has answered them, the practical answer today is usually that the records leave with the person.
We build websites and run SEO & AEO for Singapore businesses. HeyAda is a Singapore web studio — design, copywriting, code and SEO, handled end to end. We write these guides to share what actually works, in plain English. If your site isn't getting found, say hi.
Is the real list in the system, or in a notebook?
If your people keep a separate list of who to call, that gap is the whole problem — and it is usually a short conversation to work out whether it is worth closing. Tell me how the week actually runs and I will tell you honestly whether this is worth building or whether a diary is doing fine.