Don’t Break Ground on ERP Without Testing the Foundation

Implementation is not the foundation

AEC firms talk about ERP implementation like groundbreaking: a major move forward, a sign of progress, a commitment to modernization. Metaphorically, that language is dangerous.

You do not break ground on a building without testing the soil. ERP is the structure. The foundation is people, process, governance, data, and decision discipline. When firms skip foundation testing, the structure goes up anyway, and the cracks show up under load.

For CFOs, foundation gaps become reporting risk, consulting overrun, and leadership credibility problems that outlast the implementation timeline.

What the foundation actually includes

Foundation is not a kickoff checklist. It is whether the firm can carry the weight of implementation without collapsing current operations.

In AEC firms, that means billing and WIP workflows are understood, not mythologized. Job cost and project structures are agreed, not fought per project. Principals operate within process boundaries leadership will enforce. Finance has capacity. Data problems are named. Decision rights are clear.

If those conditions are weak, ERP does not lay a foundation. It exposes the lack of one.

How to test the foundation before implementation

CFOs do not need a technology test. They need an organizational inspection, ideally before vendor contracts lock timelines:

• Run readiness conversations with operators, not only executives. Ask project accounting, billing, and finance operations where the work will break.
• Document process reality, including exceptions. If the firm cannot describe how work runs today, it is not ready to design how work should run tomorrow.
• Name data problems before migration planning. Treat known WIP, job cost, and project data issues as scope, not surprises.
• Clarify enforcement. Confirm leadership will support process discipline when principals resist standardization.

The Deltek Readiness Scorecard is one structured way to run this inspection. Advisory work goes deeper, but the principle is the same: test before you build.

The momentum trap

Once ERP is framed as "we are doing this," foundation testing feels like resistance. Vendors are selected. Internal champions are announced. Steering committees are formed. At that point, honest assessment is harder, because slowing down feels like failure.

That is why foundation testing belongs before momentum, not after. CFOs are often the only executive with both the incentive and the position to insist on inspection before groundbreaking.

Test the foundation. Then commit the spend.

ERP implementation can succeed, but not if the firm treats implementation as the beginning of readiness. Readiness is what must be true before the build starts.

Do not break ground on ERP without testing the foundation. The inspection is cheaper than the rework.