Taking over Logtek's asset management system
Logtek's business runs on Lintracker, a custom system that tracks returnable equipment moving between sites, hauliers and customers. We took the system over, moved it to the cloud and have maintained and extended it ever since, upgrading, speeding up and securing it without stopping the business.
At a glance
- Client
- Logtek
- Sector
- Supply chain services
- System
- Lintracker: tracking of returnable equipment, orders, balances and reports across a supply chain
- Work
- Takeover, cloud migration, ongoing maintenance, performance, upgrades and security
- Speed
- Average page response at the morning peak cut from 1.2 seconds to 0.25 seconds
- Database
- Moved to SQL Server 2022 in a planned weekend window, rehearsed first on a copy of production
- Availability
- 99.96% of external login checks passed since monitoring began in September 2026
- Relationship
- Long-standing and ongoing
The situation
Logtek was looking for a new partner to maintain its custom business software. Lintracker records every movement of returnable equipment between depots, hauliers and the businesses they serve, keeps running balances for each account, takes orders and file feeds from customers’ systems, and produces the reports Logtek’s customers rely on.
It is the system the business runs on. Orders, deliveries and invoicing depend on it every working day, and some of the data arrives automatically overnight, so a fault does not wait for office hours.
What we did first
After listening to Logtek’s concerns we analysed the system and designed a cloud-based solution to improve performance and reduce hardware costs. With the system moved to the cloud and running more efficiently, we turned to what the growing business needed next and developed new application features.
Putting the foundations right
A system that has grown for years collects risks that nobody sees until something breaks. In 2026 we worked through them in order, without taking the system out of service:
- Releases that can be repeated. The source code was moved into Git, with a deployment pipeline that builds each release the same way, checks every server’s configuration against the expected values and runs automated tests against the live site straight after each deployment.
- A safe place to test. A staging environment that is an isolated copy of production, so that fixes are proved against real data volumes before they reach users.
- A database upgrade. The database server was rebuilt on SQL Server 2022. The build, the data copy and the switch-over were rehearsed on staging first; the live move took place in a planned weekend window and passed every check set for it.
- Backups that are proven. Database backups now go to storage in two regions, with alerts if one is overdue. A restore has been tested, and takes about nine minutes.
- Security. Stored data and backups are encrypted, the site sits behind a web application firewall, threat detection and audit logging are switched on across the hosting account, access is tightened to what is needed, and servers are patched on a fixed schedule.
- Monitoring. The site is checked from outside every five minutes from two locations, certificates are checked before they expire, and alerts cover report failures, overnight file feeds, overdue backups and errors in the application.
Making it faster
Users had learned to wait for some screens. We measured the slowest ones in production, reproduced them on staging and fixed the causes, which were mostly queries and data loading rather than hardware:
- Average page response at the morning peak fell from 1.2 seconds to 0.25 seconds after one release, and long stalls disappeared.
- A further set of fixes, proved on staging against a copy of production and due in the next release, takes screens that needed tens of seconds down to a fraction of a second: one history list goes from 55 seconds to 0.2 seconds.
Each improvement is checked against production data to make sure the results are identical, not just faster.
Keeping costs down
Part of the work was removing waste from the hosting bill: old servers, storage and backup copies that were no longer needed, and a file transfer server rebuilt on a current version of Windows at a fraction of its previous running cost. Together these cut more than $1,000 a month from the hosting costs.
Since then
We look after the system continuously: keeping it running, keeping it current and extending it as Logtek’s requirements change. Support requests and planned work are tracked in a shared backlog that Logtek can see.
It is a good example of how most of our client relationships develop. The first piece of work is a takeover or a migration with a clear outcome. Once the system is stable and the client can see how we work, maintenance and improvement carry on from there.
What it means if you are considering us
If you have inherited a system that works but worries you, this is the order we would work in: make releases repeatable and testable, prove the backups, close the security gaps, then make it faster and cheaper to run, all while it stays in use.
“Improved performance, resilience and reduced costs. What a way to start what is now a long-standing relationship.”
Have a system that needs a new home?
Say what it does, what it is built on and what is worrying you. We will reply with what we would look at first and whether we are the right people to help.