Building ERP: what it really covers beyond quotes and invoices
Job management and site budgets: margins, progress and variances in real time
A building ERP is used to run your jobs like mini businesses. For each site, you track a budget (labour, materials, subcontracting), progress and invoicing, but also the actual margin as the job moves along. The goal is simple: spot the gap between budgeted and actual early enough to correct it, not just to note it afterward.
Purchasing, supplier orders, stock and depot: avoiding stockouts and oversights
Purchasing is at the heart of the day-to-day. The ERP links requisitions, purchase orders, goods receipts and supplier invoices. On the depot side, you keep a clear view of stock levels, locations and reservations by site, with alerts on the remaining to order. Fewer oversights, fewer stockouts, less material sitting idle.
Time tracking, payroll interface and job-based cost accounting: linking hours, costs and outcomes
Time tracking ties hours to tasks and sites, including temporary staff and subcontractors. Once connected to payroll, each hour becomes a cost, then an analytical hourly cost by site. By cross-checking time and purchases, you quickly see what is profitable and what is drifting.
When does a building ERP make sense? Realistic thresholds in 2026
Headcount: practical benchmarks for a team of 10 to 50 employees
A building ERP starts to pay off when coordination no longer works “by word of mouth” and a site manager spends too much time stitching information back together.
| Headcount | Realistic threshold | Priority |
|---|---|---|
Number of simultaneous jobs: when Excel sheets are no longer enough
When you are managing more than 4 jobs in parallel, spreadsheet versions multiply, orders arrive too early or too late, and site-by-site tracking becomes blurry.
| Simultaneous jobs | Main risk | What the ERP stabilises |
|---|---|---|
| 1 to 3 | Manageable | Light centralisation |
| 4 to 7 | Coordination | Purchasing, scheduling, deliveries |
| 8 and over | Margin loss | Analytics, alerts, follow-ups |
Field warning signs: duplicate entry, stock errors, invoicing delays, disputes
- Duplicate entry for quotes, orders and hours, followed by VAT or job allocation errors.
- Recurrent discrepancies between depot, van and site, with “urgent” purchases.
- Invoices going out at month-end because delivery notes or approved timesheets are missing.
- Subcontractor disputes, missing variations, photos and site reports scattered everywhere.
If these signs happen every week, the issue is not the tool. It is the ability to keep up the configuration and the routines.
Choosing your building ERP well: criteria that avoid nasty surprises
Essential functions by trade: renovation, maintenance, multi-depot, subcontracting
A building ERP is mainly judged by its scope. In renovation, aim for job tracking, purchasing, progress claims, and a simple view of the job margin. In maintenance, look for contracts, scheduling, history and follow-ups. In multi-depot setups, require stock movements, transfers and stocktakes. With subcontracting, secure orders, progress, attachments and approval before payment.
Mobility on site and at the depot: time tracking, delivery notes, photos and validation
On mobile, check team time tracking, delivery notes, timestamped photos, approvals, signatures and punch-list management. The depot should be able to scan, pick and issue materials without re-entry. An offline mode changes everything when the network is on strike.
Required integrations: accounting, payroll, banking, quoting tools and DMS
Without connectors, you pile up duplicate entry. Ask for APIs, imports, exports, and a DMS linked to jobs. On the accounting side, the FEC export and job-allocated entries avoid workarounds. For payroll, the goal is usable time tracking, without spreadsheets, all the way through to variable pay items.
What a building ERP really costs: full budget and hidden line items
For a building ERP, the price is not limited to the licence. The budget is really driven by implementation, and by everything you pay “extra” when the team grows or when you add new use cases.
| Item | Recurring (€ / user / month) | One-off (€ / project) |
|---|---|---|
| Licence and modules | Depending on profiles | - |
| Configuration and data migration | - | Often the main cost |
| Training and support | - | To budget for |
Per-user licence: rights, profiles, modules and recurring costs
The recurring cost depends on the number of users, but also on profiles. A site manager, a buyer and an administrative user do not always need the same rights or the same modules. Watch out for add-ons that appear along the way.
Initial configuration, data migration and training: the real entry ticket
The entry ticket is translating your sites into rules: analytical structure, job stages, purchasing approval workflows, progress claim templates. Data migration and training take time, especially if files are inconsistent.
Rollout duration: typical planning and factors that extend the project
A realistic schedule is measured in weeks to months, not days. What takes longer: too much custom development, payroll or accounting interfaces to connect, dirty data, and no dedicated internal owner.
Avoiding failure: classic pitfalls and a rollout method that holds up
The “fake ERP” trap: quoting software plus an invoicing module, and the daily limits
A “fake ERP” is often just quoting software with invoicing and a few lists. At first, that works. Then, as soon as you have multiple jobs at the same time, purchasing, stock, time tracking and job costing become an endless saga. The result: duplicate entry and margins estimated by guesswork. A building ERP must cover the job, not just the quote.
Configuration: why it is the number one cause of failure and how to frame it
The software works. It is the “we’ll sort it out at the end” configuration that breaks the project: job coding, items, units, approval workflows, data-entry rules, cost structure. Keep the framing simple: short workshops, written decisions, test data, then user acceptance testing on real cases. Keep a sustainable Version 1.
Rollout without disruption: pilot, management rules, internal owner and ramp-up
- Run a 4 to 6 week pilot with one team and one depot, with clear objectives.
- Appoint an internal owner with dedicated time, and one rule: one piece of data, one accountable person.
- Ramp up in waves, with field training, support and weekly check-ins.
