Skip to content
Discuss your project

Software for family offices and their operating companies.

Consolidated reporting across operating companies, real estate, and investments, built from connected records instead of a spreadsheet someone rebuilds every quarter. The operating companies the family intends to keep are modernized in phases, with each person seeing only the entities and documents meant for them.

Illustration of a consolidated reporting layer built by Baybloom for a family office: operating company accounting, investment reporting, and property records connected, with mismatches waiting for review.

Who this is for

Principals, CIOs, COOs, and operating executives of single-family and multi-family offices that hold operating businesses directly, and the management teams of those businesses. There is no sponsor playbook and no planned exit: the family intends to keep these companies, the consolidated picture lives in spreadsheets, and every report has to respect which family members and advisors may see what. The private equity page covers fund-backed companies; this page is for patient, family capital.

What makes it urgent

  • The family report is rebuilt by hand from accounting exports, custodian statements, and each operating company’s numbers.
  • A family member is stepping into an operating company that still runs on its founder’s tools.
  • An advisor needs to see part of the picture, and the only way to share it is a spreadsheet sent by email.

What usually breaks

  • Each operating company closes its books in a different accounting system with a different chart of accounts.
  • The investment reporting tool shows the securities portfolio, but not the operating companies and property beside it.
  • Access rules live in people’s heads, so sensitive entities are shared too widely or not at all.

The workflow

Before and after the first release.

The steps we see most often in this kind of operation.

Today
  1. ReportingA spreadsheet rebuilt from exports every quarter
  2. EntitiesCompanies, property, and holding entities in separate files
  3. AccessFiles emailed to family members and advisors
  4. Operating companiesFounder-era tools and manual processes
With the first release
  1. ReportingConsolidated views from connected accounting and investment records
  2. EntitiesOne entity map showing which entity holds what
  3. AccessPermissioned views for each principal, family member, executive, and advisor
  4. Operating companiesSystems modernized in phases and documented to be kept

What we build

Software we build for family offices and their operating companies.

Consolidated family reporting

Views across operating companies, real estate, and investments by entity, asset class, and family branch, built from connected records with definitions agreed once.

Entity and holdings map

A single record of every entity, what it holds, and who is responsible for it, used by reporting, access rules, and document storage alike.

Permissioned views and portals

Access for principals, family members, executives, and advisors limited to the entities and documents each is entitled to, with every view and export logged.

Accounting and investment integrations

Connections between operating company accounting, fund administrators, custodians, and investment reporting tools, with mismatches queued for review instead of patched in a spreadsheet.

Operating company modernization

Founder-era tools and manual processes in an operating company replaced in phases, with systems documented for a business the family intends to keep.

Cash and capital views

Cash positions, capital calls, and distributions across entities in one place, so the office can plan liquidity without assembling statements by hand.

Your first release

What the first release could include.

In the first release

  • An entity map of operating companies, real estate, holding entities, and investment accounts, showing which entity holds what
  • Connections to each operating company’s accounting system and the office’s investment reporting tool
  • A consolidated view by entity, asset class, and family branch, with definitions agreed once
  • Roles and permissions for principals, family members, executives, and advisors, with every view and export logged
  • A reconciliation queue for records that disagree between systems

Usually later

  • Modernizing the core workflow of the operating company with the most manual effort
  • A secure portal where family members and advisors see the views they are entitled to
  • Cash, capital call, and distribution views across entities

Systems it may connect

  • Accounting: NetSuite, Sage Intacct, QuickBooks, and similar, often a different system per operating company
  • Investment reporting: Addepar, Masttro, and similar
  • Fund administrator and custodian statements and data feeds
  • Property management and real estate accounting: Yardi, AppFolio, and similar
  • Operating company systems: ERP, CRM, and industry-specific tools
  • Identity and document storage: Microsoft Entra ID, SharePoint, Google Workspace, and similar

How the work runs

Scoped in writing, built in releases, handed over to your team.

Scope

We start with the people doing the work and the systems around it, then write down the first release: what it includes, what it leaves for later, the integration decisions, and the acceptance criteria. Nothing is built until that scope is agreed.

Build and test

We build in releases you can review as the work takes shape, using realistic data. Every release carries tests, a security review, and documentation. Integrations are tested against real records, with exceptions visible.

Handover

Your team receives the documentation, the runbooks, and the training to run the system, and we stay on for continued engineering when you want it.

Scope and price

What shapes the scope and price.

Every project is priced from a written scope. These are the factors that move it most.

Number of entities and source systems

Each operating company’s accounting system, each custodian or administrator feed, and each property system is a separate connection with separate mapping.

Access design

Fine-grained permissions across family branches, executives, and advisors need careful design and testing, especially where some entities are restricted to a few people.

Reporting definitions

Agreeing on how value, income, and performance are shown across operating companies, real estate, and securities takes work before the consolidated view can be built.

Data access from providers

Some tools offer APIs and others only exports or statements, which decides how much of the consolidated view updates automatically.

Single-family office with operating companies

The family sees its companies, property, and investments together, and each person sees only what they should.

A single-family office often holds several operating companies, a real estate portfolio, and a securities book, and the consolidated report is rebuilt by hand from accounting exports and investment statements. A first release maps every entity and what it holds, connects each company’s accounting system and the investment reporting tool, and produces a consolidated view with definitions the principals agree on. Family members, executives, and advisors see only the entities they are entitled to, and access is logged. Modernizing the busiest operating company’s core workflow is a natural next phase.

Questions

Questions from family offices and their operating companies.

What leaders in this industry ask us first.

Does this replace Addepar, Masttro, or our investment reporting tool?

The investment reporting tool stays the record for the securities and fund portfolio. We connect it with the operating companies’ accounting systems, property records, and the direct holdings it does not cover, so the consolidated view draws on each system for what it does best.

Our operating companies use different accounting systems. Is that a problem?

It is common. Each company’s NetSuite, Sage Intacct, or QuickBooks stays in place, and the connection maps its chart of accounts to consolidated definitions the office agrees on. Moving companies onto one system is a separate decision, made company by company if it makes sense at all.

How is confidentiality handled across family members and advisors?

Access is designed with the principals: which people see which entities, which figures, and which documents. Permissions apply to every view, search, and export, access is logged, and outside advisors get views limited to their engagement. Data handling and hosting are agreed in writing before any records are connected.

How is this different from private equity work?

A fund plans for an exit and works to a hold-period playbook. A family office usually intends to keep its companies, so the work favors systems the operating team can run and maintain, documentation that outlasts any one person, and phased modernization rather than preparation for a sale.

Who is the client, the family office or the operating company?

Either, depending on the work. Consolidated reporting and access rules are usually commissioned by the office, while modernizing an operating company is scoped with that company’s management team, with the reporting the office needs agreed as part of the scope.

Where should a family office start?

Usually with the entity map and the consolidated view, because every later decision depends on seeing the whole picture from connected records. That work also shows which operating company carries the most manual effort, which is often the right place to begin modernizing.

What happens after the work goes live?

Each release moves into ongoing support with monitoring, fixes, and small changes, and larger additions are scoped as the next phase. Documentation and access records are kept current, so the office, the operating company’s team, or its IT provider can run the systems alongside us.

Discuss a family office project.

Tell us about the workflow and the systems around it.
We’ll come back with a written scope for a first release.