The family office software market has expanded significantly in recent years. There are more platforms, more feature sets, and more vendors claiming to solve the same problems than at any previous point. For a family office beginning or revisiting an evaluation, the volume of options available is not the difficult part. The difficult part is knowing which questions to ask, which answers to take seriously, and which capabilities to prioritise over which others.
A structured evaluation framework protects against two common failure modes: choosing a platform based on the quality of its demonstration rather than the quality of its data infrastructure, and prioritising breadth of features over depth in the areas that matter most. Both lead to the same outcome: a platform that looks right in a sales process and underdelivers in daily use.
This framework covers the seven areas that determine whether a family office platform will genuinely serve the office's needs over the long term.
1. Data infrastructure: the foundation everything else depends on
The single most important factor in any family office software evaluation is the quality of the underlying data infrastructure. Every output the platform produces, its reports, its analytics, its risk monitoring, and its AI-generated responses, is only as reliable as the data it is built on. A platform with an impressive reporting interface sitting on weak data infrastructure will produce impressive demonstrations and unreliable daily results.
The questions to ask are specific. How does the platform receive data from custodians, banks, and administrators? Direct SFTP feeds from institutions are the appropriate standard: structured, validated, and delivered automatically without manual intervention. Web scraping tools that extract data from banking portals produce lower-quality, less reliable data and should not be confused with genuine custodian connectivity. How many direct institutional connections does the platform maintain, and how are gaps handled for sources outside that network?
How does the normalisation process work? Data from different institutions arrives in different formats, with different conventions for naming assets, categorising transactions, and expressing valuations. A robust normalisation layer standardises all incoming data into a consistent format before it is stored. Without this, the consolidated view the platform presents reflects the inconsistencies of the underlying sources rather than a coherent picture of the portfolio.
How are data quality exceptions handled? Automated exception detection, which surfaces anomalies before they reach reporting and analytics, is the mechanism that separates a platform with genuine data integrity from one that passes problems downstream. The team should be reviewing exceptions, not reviewing every transaction.
For a detailed look at how data aggregation works in a family office context and what to look for in the infrastructure layer, that piece covers the full picture.
2. Alternative investment coverage: the hardest part of the problem
For family offices with significant allocations to private equity, real estate, hedge funds, and direct investments, the platform's ability to handle alternative investment data is as important as its handling of listed assets. Many platforms perform well on listed asset data and fall short on alternatives.
The specific questions to ask: how does the platform handle capital account statements, NAV letters, and LP reports that arrive in PDF and Excel formats from fund managers and administrators? Manual extraction is not an adequate answer at any meaningful scale. AI-powered document parsing that automatically reads, interprets, and validates data from unstructured alternative investment documents is the current standard for serious platforms.
Can the platform track capital call schedules and forward-looking cash flow commitments across all active fund positions? For an office with multiple private equity commitments, this is a practical necessity rather than a nice-to-have. Does the platform support look-through reporting that can see through fund structures to underlying holdings for exposure analysis? Without this, the consolidated exposure picture is incomplete for any portfolio with significant fund allocations.
3. Analytics depth: what institutional-grade actually means
Analytics capability varies more widely between platforms than almost any other dimension, and the demonstrations vendors provide tend to show the most visually compelling outputs rather than the most analytically rigorous ones. The questions that reveal the real depth of the analytics layer are specific.
For performance measurement: does the platform calculate both time-weighted and money-weighted returns across the complete portfolio? Can benchmark comparisons be configured to reflect the office's specific investment mandate rather than a generic default? Can performance be broken down by asset class, geography, currency, manager, and legal entity simultaneously? Is profit and loss analysis, including the separation of local return from currency effect, available at position level?
For risk analytics: does the platform support Value at Risk calculations, scenario analysis, and stress testing across the complete portfolio including alternatives? Can factor exposures be identified across both listed and private assets within a common analytical framework?
For exposure analysis: can the platform produce a consolidated exposure view across all custodians, asset classes, and legal structures simultaneously? Does look-through capability extend exposure analysis into the underlying holdings of fund positions?
A platform that can answer all of these questions affirmatively, with evidence from comparable client portfolios, has invested seriously in analytical depth. One that redirects toward visualisation quality or report design before addressing these questions has its priorities in the wrong order. For a fuller treatment of what institutional-grade analytics means in practice, that piece sets out the full standard.
4. Reporting capability: the difference between flexible and genuinely configurable
Reporting flexibility is claimed by every platform in the market and delivered well by relatively few. The distinction that matters is between platforms that offer a library of pre-built report templates and platforms that are genuinely configurable around the specific way the family holds and thinks about their wealth.
A template library is adequate for standard reporting requirements. For a family office with complex ownership structures, specific preferences for how different asset classes are presented, and multiple family members with different levels of interest and financial sophistication, a template library will require workarounds that accumulate into a manual process over time.
The questions to ask: can reports be configured to reflect the family's specific ownership structures and entity hierarchy rather than a generic default? Can different versions of a report be produced automatically for different audiences, such as a summary for a family principal and a detailed version for the investment team? Can reports be scheduled for automated delivery without manual intervention? How long does it take to build a new report template, and does it require technical expertise or can it be done by the reporting team directly?
5. Security and data architecture: the standard the SFO context requires
For a family office evaluating any platform that will hold the complete financial picture of a single family, the security architecture of that platform is not a secondary consideration. The questions to ask go beyond general security assurances.
Is the office's data held in a physically isolated environment that is architecturally separate from any other organisation's data, or in shared infrastructure with logical separation between clients? Physical isolation is the appropriate standard for information of this sensitivity. Logical separation within a shared system is not equivalent. For a full explanation of what physical data isolation means and why it matters, that piece covers the distinction in detail.
Does the platform hold current ISO 27001 certification and SOC II compliance, with independent audit evidence the office can review? How are user permissions managed within the platform, and specifically, does the AI agent, if one exists, respect those permissions and query only data the user is authorised to access?
6. AI capability: what to look for and what to push back on
AI is now a meaningful part of the evaluation for any family office platform, but the claims made in this area require careful scrutiny. The questions that reveal the substance behind the marketing are direct.
Does the platform have a live AI agent that can query the office's own portfolio data, or does it have a roadmap for one? The difference between a live capability and a planned one is significant for an office making a decision now. How does the AI agent access the portfolio data, and is that access governed by the same user permissions that apply to the rest of the platform? An AI agent that can surface information beyond a user's authorised scope is not a well-governed system.
What is the AI agent actually capable of answering? Performance questions, exposure queries, and portfolio summaries drawn from the live data environment are the appropriate scope for a well-built agent at this stage of the technology. Claims of strategic investment advice or predictive market analysis should be treated with scepticism. For a clear explanation of what an AI agent is and how it differs from a chatbot, the AI sceptic piece addresses the distinction directly.
7. Implementation, support, and the vendor relationship
The quality of the implementation process and the ongoing vendor relationship matters as much as the platform itself, particularly for a family office with complex and specific requirements. A platform that takes twelve months to implement fully, requires significant internal resource, and provides limited support for customisation is not delivering its stated capability for the first year of the relationship.
The questions to ask: what does a typical implementation timeline look like for an office with comparable complexity and asset class coverage? What resource is required from the office's team during implementation? How are custom requirements, specific reports, data sources outside the standard network, or particular analytical configurations handled? And what does ongoing support look like once the platform is live?
References from comparable clients are the most reliable input to this part of the evaluation. An office that has been live on the platform for two years, with a portfolio of similar complexity, will provide a more accurate picture of the day-to-day reality than any demonstration or sales conversation.
The evaluation question that matters most
A family office that has asked and received clear, evidence-backed answers to all seven of these areas has done the evaluation well. The platform that emerges from that process will be the right one not because it had the most impressive demonstration, but because it was built for the specific complexity, the security requirements, and the analytical depth that the family office context genuinely requires.
For offices beginning the evaluation process, Sesame One for family offices provides a starting point for understanding what a purpose-built platform covers across all seven dimensions.
