Deployment pipelines, IoT estates, security review, infrastructure migrations and the ongoing care that stops a system quietly rotting. This is where most of our long-term relationships actually sit.
Every bullet below is work we have shipped. Where a line looks like filler on another company's site, it is here because a client needed it and we built it.
Deployment pipelines, environment management, monitoring and cost control on Azure and AWS, so releases stop being events that need a Friday evening.
Sensors, firmware, telemetry and the application on the other end.
Functional and end-to-end testing, API security auditing and penetration-style review of every endpoint your application exposes, including the ones nobody documented.
Microsoft 365 tenancy work, domain and identity migrations, and virtual learning environment moves, planned so that no historic data is lost and teaching or trading continues throughout.
Ongoing maintenance, monitoring, model retraining and enhancement under a plain agreement, rolling monthly, with thirty days' notice either way and no lock-in through opacity.
Practical upskilling for your team on AI tooling, engineering practice and data literacy, delivered by people who teach at university level for a living.
The same artefacts every time, regardless of project size.
Deliberately narrow. A team our size claiming twenty frameworks is claiming one thing badly, twenty times over.
Open the work page for the full case note on any of these, including what did not go to plan.
Every account moved from .co.uk to .ac.uk across Microsoft 365 and Moodle with no historic data lost.
Sensor rig, on-device model and remote pump control, designed for a field with no reliable signal.
Functional, end-to-end and API endpoint auditing across a two-app estate.
Answered as we would answer them on a call, including the ones with awkward answers.
Often, yes. We start with a review of what is there and what it depends on, then tell you honestly whether supporting it is sensible or whether you are being asked to maintain something that should be replaced.
Agreed in the support contract and tied to severity. We do not publish a single number, because a cosmetic bug and a production outage should not have the same answer.
No. Support runs monthly with thirty days' notice. Handover documentation is written so another supplier could pick it up, which is the only honest test.
The reason a product is not working is rarely where the client first thought it was, so these three sit alongside this one more often than not.
Describe the problem rather than the specification. If a smaller piece of work would answer it, we will propose that instead.