Software that keeps working after the people who built it have gone.
Most business software isn't failing. It's drifting — no updates, no monitoring, no one who understands it, and a growing fear of touching it. We take that on monthly, including systems we didn't build.
Four situations we take over.
- The team that built it has moved on. It runs, but nobody knows why it works.
- The agency relationship ended. You need someone accountable without hiring in-house.
- It's stable but ageing. Dependencies are years out of date and nobody has time.
- You have one developer. They can't be on call, on holiday and building new features at once.
What a monthly retainer covers.
Monitoring and uptime
Alerting on failures, errors and performance before your users report them.
Security and updates
Dependency updates, patching and vulnerability fixes on a regular cycle.
Bug fixing
Reported issues triaged, fixed and released.
Backups and recovery
Verified backups and a tested restore process, not just backups that exist.
Small improvements
A set number of hours each month for changes and enhancements.
Reporting
A monthly summary of what happened, what was fixed and what needs attention.
Three levels, depending on what downtime costs you.
Essential
Business-hours support, monthly update cycle, monitoring and backups.
For internal tools where a few hours offline is inconvenient, not damaging.
Response: Within 2 working days
Most common choice
Standard
Faster response, fortnightly updates, and a monthly allowance for small improvements.
For customer-facing systems.
Response: Within 1 working day
Critical
Priority response, on-call escalation and a named engineer who knows your system.
For systems where downtime stops revenue or operations.
Response: Within 4 working hours
Support hours are Monday to Friday, 10:00–19:00 Gulf Standard Time (GMT+4).
How a handover actually works.
- 1
Audit
We review the code, infrastructure, dependencies and security, and give you a written report on its condition. You keep the report whether or not you continue with us.
- 2
Access and documentation
We get proper access, document what exists, and list what's missing or at risk.
- 3
Stabilise
We fix what's urgent first: security issues, failing backups, missing monitoring.
- 4
Steady state
Regular cycles begin, with a monthly report.
The audit can be bought on its own. Some clients take the report and give it to their existing team.
What makes this work.
- Access to the code, hosting and any third-party accounts the system depends on.
- One person on your side who can answer questions and approve releases.
- Honesty about what's broken. We'll find it anyway, and finding it early is cheaper.
Questions.
Will you support software you didn't build?
Yes. That's most of this work. It starts with an audit so we both know what we're taking on.
What if the code is bad?
Then the audit says so, and we tell you what it would cost to stabilise versus rebuild. We won't quietly maintain something that should be replaced.
Is there a minimum term?
Three months, so there's time to stabilise the system before you judge the result. Thirty days' notice after that.
What does it cost?
It depends on the size of the system and the support level. Pricing follows the audit, or a scoping call for smaller systems.
Can you also add new features?
Yes, either within the monthly allowance or as a separate build.
Do you need to move our hosting?
No. We work with your existing hosting unless there's a reason to change it, and that's your decision.