Most ERP projects are judged at go-live. That is the wrong moment to declare success. The system that matters is the one people are still using a year later, every month, because their work depends on it.
We build and run the ERP for COAR Global, a research organization with over 160 staff spread across more than two dozen countries. The platform handles timesheets, project allocations, invoicing, contracts, and expenses. Here is what its usage data actually looks like today, and what it taught us about making an ERP stick.
The numbers: 164 user accounts, of which 103 were active in the last 30 days. Roughly 100 to 113 timesheet and invoice pairs completed in each monthly cycle, consistently, month after month. 61 active projects and over 1,000 project allocations under management. The large majority of monthly timesheets pass through finance validation, not just submission.
The headline is not the totals. It is the consistency. A monthly cycle that completes at the same volume every month means the organization runs on the system, not alongside it.
Lesson 1: build around the one cycle the business cannot skip. Every organization has one process that must happen every month no matter what. For COAR it is the timesheet-to-invoice cycle: staff record time against projects, finance validates, invoices go out. We built the ERP around that cycle first and let every other module attach to it.
The effect on adoption is structural. Nobody needs to be convinced to use a system that produces their invoice. Modules that hang off an unavoidable cycle inherit its usage; modules built as standalone islands have to earn adoption on their own, and usually do not.
Lesson 2: validation workflows are where adoption becomes real. Data entry proves people were told to use the system. Validation proves the organization trusts it. When finance validates hundreds of timesheets inside the platform each month instead of re-checking them in spreadsheets, the ERP has stopped being a recording tool and become the control point.
Design the validation step for the validator, not just the submitter. The person approving 100 records a month feels every extra click a hundred times.
Lesson 3: a distributed workforce punishes complexity immediately. COAR's staff work across time zones, connectivity conditions, and levels of software familiarity. There is no walking over to a colleague's desk to ask how the form works. Anything that requires training beyond a short document simply does not get done at the edges of the network.
The practical consequence: flows must be short, defaults must be right, and error messages must say what to do next. Distributed organizations do not get gradual adoption curves. Either the flow is simple enough to complete unaided, or the data does not arrive.
Lesson 4: instrument adoption or you are guessing. Everything above is only knowable because we measure it. Active users over 30 days, cycle completion counts, validation rates: these are queries, not opinions. When a number dips, that is a support conversation to have this month, not a surprise at contract renewal.
If your ERP partner cannot tell you how many people actually used the system last month, they are reporting on the project, not the product.
The takeaway: ERP success is a usage number sustained over time. Design around the cycle the business cannot skip, invest in the validation experience, keep every flow simple enough to survive distance, and measure adoption continuously. Go-live is the start of the evidence, not the end of the project.
Leeway designs, builds, and operates ERP and integration systems for organizations that run real operations. The adoption figures above come from our own monitoring of a system we operate in production.