A Scorecard for Multi-Entity Real Estate Developers
After 30+ years working with real estate developers who manage multiple entities, I’ve asked a lot of Owners and CFOs the same question:
“What is your back-office actually costing you each month in manual work?”
Almost none of them have an answer. Not because they don’t care — because nobody has ever made them put a number on it.
That’s the problem. Invisible work costs exactly as much as visible work. It just never shows up on the P&L labeled as “manual reconciliation” or “spreadsheet babysitting.” It shows up as close-day drift, CFO burnout, and Controllers who can’t take a real vacation without the month-end slipping.
If you’re running multiple entities in QuickBooks, Sage, or Excel, you’re likely paying more than you realize — not in software licenses, but in the manual work those tools create. Real estate developer accounting software that handles multi-entity consolidation natively can eliminate most of it.
This post is a framework for making that invisible work visible. I use it with developers on a 30-minute diagnostic call we offer — but the framework works just as well if you want to score your own team without us in the room.
Why Multi-Entity Is a Structurally Different Problem
A single-entity operator with clean books has one set of financials to maintain. Manageable in QuickBooks. Doable in Excel.
A real estate developer with eight project LLCs, two operating entities, and a holding company doesn’t just have “more work” — they have a structurally different problem. Intercompany transactions. Different investor partners on each deal. Draw packages that tie to one project’s bank but consolidate to the enterprise. Change orders that need to flow into the revised budget without losing the original. Subcontractor compliance that varies by project, by lender, by state.
Tools that work fine at one entity break down somewhere between entity three and entity eight. Most developers don’t notice the ceiling until they’re already bumping up against it — usually right after a capital raise, a new project close, or a Controller giving notice.
The 8 Areas That Actually Matter
Here’s the framework. Eight categories. Each one you can rate Green (working), Yellow (workable with manual overhead), or Red (broken or fragile).
- Consolidated Multi-Entity Financial Statements
Can you get a consolidated P&L, balance sheet, and cash flow across every entity — with intercompany eliminations handled — in under five minutes? If it takes a day, or it lives in an Excel workbook only your Controller knows how to open, that’s Red.
- Project P&L from Inception-to-Date
Every developer looks at the current-period P&L. Few can answer “what is the inception-to-date margin on Project X against our original pro forma?” without a rebuild. If that question takes more than two minutes to answer, Yellow at best.
- Budget vs. Actual by Cost Code (with Modified Budget Overlay)
When a change order is approved, does it flow automatically into the revised budget? Or does it get emailed to someone, updated in Excel, and eventually reconciled? The gap between “original budget” and “what we’re actually building to” is where trust in variance reporting dies. When the PM and Accounting show up to a meeting with different numbers, it’s this category that broke.
- Monthly Draw Package (AIA G702/G703)
How long does it take to assemble the AIA G702/G703, supporting invoices, and lien waivers for a single project’s draw? Eight hours is common. Under one hour is possible. The difference between those two numbers, across 12 months and multiple projects, is roughly a full-time headcount.
- 13-Week Rolling Cash Flow Forecast
If I asked your CFO for the cash position and covenant exposure across all entities next Friday, could they answer today? Or do they need to wait for Friday’s Excel build? Reactive capital calls and missed covenant moments almost always trace back to this single gap.
- Subcontractor Compliance
Expired COIs, missing lien waivers, unsigned W-9s — the AP team usually catches these at the worst possible moment. Either right before a draw submission or in the middle of January 1099 season. Modern systems block a check from cutting when compliance is missing. Legacy setups discover the problem after the fact, then spend two weeks cleaning up.
- Investor Capital Accounts and Distribution Waterfalls
When an LP asks “what’s my capital account balance and trailing IRR,” how long until they have an answer? If the waterfall lives in one Excel file maintained by the CFO, and the capital accounts live in another workbook maintained by the accountant, you already know the answer: a week, and everyone quietly hopes there isn’t a math error.
- Month-End Close Speed
The number most developers quote is “days to close.” The number that matters is “days from period-end to books you’d defend to a lender, an auditor, and an investor — without a caveat email.” For most teams, the second number is 50% longer than the first.
The Hours-Lost Math
Here’s what this framework produces when you actually run it on a team:
Take the specific recurring tasks the CFO or Controller walks you through — consolidation, draw packages, change order reconciliation, weekly cash forecasts, COI tracking, investor reporting. For each one, record hours per month and who does it. Apply a loaded hourly rate: roughly $75/hour for Controller-level work, $125/hour for CFO work, $50/hour for staff accountant work.
Then multiply by 12.
For a developer running 5–10 entities on QuickBooks, Sage, or Excel, the median result is $60,000–$110,000 per year of invisible manual work. Some owners are surprised it’s that high. A few are surprised it’s that low.
Either way, they have a defensible number. Something they can take to a board, an investor, or just a mirror.
The Question That Tells You Everything
There’s one more question worth asking your own team. It’s the one I’ve come to think matters more than any KPI:
“What would break in our back-office if our Controller left tomorrow?”
Some Owners answer “nothing.” Process is documented, system does the work, it would be an inconvenience — not a crisis.
Most name something specific. A waterfall model. A draw package. The consolidation workbook. A 1099 spreadsheet that lives in one person’s head.
A few stare and say “everything.”
That last answer is the one to take seriously. It doesn’t mean your Controller is going anywhere. It means your business has single points of failure that nobody has mapped, and you’re one two-week notice away from months of real pain.
Putting the list on paper changes something. Once you’ve written down “the waterfall, the draw package, the consolidation workbook, the 1099 tracking, the loan covenant math,” you can’t un-see it. Making the invisible visible is the first — and sometimes only — thing that needs to happen.
Three Paths Forward
Once you’ve scored yourself against the eight categories, the honest answer falls into one of three buckets:
DIY path. You’re mostly Green with a few Yellows. Your pain doesn’t justify a platform change — it justifies process discipline. Fix the specific problems without changing tools. Document the workflows. Cross-train the team. Build the cash forecast into real estate developer accounting software designed for multiple entities — or document the gap clearly enough that you know exactly what a modern platform needs to solve.
Worth a conversation. Multiple Reds. Hours-lost cost north of $40,000/year. A single point of failure who holds keys no one else has copies of. At this point the question isn’t whether to change — it’s what and when. Modern real estate developer accounting software handles most of these categories natively, which is the conversation we have with developers every day.
Not yet. You’re growing, but not at the threshold yet. Make a note of the trigger event that will move you into “worth a conversation” — usually the fifth entity, the next capital raise, or the first institutional LP. Revisit when you hit it.
The honesty of this framework is the point. Most real estate developers have been pitched so many software demos they don’t believe anyone will ever tell them “you don’t need to buy this.” So when we do — and we do, regularly — it actually registers.
Explore real estate developer account software built for multi-entity operators →
Score Yourself, Or Let Us Help
If you want to run this yourself, the eight categories above are enough to start. Pull your team together, score each one Red/Yellow/Green, and estimate the hours behind each Red. Multiply by the loaded rate. See what number comes out.
If you want a second set of eyes on it, we run the full framework as a free 30-minute Multi-Entity Accounting Scorecard for real estate developers with three or more entities. Ten questions, eight category ratings, one page of findings, and an honest recommendation at the end. No pitch. No prep. No slides.
You keep the scorecard either way.
