Your Next ERP Won't Fix What You Haven't Diagnosed Yet
- rdmontijo
- Jun 22
- 4 min read
A new ERP is a six-figure decision. In most cases, it is also the second mistake. The first one was not fully understanding why the current system was failing before deciding to replace it.
The two things I hear most often when a construction executive reaches out about switching systems are: "We don't have good financial visibility" and "Our system doesn't do that." The first one is almost always true. The second one is not always the case.
I have spent many years working exclusively with construction companies on accounting and ERP systems. The pattern I see most often is not a software problem. It is a diagnosis problem and it is one worth identifying and acknowledging before you spend a dollar on something new.
Understand the Gap Before You Go Shopping
When I dig into why a company does not have accurate, reliable numbers, the software is rarely the only answer. More often, the gap comes from one or more of these:
• The system was never set up correctly for construction accounting
• The team does not know how to use the reporting tools that already exist
• The data going into the system is too inconsistent to produce anything reliable
• Processes around the system are manual, disconnected, or dependent on one person
None of those are fixed by switching software. They move with you.
The most telling example is the WIP schedule. A proper Work-in-Progress schedule should be available at any given moment giving leadership a clear picture of which jobs are performing and which ones are quietly depleting margin. When that schedule is being rebuilt manually in Excel every month, that is a process and reporting failure. It happens on every kind of system.
What makes it more serious is that a manual WIP creates an opportunity to adjust the numbers. That may not always be intentional but inconsistent processes produce inconsistent results, and those inconsistencies show up in your bonding, your surety reporting, and the accuracy of every financial decision tied to job performance.
A new ERP will not fix this. It will inherit it.
The Demo Will Impress You: That Is the Problem
Once a company decides it needs a new system, the next mistake happens quickly: buying based on a demo without fully understanding what the software actually does out of the box for a construction company.
"It can do that" is one of the most expensive phrases in a construction ERP sales conversation. What it often means is: it can do that with custom development, with a third-party add-on, or not quite in the way you are picturing.
Before you leave any demo, get direct answers to these three questions:
• What does this cost to build or integrate beyond the base contract?
• What can this system NOT do for a construction company?
• What new problems will this create that I do not have today?
That last question is the one most executives never think to ask. Every migration introduces new challenges. Knowing what they are before go-live is not optional it is the difference between a managed transition and a crisis.
The Implementer Is as Important as the Software
You can select the right software and still end up with a failed implementation if the wrong team puts it in.
A generalist implementer, someone who works across multiple industries, does not understand construction accounting well enough to build the system correctly. They will make setup decisions in the first 30 days that create reporting problems you will live with for years. They will not build for scalability. And if they do not understand the financial side of construction, you will not get the automation or the job-level reporting your leadership team actually needs.
The training gap compounds this. Pointing the new user to a library of prerecorded videos is not a training program. Integration assumptions, particularly around payroll, are another consistent failure point. Construction payroll is not standard, and when that integration does not work the way you expected, the workarounds become permanent fixtures.
Before you hire an implementation partner, ask:
• What percentage of your clients are construction companies?
• Who specifically will handle our implementation?
• What is their construction background?
• What does post-go-live support look like for the first 90 days?
What to Do Before You Request a Demo
The companies that get this right do the diagnostic work before they ever sit down with a vendor. That means:
• Identifying the specific reporting gaps and process failures you have today
• Acknowledging whether those are system limitations or setup and process issues
• Mapping every software you currently use and confirming compatibility
• Getting your data clean - migrating inconsistent data does not fix the inconsistency
• Involving your users/leaders from day one
When you walk into a demo with a clear picture of your actual problem, you control the evaluation. You are measuring the software against real requirements, not getting sold on capabilities you may never use.
Final Thought
The right ERP can give your leadership team accurate job performance data on demand, a WIP schedule you can trust, and the financial reporting your bonding company expects. But the software is only as effective as the foundation beneath it.
Before you decide you need a new system, take the time to fully understand why your current one is not working. Identifying and acknowledging the real gap, whether it is the software, the setup, the processes, or some combination, is what allows the next decision to be the right one.
Comments