Construction ERP: what it costs, what it should do, and how to choose

Short answer: a construction ERP tracks money and materials against projects. Its core job is connecting site requisitions, purchase orders, goods received, daily consumption and subcontractor bills to a project budget and milestones, so you know your cost position before the project ends. Cost depends on users, modules, deployment and implementation work, so get quotes for your scale instead of relying on a published average.

What makes construction different from other ERP use?

• Projects, not products. Cost is tracked per project, phase and cost code.
• Materials at multiple sites. Stock sits at a store, on site, and in transit.
• Subcontractors and labour billed by measurement and progress.
• Long timelines and changing scope, with variations and change orders.
• Cash flow driven by milestones and running bills.
• Often poor connectivity at site.

Which features should it have?

• Project and budget setup: cost codes, phases, budget versions.
• Site requisitions that flow to approval and purchase.
• Purchase orders, goods received notes and supplier bills with three-way matching.
• Inventory by site and store, transfers, and daily material consumption.
• Subcontractor work orders and measurement-based billing.
• Milestones and progress billing to clients.
• Budget vs actual and cost-to-complete reports.
• Accounting integration or a built-in ledger, with tax handling.
• Approval workflows and an audit trail.
• Mobile or low-bandwidth access for site staff.

I describe one workflow in detail in construction ERP material procurement workflow, and the product in the NodeDR Construction ERP case study.

How is it priced?

Vendors use a few models, and the headline number rarely tells the whole story.

• Per user per month, often with different prices for full and limited users.
• Per project or per revenue band, common in larger construction suites.
• One-time licence plus annual maintenance for on-premise products.
• Implementation fees: configuration, data migration, integrations and training. For a mid-size company these can equal or exceed the first year's subscription.
• Add-ons: payroll, fleet, document management, mobile apps.
• Self-hosted, open-source or source-available products remove licence fees. You pay for hosting and your own or a partner's time.

Ask each vendor for a three-year total at your user count, including implementation, with the assumptions written down.

What should you ask vendors?

• Show me a requisition becoming a payment for one of my materials, end to end.
• How do you handle a change order against a locked budget?
• What happens at a site with no internet?
• Can I export every transaction in a standard format?
• Who owns the data, where is it stored, and how is it backed up?
• What does implementation involve and who does the work?
• What does leaving look like?

How do you avoid a failed rollout?

• Start with one project and one module, typically procurement and inventory.
• Standardise cost codes and item masters before loading anything.
• Train store keepers and site engineers. They enter the data, and bad data in means useless reports out.
• Run alongside the old process for a month and reconcile weekly.
• Review budget-versus-actual reports in every management meeting. A system nobody reads is decoration.