A family office realises it has outgrown its spreadsheets. Someone searches for family office software. Most of the pages that come back are published by companies that sell family office software, and each one closes by explaining why that company is the answer.
This is not a criticism of those companies. Several publish genuinely useful material, and vendors understand the operational problems better than almost anyone. But a buying guide written by a seller will emphasise the criteria on which that seller performs well. One guide will tell you that integration architecture determines everything. Another will tell you that the general ledger is the foundation and that investment reporting platforms are shallow. A third will tell you that usability decides adoption. All three are defensible. Read together they are not a framework. They are a set of sales positions.
The result is a buying process anchored on whichever vendor published the most persuasive material, rather than on the operating reality of the office doing the buying.
There is a second reason to be deliberate this year. The build versus buy question, which had been settled in favour of buying for most of the last decade, is genuinely open again. Falling development costs and AI assisted tooling have made it plausible for a small team to assemble something workable from components, and a number of offices are asking whether they should. The honest answer for most is still no, because the hard part of this problem was never the interface. It is custodian connectivity, private market data capture and the accounting treatment underneath, and none of those get cheaper because code does. But the question deserves a real answer rather than an assumption, and the requirements work below is what produces one. If you cannot write down your requirements clearly enough to evaluate a platform against them, you certainly cannot brief someone to build against them.
This guide sets out a process that starts with your office rather than with a product.
Step one: set your requirements before you look at any platform
Requirements first is the whole discipline. Everything downstream, the shortlist, the scoring, the negotiation, is only as good as the requirements you wrote at the start.
Describe the office
Write down seven facts. Do this before opening a single vendor website, because these seven determine which platforms are plausible and which would waste a demonstration slot.
- Legal entities. How many trusts, holding companies, partnerships, foundations and operating businesses need their own books? An office with three entities and an office with thirty-five are shopping in different markets.
- Asset classes, by weight. List every class and its approximate share of net worth. Include the awkward ones: direct real estate, operating company equity, private credit, art, aviation, digital assets.
- Currencies and jurisdictions. Your reporting currency, the currencies you hold, and the jurisdictions that impose statutory requirements on you.
- Custodians and banks. Count them and name them. This list is the most useful single artefact in the whole evaluation.
- Who needs to see what. Principals, next generation family members, the investment committee, external accountants, tax advisors. Note the different view each one needs.
- Reporting cadence. The monthly consolidated pack, quarterly investment committee papers, annual tax preparation, ad hoc questions from a principal. Note how long each takes you today.
- Headcount available for the project. Be honest. This is the constraint offices most often skip, and it is the one that most often explains a failed implementation.
Build the master requirements list
Turn those seven facts into a list of specific, testable requirements. Specific means a vendor can demonstrate it or fail to. Good reporting is not a requirement. Consolidated net worth across eleven entities in four currencies, with drill down to the underlying transaction, is a requirement.
Work through the four axes described later in this guide and write requirements under each. Expect between forty and eighty for a small office. Fewer than forty usually means the list is still written at the level of features rather than operations.
Sort every requirement into required or nice to have
This is the step that makes the rest of the process tractable, and it is the one most often skipped.
Required requirements are gates. A platform either meets them or it is out, regardless of how well it scores elsewhere. If you hold assets in four jurisdictions and a platform cannot handle multi-jurisdiction consolidation, no amount of elegance in the reporting layer redeems it. Gates are not weighted, because weighting implies a trade-off and there is no trade-off available. Keep this list short and genuinely absolute. If you find yourself with twenty-five required requirements, most of them are not required.
Nice to have requirements are weighted. Everything else gets a weight reflecting how much your office actually values it, and gets scored during the evaluation. This is where the judgement lives, and it is why two offices with similar portfolios can rationally reach different answers.
The practical effect is that gates do the filtering and weights do the deciding. Applied in that order, a market of dozens of platforms reduces to a handful without anyone having sat through a demonstration.
Step two: map the stack you already have
Software does not arrive into an empty room. Before evaluating anything, write down what the office already runs and who depends on it: the accounting package, document storage, the custodian portals people log into by hand, the CRM, the spreadsheets that quietly hold something important, and whatever the external accountant and tax advisor use at their end.
Three questions matter here, and none of them appear on a feature comparison.
What does the new platform replace, and what does it have to live alongside? A platform that replaces four tools is a different proposition from one that becomes a fifth. Be specific about which systems are retiring, because a migration that leaves the old system running has not finished.
Who outside the family office team is affected? External accountants, tax advisors and administrators have their own systems and their own habits. A platform that produces exports your accountant cannot use will generate work that lands somewhere, usually on the smallest team in the chain. Ask these people what they need before you shortlist, not after you sign.
What breaks if this changes? Every office has a process that depends on a particular file arriving in a particular format on a particular day. Find those before the evaluation rather than during the migration.
The output of this step is a short list of integration requirements, which go onto the master list and get sorted like everything else. Integration requirements are frequently gates, and offices tend to discover this late.
Why is evaluating family office software across asset classes so difficult?
Because asset class support is not binary, and vendors have no shared vocabulary for describing degrees of it.
When a platform says it supports private equity, it may mean any of the following:
- A field where you type a valuation and a date, and nothing calculates.
- Commitment and drawdown tracking, with internal rate of return calculated on cash flows you enter by hand.
- Automated capture of capital calls and distributions from manager notices, posted to the correct entity and partner.
- Full capital account accounting, including carried interest, management fee offsets and allocations across a partnership structure.
- All of the above, plus look-through exposure so that a fund's underlying holdings appear in your allocation analysis.
Five very different products, one sentence on the website. The same ambiguity applies to direct real estate, operating companies, structured products and digital assets.
Three further complications make this axis unusually hard.
Private market data arrives unstructured. Capital call notices and capital account statements come as PDFs and email attachments in whatever format each manager prefers. Any platform can display this data once it is in the system. The difference between platforms lies entirely in how much human effort is needed to get it there.
Illiquid assets break performance mathematics. A time weighted return is the right measure for a listed portfolio and the wrong measure for a fund with irregular capital calls. A platform that reports a single blended figure across both, without disclosing how it reconciled the two methodologies, is producing a number nobody should rely on.
Consolidation across classes is where the errors hide. Individually, most platforms handle each asset class adequately. The failures appear when one number has to combine a listed portfolio in dollars, a Luxembourg fund in euros, a jointly owned property held through two entities, and an operating company consolidated at 60% ownership. This is the calculation that matters most to a principal, and the one demonstrations are least likely to show you.
The practical test. Take the three most awkward holdings you own. Not the largest, the most awkward. Send the anonymised structures to each shortlisted vendor and ask them to model them and produce the resulting report. How they respond, how quickly, and how many caveats they attach will tell you more than any feature matrix.
Why do small family offices struggle to choose family office software?
Not primarily because the market is opaque, though it is. Small offices struggle for four structural reasons.
The evaluation methodology in circulation was designed for larger offices. The frameworks currently published on this subject describe sixty day proofs of concept, anonymised test datasets, third party security consultants and scoring committees with divergence review. That is sound advice for an office with a chief operating officer, a technology lead and an internal accountant. An office of three people, all of whom already have full jobs, cannot execute it. So the process either does not happen or it stalls, and the decision defaults to whichever demonstration was most recent.
Pricing models are built around a different customer. Across the market, platform pricing runs from roughly $2,000 to $20,000 per month, driven by the vendor, the pricing model and whatever add-on services are bundled in. The model matters more than the headline. Where pricing scales with assets under management, an office with modest assets and genuine structural complexity pays little for capability it needs entirely, which sounds like good fortune until the implementation and support model turns out to be calibrated to much larger accounts. Where pricing scales with entities, custodians, transactions or feeds, a small office with a complicated structure can pay considerably more than a large office with a simple one. Very few vendors publish anything at all, which is why the five year projection described later matters more here than in most software categories.
There is no internal reference point. A larger office has usually replaced a system before and knows what implementation actually costs in staff hours. A first time buyer has no such calibration, and vendors are not incentivised to supply it.
Complexity does not scale with size. This is the point most often missed. A single family office with $150 million across four jurisdictions, eleven entities, direct real estate and a portfolio of venture funds has harder requirements than a $2 billion office invested through three managers in listed markets. Small does not mean simple, and tools marketed as suitable for smaller offices are often built for the simple case rather than the small one.
How should a small family office shortlist family office software?
Compress the process rather than skipping it. A three person team can complete a defensible evaluation in six to eight weeks of focused effort by filtering early and testing narrowly. Elapsed time is usually longer, because vendor response times and diary constraints are not yours to control, and because a decision of this size will wait for a principal who is travelling.
Weeks 1 and 2: requirements and longlist. Complete steps one and two above. Then apply your required requirements as filters against a directory and reduce the market to eight to twelve plausible platforms. The next section describes how.
Week 3: written screening. Send every longlisted vendor the same one page document: your seven facts, your custodian list, your required requirements, and the eight questions below. Do not take demonstrations yet. Written answers are comparable, and the quality of a written answer to a hard question is a reliable signal. Expect this to remove half the longlist.
Week 4: reference conversations, early. Start these as soon as you are in live discussion with specific vendors, not at the end. Ask each remaining vendor for two references from offices of comparable size and structural complexity, not their largest or best known clients, and speak to those offices before the demonstrations rather than after. Three questions do most of the work: what did implementation actually cost in internal hours, what still requires vendor support a year later, and would you choose again. Doing this early changes what you look for in the demonstration, which is the entire point. Done at the end, it only confirms a decision you have already made.
Weeks 5 and 6: three demonstrations, each driven by you. Send each remaining vendor your three most awkward holdings in advance and ask them to demonstrate those, in the platform, with that data. Refuse the standard demonstration. If a vendor cannot show your structures, that is your answer.
Week 7: total cost. Ask each vendor for a five year projection in writing, including implementation, data migration, integration, training and contracted annual increases. Add your own team's hours at your own rate.
Week 8: score, decide, negotiate exit terms. Apply the weights you set in week one. Before signing, settle data export: format, completeness, timeline and cost on termination. Get it in the contract. This is the cheapest clause you will ever negotiate and the most expensive one to omit.
The discipline that makes this work is setting weights in week one, before any vendor has shown you anything. Weights chosen afterwards are simply a description of the demonstration you liked most.
Get a second opinion before you commit. Whether you run this process yourself or not, it is worth having someone outside the office look at your requirements list and your shortlist before you go to contract. An experienced reader will spot the requirement you have written too loosely to test, the gate you have set that will eliminate every viable vendor, and the platform you have shortlisted that no office of your shape has ever run successfully. It costs an hour. Book a call with the Simple team and we are happy to look at what you have put together and offer a steer.
How should a new family office pick software using a directory?
A directory answers one question well: what actually exists. It converts an unbounded search into a finite, filterable list, and it does so without a product to sell you. Use it in five steps.
1. Pick your category first, not your vendor. Simple's family office software directory sorts the market into five categories: reporting, accounting, investment, management and CRM. Decide which is your primary problem. Offices that skip this step end up comparing an accounting platform against a reporting platform and concluding, correctly but uselessly, that they are different.
2. Filter by capability tag, not by marketing language. Directory listings carry capability tags such as consolidated reporting, data aggregation, portfolio management, accounting, compliance, risk management and client portal. Tags are a blunt instrument, but they are consistent across vendors in a way that vendor websites are not. Apply your required requirements here: select the capabilities you cannot operate without and see who carries all of them.
3. Filter by region and jurisdiction. Directory entries show headquarters. This matters for data residency, for custodian coverage in your markets, and for whether support hours overlap with your working day. A platform based in Singapore and one based in Luxembourg have different custodian networks and different regulatory instincts.
4. Read across the listings rather than down. The value of a directory is comparative. Ten vendor websites read in sequence produce ten separate impressions. The same ten read side by side in a common format produce a market map, and the outliers become visible.
5. Cross reference against independent evaluation. Where a platform has been assessed independently, read that assessment before the vendor's own material. Simple's directory flags which platforms feature in the Family Office Software & Technology Report 2025. Independent evaluation will not tell you which platform is right for your office, but it will tell you which claims have been examined by someone with no commercial interest in the answer.
What a directory cannot do is choose for you. It gives you a defensible longlist and a common vocabulary. The four axes below are what you apply to it.
The four axes of comparison
Score every shortlisted platform on these four axes. The first is the one that most often causes an implementation to fail, and the ordering broadly reflects that. It is close to the reverse of the order in which these subjects come up in a sales conversation.
Axis 1: Asset class coverage, and the data pipeline underneath it
Can the platform hold, value, account for and report on everything you own, at the depth you need, from data it collects rather than data you retype?
These two questions have to be answered together, because coverage without accurate automated capture is a filing cabinet. Simple's 2025 research found integration and data quality displacing visual reporting at the top of family offices' stated priorities, and this axis is where that finding lands.
Test by structure, not by asset class name. Bring your capital call, your jointly held property, your operating company at partial ownership. Ask how each is captured, how much of the capture is automated, which of your named custodians are supported by automated feed rather than file import, and which performance methodology is applied.
Axis 2: Workflow fit
Does the platform match how your team already works, and how many steps does a routine task take?
The relevant question is not whether a task is possible but how many clicks and how much re-entry it requires. Time three real tasks during the demonstration: adding a new holding, recording a capital call, producing the monthly pack. A platform that adds steps to a daily task will be quietly abandoned in favour of a spreadsheet, whatever the contract says.
Axis 3: Governance and control
Who can see what, who approved what, and can you prove it later?
Ask for role based permissions demonstrated at the level you need, which for family offices usually means entity level and sometimes document level rather than module level. Ask to see the audit trail for a valuation that was changed. Ask where data is hosted, which certifications the vendor holds and when they were last renewed, and what the breach notification commitment is in writing. For a family office, governance is not a compliance formality. It is the mechanism by which a principal, an in-law and an external accountant can all use one system without seeing each other's business.
Axis 4: Reporting complexity
Can the platform produce the specific reports your specific audiences need, without a vendor services engagement each time?
There are two questions here, and offices usually ask only the first. First, can it produce the report. Second, can your team produce the report next quarter without calling the vendor. Ask to see a report built from scratch during the demonstration. Ask what a new custom report costs after go live, in money and in turnaround time. Then ask whether every consolidated figure can be drilled down to the underlying transaction, because a number a principal cannot interrogate is a number that will be questioned.
Weighting your requirements
Weights express how much your office values each thing. Nobody can set them for you, which is the point: two offices with similar portfolios and different priorities should end up with different weights and, quite reasonably, different answers. What matters is that you set them in week one and write them down.
The starting points below reflect a typical small office. Treat them as a first draft to argue with, not a recommendation to accept. If a criterion matters more to your office than to the average, raise it and take the points from somewhere you care about less. The total has to stay at 100.
Remember that your required requirements are not in this table. Those already removed vendors at the filtering stage. What you are weighting here is everything that remains negotiable.
| Criterion | Axis | Starting weight | What you are scoring |
|---|---|---|---|
| Asset class coverage and depth | 1 | 25% | Modelled your three awkward holdings correctly, with the right performance methodology |
| Data aggregation and quality | 1 | 20% | Named custodian coverage, automated capture, validation and exception flagging |
| Workflow fit and usability | 2 | 15% | Click count on three timed routine tasks, and re-entry required |
| Reporting flexibility | 4 | 12% | Self service report building, drill down to transaction, multi audience views |
| Governance, security and control | 3 | 12% | Entity level permissions, audit trail, certifications, data residency |
| Integration and data portability | 3 | 8% | Documented open APIs, connections to the systems you are keeping, contracted export terms |
| Total cost of ownership, five year | - | 5% | All in cost including implementation, migration, training and increases |
| Vendor stability and fit | - | 3% | Ownership, funding position, and whether offices your size are a real segment |
The first two criteria both sit under axis one, because coverage and the data pipeline that feeds it fail together. Integration appears twice by design: its operational half is scored inside data aggregation, and the 8% line covers portability and exit specifically, which is a separate question and the one offices forget to ask.
Two adjustments are worth considering, and they reinforce each other.
If more than a third of your net worth sits in private markets, move five points to asset class coverage, taking three from reporting flexibility and two from integration and portability.
If your office is genuinely three people or fewer, move five points to workflow fit, taking three from reporting flexibility and two from cost and vendor stability. In a small team adoption is the binding constraint, and an elegant report nobody produces is worth nothing.
If both apply, which for a small office with private market exposure is the common case, the resulting profile is asset class coverage 30%, data aggregation 20%, workflow fit 20%, governance 12%, reporting flexibility 6%, integration and portability 6%, cost 4%, vendor stability 2%. Reporting flexibility falling that far is deliberate. An office of three with a complicated portfolio needs correct numbers and a system its people will actually open, and can live with a plainer report for a year.
Score each shortlisted platform from one to five per criterion, multiply by the weight, and total. The number will not make the decision for you. Its value is in exposing where two platforms you feel differently about actually differ, and in giving a principal something to review that is not a preference. If the top two land within a quarter point of each other, the scores are not separating them, and you should decide on the quality of the implementation team and what the references told you.
A worksheet version of this, with the requirements gating, live formulas, the question bank and a five year cost model built in, accompanies this guide.
The vendor question bank
Eight questions for the written screening in week three. Written answers, from every longlisted vendor, to identical questions.
- Of the custodians and banks on the attached list, which do you support through automated feeds today, which through file import, and which not at all?
- Describe precisely how a capital call notice from a private fund becomes a posted transaction in your system. Name every step that requires a human.
- Which performance methodology do you apply to illiquid holdings, and how is a blended figure across liquid and illiquid assets calculated and disclosed?
- Can permissions be set at entity level and at document level? Demonstrate with a scenario in which a family member sees only their own holdings.
- Which of the systems on the attached stack list do you integrate with today, and what does an integration cost where one does not exist?
- What does a new custom report cost after go live, in fee and in turnaround time, and can our team build one without you?
- Provide a five year all in cost projection for an office of our profile, including implementation, data migration, integration, training and contracted annual increases.
- On termination, in what format, how completely, within what timeframe and at what cost is our data returned? Is this in your standard contract?
Then a further set for the three shortlisted vendors, in the demonstration.
- Show us our three awkward holdings, modelled, with the resulting report.
- Show us a report built from nothing, now.
- Show us the audit trail for a valuation that was changed.
- Show us what happens when a data feed fails or a required field is missing.
- Tell us who performs the implementation, how many implementations that team completed last year, and who our named contact is after go live.
The last question in each set is the one vendors answer least comfortably and the one that predicts the most.
What this costs, properly counted
The licence fee is the smallest number in the decision. A five year total for a family office platform includes the annual licence, implementation configuration, data migration from legacy systems and spreadsheets, integration development, staff training, a period of parallel running, and contracted annual increases.
Two of these are routinely omitted from budgets and routinely dominate the overrun. Integration development is the first, particularly where a vendor restricts API access to its own professional services team, which converts an engineering task into a billable engagement at the vendor's rate. Parallel running is the second: operating the old and new systems simultaneously and reconciling them daily, for which the conventional guidance is two to three months. It is the only reliable way to discover that a migrated number is wrong, and it is entirely a cost in your team's hours rather than the vendor's invoice.
Ask for the five year projection in writing during screening. A vendor unwilling to produce one is telling you something.
The accompanying worksheet computes this total from your own figures, including your team's hours at your own blended rate, and expresses it as a multiple of the year one licence fee. That multiple is the number to take to a principal.
Five mistakes to avoid
Treating every requirement as equally binding. Gates filter, weights decide. An office that weights everything ends up with a shortlist full of platforms that cannot do something it actually needs.
Comparing platforms from different categories. An accounting core and a reporting layer are not competitors. Decide which problem you are solving first.
Letting demonstrations set the criteria. Demonstrations use clean data and ideal cases. Set your weights before the first one.
Treating small as simple. Structural complexity is independent of assets under management. Buy for your structure, not your size.
Signing without exit terms. Negotiate data export format, completeness, timeline and cost before signature, when you still have leverage.
Where to start
Begin with the market, not with a vendor.
The Simple family office software directory lists vetted platforms with capability tags, headquarters and, where available, independent evaluation. This is where the longlist comes from.
The Family Office Software & Technology Report 2025 covers where the market is moving on integration, data quality and AI, and which platforms have been assessed independently. Read it before the vendor material.
Category guides. If the primary problem is entity accounting rather than investment reporting, start with family office accounting software. If it is investment reporting and analytics, start with portfolio management software for family offices.
Simple Select runs this process for offices that would rather not run it themselves: requirements definition, matching against vetted vendor data, a tailored shortlist, and support through evaluation and negotiation. In fairness to the argument this guide opens with, Simple has a commercial interest in that service. What Simple does not have is a platform in the directory, which is the conflict that actually distorts a software recommendation.
And if you are running the process yourself, book a call and let us look over your requirements list and shortlist before you commit. A second set of eyes on an hour's call is cheap insurance against a five year contract.
About this guide
Market data in this guide is drawn from Simple's Family Office Software & Technology Report 2025, based on 40 vendor surveys and data from more than 11,000 platform users, and from Simple's ongoing vetting of the vendors listed in the software directory. Implementation and parallel running durations reflect conventional practice as stated by vendors rather than measured outcomes. Simple does not accept payment for rankings or inclusion in this guide.