Skip to content

Software maintenance and support services

Ongoing Development and Maintenance for Software You Rely On

Software needs care after launch: updates, fixes, security patches, and new features as your business changes. We keep it healthy and moving forward, month to month, and either side can end it with 30 days' notice.

How it's priced

A short form. We reply within one business day, Eastern Time.

At a glance

First step
A fixed-fee technical review, for software we didn't build
Terms
Month to month, 30 days' notice
Every change
Code-reviewed and covered by tests
Your code
In your repositories and accounts

Signs your software needs a maintenance plan

Most software problems start small and quiet.

  • Updates and security patches keep slipping because nobody owns them.
  • Small bugs pile up, and your team works around them.
  • The developer or agency who built it has moved on.
  • You have a list of improvements, but nobody to build them.
  • An outage or a failed update would hurt your business, and nobody is watching for one.

Options

Three ways to keep your software moving

Pick the level of help you need.

Maintenance and support

Updates, fixes, monitoring, and small improvements that keep your software healthy and current.

Ongoing development

Monthly development time for new features and larger improvements, planned with you.

Dedicated development

Development time reserved for your product each month, for software that keeps growing.

What maintenance covers

The routine work that keeps software healthy

We also look after software other teams built, after a fixed-fee technical review.

Framework and library updates

Keeping the platform your software runs on current and supported.

Security updates

Updates that fix known security issues in the libraries and frameworks your software uses.

Bug fixes

Finding and fixing problems, each one reviewed and tested before release.

Monitoring

Watching for errors and outages, so problems are noticed early.

Small improvements

The steady list of tweaks that make software easier to use.

Mobile OS updates

Keeping iOS and Android apps working as Apple and Google release new versions.

Deliverables

What you get

  • A monthly arrangement that runs month to month, with 30 days' notice to end it
  • Updates, fixes, monitoring, and small improvements
  • Every change made in your repositories and hosting accounts
  • One day-to-day contact who knows your software

On every project

  • Working software to see and try every 1 to 2 weeks
  • Code review and automated tests on every change
  • Accounts in your name, and work that's yours as each invoice is paid

Process

How ongoing work runs

  1. 01

    Technical review (fixed fee)

    For software we didn't build, we review the code, the hosting, and open issues first, and you get a written plan and estimate.

  2. 02

    Agree the monthly plan

    We agree what's covered each month: maintenance, development time, or both.

  3. 03

    Work you can see

    You see progress in working software every one to two weeks.

  4. 04

    No long commitment

    Ongoing work runs month to month, and either side can end it with 30 days' notice.

Scoping and pricing

How ongoing work is priced

Maintenance and ongoing development are billed monthly. The amount depends on the software and how much work you need.

There's no long contract: either side can end ongoing work with 30 days' notice.

How we scope and price projects

What moves the cost

  • The size and age of the codebase
  • How many integrations and outside services it relies on
  • How much new development you want each month
  • How critical the software is to your daily operations

FAQ

Questions about Ongoing Development & Maintenance

What does a maintenance plan include?

Updates, security patches, bug fixes, monitoring, and small improvements. Larger features fit under ongoing development.

Can you maintain software another team built?

Yes. We start with a fixed-fee technical review, so we both know the state of the code before we commit to looking after it.

Is there a long contract?

No. Ongoing work runs month to month, and either side can end it with 30 days' notice.

What happens to our code if we stop?

Nothing needs to be handed back: the code is in your repositories, the software runs in your hosting accounts, and the work becomes yours as each invoice is paid.

Tell us about the software you need looked after

What it is, who built it, and what needs attention. A few sentences are enough to start.

We reply within one business day, Eastern Time.