The ERP playbook
Every ERP project we've watched a contractor or FM company run goes through the same six stages, whether they name them or not. This playbook names them, and links each one to the specific guidance we've written for it.
Most ERP projects start with a complaint, not a plan — a spreadsheet that broke, a margin nobody can explain. Before you shortlist anything, put a number on what the current setup is actually costing you.
A requirements document written after watching one vendor's demo just describes that vendor. Build yours from your own job-costing and reporting gaps first, then let vendors respond to it.
Construction and FM software is a noisy category with a lot of generic accounting tools wearing a construction skin. A short list of three to five, chosen against your requirements document, is enough.
A scorecard weighted toward job-cost accuracy, multi-site control and statutory compliance catches problems a slick UI hides. Score every shortlisted vendor the same way, including the ones you already like.
Migration and training are where ERP projects lose their momentum. Sequence sites deliberately, onboard subcontractors with a fixed checklist, and don't treat historical data as optional.
The rollout team moves on; the habits have to stay. Weekly margin checks and a dashboard someone actually opens are what separate a system that pays for itself from one that quietly reverts to spreadsheets.
JobNext (facilities management, GCC) and ProjectsNext (contractors, India & GCC) are built by the same team that writes this playbook.
See both on the home page