Skip to content

Website and application maintenance

Our website maintenance services keep your site or web application updated, backed up and monitored on a monthly plan, with small changes handled as they come up, including software someone else built.

Software needs care after launch. Libraries need security updates, backups need testing, and connections to other systems break when those systems change. A monthly plan means someone is responsible for all of it, and you have one place to send requests.

Maintenance and support
Illustration of maintenance and support work, with sample content

For example: a monthly plan for a site someone else built, where updates, backups and small changes happen without you chasing anyone.

An illustration of the kind of work we do, not a client project.

Your site today

Before
Last updateNobody is sure
BackupsNever checked

Customer: Who can change the banner on the home page?

This month’s plan

After
Security updatesApplied
BackupTaken and restored in a test
MonitoringOn
Small changeBanner updated

What website maintenance includes

  • Security and dependency updates

    Frameworks, plugins and libraries kept current, and tested before each update goes out.

  • Bug fixes

    Problems found by you, your customers or our monitoring, fixed and checked.

  • Backups, tested

    Regular backups, and a test restore so you know they actually work.

  • Monitoring

    Uptime and errors watched, so problems are noticed before your customers report them.

  • Small changes and content updates

    New pages, banners, text and image changes, handled as requests come in.

Want this for your business?

Tell us what you need. A founder reads every enquiry and replies with questions or a proposed scope.

Start a project

Who it’s for

  • Businesses after a launch

    Whoever built the software, someone needs to keep it updated and working.

  • Sites and apps nobody is looking after

    No updates, no tested backups and no one to call when something breaks.

  • Teams with a steady flow of small changes

    Regular updates without hiring a full-time developer.

What you get each month

Each month you see what was done, and the accounts and records stay in your name.

Handover record Checked by a reviewer
  • A monthly summary of the updates, fixes and changes made
  • Backup and test-restore records
  • Monitoring alerts sent to your named contact
  • An up-to-date list of the accounts and services the software uses
Illustration of a handover record

What we need from you

A project moves fastest when these are ready. We help you put together anything you do not have yet.

  1. 1Access to the code, hosting and domain
  2. 2Any notes on how the software was built and deployed
  3. 3A named person to send change requests
  4. 4A first review of the current state, before the plan starts

How an engagement runs

  1. Scope document

    Scope: customer portal

    What we deliver

    • Customer sign-in, with roles
    • Order status page
    • Invoice downloads
    Not includedMobile appDone whenTested with your real orders

    Agreed by you before the build starts

  2. This week’s build

    This week’s increment

    Order status page

    Ready to view

    feat: order status page

    test: status for each order type

    docs: how statuses are calculated

    Next increment: invoice downloads

  3. Review checkpoint
    Our reviewer
    • Checked against the scope
    • Tests read and run
    • Ready for you

    Your approval

    Approve milestoneRequest changes
  4. Handover pack

    Code repository

    In your account

    Credentials record

    Transferred to you

    Documentation

    What was built and how

    Runbook

    Deploy, roll back, fix common problems

    Maintenance available on a monthly plan

What affects the cost

We quote after a scoping conversation, so there is no fixed price on the site. These are the factors that move the cost of this work up or down; the proposal states the scope, what is not included and the price.

Technologies we commonly use

  • Websites and content management systems
  • React and TypeScript applications
  • Python applications
  • Cloud hosting
  • Backups and uptime monitoring
  • Payment and messaging integrations
Size and age of the software
Older software with outdated libraries needs more work to keep safe.
Number of changes each month
How many small changes and content updates you expect.
Monitoring and response
How quickly problems need attention, and outside which hours.
Hosting and integrations
How many connected systems and services need checking.

Questions

Usually, yes. We review the existing code and hosting first, then tell you what a maintenance plan would cover and anything that needs fixing before it starts.

Tell us what you want to build.

Describe the work. We will scope it with you, or tell you plainly if it is not work we should take on.