An independent financial advisor from Canton Ticino, with fifteen years of experience and about one hundred and fifty clients in his portfolio, describes a situation that is not an isolated case. "Up to about eighty clients, I knew them all personally. I knew their history, their habits, the details of their lives that counted for financial decisions. Now we are at one hundred and fifty. I've had a CRM for three years, well updated, with notes for every client. But I have the feeling that the first thirty or forty clients still receive an attention the rest no longer get. And I don't know what to do".
This feeling is not an impression; it is a constant that can be observed in the work of an independent financial advisor. There is a threshold, different for each advisor but usually between eighty and one hundred and twenty clients, beyond which a personal relationship held in a purely manual way starts to fray. Not because the advisor has become worse; because the number of relationships simultaneously managed exceeds the human capacity to keep them all at the level the client would perceive as "personal attention".
Beyond this threshold, the difference is not between those who use AI and those who do not. It is between those who have structured their knowledge of clients and those who have not.
The CRM as a contact system
A CRM, for an independent financial advisor, serves mainly to keep track. Who the client is. When he was last seen. What was said. When to call him back. This information is valuable, and a well-updated CRM is a huge difference from the alternative of keeping everything in a diary or in memory.
But a CRM does this one thing: it tracks. It does not sustain. A client who has not been called for six months is flagged by the CRM as an anomaly only if someone set a six-month reminder. If nobody set it, the CRM does not alert. A client who has changed bank and has not said so, the CRM does not know. A client receiving communications from the competitor is not in its flow, the CRM does not see it.
The CRM, in other words, is a well-organised archive, not an active observatory. The relationship it sustains is only the one the advisor decides to sustain actively, with reminders set by him, notes written by him, follow-ups scheduled by him. Beyond one hundred clients, the advisor does not have the time to do this work with the same quality for everyone.
What sustaining a relationship actually requires
Sustaining the relationship is an activity different from mere tracking. It includes at least four components.
The first is contextual presence at the right time. If the client receives a premium on his life policy in June, a brief contact in June with a greeting and an informed question ("it's the renewal of the 2018 policy, everything in order?") is not a reminder: it is a signal that the firm is present. If the client has a child who has just turned eighteen, a contact flagging availability to discuss education planning or a first investment is a form of attention. These contextual contacts are not calendar updates; they are observations on the client's life translated into communication.
The second is proactive reporting. Not the automatic quarterly report nobody reads, but an informed comment on why the client's portfolio performed a certain way over a specific time window, referring to what the client had said the previous time. A client who had expressed concern about inflation at the last meeting feels seen when he receives an update commenting on his concern in the light of new data.
The third is personalised financial education. Not generic content on the site, but targeted notes on the client's situation. An entrepreneur client near retirement receives content relevant to managing post-activity income; a client in the accumulation phase receives something else. This personalisation is perceived as attention, even when partially automated.
The fourth is early warning. If an important deadline is approaching, a regulatory change affecting the client's specific situation, a market event intersecting his portfolio, the advisor flags it before the client discovers it from other sources. This type of communication is what separates an advisor perceived as proactive from one perceived as reactive.
None of these four components is covered by a standard CRM. All four require a knowledge infrastructure integrating registry, history, portfolio and market, plus an active observation system that notices when it is time to intervene.
The structural limit of the vertical CRM
There are vertical CRMs for financial advisors (Salesforce Financial Services, GoalGetter, some Italian products such as Diaman or Inforisparmio). Compared to a generic CRM, they offer specific financial features: portfolio tracking, integration with valuation systems, preset reports.
Even these tools, however, remain in the category of "evolved contact system". They do better what a generic CRM does; they do not do something different. They do not autonomously observe the client's life, do not generate personalised communications based on new observations, do not educate contextually.
To do that different thing, a layer above the CRM is needed, fed by data from the CRM and the portfolio management system, but adding an observational and proactive dimension. This layer, in practices that have adopted it, radically changes the relationship with clients beyond the threshold of one hundred.
The Ticino advisor cited at the opening describes the pre-layer situation well: the first thirty or forty clients, the ones he has known longest, receive the attention that remembers who they are. The other hundred receive the level of attention his physical time allows, which is lower.
With an operational-cognitive layer integrating portfolio data, relational history and active observation, the relationship changes in three concrete ways.
The first concerns unsolicited communications. If the system observes that a client has not been contacted for four months and his foreseeable personal situation (age, life event, phase of accumulation) suggests contact, it generates an alert for the advisor with a communication proposal already adapted to that client. The advisor reviews it, modifies it if necessary, sends it. Time dedicated: two minutes instead of twenty.
The second concerns the quality of replies to client communications. When a client writes with a question, the system prepares the reply with full context: client history, updated portfolio, recent conversations, preferred style. The advisor does not need to rebuild the context every time; he already receives a possible reply requiring only verification and final personalisation.
The third concerns silent clients. The system actively observes who has been silent too long, who has had portfolio changes without communicative accompaniment, who shows a pattern of interactions drifting from normal. These signals emerge, and the advisor can intervene before silence becomes abandonment.
What it takes to build it
The critical point is that this layer does not come off the shelf. It is built on the advisor's specific work. The knowledge sustaining the relationship must be made explicit and structured: which life events of the client generate targeted communications, what style this advisor uses (formal, informal, technical), what the categories of clients are and their typical needs, how escalations between advisor and client are handled when problems emerge.
This preliminary work requires some weeks of structured conversation with the advisor, and produces two distinct assets. The first is an operational map of the practice, useful also for any transfer of clients to new collaborators. The second is the knowledge base feeding the technology layer.
Only after this phase does it make sense to introduce automatic tools. Introducing them before produces the classic result: underused tools because they lack the context to generate value.
A different threshold for those who have structured
The advisor who has done this work does not operate with a threshold of one hundred and twenty clients. He operates with a much higher threshold, because the repeatable part of the relationship is handled by the system while the unique part remains human. Portfolios of two hundred or two hundred and fifty clients, impossible to manage well purely manually, become manageable with individual attention that is still perceived.
This is not an efficiency equation; it is a strategic difference. An advisor with a practice of one hundred and twenty clients, where each client receives attention perceived as unique, is a different business from an advisor with two hundred clients where the service is perceived as decent but generic. The second grows in volume and starts to look similar. The first builds a defensible, recommendable practice.
A side effect of this structuring is worth noting. When an advisor takes an extended break, or decides to hand over his practice to a successor, the handover is qualitatively different. The successor does not inherit a list of contacts and some notes; he inherits an operational map of how the relationship with each client category is sustained. Continuity, for clients who usually fear generational transitions, becomes credible.
If you recognise yourself in the Ticino advisor, with the feeling that beyond a certain threshold the quality of the relationship is no longer what it was, the step to take is not another CRM. It is to map the work that today sustains the relationship, understand which part can be structured and which remains human, and decide whether to build the cognitive layer that today is missing. It is done in a forty-five-minute conversation that remains useful even if you decide not to go ahead.