CRM & ERP systems
When the system of record stops matching the business
CRM and ERP are where a company keeps its truth. When the software cannot express how you actually work, people build a shadow process in spreadsheets and the truth moves out of the system.
In short
Most CRM and ERP problems are configuration and process problems rather than software problems. Before customizing or replacing, the questions are whether the workflow in the system matches the workflow in the business, whether the data is clean enough to trust, and whether the people entering it get anything back. Replacing a platform without answering those reproduces the same situation on a newer licence.
When it applies
Signals this is the work
If more than one of these is true today, the problem is usually further along than it looks from the outside.
The real process lives in spreadsheets
The system holds the record after the fact. The actual work happens somewhere else.
Nobody trusts the pipeline or the stock figure
Numbers are checked against another source before anyone acts on them.
Customization has accumulated
Years of small changes nobody can now safely remove, and an upgrade that has been deferred three times.
Data is entered more than once
The same customer or order exists in two systems, keyed twice, drifting apart.
Adoption is enforced rather than chosen
People use it because they are told to, which means the data quality is whatever compliance produces.
How we do it
The sequence
- 01
Follow the work, not the org chart
Sit with the people doing it. The documented process and the real one differ, and the difference is where the project succeeds or fails.
- 02
Exhaust configuration first
A large share of "we need custom development" is a module bought and never set up. Configuration is cheaper to own and survives upgrades.
- 03
Fix the data before the workflow
Duplicate customers and inconsistent product codes undermine everything downstream. This is scoped as real work, not a migration footnote.
- 04
Customize narrowly and deliberately
Where the business genuinely differs, extend rather than fork, so upgrades stay possible.
- 05
Integrate rather than duplicate
One authoritative source per fact, with the others reading from it.
- 06
Make entry worth doing
People maintain data they get value from. If the system only takes, the data decays whatever the policy says.
What we will not do
The refusals
- Replace a platform before establishing whether it was ever configured properly.
- Customize around a process that should be simplified instead.
- Migrate dirty data on the assumption it will be cleaned later.
- Promise an upgrade path while forking core behaviour.
Questions
Before you ask
Tell us what isn't working.
One process, one system, one decision you are stuck on. We will come back with how we would approach it, what it would take, and whether it needs building at all.