After the launch
What happens to an application in the year after its builders move on
We do not have an office in Saudi Arabia
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
Nothing dramatic, at first. The application runs, users adapt to its quirks, and the team that built it disperses to the next project. Meanwhile the platform underneath keeps publishing security patches the application no longer takes, a defect reported in month two is still open in month nine because nobody owns it, and the engineer who knew why the invoicing module tolerates duplicate references resigns without writing it down. Each of these is small; together they are the slope an application slides down until a routine change becomes frightening.
Support, done as a discipline, interrupts the slide. It does not matter whether we wrote the system or inherited it from another firm: the work is the same — a queue with owners and severities, a schedule that keeps the dependencies current before they become emergencies, and a record of the system’s behaviour that grows with every fix instead of shrinking with every departure.
The queue
How a defect travels from a user complaint to a fix in production
The value of a support arrangement is not that fixes happen — anyone can patch under pressure — but that they happen the same way every time, at a severity the business agreed to in advance.
Triage against agreed severities
Every report is classified by the impact scale the business signed off — what blocks revenue, what blocks a team, what merely annoys — so the response window is a commitment, not a mood. An owner and a response window for every report.
Reproduce before touching code
The defect is reproduced and captured as a failing test first, because a fix for a problem you cannot reproduce is a guess wearing a commit message. A failing test that pins the defect down.
Fix the cause, keep the guard
The change addresses why the defect happened rather than papering over where it showed, and the test that caught it stays in the suite so the same failure cannot quietly return. A cause-level fix that cannot silently regress.
Release on cadence, not on panic
Fixes and small enhancements ship in a regular, rehearsed release with a rollback; only the top severity earns an expedited path, because an operation that ships everything urgently ships nothing carefully. A production change with a rollback behind it.
The quiet debt
The dependency that aged quietly until it blocked everything
The most expensive line in many support histories is an upgrade that was skipped. A framework version falls out of support, the team defers the jump because nothing is visibly broken, and two years later a security advisory forces the upgrade at once — except now it spans four major versions, a dozen breaking changes and a freeze on every other piece of work while it lands. Dependency currency is not housekeeping; it is the difference between many small upgrades on your schedule and one enormous upgrade on an attacker’s.
So currency work rides the same cadence as the queue: patch releases applied as routine, framework jumps scheduled while they are still small, and each upgrade proven by the same test suite that guards the fixes. The record grows alongside — which versions run, why an odd pin exists, what the last upgrade broke — so the next person to touch the system inherits knowledge rather than archaeology.
Three contracts
Which contract answers when the application misbehaves, layer by layer
Application support, managed cloud operations and a post-delivery warranty are routinely confused, and the gap between them is where incidents go unowned. They watch different layers and end at different lines.
| Option | What it watches | What a typical fix looks like | What it cannot see | Best for |
|---|---|---|---|---|
| Application support (this) | The code, its dependencies and its behaviour in real use. | A code change with a test behind it, released on the agreed cadence. | The health of the servers, networks and platform underneath. | The application layer |
| Managed cloud operations | The infrastructure — compute, network, backups, cost, platform patching. | A configuration, capacity or platform change, made in the estate. | A defect inside the application’s own logic. | The platform underneath |
| A post-delivery warranty | Defects in what was just delivered, for a fixed window. | A correction by the team that wrote the code, at no charge. | Anything that changes after the window closes — aging dependencies, new usage, new needs. | The weeks right after delivery |
Our role
What sits on our support queue and what stays with your product owner
- 01
Severities agreed before the first ticket
We agree with the business what counts as urgent before anything is urgent, so triage is the application of a rule rather than a negotiation held during an outage.
- 02
Currency as routine, never as crisis
Patches and framework upgrades ride the regular cadence while they are small, so the estate never faces a forced, multi-version jump on a deadline set by a security advisory.
- 03
A memory that survives departures
Every fix and upgrade updates the written record of how the system behaves and why, so the knowledge sits in a document your organisation owns rather than in the head of whoever leaves next.
Which enhancements are worth their cost, and in what order, are product decisions that stay with you; we keep the queue honest, the dependencies current and the record written, so those decisions are made about a system that is understood.
Common questions
What buyers ask
Can you take over support of an application another firm built?+
Yes — it is the usual starting point, and it changes the first weeks rather than the service. We begin with an onboarding pass: read the code, inventory the dependencies and their support status, map the deployment path, and write the first version of the behaviour record from what the system actually does. Early fixes are deliberately chosen from the low-risk end of the queue, because each one teaches us the system under the safety of a small change. What we do not do is refuse the engagement because the code is imperfect; imperfect code in production is precisely what support exists for.
Our cloud is already under managed operations. Why does the application need its own support?+
Because the two contracts watch different layers. Managed cloud operations keep the platform healthy — compute, network, backups, cost, patching of the infrastructure itself. None of that fixes a defect in your application’s business logic, upgrades the framework your code is written against, or ships the small enhancement your operations team has been waiting on; those live above the infrastructure line, in the code. The arrangements complement each other, and the useful work at the boundary is naming it: when an incident arrives, it should be obvious within minutes whether it belongs to the estate or to the application.
Where does a small enhancement end and a new project begin under a support agreement?+
At the point where the change alters the system’s shape rather than its details. A new field, a report, a workflow tweak, an integration touched at an existing seam — these ride the support cadence, because they change behaviour inside the current architecture. A request that changes the data model, opens a new integration surface or needs its own design decisions is a project, and we say so at triage rather than letting it swell quietly inside the queue until it starves the fixes. The distinction is drawn by risk and shape, not by hours alone, and drawing it openly is part of what the agreement pays for.
In this cluster
Next step
Hand us the queue
A support assessment that inventories the application, its dependency debt and its undocumented knowledge, then proposes severities, a release cadence and a first month of the queue.
Hand us the queue
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly

