Support and maintenance for software that is already live

Most months you will not ask us for anything. Nothing breaks. Nothing needs deciding. The invoice arrives anyway.

Anyone who pretends otherwise loses the argument in month three. That is when the first genuinely quiet month makes the whole arrangement look like money for nothing.

What the arrangement gives you is the right to ask. You do not have to book a scoping call or wait for a quote before you ask. A ten minute fix costs ten minutes when someone already holds your system in their head. Without that, the same ten minutes costs a fortnight of finding a person who will look.

There is a second thing in the price. If the product is down on the morning of a launch or a board meeting, nobody asks the code. They ask whoever signed for it. Where the risk could have been named in advance, the question afterwards is why it was still sitting there.

So here is the question worth asking at renewal. What happened last month, when nothing broke? It has an answer, and the answer has dates in it.

Those are records against everything, not against your stack, and most will never touch you. The number that sits closer is this one. 279 vulnerabilities were added to the CISA catalog of known exploited vulnerabilities in the twelve months to 31 August 2026. That is about 23 a month, and that catalog lists only flaws with confirmed exploitation in the wild.

One more, and the population is what makes it usable. Among 947 codebases whose owners submitted them for commercial audit or acquisition due diligence, 92% carried components at least four years out of date.

One of those rows carries a consequence worth stating exactly. From 31 August 2026, an update submitted to Google Play must target Android 16 or higher. An app not raised to that level cannot ship an update at all, including one that carries a security fix. The exception is the extension Google offers, which runs to 1 November 2026. Copies already installed on phones keep working, and that is why this one goes unnoticed until you need to ship something urgent.

The two shapes are an Annual Maintenance Contract and a lean arrangement. The first suits a system that keeps changing and needs both maintenance and growth work. The second suits a product that is stable and needs someone available rather than someone busy.

Both run through the same change-note process as the build. After sign-off the estimate becomes the baseline. Every change request after that becomes a change note with time, effort and cost, approved before the work starts. Nothing in the build moves on a re-scope you did not accept.

The form does not return a price. It returns a conversation with a named person. The two ends of that table sit far enough apart that a number produced without looking at your system would be a guess.

If the thing on your mind is reducing what your live system costs to run, that is its own piece of work.

So the arrangement here is built the other way round. A core team is assigned only to your project. You talk to the lead software engineer directly. No rotation, no context-switching, and no handoff you did not agree to. Tirth Bodawala and Ajay Patel, who founded this firm, still take production calls. There are more than fifty people here, and that depth stands behind your team instead of pooling your request into a queue.

If what you need is closer to software engineering with the reasoning handed over, that is the build side of the same practice.

Our window is 10:00 to 19:00 IST, which is 04:30 to 13:30 UTC and never shifts. In the northern summer that is 05:30 to 14:30 in the UK and 00:30 to 09:30 US Eastern, and both run an hour earlier once the clocks go back.

The clock measures acknowledgement by a named person who has engaged with the issue. It does not measure resolution. How long a fix takes depends on what the issue turns out to be. We do not commit to that number, because nobody can honestly commit to it before looking.

The window is Monday to Friday, 10:00 to 19:00 IST. P1 is four working hours. P2 is twenty-four working hours. Everything else is seventy-two working hours. Seventy-two working hours is exactly eight working days, so it is worth seeing on a calendar rather than in units.

One limit comes with that. Raise a P1 at 17:00 on a Friday and a named person is on it at midday on Monday. There is no out-of-hours paging.

Several of the longest-running arrangements here started as a single project. The client checked the work against what was promised, then asked for more. Most builds carry on past launch as ongoing work. The longest active partnership at this firm runs more than a decade.

That is a fact about the firm, not a promise about any one person. We do not publish a retention figure and we are not going to invent one.