ERP Implementation Lessons from a Construction Company

ERP projects have a reputation for going wrong. Billions spent on SAP implementations that never go live. Custom systems that take three years instead of one. Adoption failures where expensive software sits unused because nobody changed how they work.

When we built Readybuild — an ERP for construction companies covering project management, bid tracking, accounting, and resource planning — we learned that the technical build was straightforward. The hard part was everything else.

The Technical Build

Readybuild is a React + Node.js application with PostgreSQL, deployed on AWS. The core modules are project management with Gantt-style scheduling, bid tracking with version history, accounting with job costing, and a resource planning module that handles both equipment and labour across multiple sites.

The technical challenges were real — particularly the job costing module, which needed to aggregate costs across projects, cost codes, and time periods in real time without killing database performance. We solved that with materialised views and a careful caching strategy.

What Almost Killed the Project

Six months into the build, the client's site supervisors weren't using the system. They had their own spreadsheets, their own processes, and no incentive to change. The system was technically complete. Nobody was using it.

This is the ERP failure mode that nobody talks about: the system works but the organisation doesn't change. Software adoption requires organisational change management, and that's not something you can build.

What We Did

We went back to basics. Three weeks of on-site sessions with site supervisors, understanding their existing workflow, identifying where the system created friction instead of removing it. We rebuilt the mobile interface based on what we learned — simplified down to the three actions supervisors needed to do most often.

We also pushed the client to designate "champions" on each site — supervisors who were enthusiastic early adopters and could support their colleagues. That human element mattered more than any feature we could add.

What ERP Projects Actually Need

Executive sponsorship that's visible and real — not just budget approval, but executives who use the system themselves. A clear answer to "what's in it for me" for every user group. Enough simplification that the system is easier than the existing process, not just more powerful.

The technology is the easy part. The hard part is understanding how people work today and designing a system that they'll actually want to switch to.