BLOG ยท FINANCIAL SYSTEMS

WE DO NOT PATCH A BROKEN STRUCTURE.

Most construction companies inherit a financial system built for a company half their size. You can't repair your way out of that, and the attempts cost more than the rebuild.

BY JOSH LUEBKERPublished March 6, 2026Updated August 8, 20262 min read
QUICK ANSWER

We replace financial systems instead of fixing them because a flawed structure produces unreliable information regardless of what you bolt onto it. Most construction companies inherit their financial system, and it was usually built when the company was much smaller, so it was never designed for larger projects, more employees, complex job costing, or multiple projects running at once. When problems appear, the standard response is to patch: add staff, install new software, request additional reports. Those changes rarely solve the issue, because reports generated from a broken system still produce unreliable information, and every patch adds cost and another person to train while the output stays wrong. The better move is to rebuild the structure itself, which means redesigning the job costing architecture, the WIP reporting process, the forecasting system, and the owner's decision reporting. The goal isn't simply better accounting. It's a financial system that gives the owner clear visibility into the business.

This is the least popular answer in the room and it's still the right one. Nobody wants to hear that the thing they have been feeding for six years has to come out, so most companies spend two more years proving it does.

THE FULL BREAKDOWN

The most common patch is another bookkeeper, and that page takes the argument apart in full. Read Why Bookkeeping Is Not the Problem for the complete treatment, worked figures included.

THE PROBLEM WITH INHERITED FINANCIAL SYSTEMS.

Most construction companies inherit their financial systems. Nobody sat down and designed one; it accumulated, usually when the company was much smaller and the stakes were lower. Whatever was set up then was set up for the company that existed then.

That structure wasn't designed for what the business is doing now:

Larger projects
More employees
Complex job costing
Multiple projects running simultaneously

As the business grows, the system begins producing unreliable information. Not late information, not incomplete information. Wrong information, delivered on time.

WHY SMALL FIXES RARELY SOLVE THE PROBLEM.

When financial issues appear, companies patch. They add staff. They install new software. They request additional reports. Each of those feels like a responsible response, and each of them leaves the structure where it was.

If the underlying structure is flawed, none of it solves the issue. Reports generated from a broken system still produce unreliable information, and a second person producing that information twice as fast produces wrong answers twice as fast. The patch isn't neutral either. It costs money, it costs time, and it buys the belief that the problem is being dealt with while the company keeps making decisions on bad numbers.

REBUILDING THE FINANCIAL SYSTEM.

Sometimes the better move is to rebuild the financial structure rather than adjust it. That sounds like the more expensive route and it usually isn't, because it's the only one that changes the output. It involves redesigning the components that produce every number the owner sees:

Job costing architecture
WIP reporting processes
Forecasting systems
Owner decision reporting

The goal isn't simply better accounting. The goal is a financial system that gives the owner clear visibility into the business.

WHAT TO DO WITH THIS

THE SHORT LIST.

Before you add a person or buy software, ask whether the structure could produce a right answer if it were staffed perfectly. If not, don't staff it.
Assume your financial system was designed for the company you were three years ago. It almost certainly was.
Rebuild in this order: job costing architecture, WIP reporting, forecasting, then owner reporting. Each one depends on the one before it.
Count what the patches have already cost you. Two years of software trials and extra hires is usually more than the rebuild.
COMMON QUESTIONS

FREQUENTLY ASKED.

Because the usual fixes don't touch the thing that's wrong. Adding staff, installing new software, and requesting more reports all leave the underlying structure in place, and reports generated from a broken system still produce unreliable information. If the architecture was built for a much smaller company, the only change that alters the output is redesigning the architecture.
Four components: the job costing architecture, the WIP reporting process, the forecasting system, and the reporting the owner uses to make decisions. Those four are what produce every number an owner looks at, so a redesign that stops short of any one of them leaves a weak link in the chain.
On its own it's a patch. Software records and organizes data according to a structure somebody gives it, so installing a better product on top of a flawed job costing architecture gives you the same unreliable information in a cleaner interface. The structure comes first and the software follows it.
WHAT THIS TIES INTO
Josh Luebker, The Construction CFO
Josh Luebker
FRACTIONAL CFO · THE CONSTRUCTION CFO

Former commercial project manager and master electrician: 150+ projects worth $2.1B combined, from $50,000 to $300M. Now fractional CFO to commercial subcontractors.

PATCH OR REBUILD, GET A STRAIGHT ANSWER.

A call is 20 minutes and it's not a presentation. Bring what you're running on now, and you'll hear which parts of it are worth keeping and which ones are costing you every month they stay.

You don't hire a CFO because it's safe, you do it because the real risk isn't having one.
Book a 20 minute diagnostic

20 minutes. No sales pressure. We will tell you exactly what's broken before we talk about anything else.

OR START WITH THE WORKBOOKS. NO CALL NEEDED.