Why we always quote for end-user workshops, change management and post-go-live support

The people who decide are not the people who drive

Managers, administrators, consultants, system architects, product managers, developers: none of them will work in the system day in, day out. They will not drive the car, so they will not sense what it means when the reversing camera has no button you can find with your thumb. The end users will. When they cannot feel the controls, they stop looking at the screen and keep their own list. Adoption drops, data quality follows, and garbage in becomes garbage out, for the dashboard, for the forecast, for the AI. Then everyone suffers, including the people who signed the contract.

The industry data agrees. In Panorama Consulting's 2026 ERP Report, fewer than a quarter of organisations reported an intense focus on organisational change management. Among projects that overran their schedule, organisational issues (governance, resistance to change, process redesign) were the most common cause. And demand for change-management and post-implementation services grew faster than demand for selection support. Their conclusion is ours: with modern cloud ERPs most vendors meet baseline functionality; projects go wrong on process ownership and user adoption ³.

Why a standard terminology

Finance says "invoice", operations says "delivery", the vendor says "transaction", the tax adviser says Beleg. An ERP forces all four to mean the same thing. We start every project with a shared glossary (the words the business, the partner and the system will use for the same object) and we keep it current. It is unglamorous, and it prevents half the misunderstandings that later look like software defects.

Why the focus on institutional learning

An implementation is the largest concentrated learning event most companies ever go through, and most of that knowledge evaporates. It sits in the consultants' heads, in email threads, in one administrator who leaves eighteen months later. We design against evaporation: numbered documentation that grows from the first workshop; a support portal owned by the business; an internal administrator who has been in the project since day one; processes described in terms of purpose, so the next person understands why, not only how. Structured knowledge is also what makes a business ready for AI: an assistant can only be as clear as the documentation it reads.

Why we quote for it

End-user workshops, change management and additional post-go-live support cost money. We know. We also see the long-term value, project after project, and we come from the end users ourselves. We are, frankly, suckers for the end users. We care whether the warehouse trusts the screen and whether the accountant closes the first month without us.

So we quote for it. Every time.

You decide.