Excel or family office software: when the spreadsheet stops holding
Updated: 2026-09
In family offices the spreadsheet breaks not on arithmetic but at three points: versioning with several editors, access control over sensitive data, and evidencing work to an auditor. Until those three press, Excel is a legitimate choice.
Most boutique family offices work in spreadsheets, and that is not a failing. Excel is flexible, costs nothing extra, everyone can use it, and it adapts to any peculiarity of a structure without anyone having to request a product change.
So the spreadsheet does not fail where you would expect. It calculates reliably, it consolidates, it presents. It breaks elsewhere: as soon as several people edit the same file, as soon as different people may see different things, and as soon as somebody must evidence who changed what and when.
This comparison names the moment to switch by concrete signals rather than by asset thresholds.
| Criterion | Innopulse | Alternative |
|---|---|---|
| Flexibility on special cases | Structured: persons, companies, trusts, foundations as a data model. Special cases need modelling. | Unbeatable. Any peculiarity fits in a new column — that is the real strength. |
| Several editors | Concurrent work with roles and permissions; no competing file versions. | The first hard breaking point: competing versions, overwritten changes, "copy_final_v3". |
| Access control | Selective per mandate and per person; tenant isolation at the database layer. | Effectively all or nothing. Whoever has the file sees everything in it. |
| Evidence / audit trail | Continuous audit trail; who changed what and when is evidenceable. | Absent. For an audit or supervisory review, that is the critical point. |
| Deadlines and periodic controls | Due reviews surface per mandate rather than living in a separate list. | A separate deadline list somebody has to maintain — and which goes stale exactly when it matters. |
| UBO across jurisdictions | Assessed against the rules of the relevant jurisdiction, visible per mandate. | Manual research and manual upkeep; error-prone on cross-border structures. |
| Cost | Licence cost, in exchange for removing a substantial share of manual upkeep. | No direct licence cost — the cost sits in working hours and is therefore poorly visible. |
| Switching risk | A CSV export is enough; columns are mapped automatically, entities become mandates. | No switch needed — which is exactly why the move gets postponed so often. |
When an alternative is the better choice
If you run a single mandate with a simple structure and work on it alone, a well-kept spreadsheet is sufficient and the cheaper solution.
If your structure is so idiosyncratic that no standard product models it without contortion, the spreadsheet is for now more honest than a forced data model.
If there is no external duty to evidence and no third party needs access, two of the three reasons to switch are absent.
FAQ
How do I know the spreadsheet no longer holds?
Three signals: several people edit the same file, different people may see different things, or somebody asks for evidence of who changed what and when.
Is Excel unprofessional?
No. It is a powerful tool and entirely sufficient for many structures. The question is not professionalism but whether the three breaking points already press on you.
How much work is the move?
FLIORE names CSV as the path: export from the spreadsheet, automatic column mapping, entities become mandates. The effort sits less in the import than in tidying your own data beforehand.
What happens to our grown formulas?
Calculation logic is covered by the product; anything that must stay bespoke should be named before the move. That is the most honest checkpoint in any migration.
Can we move gradually?
Yes, usually one mandate first. That limits the risk and reveals which peculiarities of your structure still need modelling.
FLIORE
FLIORE is built precisely for the practices working in spreadsheets today — that is the explicit target, not a side case.
The move runs through CSV export with automatic column mapping; entities become mandates, holdings become assets. Most teams are running the same day.
The spreadsheet’s three breaking points — versioning, access, evidence — are the core of the product rather than a retrofitted extra.