When a 20-project portfolio outgrows its own accounting.

Twenty active real estate projects. Real assets, real revenue, real investors. And no unified financial architecture holding any of it together.

That's the situation I walked into as CFO of a development group — and it's more common than most people outside these businesses would believe. Nothing was broken in an obvious way. The projects were getting built. Money was coming in. But the finance function had been assembled the way most founder-run finance functions are: one solution at a time, each one solving yesterday's problem.

What "outgrown" actually looks like

The symptoms weren't dramatic. They were quiet, and expensive:

• Fragmented visibility for the Board. Twenty projects meant twenty versions of the truth. Nobody could answer "how are we actually doing" in one number without a week of assembly.
• No systematic investor management. Investor relationships lived in individual inboxes and individual memories — which works until you need to raise again, at speed.
• Financing capacity that hadn't kept pace. The portfolio had grown; the credit structure behind it hadn't. The business was bigger than the balance sheet supporting it.

Here's the part worth sitting with: none of those are accounting problems. The bookkeeping was fine. The architecture was missing.

Founder-run finance doesn't fail because someone did the math wrong. It fails because nobody was ever asked to design the system.

What we actually did

We rebuilt financial control end to end. Not a new report — a new structure. Unified financial architecture across all twenty projects, so the Board saw one coherent picture instead of twenty fragments. A tax and financing strategy designed for long-term sustainability rather than quarter-to-quarter survival. And we automated investor relationship management, so the fundraising engine could scale past the founder's personal bandwidth.

Partway through, the business needed more than a CFO, and I stepped in as interim CEO to see it through. That's a detail worth mentioning for one reason: financial architecture only sticks when somebody stays in the room long enough to make the operating decisions it implies.

The results

• EBITDA doubled.
• Credit facilities secured exceeded US$50 million — capacity that matched the portfolio's actual size.
• Assets under management grew 50% in 18 months.

But the outcome I'd point to isn't a number. It's that an informal, founder-dependent finance function became one a Board and outside investors could rely on. That's the difference between a company that grows and a company that can be handed to someone else and keep growing.

The lesson for anyone growing fast

Every business eventually outgrows the finance function it started with. The dangerous part is that it happens invisibly — revenue keeps climbing, so nobody looks under the hood until a Board asks a question no one can answer, or a lender declines a facility the business clearly deserves.

Two questions worth asking yourself this quarter. First: if your Board asked for one number on the whole business tomorrow, how long would it take to produce — and would you trust it? Second: is your financing capacity sized to the business you have, or the one you were three years ago?

A later version of the same problem, from a business where revenue quadrupled while the operation underneath it stood still: revenue grew four times over and margin did not follow.

If either answer makes you uncomfortable, that's not a failure. It's just the signal that the business grew faster than its structure — which is, all things considered, a good problem to have. It's also a solvable one.