04 — ERP solutions
One picture of the operation.
ERP work fails when the software arrives before the process. We follow a real order, hire, or close, then configure only the fit and connect what should stay outside.
Start with one process that currently lives in three tools and a spreadsheet.
Scroll and this stack opens.
Watch it happen
What we offer
-
01
Process mapping
The path a transaction actually takes, including the exception everyone handles in chat. That exception is part of the design.
-
02
Fit and gap
What a candidate system already does, what you should change in the business, and what you should not customise.
-
03
Implementation
Master data with an owner, roles that match the work, and a thin slice reconciled before the rest is configured.
-
04
Integration, not another island
The systems that should keep their job stay connected. People stop re-entering the same customer, item, or invoice.
How an engagement runs
-
01
Follow one process to the end.
An order, a hire, a month-end close. We write who touches it, which system they open, and where the numbers get copied.
You see: the process you actually run. -
02
Separate process change from system change.
Some gaps are the business. Some are the software. We mark which is which before anyone configures a screen.
You see: a fit and gap, with owners. -
03
Configure a thin slice and reconcile it.
Master data, roles, and one complete transaction. We compare it to the way the numbers are produced today.
You see: one process working inside the system. -
04
Train the exception path, then cut over.
The people who handle the weird cases learn it first. Then we cut over with a checklist, and connect the systems that remain.
You see: a cutover, and who supports the next week.
What the engagement is made of
-
Process maps
Steps, roles, and the exception. Specific enough that an operator can point at a missing box.
-
Master data ownership
Who creates a customer, an item, or an account, and who is allowed to change it after go-live.
-
Role design
Access follows the work. The person who approves is not the person who enters, unless that is a real constraint we wrote down.
-
Integration boundaries
What the ERP owns, what another system owns, and the fields that must match on both sides.