Free checklist Book a call →
Home/ Solutions/ Application maintenance and support

Grow

Application maintenance and support

This is the "we run" half of what we do. Monitoring on your live application, fixes with agreed response targets, security updates, a small amount of improvement work each month, and a written report so you can see what happened.

Book a call → Get the CTO checklist

What this covers

Application maintenance and support, end to end.

Monitoring and alerting

We watch uptime, errors and the things that matter in your application. Alerts reach us, not just a dashboard nobody opens. When something breaks at 2am, the first person who knows is us rather than your customer.

Fixes with response targets

Every retainer has agreed response times by severity. A checkout that is down is not the same as a misaligned button, and the targets reflect that. You know what you get before you sign, not after something goes wrong.

Security updates and patching

Dependencies, frameworks, plugins and platform versions get updated on a schedule rather than when something forces the issue. Where an update carries risk we test it first and tell you what changed.

Monthly improvement work

A retainer includes hours for improvements, not only repairs. Copy changes, a new CMS field, a slow page made faster, a small feature. You decide the priority each month; we do the work.

Backups and rollback

We keep backups and we test that they restore. Every change we ship can be reversed. This matters most for AI agents and copilots, where a prompt or model change needs a way back if behaviour shifts.

A monthly report you receive

One document each month: uptime, what broke and why, what we fixed, what we improved, what we patched, and what we recommend next. Written in plain English, sent to you whether or not you ask for it.

How it runs

Plan. Build. Run.

01

Thirty minute call

You tell us what the application is, what it runs on, and what has gone wrong in the past. We ask what downtime actually costs you. No forms and no discovery invoice before we have spoken.

02

Handover and audit

We take access, read the code, map the hosting and integrations, and write down what we find. If there are risks already present we say so now rather than discovering them during an incident.

03

Fixed scope and price

You get the response targets by severity, the monthly improvement hours, what is covered and what is not, and the price. One page. Nothing changes without you agreeing to it first.

04

We run it

Monitoring goes live, patching starts, and improvement work runs each month. The report arrives monthly. If the application outgrows the retainer we tell you and re-scope it.

Why infoloop

We do not hand over and leave.

  • We run what we buildRunning live software is our second half, not an afterthought sold on at the end. The people who maintain your application are the people who build applications every day.
  • Response targets in writingSeverity levels and response times are agreed before the retainer starts and written into it. You are not relying on goodwill or on how busy we happen to be that week.
  • You get a report without askingThe monthly report goes out on schedule. Uptime, incidents, fixes, patches, improvements. You do not have to chase anyone to find out what you paid for.
  • We take on other people's codeYou do not have to have built it with us. We audit what exists, say plainly what state it is in, and take it on from there.
  • Production experience with AIWe put AI agents and copilots into production with guardrails, monitoring and rollback. If your application includes one, maintaining it is not new territory for us.

What you get

Every engagement includes these, in writing, before work starts.

  • Uptime and error monitoring with alerts routed to us, not to an unwatched dashboard
  • Agreed response-time targets by severity, written into the retainer before it starts
  • Scheduled security patching across dependencies, frameworks, plugins and platform versions
  • A set number of improvement hours each month, prioritised by you
  • Tested backups and a documented rollback path for every change we ship
  • A monthly written report covering uptime, incidents, fixes, patches and recommendations

Who this is for

Three situations where this is the right call.

The agency handed over and left

The build is finished, the team that made it has moved on, and nobody owns the application now. Things break and there is no one to call. You need a named team that holds it going forward.

Something is live and nobody is watching it

The application works, so far. There is no monitoring, patching has not happened in a year, and you find out about problems when a customer emails. You want that reversed before it costs you.

One internal person carries all of it

A single developer or operations person holds the whole application in their head. They cannot take leave without risk, and you have no cover if they go. A retainer gives you a second pair of hands and written documentation.

Proof

Software we built, and still run.

We run: the managed retainer

Read it →

What a retainer should include

Read it →

What is a managed retainer?

Read it →

Questions

What buyers ask us first.

What does an application maintenance retainer from infoloop cost?
Price depends on the application, how it is hosted, the response targets you need and how many improvement hours you want each month. We do not publish a rate card because a Webflow marketing site and a production AI copilot are not the same commitment. The shape is always the same: a thirty minute call, then a fixed scope, timeline and price in writing before any work starts. The retainer states what is covered, what is not, and what happens if the application outgrows it. Nothing is charged that you have not agreed to in advance.
How quickly do you respond when something breaks?
Response times are agreed per retainer and set by severity, so an application that is down is treated differently from a cosmetic problem. Those targets are written into the agreement before it starts rather than being decided during an incident. Monitoring means alerts reach us directly, so in most cases we are already looking at the problem before anyone on your side has reported it. We record incidents and their resolution in the monthly report, so you can see over time whether the targets are being met.
What happens after launch, and does maintenance start straight away?
When we build something, the run phase follows the build phase directly. There is no gap where the application is live and unowned. Monitoring is configured before launch, so the first day in production is already covered. If we did not build it, the retainer starts with a handover and audit: we take access, read the code, map the hosting and integrations, and write down what we find, including anything already at risk. Only after that do the response targets and improvement work begin.
Will you maintain an application that somebody else built?
Yes. Most maintenance work arrives that way, usually when the original agency has handed over and moved on. We begin with an audit: what the application is built on, how it is hosted, what is out of date, what is undocumented and what is fragile. We give you that assessment in plain English before you commit to a retainer, including anything we think should be fixed first. If we think the application needs rebuilding rather than maintaining, we say so.
What is actually in the monthly report?
Uptime for the period, any incidents with what caused them and how they were resolved, the fixes we made, the security updates and patches we applied, the improvement work we completed against the hours available, and what we recommend doing next. It is written in plain English rather than as a list of ticket numbers. You receive it on schedule each month without having to ask for it, which is the point: you should be able to see what you are paying for without chasing anyone.
Can you maintain AI agents and copilots, not just websites?
Yes. We put AI agents and copilots into production with guardrails, monitoring and rollback, and maintaining them is part of the same work. It differs from maintaining a normal application because behaviour can drift when a model, a prompt or the underlying data changes. So the monitoring covers behaviour as well as uptime, and every change to a prompt or model has a tested way back. We also maintain Webflow and Shopify sites, headless CMS setups including Webflow CMS and Strapi, and the systems we build.

Related

You might also need.

Performance Marketing Services

Paid acquisition measured against pipeline, not impressions.

See more →

eCommerce Growth Solutions

Merchandising, retention and checkout work that moves store revenue.

See more →

UX Optimization & Accessibility

Making the journey faster to complete and usable by everyone.

See more →

Tell us what is live and who is watching it

Thirty minutes on a call. Tell us what the application is, what it runs on and what has broken before. You get back a fixed scope, response targets and a price in writing. No obligation to go further.

Book a call → Get the CTO checklist
Book a call Checklist