Family Office Software: Build or Buy, and Why the Ownership Graph Decides It
The threshold is roughly 30 legal entities, and the condition underneath it is whether a workbook has quietly become your system of record.
On this page
The threshold is roughly 30 legal entities, and the condition underneath it is whether a workbook has quietly become your system of record. Below 30 entities, with most assets marketable and one household reporting to itself, buy: Addepar or Black Diamond for the portfolio, Canoe Intelligence or Arch if you hold funds, Sage Intacct or QuickBooks for the books. Above 30 entities, with alternatives past a quarter of assets and two people whose real job is moving numbers between systems, build the consolidation layer above those feeds at $60,000 to $130,000 over 12 to 16 weeks. Most offices that ask the question have already crossed the line and are still paying for it in staff time.
When is off the shelf genuinely the right call here?
Buy, without hesitation, if 80 percent or more of your assets are marketable, you run fewer than about 10 legal entities, and one household is reporting to itself. Addepar or Black Diamond will give you a stronger product than a first custom release and will be live in about six weeks rather than sixteen. Add Canoe Intelligence or Arch if you hold funds and the pain is document keying. Spend the savings on a better controller.
Keep the general ledger in every scenario, at every size. Sage Intacct and QuickBooks already do entity bookkeeping, your auditors already know them, and replacing them roughly doubles the scope of any build for almost no return. Asset Vantage and FundCount are worth a look if accounting is your centre of gravity and the portfolio is secondary. They get closer to the books and give ground on portfolio analytics.
Buy Canoe Intelligence or Arch outright if extraction is your only real problem. Rebuilding extraction to avoid a subscription is a poor trade at any size.
The signal that buying is still right is that nobody reconciles to a workbook. If the quarterly pack is assembled from vendor reports and the controller's job is review rather than transcription, you do not have a software problem. What ends the buy case is not asset value. Offices well past a billion dollars run happily on Addepar when the structure is simple, and offices at $300 million cannot, because they hold 70 entities and a third of the money sits in funds that report by document rather than by feed.
When does a custom build actually pay off?
The build case starts when a workbook becomes the system of record by accident. Not when someone uses Excel, everyone uses Excel, but when there is a file called something like Consolidated_Master_v7_FINAL, it takes the controller four days to roll forward each quarter, and it is the only place the whole picture exists.
Build when three or more of these are true.
- More than about 30 entities, or any structure with look through and ownership percentages that changed on specific dates. A gift made in 2021 that shifted three sibling trusts' slices is the case that quietly breaks every reporting tool you own.
- Alternatives above roughly a quarter of assets. Sixty fund positions means 40 general partner portals, 40 logins, and statements landing anywhere from day 45 to day 90.
- Two or more full time people whose actual job is moving numbers between systems.
- The family asks questions your vendor's report writer cannot answer and the honest reply is give me until Friday. Exposure to commercial real estate, and how much of it is levered, is a Friday question in a workbook and a click in a real system.
- One person understands the model, and if they leave, the office reconstructs its net worth from source documents.
The economic test underneath all of that is the second and third points together. A senior person losing three to four weeks a quarter keying fund statements, plus one to two full time equivalents on reconciliation, is the number that makes a $134,000 build look ordinary. If your alternatives allocation is small and nobody is retyping, the same build is an expensive way to make a working process prettier.
How do they compare on the things that matter in this industry?
On marketable securities, buying wins outright and permanently. Custodian connectivity, performance calculation and benchmark handling are solved problems, and Addepar is genuinely strong at them.
On the ownership graph, a build wins because no vendor owns yours. Your structure is a directed graph with minority stakes, share classes and edges that changed on dates, not a clean hierarchy. A build makes it a first class object: nodes for entities, edges carrying a percentage, an effective from and effective to date, a class of voting, non voting, limited partner, general partner or preferred, and a look through flag. Consolidation stops being a formula and becomes a traversal as of any date you name. This is a configuration ceiling rather than a complaint. Commercial platforms model hierarchies well, and a hierarchy cannot answer a consolidated net worth question as of December 2021.
On alternatives data, it splits cleanly. Buy the extraction, build the mapping. Canoe and Arch will read the file. Neither knows that the Fund VII position is held 60/40 across two trusts, or that the direct deal with no portal and a quarterly email from the sponsor's assistant needs identical treatment.
On reporting, a build wins on time rather than on charts. Family office reporting is bitemporal: what you knew on 1 November about 30 September differs from what is true about 30 September today, and both matter because one version went to a trustee. Power BI (Business Intelligence) and Tableau assume one truth per row, which is why quarter over quarter figures stop tying.
On permissions, a build wins because family permissions are branch shaped and commercial products are advisor and client shaped.
On integration burden, buying wins. Every feed you own is yours to maintain, and the fixed width file dropped nightly on a secure file transfer server will change format without notice.
What does total cost of ownership look like at your scale?
A focused first release runs $60,000 to $130,000 over 12 to 16 weeks: the entity ownership graph with effective dated edges, the consolidation engine with look through and intercompany eliminations, one custody feed, the alternatives document pipeline with a human review queue, and dashboards worth showing a principal. The full platform, adding partner capital accounts, tiered waterfalls, multi currency with translation, cash and capital call forecasting, the family portal and a mobile view, runs $150,000 to $400,000 phased over 6 to 12 months.
A worked shape. An office with 62 entities, 45 percent in alternatives across 58 fund positions, two custodians and Sage Intacct: discovery $12,000, ownership graph $21,000, consolidation engine $23,000, first custody feed $14,000, alternatives pipeline $28,000, bitemporal ledger $13,000, dashboards $12,000, and general ledger integration with testing and training $11,000. That is $134,000. An office with 18 entities, 12 fund positions and one custodian lands nearer $68,000.
One module dominates the upside. Partner capital accounts with tiered waterfalls, preferred return, catch up, carry tiers, side letters and clawback run $45,000 to $110,000 on their own, and they are where fixed price bids die. If your allocations are straight percentage splits with no carry, say so in the first meeting and take that money off the table.
Running costs are single tenant hosting in your own cloud account at $400 to $1,100 a month, a per page inference cost on extraction that is visible but small, and support and enhancement at 12 to 18 percent of build a year. The line nobody budgets is custody feed maintenance. A feed with a documented interface adds $6,000 to $12,000 to build. A nightly fixed width file adds $14,000 to $25,000 and needs attention indefinitely.
Compare that against people rather than licences. You keep paying Addepar either way.
What does the hybrid look like, and when is it the honest answer?
In this category the hybrid is what we recommend to almost every office that builds.
Keep Addepar or Black Diamond for the marketable portfolio and treat it as a feed. Keep Sage Intacct or QuickBooks for the entity books and pull trial balances through the interface. Keep Canoe or Arch for extraction if you already run one. Then build the middle: the ownership graph, the consolidation engine, the bitemporal ledger and the reporting layer that reads from all three. That is the layer nobody sells, because it is the layer specific to your family.
The thin version is thinner still. If a senior person loses three to four weeks a quarter to fund statements, the alternatives pipeline on its own runs $30,000 to $52,000 over six to eight weeks: per entity intake inboxes, classification, extraction with a confidence score per field, and a review queue showing the source page beside the value. It takes that time back immediately, and it does not solve consolidation, which is worth saying plainly before anyone buys it as a first step.
Sequence deliberately. Build the graph and the consolidation engine first and test them against a quarter you have already closed. Start custodian onboarding paperwork in week one, because it moves on its own timetable regardless of your plan. Defer the family portal, the most visible deliverable and the least urgent, which is far easier once the graph has been in production for a quarter. Run one full quarterly close in parallel with the workbook before switching it off. Every office we have built this for wanted that quarter.
Which should you choose, by operator size and stage?
Under 10 entities, mostly marketable, one household reporting to itself: buy Addepar or Black Diamond, add Canoe if you hold funds, keep the ledger you have, and stop. Revisit when entity count climbs or the alternatives allocation passes a quarter of assets.
Ten to 30 entities with a growing fund allocation: buy the platform and buy the extraction. The interim discipline that costs nothing is to record ownership percentages with effective dates in a maintained document rather than in cells, and to make sure someone other than the controller can read it. Most of the exposure at this size is key person risk, not tooling.
Past 30 entities with alternatives above a quarter of assets, or with two people reconciling full time: build the consolidation layer at $60,000 to $130,000 and keep every vendor you have. Start with the graph, one custody feed and the document pipeline. Prove the Tuesday question gets answered on Tuesday before scoping anything else.
Offices with partnership allocations, carried interest, multiple presentation currencies, or a portal serving beneficiaries: the full programme at $150,000 to $400,000 across two or three quarters. Scope the waterfall separately and price it separately, because it is the one module where a confident fixed price is a warning rather than a comfort.
Whoever you hire, put your real structure chart on a whiteboard in the first meeting and watch what they draw. If they reach for effective dated edges, look through, share classes and intercompany eliminations without prompting, they have done this before. If they draw a parent and child tree, they will find the problem at month four on your budget. Settle code and infrastructure ownership in writing before kickoff.
If you would rather scope this before committing budget, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Only 22% of firms are 'future ready' having significantly transformed digitally; these companies show average revenue growth 17.3 percentage points and net margins 14.0 percentage points above their industry average. Source: MIT Center for Information Systems Research (MIT Sloan) (2022) →
- An independent Forrester Total Economic Impact study of OutSystems found a 363% three-year ROI with payback in under 6 months, illustrating that faster, lower-labor build approaches can materially shift the payback math. Source: Forrester Consulting (commissioned by OutSystems) (2024) →
- Across 1,471 IT projects the average cost overrun was 27%, but one in six projects was a 'black swan' with an average cost overrun of 200% and a schedule overrun of nearly 70%. Source: Harvard Business Review (Bent Flyvbjerg & Alexander Budzier, University of Oxford) (2011) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
Frequently asked questions
If we build, what does it cost to move off Addepar later?
Less than you would expect, because in the shape we recommend Addepar is a feed rather than the system of record. Positions, transactions and valuations already land in your own model with your own entity mapping, so replacing the feed is a connector project rather than a migration.
Moving off in the other direction, meaning back to a vendor as the system of record, is the expensive one. Effective dated ownership, eliminations and the bitemporal history have nowhere to go in a hierarchy based product, and you would be choosing to lose them.
What happens if Addepar, Canoe or our custodian changes pricing?
Your exposure is proportional to how much of your model lives inside someone else's product. If the ownership graph, consolidation, eliminations and reporting history are yours, a price rise is a negotiation about one component with real alternatives behind it.
If the vendor holds the consolidated picture, the renewal conversation happens with your reporting as the deposit. Either way, budget a few days a year for feed maintenance regardless of pricing, because file formats change on the provider's schedule and not yours.
How long before the master workbook stops being the system of record?
Around week 12 to 16, once the ownership graph, one custody feed and the consolidation engine are live and tested against a quarter you have already closed. That is the point where the consolidated number comes from the system rather than from cells.
Most offices then run one full quarterly close in parallel before switching the workbook off. Full retirement, including partner capital accounts and the family portal, usually lands 6 to 9 months in.
Is Addepar enough for an office with 40 entities?
It depends far less on the count than on what sits on the edges between them. Forty entities in a clean hierarchy with stable percentages and mostly marketable assets is well within what Addepar handles, and building would be hard to justify.
Forty entities with minority stakes, share classes, percentages that changed on specific dates, a related party loan needing elimination, and tax basis wanted alongside fair value on the same node is a different question. That is the configuration ceiling, and it is where offices keep Addepar and build the layer above it.
Can we build only the alternatives document pipeline first?
Yes, and where a senior person loses three to four weeks a quarter to fund statements it is the highest return opening move. Per entity intake inboxes, classification of capital calls, distribution notices, quarterly statements and tax schedules, extraction with a confidence score per field, and a review queue showing the source page runs $30,000 to $52,000 over six to eight weeks.
Be clear about what it does not do. It does not consolidate, and it only pays fully once the extracted figures map onto your entity structure with the right ownership percentages.
Should we replace Sage Intacct or QuickBooks as part of this?
No, in almost every case. Entity bookkeeping is a solved problem, your auditors already know those systems, and replacing the general ledger roughly doubles scope for very little operational gain. Pull trial balances through the interface and build the consolidation and reporting layer above.
The one exception is partner capital accounts with tiered waterfalls, which no small business general ledger handles. If your structures need carry, that module is custom regardless of which ledger you keep.
Why are partner capital accounts and waterfalls so expensive?
Because preferred return, catch up, several carry tiers, side letters that vary terms per investor, and clawback across a fund's life all interact, and the testing burden is larger than the build. A waterfall that is almost right is worse than none, because someone will rely on it.
Budget $45,000 to $110,000 for the module alone. If your allocations are straight percentage splits, say so early and remove it from scope entirely.
Who owns the code and the family data if an agency builds this?
The repository should sit in your organisation from the first commit, infrastructure should run in your cloud accounts, documents should live in your storage, and the contract should assign full ownership with no licence back. At Digital Heroes the client owns the code from commit one.
Make the runbook and a documented export path named deliverables, and require per view audit logging and single tenant hosting. An office that replaced a dependency on a spreadsheet with a dependency on a development firm has not solved its problem.
How much does a custom BI dashboard cost for a small business?
For a small business, a focused first dashboard typically runs $25,000 to $60,000 when it covers 2 or 3 data sources, daily refresh, and 5 to 7 core metrics. Across 2,000+ Digital Heroes projects, budgets climb past that only when real-time data, complex permissions, or customer-facing access enters the scope. If a quote for a simple internal dashboard exceeds $75,000, ask exactly which of those three is pushing it there.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
How long does it take to build a custom BI dashboard?
A working first version usually ships in 4 to 8 weeks, and a full production build with multiple integrations and permissions takes 3 to 6 months. In Digital Heroes delivery experience, schedules slip on data access, meaning credentials, API approvals, and cleanup of source data, far more often than on the dashboard screens themselves. Lining up access to every data source before kickoff routinely saves 2 to 3 weeks.
How do I make sure each client sees only their own data in a shared dashboard?
That is row-level security, and it must be enforced in the database or API layer, never by hiding filters in the interface. Each query carries the logged-in client's identity, and the data layer refuses to return rows outside their account, so a crafted URL or modified request cannot leak another client's numbers. Make any vendor show you exactly where that filter lives, because interface-level filtering is the most common security mistake we find when auditing dashboards built elsewhere.
How do I vet an agency or developer for a BI dashboard project?
Ask them to walk you through the data model of a past project, not a portfolio of pretty charts, because dashboard failures are almost always data modeling failures. Good answers mention specifics like star schemas, dbt, incremental refresh, and how they handled a source schema change after launch. Then ask for a fixed-scope discovery phase with a written data audit as the deliverable, so you judge their real work for a small spend before committing to the build.
What should the first version of a dashboard include, and what can wait?
Version one should answer 5 to 7 questions your team already asks every week, pull from your 2 or 3 most important data sources, and refresh daily. Real-time data, custom report builders, scheduled email exports, and write-back features can all wait for version two. Across our projects, teams that launch a narrow version one reach a dashboard people actually use roughly twice as fast as teams that try to cover every department at once.
Will a custom dashboard stay fast once our data hits millions of rows?
Yes, if it aggregates before it displays; no dashboard should scan millions of raw rows on every page load. The standard techniques are pre-aggregated summary tables, incremental refresh, and caching, which keep typical page loads under 2 seconds even on datasets in the hundreds of millions of rows. Ask your vendor how the dashboard behaves at 10 times your current data volume; a good one gives a specific answer about aggregation, not just a bigger server.
How many SaaS seats do we need before building custom becomes cheaper?
The crossover usually shows up between 20 and 50 seats on premium tiers. Salesforce Enterprise lists at $165 per user per month, so 40 users cost about $79,000 a year in subscriptions, which is real money against a custom system you would own outright. Run the comparison over three years: if subscription spend beats the build cost plus 15-20% annual maintenance, custom wins on price before you even count workflow fit.
How do I work out whether a custom dashboard will pay for itself?
Add up three numbers: hours of manual reporting it removes each month, license seats it replaces or avoids, and the value of one or two decisions it speeds up, like catching margin slippage a month earlier. Across Digital Heroes projects, internal dashboards typically pay back in 8 to 18 months, and customer-facing dashboards pay back faster when analytics is a paid feature or reduces churn. If the honest math does not clear payback within 2 years, buy an off-the-shelf tool instead.
How do I vet a software development agency before signing a contract?
Ask to speak with two past clients whose projects resemble yours in size and industry, and ask exactly who will write your code, since some agencies sell senior faces and deliver junior or subcontracted hands. Demand a written specification with acceptance criteria before any fixed price, and check that their portfolio links to products that are actually live. An instant quote given without questions about your workflows is the clearest warning sign there is.
How many people does it take to build a custom BI dashboard?
A typical build runs with 3 or 4 people: a data engineer for pipelines and modeling, a full-stack developer for the application and charts, a part-time designer, and a project lead. One strong freelancer can handle a single-source internal dashboard, but in our experience solo builds stall once multiple integrations, permissions, and customer access are added. Team size matters less than having one person explicitly own the data model.
Who can build a custom business intelligence dashboards system?
Digital Heroes builds custom business intelligence dashboards systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other business intelligence dashboards companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Aaradhya.
Senior Backend Engineer · Python · Delhi · 4 posts on the site
Published · Last updated .
