Work
The shape of the
engineering problems.
What these systems looked like before, what was engineered, and what the business ended up able to do.
Engineering transformations
Three states an operation gets stuck in.
Each of these is a shape rather than a single project — the same problem turns up across industries with different software behind it, and the engineering answer is recognisably the same. Client names, internal metrics and implementation detail are not ours to publish. What is described here is the engineering.
- 01
The answer exists, but no system holds all of it.
Systems involved
- ERP
- Warehouse system
- Production planning
- SQL databases
Separate systems, each correct on its own
One reconciled operational model
What was engineered
An integration layer that reads each system on a schedule, resolves the same entity across them, and holds one model the rest of the software can query — with the source of every figure kept alongside it.
Capability the business ends up holding
A question that used to be assembled by hand is answered on demand, and every figure in the answer can be traced back to the system it came from.
- 02
Input arrives in a shape nobody controls.
Systems involved
- ERP
- Supplier files
- Databases
Files re-keyed by hand, errors found later
Validated intake with an exception queue
What was engineered
An automated intake that asserts a schema on every incoming file rather than assuming one, transforms what passes, and holds anything ambiguous for a person to decide instead of guessing.
Capability the business ends up holding
Re-keying stops being a job. Exceptions become a queue somebody owns rather than a discovery three weeks later.
- 03
The system that cannot be changed and cannot be replaced.
Systems involved
- Legacy application
- Databases
- Internal tools
A frozen application everyone works around
A service layer the business can build on
What was engineered
A new interface and a service layer in front of the existing database, so functionality can be added and integrated against without touching the parts that still work.
Capability the business ends up holding
Change becomes possible again without a migration project, and the next piece of software has something to connect to.
What this is evidence of
Systems that were already running.
None of these started from an empty repository. Each one had an ERP that was staying, a database that was fine, and a process that could not stop while the work happened — which is the condition most of this engineering runs under. What we engineer sets out the capability; this is the same capability with systems attached.
Your systems.
Your processes.
Engineered for what comes next.
Bring one process, one system or one question. A conversation with the engineers who would do the work.