Construction is one of the hardest industries to fit into off-the-shelf ERP. The software assumes products, stock and repeatable orders. A contractor has projects, variations, retention and subcontractors — none of which map cleanly onto those ideas.
Where generic ERP breaks down
- Cost is per project, not per product. Management needs committed versus actual cost per project, live, not a month-end reconciliation.
- Variations are constant. A system that treats the contract value as fixed is wrong from the first week.
- Retention has to be tracked for years. Money held back on a project completed two years ago still needs chasing, and spreadsheets lose it.
- Subcontractor payment applications have their own approval chain that rarely resembles a purchase order.
Compliance is not optional
Any system issuing invoices in Saudi Arabia must satisfy ZATCA e-invoicing — structured XML, cryptographic stamping and reporting or clearance depending on the phase you fall into. This is not a feature to add later; it constrains the invoicing design from the start. A system that generates PDFs and calls them invoices will fail an audit.
Start with the bottleneck
The most common ERP failure is buying the whole suite and rolling it out at once. Two years later, finance uses it and the site does not, and the data is worth less than the spreadsheets it replaced.
A better sequence:
- Identify the single process costing the most money or time today — usually project cost tracking or subcontractor payments.
- Build or configure that, get it genuinely used, and let it prove itself.
- Extend from working software rather than from a specification document.
Build, buy, or somewhere between
Buying makes sense when your processes are ordinary and you are willing to change them to match the software. Building makes sense when a process is genuinely your competitive advantage, or when the off-the-shelf options need so much customisation that you are effectively paying twice — licence fees plus development.
The practical answer is often both: a standard accounting package for the ledger, and a purpose-built layer for project cost, variations and payment applications, integrated through an API.
Where BK IT fits
We build ERP and custom business systems in Next.js, Node.js and PHP, including e-invoicing integrations, and we work inside a construction group — so the workflow around retention, variations and subcontractor payments is not something we have to be talked through.
If you are weighing a rollout, tell us which process hurts most and we will scope that one first.