Long-term Software Support
We run what we build. Niche software we wrote over a decade ago is still in production today, and the team that built it is still the team that looks after it.
Code with nobody behind it is a liability. Most software handovers produce exactly that: a codebase, a repository, maybe some documentation, and a relationship that ends at go-live. We don't work that way. We've been running software for clients for over a decade, and some of the niche systems we built early in that history are still quietly doing their job today.
Long-term support means the people who understand the system are the people who maintain it. No new firm having to reverse-engineer decisions made years ago. No gap in institutional knowledge when something changes. When a dependency needs updating, a platform changes beneath the application, or a business process evolves, we're already across it. We built the visual voicemail platform and a string of niche systems still running a decade on, and we're still the ones answering the phone when something needs attention.
- Ongoing maintenance and dependency management: libraries updated, platforms kept current
- Bug fixes and incident response from people who know the codebase
- Incremental feature development as the business need changes
- Security reviews and patching as vulnerabilities surface in dependencies
- Documentation maintained alongside the code, so the system is understandable to more than one person
- Architecture evolution advice when the system outgrows its original design
Quick questions
We have software built by someone else. Can you take it on?
Sometimes. We'll do a code review first and give you an honest assessment of the state of it. Some codebases are clean and well-documented and the handover is straightforward. Others have technical debt that makes support uneconomic without a cleanup phase. We'll tell you which is which before we commit to anything.
How do you handle systems built in older technology?
Carefully. Running old software is often the right call: migration has a cost and a risk, and a stable system that works doesn't always warrant either. We look at the operational risk of the current technology, the cost of migration and the business case for change. If the existing system is doing its job, we'll say so.
What does ongoing support actually cost?
It varies with what the system needs. Some software runs for months without needing attention; some has regular change requests. We work on a retainer that reflects realistic demand, reviewed periodically. We don't charge for time the system doesn't need.
We've shipped systems still running a decade later.
Custom software, AI agents and automation for real business problems. We design, build and run production systems — not prototypes. We ship working software that scales from a first version to national platforms. All of Build →
Need this sorted?
Tell us what you need. A real person replies — not a bot, not a call centre.