The Missing Margin.
The margin you underwrote, estimated or budgeted and the margin you actually kept are rarely the same number. The gap is what I write about, and it almost never has one cause.
It's the assumption nobody went back to check.
The lease-up pace in the pro forma. The change order nobody priced. The purchase made in the field three weeks before finance saw it. The pay app that went out late. The interest carry on money borrowed to cover the delay, and the extension fee after that. Overhead that never got recovered. A cost code that was wrong from the first day of the job.
Each one is small. Together they're the difference between a project that made money and one that looked like it would.
The harder part is timing. By the time most reporting shows a project going sideways, the decisions that caused it are already made and the window to do anything about it has closed. Finding the number after the fact is accounting. Finding it while you can still change the outcome is the job.
That is true of a specialty contractor with eleven open jobs, a developer with three facilities and a lender covenant, and a fund with a reporting pack nobody reads until the quarter is over. Different statements, same leak.
Same leak, different statement.
Real assets get bought, financed, developed, built and operated. The margin can go missing at every one of those handoffs, usually in a place the financial statements summarize instead of show.
The structure
The capital stack that worked at closing stops working when the schedule slips. Rate, reserves, extension fees and covenants all move with time. The model usually doesn't.
The budget
Contingency, carry and soft costs are where the original deal quietly gets repriced. Nobody announces it. It just shows up as a smaller number at the end.
The job
Job cost, change orders, procurement and WIP. The margin is decided in the field long before the accounting finds out about it.
The cash
Pay apps, lender draws, retainage and lien waivers are cash-flow mechanics, not paperwork. A clean draw package gets funded. A messy one waits, and the carry doesn't wait with it.
The property
Once the building opens, the leak moves to the rent roll, the operating budget, the capex plan and the reporting pack that lands three weeks after month end.
The seams
Property system, job cost system, GL, spreadsheet. Every seam between them is paid for in people, and the person reconciling it is usually the only one who knows what's broken.
Six leaks, in the order I usually find them.
Bad assumptions
The estimate assumed a crew, a lead time or a price that never showed up. The pro forma assumed a lease-up pace and an exit. Nobody went back to check either one.
Weak controls
A purchasing policy without a system-enforced gate is a PDF. The control has to live in the workflow.
Disconnected systems
Every seam between two systems is paid for in people. Job cost and the GL do not agree on their own, and neither do the property books and the investor report.
Delayed information
A report on the 3rd describes a decision already made on the 28th. Late and accurate is still late.
Unmanaged spend and carry
Cards, POs and field buys leak quietly and constantly. So do interest carry, extension fees and the rate cap nobody priced for the delay.
Decisions nobody revisits
A surprise that shows up every quarter is not a surprise. It is a process with no owner.
One job, one number, one sentence of consequence.
Written for owners, developers, GCs, subs and the owner's rep who signs the draw. The cost-reporting workbook I actually use comes with the first letter.
Five people asking if the same invoice was paid
Five people asking about one invoice is not a communication problem. It is a system that nobody can see into, so everybody asks the person who can.
What the demos didn't show
Every seam between two systems is paid for in people. The demo runs on clean data and one happy path.
Project-based spend is a different animal
Job cost and the GL never agree on their own. Retainage, pay apps and lien waivers are cash-flow mechanics, not paperwork.
BluePrint: three questions for every booth
What does it replace, who has to change their day, and what happens at month-end.
A purchasing policy without a system-enforced gate is a PDF
If the control lives in a document instead of the workflow, it is a preference, not a policy.
Send the report on the 31st, not the 3rd
Took the close from 15 days to 10, mostly by fixing the sequence, not the staffing.
One theme, told five ways.
A long episode, a webinar, an article, the clips and the posts. Three this season, each one a piece of the missing margin.
The builder's tech stack, from the CFO chair
A walk through the stack a mid-size builder actually runs, the handoffs between each piece, and the headcount those handoffs quietly require.
Comes with the WIP template
Field to ledger
From the daily report to the trial balance: where the numbers diverge, which divergences are real, and which ones are just timing nobody reconciled.
Late October
AI, with something to lose
An unreviewable AI deliverable is an unreviewed journal entry. What to ask for before letting it near the close.
November
Where I've been standing.
Conferences, panels and trade-show floors. If you are there, find me. I am usually the one asking the booth three questions: what does it replace, who has to change their day, and what happens at month-end.
- Sep 22–24BluePrint · Las Vegas
On the floor with three questions for every booth.
- Sep 29On Ramp · panel
Moderating “Taming Project-Based Spend.”
- Oct 20–23Procore + CFMA · Orlando
What I'd want from a construction ERP, asked in person.