Software maintenance is the ongoing work of keeping software running, secure and useful after it has gone live. It covers fixing defects, applying security updates, adapting the software as the world around it changes and making small improvements over time. Support is the related help given to the people using it.
What software maintenance and support means
Launch day is not the finish line. Once your bespoke software is live and people are using it, a second phase of work begins: keeping it working. That work is software maintenance.
Maintenance is the technical side: changes made to the software itself. Support is the human side: helping the people who use it, answering their questions and logging the problems they hit. The two are bought together because they feed each other, and a support call often ends in a maintenance fix.
This phase is the longest part of a system's life. The UK Government's Service Manual describes a live service as one that is continuously iterated and improved, never simply "done". Good software is looked after, not just built.
The four types of software maintenance
Maintenance is not a single activity. The international standard ISO/IEC 14764, which covers software maintenance, groups the work into four recognised types. In plain English:
- Corrective: fixing defects. Something is not behaving as it should and the fault is put right.
- Adaptive: keeping pace with change outside the software, such as a new regulation, a new integration, a new browser or a new device.
- Perfective: small improvements. Refining features, tidying the interface or speeding things up in response to how people actually use the system.
- Preventive: work done before anything breaks, to head off future problems and reduce the build-up of avoidable complexity.
A healthy maintenance arrangement covers all four. A supplier who only ever does corrective work is firefighting, not maintaining.
What a support agreement and an SLA cover
Maintenance and support are usually bought through a support agreement: a contract, often renewed annually, that sets out what help you get, how fast and at what cost. It is worth reading as carefully as the original build contract.
Inside that agreement sits the service level agreement, or SLA. The SLA is the promises part. It states the hours support is available, how you report a problem and, most importantly, the response and fix times the supplier commits to for different severities of issue. A system being down is treated more urgently than a cosmetic glitch.
A clear SLA also says what is included in the fixed fee and what counts as a chargeable change, so a new feature request is never confused with a bug fix. A thorough agreement also addresses what happens if the supplier ceases trading, which is where source code escrow can protect your access to the software.
Support tiers a buyer might be offered
Most suppliers package support into tiers, so you pay for the level of cover your software actually needs. The labels vary, but the ladder is usually similar.
- Basic: security updates and fixes for serious defects, with support during office hours. Suitable for a system that is useful but not business-critical.
- Standard: faster response times, a set allowance of small changes each month and a named contact. The common choice for software a team relies on daily.
- Premium: the quickest response times, extended or around-the-clock cover and priority handling. Aimed at software the business genuinely cannot run without.
There is no single right tier. Match it honestly to how much it would cost your business if the software stopped working for an afternoon.
Why bespoke software is never truly finished
Bespoke software does not wear out like a machine, but it does not stand still either. The world around it keeps moving: security threats evolve, the browsers and devices people use are updated, the law changes and your own business needs shift.
Software left untouched slowly falls behind all of this. It becomes less secure, harder to use and more expensive to change later. Neglected long enough, a working system turns into a legacy system that is risky and costly to modernise.
Maintenance is what prevents that. A small, steady investment keeps the software you commissioned a working asset across its whole life, rather than a one-off purchase that quietly decays. It is the closing, ongoing stage of the software development lifecycle.
Good software is looked after, not just delivered Commissioning custom software is the start of a relationship, not the end of a transaction. Red Eagle Tech's bespoke software development service includes clear, plain-English maintenance and support so your system stays secure and useful long after launch. If you would like to talk an idea through, the form below is the place to start.
