Guide · 10/20/2026
Family Office Technology With an Independent Partner
Family office technology with an independent partner: requirements first, vendor selection with no referral fees, implementation oversight and a monthly close.
By Pedro Souto
Family office technology is usually bought before it is designed. A family with €20–150M, four banks and a dozen entities decides it needs a platform, and everyone offering to help is paid by someone: the vendor by its licence, the certified partner by the vendor, the bank by keeping the assets, the consultant perhaps by a referral fee. Unless the family pays an independent partner itself, nobody in the chain works for it. This guide is for that family. Its conclusion: separate the roles, and get every party’s payments in writing.
PWA does not sell, resell or build software, and takes no referral fees from vendors or banks: it is paid by the family, and only by the family. PWA does not manage money, hold mandates, take commissions or give regulated investment, tax or legal advice.
How do we design, implement and operate a family office technology platform with an independent partner who does not sell software?
Separate the roles. The family owns the requirements, the data model, the vendor contract and every administrator credential. An independent partner, paid only by the family, writes the requirements, runs the selection, holds the vendor to acceptance tests and reviews the monthly close. The vendor implements its own platform.
| Stage | What the family owns | What the partner does | What the vendor does |
|---|---|---|---|
| Design | The signed requirements document and the data model | Writes both with the family’s staff, before any demo | Nothing yet |
| Select | The decision, the contract in its own name, direct payment to the vendor | Runs the request for proposal, scripted demos, references and disclosure letters | Answers the request, demonstrates on the family’s own sample month, quotes one annual total |
| Implement | Administrator credentials and the final sign-off | Owns the acceptance tests and the issues log | Configures, connects bank feeds, loads history, trains users |
| Operate | The data, the close sign-off, the annual export | Reviews the monthly close, access and the annual provider and fee review | Runs and maintains the platform, fixes feeds |
In practice the roles blur within weeks: the consultant who ran the selection becomes the implementer, the implementer keeps the administrator password, and the person reconciling the data is paid by the vendor whose system it checks. The family ends up owning a system it cannot check and cannot leave.
Who is paid by whom in family office technology
Adoption is rising, so more parties earn from the sale. Two recent surveys show the direction.
69%
of family offices have adopted automated investment reporting systems, up from 46% a year earlier
RBC Wealth Management and Campden Wealth, North America Family Office Report 2025, release of 16 October 2025
44%
of US family offices face technology challenges
Merrill and Bank of America Private Bank, 2025 Family Office Study, 335 US decision-makers, fielded May–June 2025
Both are US-weighted. The RBC and Campden release covers 317 offices worldwide, 141 in North America, and does not say which base the 69% uses.
Six parties behind family office technology solutions
Every one of these parties can do good work. The question is who pays each, and what that payment rewards.
| Party | Who pays them | What they are good at | Where the conflict sits |
|---|---|---|---|
| Software vendor | The family: licence or subscription, plus the vendor’s own implementation fees | Knows its product in depth; controls the roadmap and the fixes | Recommends its own product; its implementation team knows one platform |
| Reseller or certified implementation partner | The vendor (margin, partner discount or revenue share) and the family (service fees) | Fast configuration on the one or two platforms it is certified on | Its income depends on the family choosing a platform it resells or implements |
| Consultant, accountant or law firm with a referral agreement or alliance | The family for its advice; the vendor for introductions, where a programme exists | Knows the family, its entities and its history | A referral fee is paid by the vendor and depends on which vendor is chosen |
| Private bank portal or bank-run aggregation | The bank, through the relationship and the assets it holds | Accurate, timely data on what the bank itself holds | Built around the bank’s own book; the data and access stay with the bank |
| Administrator or multi-family office with its own platform | The family, through administration fees that include the platform | One provider for accounting, administration and reporting | The platform comes with the service; leaving one means leaving the other |
| Independent partner | The family only, at a fixed fee | Requirements, selection, acceptance tests, review of the close | Knows less about any one product than the vendor; has a reason to stay engaged |
The last row is not free of incentives either: an independent partner has a reason to stay engaged. The remedy is a fixed scope, a fixed fee and a written end point for each stage.
Software referral fees: a published example
Referral programmes are legal, common and, in the better cases, published. Asora, a family office software vendor, pays “20% of first-year subscription revenue”, calculated on the net software subscription revenue Asora receives from the customer in the first year, with taxes and implementation, setup or service fees excluded. It is aimed at “accountants, lawyers, and advisors with family office relationships”, with “no tiers and no hidden conditions.” That is a clear, disclosed programme, but the disclosure sits on the vendor’s website, while the family hears the recommendation in a meeting. The remedy is the disclosure letter below.
Research sits in the same economy. KPMG and The Table Club’s 2025 report on technology in Australian family offices was co-sponsored by Eton Solutions, a family office software vendor, according to Eton’s own page. It can be useful; read it knowing who paid for it.
Regulation does not do this work for the family either. The EU inducement rules under MiFID II are written for investment firms and the investment services they provide; a family should not assume any rule of that kind obliges a technology consultant to disclose a vendor fee. Ask in writing. The same discipline for financial advisors is set out in how to check if a financial advisor is independent. None of this is legal advice.
Design: requirements and a data model before any demo
A demo on clean sample data makes the family compare screens instead of fit. So the requirements come first: the partner drafts them and the family signs them before any demo. Deloitte Private makes the same point: “Even if a third-party consulting firm is engaged, the family office staff must play an active role in software requirements and design, as well as testing.” No outsider knows which entity owns the Lisbon flat.
The requirements document runs to a handful of pages:
- Entity register. Every company, trust, foundation and holding company, with ownership percentages and control.
- Accounts and custodians. Every bank and custodian (the bank or regulated firm that holds the securities and cash in safekeeping), every account, its currency and the data it can send.
- Asset classes. Listed securities, cash, private markets (capital calls, distributions and the lag before a net asset value, or NAV, arrives) and property.
- Valuation policy. Who values unlisted assets, how often, from which source, and what happens when a value is stale.
- Reporting currency and look-through. One currency; holdings shown through each entity or only at the top.
- Users and access roles. What the founder, the next generation, the staff and outside advisors each see.
- Report set and frequency. The few reports the family actually reads, and who receives them.
Family office data management starts with the data model
The data model is the second document: how entities, accounts, positions and transactions relate, and which identifiers tie them together. The family keeps it whichever software it chooses, so a later change of platform is a migration, not a rebuild (the argument is in build vs buy family office reporting). Good family office data management is mostly one entity register, one list of accounts and one owner for each manual value. Consolidated reporting, one regular report of everything the family owns valued on one date and basis, is only as good as those three lists.
Selection with no reseller margin
With the requirements signed, selection becomes a test rather than a sales process:
- Long list. Six to ten platforms that serve families of this complexity in this region. For criteria and a vendor comparison, see family office software; this guide ranks none.
- Request for proposal on the family’s requirements. Every vendor answers the same document, line by line: supported, supported with configuration, supported with development, not supported.
- Scripted demo on the family’s own sample month. Two or three shortlisted vendors receive an anonymised month of real statements (a messy bank feed, a capital call, a property revaluation, a currency the family does not report in) and show that month, not their sample data.
- References. Two families of similar complexity, from the vendor’s list but asked the partner’s questions: how long go-live took, what broke, who maintains the data now.
- One annual total in euros, and a direct contract. Licence, implementation, feeds, support and any managed service as one yearly figure for years one and two. The contract is in the family’s name, paid directly to the vendor, with no mark-up through anyone.
What an independent technology consultant does in a selection
An independent technology consultant writes the documents, runs the meetings, scores the answers against the requirements and puts the comparison in front of the family. It does not choose. The family chooses, with every party’s payments on the table.
The disclosure letter
Before the shortlist, every party in the selection signs a short letter: each vendor, the partner and any advisor whose opinion the family will hear. It can be this plain.
Please confirm in writing, for your firm and for anyone working on this engagement:
- Every payment or benefit received in the last three years from any software vendor, bank or platform provider that could be part of this selection: referral fees, partner discounts, revenue share, resale margin, sponsorship, paid events or travel.
- Whether you are a reseller, certified implementation partner or member of any partner or referral programme, and for which vendors.
- Whether any fee you charge us, or any payment you receive from anyone, depends on which vendor we choose.
- That you will tell us in writing if any of the above changes before the contract is signed.
A “yes” to any line does not disqualify anyone. It tells the family how to weigh what that party says.
Family office software implementation: what to hold the vendor to
The vendor configures the platform, connects the bank feeds and loads the history: it knows its product and should do the work. The partner owns the acceptance tests and the issues log. The family holds every administrator credential from day one and signs the final acceptance. Two rules save most of the trouble: price every change request before work starts, and send the issues log to the family weekly.
| Test | Pass criterion | Who signs |
|---|---|---|
| Go-live month reconciliation | Every account’s positions and cash match the custodian statement at month-end; any difference explained in writing | Family, after partner review |
| Entity tree and ownership | Every entity and ownership percentage matches the entity register signed at design | Family |
| History | Transactions and valuations loaded to the agreed start date; performance for a sample period recalculated and matched | Partner, then family |
| Private markets and property | Each position entered with its source document (capital account statement, valuation report) and the valuation date shown | Partner |
| Access roles | Each user sees only what the access matrix allows, tested by logging in as each role | Family |
| Parallel run | One or two month-ends produced in both the old and the new set-up, with differences explained | Family, after partner review |
Duration depends on entities, banks, private-markets and property positions, and how clean the history is. Masttro, for example, states a time to go live of “typically 12 to 14 weeks, with dedicated onboarding team”. That is the vendor’s estimate for the vendor’s work; the family’s own work (entity register, source documents, decisions on history) usually sets the real date.
Operating it: who maintains the data, the monthly close and the controls
Go-live is the start of the work. Asked about operational risks, family offices in the RBC and Campden survey most often cited manual processes and over-reliance on spreadsheets; a platform removes some of that, not the need to check the numbers every month. The first decision is who maintains the data: family office staff, the vendor’s managed-service team or an outsourced administrator. Any can work, if the role is named in writing and separated from the role that checks it.
| Task | Family | Data maintainer | Independent partner | Vendor |
|---|---|---|---|---|
| Feed breaks | Informed | Investigates, raises with bank or vendor | Reviews the log monthly | Fixes the connector |
| Manual entries (property, private markets) | Supplies source documents | Enters, with a second person checking | Samples against source | None |
| Monthly reconciliation | None | Reconciles every account to the custodian statement | Reviews | Supports on feed issues |
| Close sign-off | Signs | Prepares the close pack | Reviews before sign-off | Never |
| Mapping changes (new account, entity or asset) | Approves | Requests and records in the change log | Reviews the log | Configures |
| Quarterly access review | Approves the user list | Prepares it | Checks leavers and roles | Applies changes |
| Annual export test | Owns the result | Runs the export | Checks the export can rebuild the reporting | Provides the export |
| Annual provider and fee review | Decides | Supplies usage and open issues | Prepares the review | Supplies renewal terms |
The monthly close
The monthly close is when the family’s numbers become numbers it can rely on. The data maintainer reconciles every account to the custodian statement, explains every break above the agreed tolerance, updates the manual values with their source documents and prepares a short close pack. The partner reviews it; a named person on the family side signs it. The calendar across several banks is covered in consolidated reporting across multiple banks.
Data controls in five lines
- A written tolerance for breaks. Any difference above a set amount is explained before sign-off.
- Maker-checker on manual entries. Every value entered by hand is checked by a second person against its source.
- A change log on mappings. Every new account, entity or asset class has a dated entry: who asked, approved and configured it.
- A quarterly access review. Leavers removed, roles checked, the administrator account still with the family.
- Nobody paid by the vendor signs off the close. Its managed-service team can prepare the work, not approve it.
Payment approvals and call-back controls are a separate subject, covered in the family office Excel guide. How PWA sits above this layer month to month is on the family office technology platform page; oversight of the banks and managers behind the feeds is private wealth oversight.
How to tell an independent partner from a reseller
Many firms call themselves independent or vendor-agnostic, and many are. The test is what the firm will put in writing.
Seven written questions for any independent technology advisor
- In the last three years, have you received any payment or benefit from a software vendor, bank or platform provider? From which, and in what form?
- Are you a reseller, certified implementation partner or member of a referral programme for any platform we might consider?
- Does any part of your fee, or any payment to you from anyone else, depend on which platform we choose?
- Whose name will be on the software contract, and who will pay the vendor?
- Who will hold the administrator credentials, during implementation and after it?
- Do you build, host or operate anything our data passes through?
- When we stop working with you, what happens to our data, our documents and the configuration, and what do you hand over?
Red flags
- Answers given only in conversation, or “we are vendor-agnostic” with no written statement of payments received.
- A discount on the partner’s own fee if the family chooses a particular platform.
- The partner, not the family, holds the administrator account.
- The software invoice routed through the partner rather than paid by the family to the vendor.
None of these proves bad faith. Each means the family has handed part of the decision, or the control, to someone it does not pay. For a family with several banks, see the Case Study a founder, four banks, eleven entities, no single view.
What PWA does and does not do here
PWA’s role in family office technology is design, selection, oversight of the vendor’s implementation and review. The vendor implements its own platform, and the family signs the contract and pays the vendor directly. The work follows a fixed ladder:
- A Wealth Operations Review maps the current set-up: entities, banks, reporting, who maintains what, and which parties are paid by whom.
- The Architecture Blueprint covers the requirements, the target operating model, a platform shortlist with real costs and a 12-month implementation roadmap with an owner for every step. Fixed fee, by proposal.
- The Oversight Retainer is PWA as the independent coordination layer above banks, vendors and advisors, on a fixed rhythm: review of the consolidated report, oversight of the vendor and the close, and the annual provider and fee review. Fixed fee, by proposal.
Before anyone shows you a demo, find out what your set-up needs and who in the room is paid by whom.
A Wealth Operations Review examines how your wealth is organised today: what is fine, what is fragile, what to change first, and what it all costs. €7,500 fixed, written, ten working days, refunded in full if it finds nothing worth more than its fee.
Request a Wealth Operations ReviewPrefer a call first?Questions we hear
What does an independent family office technology partner do?
It writes the family’s requirements and data model, runs the software selection, holds the vendor to acceptance tests during implementation and reviews the monthly close afterwards. It is paid only by the family, takes no fee from any vendor or bank, and does not configure the platform itself: the vendor implements its own product.
What is a software reseller, and why does it matter to a family office?
A software reseller sells another company’s licences and usually implements them, earning a margin, partner discount or revenue share from the vendor. That is legal and common. It matters because a reseller’s income depends on the family choosing a platform it resells, so its advice on which platform to buy is not neutral.
Do technology consultants receive referral fees from software vendors?
Some do, legally and openly. Asora, a family office software vendor, publishes a referral programme paying 20% of first-year net subscription revenue to accountants, lawyers and advisors who introduce family offices. The point is not that such fees are wrong. It is that the family should ask, in writing, before taking anyone’s recommendation.
How long does a family office software implementation take?
It depends on the number of entities, banks and private-markets positions, and on how clean the history is. Vendors publish their own estimates: Masttro, for example, states a typical go-live of 12–14 weeks. Plan for a parallel run over one or two month-ends before the old spreadsheets are switched off.
Who should sign off the monthly close in a family office?
A named person on the family side, usually the family office head or finance lead, after the data maintainer has reconciled every account and explained every break above the agreed tolerance. An independent reviewer can check the work. Nobody paid by the software vendor, including its managed-service team, should sign off the close.
Can a private bank’s portal be the family’s reporting system?
For assets held at that bank, a bank portal is usually accurate and timely. As the family’s reporting system it has limits: it shows what the bank holds, it may not carry other banks, private markets or property, and the data and access stay with the bank. A family with several banks usually needs a reporting layer it owns.
Can the vendor’s own team implement the platform without a consultant?
Yes. The vendor’s team knows its product better than anyone and should do the configuration. What it cannot do neutrally is write the family’s requirements, choose between itself and a competitor, or sign off its own work. A family with in-house finance staff can do those parts itself; otherwise an independent partner does.
Sources
All pages opened and checked on 20 October 2026.
- RBC Wealth Management and Campden Wealth, “2025 RBC and Campden Wealth Report: North American family offices adapt to uncertainty and embrace AI, innovation”, newsroom release, 16 October 2025. Supports: 69% adopted automated investment reporting systems, up from 46%; 317 responses, 141 from North America; manual processes and over-reliance on spreadsheets most cited operational risks. rbcwealthmanagement.com
- Merrill and Bank of America Private Bank, “2025 Family Office Study”, undated page (survey fielded May–June 2025). Supports: 44% face technology challenges; 335 US decision-makers; offices with at least $25 million. ml.com
- Asora, “Referral partners”, undated page (© 2026). Supports: 20% of first-year net subscription revenue, exclusions, audience, no tiers. asora.com
- Eton Solutions, “KPMG & The Table Club Family Office Report”, 2 June 2025. Supports: Eton Solutions as co-sponsor of the report. eton-solutions.com
- KPMG Australia, “Technology and the family office”, page dated 24 February 2025. Supports: report by KPMG and The Table Club on Australian family offices. kpmg.com
- Deloitte Private, “Family office technology solutions”, undated (originally published in Family Office Magazine). Supports: the quotation on staff taking an active role in requirements, design and testing. deloitte.com
- Masttro, “Masttro vs. FundCount”, undated comparison page. Supports: “typically 12 to 14 weeks” to go live (vendor statement). masttro.com
Pedro Souto is the founder of PWA — Private Wealth Advisory. He works with UHNW founders, families, and single-family offices to build an independent operating layer around complex wealth — combining markets, analytics, technology, and governance to turn fragmented advice into one coherent picture, and to make someone, finally, responsible for the whole of it.