Selected work
Four engagements, written up the way an engineer would want to read them.
Several clients are named only by sector at their request. Where that is the case the architecture detail is fuller, because it has to carry more of the weight.
01Financial services · 2025 · Client anonymised
Moving eleven million accounts off a mainframe without a maintenance window
Zero-downtime migration of a core ledger, completed over fourteen months.
- Product engineering
- Cloud infrastructure
- DevOps & scaling
A tier-one East African bank
02Logistics · 2025 · Client anonymised
Turning nine disconnected depot systems into one operating picture
A consolidated visibility platform across nine countries and four legacy systems.
- Product engineering
- Mobile development
- Data & AI systems
A pan-African logistics operator
03Insurance · 2024 · Client anonymised
Cutting claims triage from six days to under one
Document-driven claims triage with a human decision point retained by design.
- Data & AI systems
- Product engineering
- Design systems
A regional insurance group
04Retail · 2024 · Client anonymised
Surviving a campaign that had taken the old platform down twice
Commerce replatform sized against a measured load profile rather than a guess.
- DevOps & scaling
- Cloud infrastructure
- Product engineering
A national retail chain
A note on references
Client references are available under NDA during vendor review, including direct conversations with the technical leads who worked alongside us.
Common questions
Can Acorn Code Lab name its clients?
Some engagements are published with the client named and others by sector only, at the client’s request. Where a client is anonymised, the case study carries fuller architecture detail to compensate, and direct references — including conversations with the technical leads who worked alongside the studio — are available under NDA during vendor review.
What kind of projects does Acorn Code Lab take on?
Systems that carry revenue, regulation or both: core banking migrations, multi-country operations platforms, document-driven claims automation, and commerce replatforms sized against measured load. The common thread is a hard constraint the client cannot move — a regulator, a maintenance window, a launch date or a network.