After launch, an annual support agreement covers:
Support days are agreed per year. New features are not part of support; they go through a change request (below). If you want us to manage your cloud environment too, we add that to the agreement.
These are our typical targets. Your contract confirms the exact figures and hours.
| Severity | What it means | First response | Resolution target |
|---|---|---|---|
| 1 — Critical | A core process is down, data is at risk or there is a security incident. No workaround. | Within 1 hour, any day | Most resolved within 24 hours |
| 2 — High | The system works but in a severely reduced state, with significant business impact. | Within 1 working day | Most resolved within 72 hours |
| 3 — Medium | A time-sensitive issue with limited impact on day-to-day work. | Within 2 working days | Most resolved within 96 hours |
| 4 — Low | A minor issue with an effective workaround. | Within 4 working days | Most resolved within 1 week |
We watch production so problems surface before your users report them. Error tracking and alerts cover the application, servers and integrations. We apply security updates on a planned schedule and check the impact before each upgrade. When a release causes a problem, we roll back first and find the cause after.
Support keeps what you have running. New features, or changes to agreed behaviour, go through a short written change request: what changes, why, the effect on timeline, and a fixed price. Nothing starts until you approve it in writing. Each ticket is tagged as a defect or a change, so the line stays clear.
You get a regular report, monthly or on request, showing:
We tell you in writing before the support allowance runs out, and we meet at an agreed rhythm to review what's working and what's next.
You own the code and IP on final payment. The source lives in your repository, and accounts sit under your organisation's identities, not our engineers' personal emails. When you move support in-house or to another vendor, you get:
Yes. Support after launch runs under an annual agreement sized to your system, and the warranty period is agreed per project.
Yes. We start with a short code review, agree what we're taking on, and then support it under the same terms.
Yes. Normal support runs Monday to Friday in UAE business hours, and critical issues are supported on weekends and after hours too.
You keep everything: code, documentation and accounts. We run a structured handover and remove our access.
Planning a launch, or need support for a system you already run? Book a Discovery Session.