Business software · 3 min read
Software maintenance: what support should cover
Software maintenance keeps an existing system usable as dependencies, security needs and business conditions change. Support helps users resolve incidents. Agree what each covers, when help is available and who owns recovery; hosting alone is not a complete support arrangement.
By Raja Wahab, Co-founder, Fixby Studios · Published · 3 min read
Separate four different services
Hosting provides the environment in which software runs. Maintenance includes updates and preventive work. Incident support deals with something that has gone wrong. Product development adds or changes behaviour. A quote labelled support can mean any combination of these.
Ask for examples of included and excluded work. Changing a button label, fixing a defect and adapting to a third-party API change may be treated differently by a supplier.
Questions for the support agreement
| Topic | What to clarify |
|---|---|
| Availability | The hours and channels through which issues are accepted |
| Priority | How a total outage differs from a minor inconvenience |
| Response | When someone begins assessing the issue |
| Resolution | Whether a fix time is promised or only a target |
| Updates | Which dependencies and environments are maintained |
| Recovery | Who restores data and tests backups |
| Reporting | How incidents and completed work are recorded |
Response time is not resolution time
An acknowledgement in an hour does not mean the system will be fixed in an hour. Some incidents depend on external services or require careful data checks. Ask what happens during an extended incident and how you will receive updates.
Choose support hours based on when the system matters. A tool used only during office hours has different needs from a customer service relied on overnight.
Budget from the actual system
There is no universal maintenance percentage that fits every project. Costs vary with integrations, usage, infrastructure and the level of cover. Request an itemised recurring estimate and a clear method for approving additional work.
Track actual support needs after launch and review the arrangement. Underfunded support can leave important updates undone; an oversized package can pay for coverage the business does not need.
Make recovery testable
A backup existing is not proof that it can be restored. Agree the restoration process, how often it is rehearsed and the amount of recent work the business could tolerate losing. Record who can access the necessary accounts if the usual contact is absent.
Keep handover possible
Maintain current account ownership, documentation and release instructions. Another developer should not have to reverse-engineer the entire system to apply an urgent fix. Good support reduces dependence on one individual rather than increasing it.
Sources
Raja Wahab is co-founder of Fixby Studios, a Huddersfield studio building websites, SEO, social media and business software for small, owner-managed businesses across West Yorkshire.
Next step
Let's get your business seen.
Get a free Blueprint with a clear plan, honest pricing and no jargon.
Tell us which task takes too much time and we'll assess a focused software or automation project. Business software and automation
Prefer to talk it through? Contact Fixby Studios, email info@fixbystudios.co.uk or call 07737 067552.