Anyone selecting family office software routinely compares products that are not in the same category at all. A net-worth tracker and an institutional reporting platform solve entirely different problems, even though both carry wealth in their marketing.
This article sorts the categories and describes the opening question that precedes any product comparison. The wider context is in the guide to the family office operating system.
The wrong and the right opening question
The wrong question is: from what asset volume does software pay off? Volume is the wrong measure. A single large mandate with a simple structure can be easier to run than five small ones with nested vehicles across jurisdictions.
The right question is: where does the time actually go? If it is producing reports, a reporting and aggregation platform is the category. If it is finding documents, tracking deadlines and evidencing work, it is an operating system. That distinction organises the whole market.
The five categories
Net-worth trackers give a consolidated overview across a broad range of assets at a low barrier to entry. They are built for individual wealth owners and their advisers, not for mandate administration, KYC controls or invoicing.
Reporting and aggregation platforms automate data inflows from banks and custodians, cleanse them and produce reports. They cover reporting strongly; compliance operations must be solved elsewhere.
Enterprise suites offer deep analytics, extensive integrations and modelling of complex ownership. Implementation is project-based and operation presupposes resources — usually oversized for a boutique.
Operating systems start with mandates, beneficial owners, KYC with an audit trail, deadlines, documents and invoicing, and deliver consolidation on top. They demand structure before value appears.
And finally the spreadsheet, which remains a legitimate choice for very small structures.
Where spreadsheets break
The spreadsheet does not break on arithmetic. It breaks with several concurrent editors, with graduated access control, and with evidencing work to an auditor. Until those three points press, a well-kept spreadsheet is the cheaper solution.
That test is more concrete than any volume threshold: do several people edit the same file? May different people see different things? Does anybody require evidence of who changed what and when? Answer all three with no and you need no platform.
The criteria that count in operation
Beyond category, five points decide. First, the location of the data together with encryption, tenant isolation, the processing agreement and subprocessor transparency — with wealth, structure and personal data, regularly a knockout criterion.
Second, the hardness of tenant isolation: does it run in application logic alone or at the database layer? The difference shows when a filter is missing in application code. Third, the handling of AI: mandate-bound, cited, no training on client data — or unclear. Fourth, the migration path, because it decides whether adoption is realistic at all. Fifth, data quality: are missing FX rates, stale valuations and feed errors surfaced before they reach a report?
The most common selection mistake
Comparing products from different categories on feature lists selects the product with the longest list — not the right one. A long list signals category, not fit: enterprise suites naturally have the longest lists and are still usually the wrong choice for a boutique.
Categories can be combined
A common and sensible combination is an aggregation platform for data collection and an operating system for operations. What matters then is checking the interfaces, or you end up maintaining data twice — which costs more than the system you were trying to avoid.
A detailed comparison of the categories with their limits is at family office software compared; the special case of moving from spreadsheets is covered in Excel or family office software.