Home/Case Studies
Production systems delivered in enterprise environments.
Each of these describes a system that runs today: the organization and the problem, the constraints that shaped the design, what was built, how it was delivered, and what changed as a result. Client names are withheld; sectors and figures are not.
Case studies
Consolidating a 3 TB content estate into OpenText Content Server
More than a million files and folders had accumulated across five separate repositories, each with its own storage model and idea of what a version is. All of it had to reach OpenText with structure, history and metadata intact — and a migration of that length will be interrupted.
Biometric attendance into SAP for 3,000 employees across five sites
Payroll depended on four scheduled jobs owned by a vendor the business had decided to retire. When those servers were decommissioned, attendance would have stopped reaching SAP at every site, silently, and nobody would have known until payroll noticed.
187 enterprise forms compiled out of a vendor platform into React
Hundreds of business-critical forms were locked inside an aging, proprietary ERP forms platform. The client's own developers estimated two days to rebuild each one by hand, which made the estate a project nobody would fund.
avocadoctor — a support agent that runs on your own hardware
An agent that reads a support ticket and its evidence bundle, investigates across every layer of a virtual-desktop stack, and posts a drafted diagnosis with the evidence behind every claim. The language model runs on-premises, and the agent refuses to commit an answer it cannot ground in stored evidence.
Have a system like one of these?
A migration that cannot lose a record, an integration nobody owns, a platform you need to get off, or an AI use case where the data cannot leave your network. Describe it and we will respond with a practical next step.