Legacy systems & automation
A reliable older system can still leave someone phoning a supplier for a licence or copying figures between spreadsheets. We start with the person who does the job, including the exceptions that never made it into the manual.
Describe a manual taskOur founder’s previous engineering work
Renewing licences across a fleet of older devices.
Hundreds of devices were still in production after mainstream support ended. When their software licences came up for renewal, an engineer had to phone the supplier.
In that role, our founder built a way to apply the renewals in bulk across the fleet. It took a recurring job off the engineers’ hands while the devices stayed in service.
Up to
150
engineering hours a year
Our founder’s estimate for this project. The figure has not been independently audited.
How do we change a working system safely?
We trace one workflow, identify where a failure would matter and agree how to go back if a change behaves differently in use.
See the automation demonstrationMap older systems and dependencies
Document how data moves between software, spreadsheets and suppliers. Identify unsupported interfaces, fragile steps and the checks people rely on.
Automate repetitive work
Replace manual exports, copy-and-paste reporting or recurring checks with scripts, scheduled jobs or a small application.
Integrate and test changes
Use an API, file exchange or controlled import that suits the existing system. Reconcile results, agree a fallback and hand over instructions.
Software and integration support.
From a small internal tool to a phased system change, we’ll scope the work around data access, dependencies and how much disruption your business can tolerate.
Discuss your workflowWhich step do you repeat?
A description of one awkward job is enough for the first conversation. Tell us which systems it crosses.