Skip to content

Design and growth

Website and app maintenance that keeps things running

One plan for updates, security, monitoring, backups and the small changes that keep your product useful.

An engineer monitoring server dashboards across several screens

Overview

Updates, security, monitoring and small improvements for sites, apps and software.

Software starts ageing the day it launches. Operating systems update, plugins change, certificates expire and someone eventually asks for a small change that turns into a week of work because nobody remembers how it was built. A maintenance plan prevents that drift. We keep things updated and monitored, fix issues before customers notice, and use the remaining hours on improvements you choose.

What is included

  • Uptime and error monitoring
  • Security patches and updates
  • Daily off-site backups
  • Monthly health report
  • Bug fixes and small changes
  • Agreed response times

What you can expect

  • Fewer surprises

    Uptime, error and security monitoring alert us before customers notice a problem.

  • Always up to date

    Core, plugins, dependencies and OS targets updated on a schedule and tested on staging first.

  • Backups you have tested

    Daily off-site backups with regular restore tests, so recovery is a procedure, not a hope.

  • Steady improvements

    Unused support hours go towards small enhancements from a backlog you control.

How a maintenance and support project runs

The same four-stage rhythm we use on every engagement, tuned for this kind of work.

  1. Onboard

    Review the codebase, hosting, access and backups, and fix anything urgent.

  2. Stabilise

    Set up monitoring, alerts, staging and a regular update schedule.

  3. Maintain

    Apply updates, handle requests and resolve issues within agreed response times.

  4. Report and improve

    Share a monthly health report and use spare hours on your improvement backlog.

Tools and platforms we use

  • UptimeRobot
  • Sentry
  • Cloudflare
  • GitHub
  • WP-CLI
  • Firebase
  • AWS
  • Jira

Maintenance and support questions

What people usually ask before starting a maintenance and support project.

What does a maintenance plan include?

A typical plan covers security patches, core and dependency updates, uptime and error monitoring, daily off-site backups, bug fixes and a set number of hours each month for small changes. Response times and hours are agreed in writing, and you receive a monthly report of what was done.

Can you maintain a site or app built by another agency?

Yes. We start with a short onboarding review of the code, hosting, access and backups, and tell you about any urgent risks. After that, it is covered by the same plan as anything we built ourselves.

How quickly do you respond to problems?

Response times depend on severity and are set in your plan, for example within hours for a site outage and within one or two business days for a minor change. Monitoring often lets us start on outages before you report them.

Do unused hours roll over?

Unused hours can roll over for a limited period or be used on improvements from your backlog, depending on the plan. We agree this up front so there is no confusion at the end of the month.

Do you maintain mobile apps as well as websites?

Yes. App maintenance covers yearly iOS and Android updates, SDK and dependency upgrades, store policy changes, crash monitoring and small feature work, so the app keeps working and stays listed.

Can we cancel or change the plan?

Yes. Plans run month to month or quarter to quarter with a short notice period. If you leave, we hand over access, documentation and backups so the next team can take over smoothly.

Talk to us about maintenance and support

Tell us what you need. We reply within one business day with next steps, questions or a time to talk.

Chat on WhatsApp