Ask three companies why their ERP project succeeded and you will get three different answers. In our experience each sector has one capability that, if it works, justifies the whole programme — and if it does not, nothing else compensates.
Trading: landed cost, or you do not know your margin
Most importers can tell you their gross margin on paper. Fewer can tell you the true cost of the goods sitting in the warehouse, because freight, duty, clearing and handling never reached the product cost. They were posted as expenses, in a different month, against a different account.
The consequence is quiet but expensive: prices set from an understated cost, and discounts approved on a margin that does not exist.
Fixing it needs three things working together:
- Perpetual inventory valuation, so stock value in accounting always matches stock on hand.
- Landed cost allocation spreading freight, duty and clearing across the shipment by value, weight or volume.
- Discount approval limits by role, so margin protection is policy rather than negotiation.
Once those are live, margin per order line, per customer and per product family becomes a report instead of a year-end surprise.
Manpower supply: document expiry is the whole risk
When your product is people, the operational risk is not stock — it is paperwork. Residence permits, medical certificates, contracts, trade licences and site passes all expire, and each expiry that is missed becomes a penalty, a blocked site entry or a worker who cannot be deployed.
One file per client site, updated by whoever remembers. Expiries are noticed when someone is turned away at a gate.
One employee master carrying every document with its expiry date, and automated alerts raised weeks ahead to a named owner.
The second capability that matters here is reconciliation: attendance and timesheets should feed both payroll and client invoicing from the same source. When they are calculated separately, the two never agree, and the gap is almost always in the client's favour.
Facilities management: contracts are kept on evidence
FM contracts are won on price and retained on proof. The client wants to see that planned preventive maintenance happened on schedule, that reactive jobs were closed within the SLA, and that the technician who signed the job card was actually on site.
That means the system has to:
- Generate the PPM calendar from the contract, not from a separate spreadsheet that drifts out of sync.
- Route every reactive request into one queue — phone, email and WhatsApp requests all becoming tickets with a clock running.
- Capture the job on mobile: parts used, time spent, photos and customer sign-off.
- Report SLA performance per building and per contract, so the renewal conversation starts from data.
Technician utilisation follows almost for free once jobs are captured properly — and it is usually the number that pays for the project.
The pattern
In each case the decisive capability is not the flashiest module. It is the unglamorous one that closes a specific leak: cost that never reached the product, a date nobody was watching, evidence that was never captured. Find that leak first, and the rest of the ERP scope arranges itself around it.
Which leak is costing you most?
Thirty minutes is usually enough to identify it. No slide deck.
Book a Consultation