Skip to content
COGNIVISE
Running software

What should software support cover after launch?

Support and maintenance get written into contracts as one line and then mean different things to each side. Here is what each actually covers, and what to settle before you need it.

Published Updated 2 min readView as Markdown
On this page · 5 sections
  1. 01They are two different things
  2. 02What is normally included
  3. 03What does a well-handled incident look like?
  4. 04What about out-of-hours cover?
  5. 05Terms, pricing and ownership

They are two different things

Maintenance keeps the software healthy: security patches, dependency updates, fixing defects, keeping it running as the platforms underneath it change. It happens whether or not anyone reports a problem.

Support is what happens when someone does report one: triage, diagnosis, a fix or a workaround, and telling the person who reported it what is going on. It is reactive by definition.

A contract that says "support and maintenance" without separating them is where the arguments start. One side means "you will answer the phone", the other means "we will apply security updates".

What is normally included

Security and dependency updates
Libraries and platforms release fixes constantly. Software that is not updated does not stay still — it gets less secure while sitting untouched, which is how systems drift into legacy software.
Monitoring and alerting
Knowing something is wrong before a customer tells you. If nobody is watching, your monitoring is your users.
Defect fixes
Things that were meant to work and do not. Worth writing down explicitly, because this is the line most often disputed.
Small improvements
Changes that are too small to be projects. Usually capped as a block of time per month, which is a reasonable way to handle it.
New features
Normally not included. If your agreement does not say so, assume both sides think the other is wrong about it.

What does a well-handled incident look like?

  • It is acknowledged quickly, and you are told who is working on it.
  • You get updates at an agreed interval, even when the update is that nothing has changed.
  • The service is restored first, by a fix or a workaround, and the lasting fix follows.
  • Afterwards you receive a short written account of what happened, why, and what will stop it recurring.

What about out-of-hours cover?

Decide whether your software needs it. A tool used only in office hours may not. A shop or booking system that takes orders overnight may. Ask what the supplier's hours are, whether urgent help is available outside them, how it is reached, and whether it costs extra. Do not find out on the night.

Terms, pricing and ownership

Who owns the code and the accounts, how support is priced, how you check it is working and what to agree before launch are contract questions, and they have their own guide: software maintenance contracts: what a fair one includes. If you would rather have someone run support for you, see application support and maintenance.

More from the blog

Next step

Tell us what you are trying to build

Tell us what you need built, or who you need to build it, and we'll tell you plainly if we're the right people.