Application maintenance services for the AI systems we build — a named escalation point after we leave.

The ongoing work of keeping a delivered system healthy after the builder hands it over: monitoring, security patching, fixes when something breaks, and updates when the platform underneath changes. Classic application maintenance covers legacy software estates. Ours covers the AI systems we build — where the model underneath changes on a schedule and the people who built it are the right people to fix it.

You do — that’s the whole point of the handover. You get the documentation, the admin and user training, and a runbook for the common cases. If you want us to stay on as the named escalation point, that’s a monthly arrangement you choose and can cancel. The handover is real either way; maintenance is a service, not a leash.

That’s scheduled work, not an emergency — model providers publish retirement and deprecation dates well in advance. We track the versions your system depends on, test the replacement against your real cases, and ship the change before the old version disappears. The failure mode without maintenance is discovering the drift when a user notices the answers changed.

Scope, people, and terms. Classic AMS is a ticket queue across your whole software estate, staffed by whoever is on shift, on a multi-year contract. This is application support services for one purpose-built system: the people who built it take the escalations, the scope is the system and its AI models, and the arrangement is monthly and cancelable.

Three things: health (is the system up and answering), cost (what the model usage is running, so the bill never surprises you), and security (vulnerability findings on the stack, with patches applied on an agreed schedule). Where it makes sense, monitoring lands in your own dashboards so your team sees what we see.

A flat monthly figure agreed up front — no question-mark price tag, no percentage-of-estate pricing. It’s cancelable: the documentation and training we deliver make the system genuinely yours, so staying with us is a decision you make every month, not a dependency we engineered.

Then that’s what you get. Every build we deliver comes with documentation, training, and a walkthrough with whoever will own it internally — the “keys in your pocket” version. The maintenance structure exists because buyers ask for it, not because the tool needs us to keep running.