monthly support

Support retainer

When production breaks or a dependency needs urgent patching, there's nobody to call.

The problem

Small teams rarely have someone whose job is to keep production healthy. Alerts go unread, packages fall behind on security updates, and when something breaks, the person who understands it may be on holiday or long gone. After a project ends, the people who built the system walk away with the knowledge.

How we approach it

  • Agreed response times. You know how quickly we'll pick up a production issue, written into the contract and set at a level we can always keep.
  • A monthly health review. We go through your dashboards, alerts, error trends, cloud costs and upcoming support deadlines, and send you a short report with anything that needs action.
  • Updates before they become incidents. Runtime, package and security updates applied and tested on a regular schedule, not after an audit finds them.
  • Hours when you need them. A set number of support hours each month for fixes, small changes or advice, with unused hours visible in every report.
  • Continuity. The same senior engineers handle your system every month, so nothing needs explaining twice.

It works best for systems we've built or reviewed, so we usually start with a Health Check if we don't know your setup yet.

What you get

  • A named contact and agreed response times
  • A monthly health report with recommended actions
  • Security and dependency updates kept current
  • Support hours for fixes and small changes

How we scope it

A monthly retainer with a fixed number of hours and agreed response times. It starts after a Health Check or a completed project, and can be ended with a month's notice.

questions

Support retainer: common questions

What does a support retainer include?

Agreed response times for production issues, a monthly review of dashboards, alerts and costs, dependency and security updates kept current, and a set number of senior support hours each month.

Which systems do you support?

.NET applications, Azure and AWS infrastructure, data platforms and integrations, including systems we didn't build. We start with a short onboarding review of your system.

What if we need more hours in a month?

We agree up front how extra hours are handled, so a busy month never brings a surprise bill.