VerdeWealth

The Method Was Always the Asset

Software was the hard part.
It was standing in front of something harder.

In July 2026, one of India's larger independent wealth managers in Mumbai, with nearly $1 billion under management, sent us the files behind their performance reporting. We wanted to know whether their calculations could be reproduced from the files that were supposed to explain them. They sent a workbook of index data, a sample report, a goal-planning model, a client proposal, and a text file they described as a prompt.

It was not a prompt. It was nine numbered decisions with their reasons, written to be executed rather than read, built by the firm's own lead analyst with a frontier model and a text editor.

Five of the nine exist only to cope with market data that turns up late, partial, or under the wrong name. These are one analyst's rules for one reporting workflow. What matters is that it runs, and that the firm sends its output to clients.

Then we checked it against the source data, which is when it got interesting.

The report ends with a total row saying the figures are weighted by amount. Two of the three legs are. The third uses aggregate amounts instead, overstating the return by about eight percentage points. The same error flows through to the reported outperformance.

Elsewhere a benchmark is labelled as one index and priced with another. Several schemes are benchmarked against weighted composites whose gold and silver legs are dollar spot prices, so an Indian gold fund's return carries a currency move its benchmark does not.

10 of 19 rows could not be reproduced from the supplied data.

This is not the kind of failure deterministic software catches.

The arithmetic sits in a script and is deterministic; it will return the same number twice. The definition sits in prose, in a file, and prose does not run. Nothing was ever comparing the script with the file, so nobody inside the firm had occasion to notice the two disagreed. It is the structural gap double-entry bookkeeping exists to close.

The same firm's retirement planning has the same shape. Their spreadsheet uses a five per cent assumption here and six per cent elsewhere, with no clear statement of whether the five is real or nominal. On one household, that assumption more than doubles the required retirement corpus. The issue is not the assumption itself; it is that the decision is embedded in the spreadsheet without being made explicit.

You might say this is a feature of a fast-growing market with thin controls, and that a supervised European wealth firm has formal review and control processes to catch it. The opposite holds, and it gets worse as the firms get smaller. The median Swiss independent asset manager runs on 3.3 staff and 68clients. There is no second person to check the total row and no research desk to send the data request to. The method is one partner's spreadsheet and his memory of why it was built that way.

That firm sent us files covering one reporting workflow and one planning model. The index mismatches are the easy fixes. The harder question is what sits underneath the rest of the firm.

But the more interesting question is what happens when software becomes cheap enough to make and discard.

And when applications become cheap to make, personalisation becomes cheap with them. A client no longer needs the same portal as every other client. Their software can organise itself around their goals, holdings and decisions. An adviser can see the same client through upcoming maturities, shortfalls and conversations that need to happen. A research analyst can see something different again. The application can fit the person and the job rather than forcing both into the same app.

But the logic underneath those views cannot change with each one. What counts as the cost basis. Which index a fund is measured against. Whether five per cent means real or nominal. When a goal is off track. What can be said to which client, when the software must refuse, and what gets recorded afterwards. Those are not interface choices. They are the firm's way of deciding.

Every adviser works from it. Every client receives its consequences. A regulator can ask about it years after the person who wrote it has gone.

That is the firm's method. Writing it down was not the hard part; the analyst had already done that. The hard part is making it the firm's method rather than one analyst's implementation: something the firm can approve, preserve, and make every personalised application answer to.

The more personalised the software becomes, the more valuable the firm's method becomes.

The existing platforms were built for the opposite economics. Software was expensive, so one application had to serve thousands of firms. The dashboard could be branded. The reports could be configured. The workflow could be customised. But the application remained the common thing, and the firm adapted its practice to it.

Direct platforms remove the adviser. Adviser platforms give thousands of advisers progressively better versions of the same software. Both are now adding generated interfaces and governed AI. But the common thing is still the vendor's application and the shape it expects the firm's method to take. The firm varies inside it. Neither is built to make the software personal while preserving what makes one firm different from another.

Cheap generation breaks that model.

The application no longer has to be the common thing.

It can vary by firm, by role and by client.

When something that used to be hard becomes cheap, competition moves to what it was standing in front of. Quartz made accuracy cheap, and accuracy had been the industry's whole claim. In 1972 Audemars Piguet launched the Royal Oak at 3,300 francs, a steel watch priced above a gold Patek. Paul Graham calls what followed the brand age. In wealth management, software was standing in front of the firm's method.

The method was always the asset.

It has only just become separable, and therefore ownable.

That is what VerdeWealth is built for: applications that fit the firm, the adviser and the client, each answering to the firm's method.

Make the Method Scale →