What we did, and why that way
What was failing, what was decided, and what was left running afterwards.
-
A company running a years-old proprietary ERP, with reporting assembled by hand in spreadsheets
The data was there, the answers were not
An old ERP with no API, an undocumented database, and a report that took an hour. Decisions waited on it.
Out The same report in ten seconds, without touching the ERP
Read the case -
Freight forwarder with ocean, air and land operations across several markets
The only API was a person
To find out where their cargo was, the client had to ask somebody. During office hours, and usually without the context to decide anything with the answer.
Out Portal, app and API: clients answer themselves, at any hour
Read the case -
Organisation with network infrastructure across several sites
A thousand devices and no master key
A network of a thousand devices administered with local accounts, until someone got in and wiped configurations.
Out Centralised access, run by the client’s own team
Read the case -
Growing organisation, several sites and plans to open more
Infrastructure built so it would not be built again
Critical services running on desktop computers, public IP ranges assigned by hand, and a datacenter nobody could explain in full.
Out The network redesigned, and a standard for the next site
Read the case