Maintain
Hosting, support and improvement after go-live.
Go-live is the start, not the end
A system in production is how your organisation gets through the day, and it needs attention to stay that way. Bugs surface, vulnerabilities are published, frameworks reach end of life and cloud bills drift upward. Meanwhile the business keeps moving and asks for changes too small to justify a project.
Operational Support
Close support in the first weeks after launch, then ongoing fixes. You talk to the people who built it.
Security and Patching
Security review, dependency upgrades before versions fall out of support, regression tests on every change.
Performance and Hosting
Run on Microsoft Azure and sized to the usage we measure, with a recovery position that has been tested.
Changes and Improvements
New reports, integrations and small changes handled alongside support, without a formal project each time.
We load-prove what we build before it goes live. The last integration held 17 times peak load. Read the integration case study.
How we work on any existing systems you have
What we hold ourselves to
What makes the difference between a support contract and someone who actually looks after your platform.
- Reliability
- Monitoring and alerting on everything we run, with a clear escalation path and an agreed way of working when something goes wrong. Every incident gets written up, fixed, and where possible designed out.
- Continuity
- The same people look after your system month after month, so nobody has to relearn it each time it needs attention. Where we built the platform, that knowledge runs unbroken from the first day of development.
- Improvement
- We review the platform with you regularly and bring our own recommendations to it. Support is a long-term arrangement, and it should leave the system better than it found it.