Two companies offer monthly maintenance. One means hosting and updates; the other also includes help with user requests. Comparing the subscription totals alone tells you little.
Ask for a description of the everyday service. What happens routinely, what starts when you raise a ticket and which tasks require a separate order?
Separate four areas
Infrastructure covers where the system runs and the agreed administration. Technical maintenance may include updates, monitoring and backups. Support describes how you get help. Development covers changes to functionality and deserves a separate allowance.
The labels do not guarantee the scope. For backups, ask about restoring data and checking that recovery works. For updates, ask about compatibility testing and what happens if a new version causes a problem.
Understand the response clock
“Response within four hours” is an example of wording that needs clarification. Does it mean working hours? Is the response an acknowledgement, the start of investigation or a workaround? When should you expect service to be restored?
Describe several incident categories, such as a complete outage and a defect in a rarely used report. Agree how each is reported, prioritised and communicated. This is more useful than one impressive time commitment with an unclear meaning.
Find out how the allowance works
If the fee includes a bank of hours, establish which activities consume it, whether unused hours carry over and who approves extra work. Ask to see an example monthly activity report.
Finally, compare the cost over several years and the handover arrangements at the end of support. A clear maintenance description should answer an ordinary question: “If this problem happens tomorrow, who will handle it, and is it included in the price?”
Every number in this article, plus thousands of other contracts, is in the database.
Open the database