An inherited portfolio arrives with a retention decision attached. Treat the handover as the product moment it is, and design for the window in which that decision gets made.
The Capgemini World Wealth Report 2025 records that 81% of next-generation high-net-worth individuals expect to switch wealth managers within one to two years of inheritance. That figure describes stated intent rather than completed moves, but it locates the risk precisely: the relationship that held the parent is not the relationship that holds the heir.
The inheriting client is a different user
The prior generation optimised for preservation and trusted institutional expertise delivered through a named individual. The inheriting client expects growth, access and alignment with stated values, and expects to see all three without booking a meeting.
That is a change in interface expectations before it is a change in product. Portfolio composition, mandate and fees can stay identical and still fail if the heir cannot read them unaided.
Segment on behaviour rather than age. What matters operationally is whether a client will self-serve, how much explanation they want attached to a number, and whether they will act on a recommendation they did not ask for.
Design the first ninety days
The switching window opens at transfer and closes within about two years. Map what the heir actually encounters in the first weeks: documents to sign, an unfamiliar portal, a relationship manager they did not choose, and positions they did not select.
Identity, mandate and access, with nothing left pending on the client’s side.
What they now own, in their language, without a meeting.
One reversible action they can complete unaided.
Evidence the action did what the interface said it would.
Instrument each step. Drop-off here predicts a switch better than any satisfaction score.
Four stages of an inheritance handover: transfer, orientation, a first reversible decision, and confirmation.Give the heir one decision they can complete alone and reverse. Confidence is built by a completed action with a visible result, not by an onboarding tour.
Augment the relationship manager, do not replace them
Digital-first does not mean unattended. The relationship manager holds context no interface has: family structure, prior commitments, and what was promised verbally and by whom.
Decide which tasks the client may complete without the manager, which require the manager to act, and which the manager may not override. Put that boundary in the product rather than in guidance.
Then give the manager the same view the client sees. Most trust failures at handover are not disagreements about strategy; they are two parties reading different numbers.
Make values-alignment auditable
Stated preferences around ESG and alternative assets are now part of the mandate conversation rather than a reporting appendix. If the platform accepts a preference, it has to be able to show where that preference changed a holding.
The client sets a preference somewhere they can find again.
The preference reaches the allocation logic, not just the CRM.
The portfolio view shows what it excluded or included, and why.
Where it cannot be honoured, the interface says so before submission.
A preference the system cannot evidence is a liability, not a feature.
Four requirements for a values preference control: stated, applied, evidenced and bounded.The fourth is the one most often skipped. Declining a preference clearly costs less than appearing to accept one you cannot act on.
Measure retention, not satisfaction
Set the success measure at account level and inside the switching window: assets retained twelve and twenty-four months after transfer, unaided task completion, and the share of decisions the heir initiates.
Agree those thresholds before the redesign starts. Loyalty is an outcome of the handover experience, and it is measurable on the same calendar as the risk.
Written by the studio, from work in delivery
