80 PERCENT SPENT. 60 PERCENT COMPLETE.
A $2.8M CMU and brick subcontractor kept finishing jobs with 80 percent of the budget spent and 60 percent of the work complete. He thought retainage was the trouble, money already earned and held where he couldn't reach it. The job cost report said something else in its first cycle. CMU made money and brick gave it back. He priced brick per unit at a rate built for production wall. Soldier courses and the directional cuts around windows and doors take labor at a different rate. He was about 20 percent light on every brick job, for roughly eighteen months.
He was excellent at takeoff and his relationships were good. One blended labor code averaged a winning scope with a losing one. The number it reported described neither, so the problem got past every review he did.
- Revenue
- $2.8M
- Before
- Jobs finishing at 80 percent of budget spent against 60 percent of the work complete. Brick labor priced about 20 percent light.
- After
- Brick rates rebuilt by type and billing corrected. Receivables pulled in from 90 to 30 days, and bids now carry 10 percent net before taxes.
- Time
- One job cost cycle to diagnose, and about six weeks to rebuild the rates and correct the billing.
A $2.8M MASONRY SUB. SIX MONTHS IN, SOMETHING WAS OFF.
A masonry contractor doing $2.8M in CMU and brick for commercial work. Within about six months he noticed his estimates and his bank account disagreed. He hadn't found the cause. He had personally guaranteed the company's merchant cash advances. One missed payment put his house, his vehicles and his investments at risk.
HE THOUGHT IT WAS RETAINAGE.
That's the usual first answer, and it's usually wrong. Retainage is money you've earned and can't touch yet, so it explains a timing problem. It doesn't explain jobs finishing at 80 percent of the budget with 40 percent of the work still to build.
Two cash problems covered up the pricing one. He was underbilled by roughly 10 percent, so his billing understated the work in place. Receivables were at 90 days, so what he did bill came in late. Together they made a pricing failure look like a cash shortage. So he took merchant cash advances and never repriced anything.
The personal guarantee is worth saying plainly. It's standard on a merchant cash advance and almost nobody reads it. By the time you sign one, you're too worried about Friday to read page four.
ONE CODE, TWO DIFFERENT TRADES.
The job cost report answered it in the first cycle, once labor reported by scope. CMU was making money. Brick was giving it back. A single blended masonry labor code had been averaging the two, so the report showed a middling number that matched neither scope and looked survivable.
The brick rate was the fault. He priced brick per unit with a rate built for production wall, the fastest brick a mason lays. Soldier courses and the directional cuts around window and door openings use labor at a very different rate. One number for all of it left him about 20 percent light on brick labor.
Over roughly eighteen months that cost a few hundred thousand dollars. It never looked like a bad job, because every job had some CMU in it to average it back toward acceptable.
WHAT CHANGED, WEEK BY WEEK.
THE NUMBERS, NOT THE FEELING.
The diagnosis took one job cost cycle, because splitting the two scopes was enough to show it. Rebuilding the brick rates by type and fixing the billing took about six weeks. The merchant cash advances were caught roughly six months into their term, which is why they could be paid off. A year in, the compounding makes them very hard to clear.
DOES THIS SOUND FAMILIAR?
If this is you, you probably have two scopes under one cost code. Masonry with CMU and brick, mechanical with pipe and sheet metal, electrical with rough-in and underground. If one scope is priced right and the other isn't, a blended report averages them. The number looks tolerable and tells you nothing.
The tell is repetition. One job at 80 percent spent and 60 percent complete is a job. The same result over and over is a rate, and a rate is a decision somebody made once.
The second tell is a unit price used across work that is not uniform. Brick per unit is fine if all the brick is the same brick. The moment a job has soldier courses and cut-heavy openings, a single rate is charging production speed for work that cannot be built at production speed.
See how CFOS applies to masonry subcontractors specifically on theCFO for Masonry Contractors page, or book a 20 minute call. Josh won't pitch you or send a proposal.
