Lisa is the controller at a single family office with about $900 million in assets across public equities, private funds, real estate, and a handful of direct deals. She has one staff accountant. Between the two of them, they handle accounts payable, bank reconciliations, investor reporting, capital call processing, cash management, and the quarterly close. Lisa has been doing this for eleven years and she is good at it. That is worth saying upfront, because nothing in this article is about competence. It is about what happens when competent people are asked to hold together a process that was never designed for the volume and complexity it now carries.

On Monday morning, Lisa opens her laptop to fourteen new emails. Three are capital call notices from different GPs, each formatted differently. One is a PDF with clean tables. One is a scanned image. One is an Excel file with columns that don’t match anything in her system. She also has two investor inquiries asking for updated performance figures, a bank statement that needs reconciling before she can confirm a wire, and a message from the family’s tax advisor requesting documentation she already sent in February.

She starts with the capital calls because those have deadlines. She reads each notice, pulls the relevant figures, and keys them into the accounting system manually. Then she cross-checks the amounts against the commitment records she maintains in a separate spreadsheet, because the accounting system doesn’t track unfunded commitments the way the family wants to see them. The spreadsheet pulls from one source. The accounting system pulls from another. The custodian portal shows a third number. Getting all three to agree is a recurring project that never quite finishes.

By 10 a.m. she has been working for two hours and has not yet started on anything she planned to do today.

This is a story about Lisa’s week. It is also, in some version, a story about your week if you work in a family office back office with a small team, a growing portfolio, and a stack of tools that were never built to talk to each other.

Monday morning, five tabs deep

Lisa gets to her desk at 7:45 because she likes the quiet before everyone else logs on. By 8:10, that quiet is gone. Fourteen new emails. Three capital call notices from different GPs, each in a different format. A bank statement she needs to reconcile before she can confirm an outgoing wire. Two investor inquiries asking for updated performance numbers. And her staff accountant James won’t be in until nine.

She starts with the capital calls because those have deadlines, and to process them she does what she does every morning. She opens the accounting system, the custodian portal, an Excel spreadsheet she maintains for tracking unfunded commitments, and Outlook. She pulls the same data point — how much has been called against a given commitment — from three different places. The three numbers don’t agree. The custodian hasn’t reflected a wire from last week. The spreadsheet was last updated on Thursday. The accounting system shows the most recent posting but not the one she’s about to make. She reconciles the three in her head, decides which one is current, and moves forward.

Most family office finance teams work this way. Financial data lives in multiple disconnected systems, and each one becomes its own version of the truth. Custodian platforms track positions and balances on their own schedule. Accounting systems reflect what’s been posted. Spreadsheets fill the gaps that neither system was designed to cover. None of them update in sync, and none of them were built to talk to each other.

The industry term for this is data silos, and it understates the problem. A silo sounds like a storage issue, something passive. In practice, data silos create active, recurring work. Every question that touches more than one system requires someone to go find the answer in each one and decide which is right. For a team of two, that someone is almost always the most senior person in the room, because she’s the one who knows which source to trust and when. That work doesn’t show up on any task list. It just eats the morning.

It also introduces risk that’s easy to miss. When a controller reconciles three numbers at 8:30 on a Monday and makes a judgment call based on memory of what was posted last week, she is probably right. She’s been doing this for years. But the process depends entirely on her being right every time, with no system verifying the result. As the portfolio grows and the volume of these micro-reconciliations increases, the margin for error gets thinner. The family office doesn’t have a data integrity problem today. It has a process that will eventually produce one.

By 10 a.m. Lisa has been working for two hours and has not started on anything she planned to do today.

Midweek crunch

On Wednesday morning Lisa gets a capital call notice with a seven-day funding deadline. That’s tight but not unusual. The problem is that she needs to confirm available liquidity before she can approve the wire, and the family’s cash is spread across multiple accounts and entities. She checks the custodian portal for one account, the bank’s online platform for another, and a spreadsheet James updates manually for a third. Each one reflects a slightly different point in time. She builds a picture of available cash the way you’d build a puzzle, pulling pieces from wherever they happen to sit.

An hour later, the family’s patriarch calls. He’s meeting with his estate attorney on Friday and wants a consolidated view of his holdings across all entities. Lisa knows the data exists. It’s in the accounting system, the custodian feeds, last quarter’s GP statements, and a set of Excel files she maintains on the side because the reporting tool can’t combine everything the way the family wants to see it. Pulling it together into something presentable will take most of a day. She doesn’t have most of a day.

This is where the concept of a single source of truth becomes very concrete. In an office where portfolio data, accounting records, and reporting outputs all live in different systems, there is no report Lisa can run that gives the patriarch what he’s asking for. She has to build it from scratch every time, assembling numbers from five or six places and reconciling them along the way. The output looks simple. A few pages of holdings, performance figures, and allocation data. Nobody looking at it would guess how many hours and how many sources it took to produce.

Wealth data integration is the term for solving this problem at the infrastructure level. It means bringing portfolio data, accounting records, transaction history, and reporting into a single platform so that the information only needs to be entered or captured once and is then available everywhere it’s needed. The appeal is obvious, but it’s worth being specific about what it actually changes in a day-to-day workflow.

When a family office operates from an integrated data environment, a request like the patriarch’s consolidated report becomes a reporting exercise instead of a research project. The data is already there, already reconciled, already current. The controller runs a report, reviews it, and sends it. She doesn’t spend six hours pulling from multiple systems and hoping everything ties. The same applies to the capital call Lisa processed on Monday. In an integrated system, the commitment records, the cash balances, and the accounting entries all reflect the same underlying data set. She doesn’t need to check three sources and reconcile in her head, because the three sources are actually one source.

For offices with two or three people running finance, this distinction matters in a very practical way. Every hour spent assembling and reconciling data is an hour not spent on cash planning, exposure analysis, or the kind of forward-looking work that a family office actually hires experienced controllers to do. The work gets done. The books close. The reports go out. But the people doing it know that most of their week goes to data handling, and very little of it goes to the work that benefits from their judgment.

Lisa tells the patriarch she’ll have the report by Thursday evening. She’ll be at her kitchen table after dinner finishing it.

Thursday’s quiet question

Lisa sends the consolidated report at 4:15 on Thursday, about an hour later than she promised. It’s accurate. She’s confident in the numbers because she checked every one of them herself, tracing each figure back through the accounting system, the custodian portal, and the spreadsheets she maintains on the side. The report looks simple. A few pages of holdings, performance, and allocation data across entities. Nobody looking at it would guess what it took to produce.

She spends the rest of Thursday afternoon catching up on the work that slid during the week. While James finishes the bank reconciliations, she thinks about a conversation she had at a conference last month. A peer at a similar-sized office mentioned that her team had moved to a single platform that handled accounting, portfolio data, and reporting in one place. No more spreadsheets stitching the systems together. No more rekeying GP documents by hand. Lisa didn’t ask many questions at the time. She was distracted, already thinking about quarter-end. But the conversation stuck.

It’s a conversation that’s happening more often across family offices. As portfolios grow and teams stay the same size, the math starts to work against the patchwork approach. A 2025 study from BNY Wealth identified understaffing as a key constraint on family office operations, and the pattern is familiar to anyone running a lean back office. The workload increases with every new investment, every new GP relationship, every additional entity in the structure. The team does not increase with it. Something has to give, and usually what gives is the controller’s evening.

Some offices have responded by outsourcing pieces of the operation. Bill pay, fund administration, data entry, reconciliation. Outsourcing can relieve pressure on a small team, and for certain functions it makes good sense. But it doesn’t solve the underlying fragmentation problem. If the data still lives in five places, someone still has to manage the integration, whether that person is an employee or a vendor.

Other offices have started looking at the technology itself. The shift toward integrated platforms, where portfolio accounting, partnership accounting, general ledger, and reporting all operate from a shared data set, has been gradual but steady. The appeal is straightforward. When the data only needs to be entered once and is available across all functions, the reconciliation work that eats up so much of a small team’s week goes away. The controller stops being the human integration layer and starts doing the analytical and advisory work she was hired for.

This is not a small change and nobody should pretend it is. Moving from a patchwork of systems and spreadsheets to an integrated platform takes planning, time, and organizational willingness. But the offices that have made the move tend to describe the same result. The work didn’t disappear. It changed shape. It became more focused and less repetitive, and the team got back hours every week that used to go to data handling.

Lisa hasn’t made any decisions. She hasn’t sent any emails or scheduled any demos. But she bookmarks a few pages before she closes her laptop on Thursday night. It’s a small thing.

Friday, heading home

Lisa’s week ends the way it usually does. The capital calls are funded. The investor inquiries are answered. The bank recs are done. The consolidated report is in the patriarch’s hands. The books are in good shape. By any reasonable measure, it was a successful week.

But she also knows what it cost. Two late nights. A skipped lunch. A Wednesday spent assembling a report that should have taken an hour and took six. James spent most of his week on manual data entry and reconciliation work that would evaporate if the systems talked to each other. Neither of them touched cash forecasting, exposure analysis, or any of the work that would make next quarter easier than this one.

The pattern is familiar to anyone who has worked in a small family office finance function. The week fills up with operational tasks that are necessary and urgent and leave very little room for the work that is important. The team closes the books and delivers the reports, and then the next week starts and the cycle repeats. It works. But it works in a way that depends on the stamina and institutional memory of one or two people, and that is a fragile thing to build an operation around.

Lisa isn’t burned out. She still likes the work. She likes the family, she likes the complexity of the portfolio, and she’s proud of what she and James manage to produce with limited resources. What’s starting to shift is her sense of whether this is the only way to do it. That conference conversation planted something. The idea that the spreadsheets and the rekeying and the late nights aren’t inevitable. That other offices have found a way to keep the rigor without the grind.

She hasn’t named it yet, but what she’s looking for is a setup where the data works for her instead of the other way around. A single source of truth that doesn’t live in her head. A week where Wednesday evening is just Wednesday evening.

That might be where it starts.