A software maintenance and support contract is the agreement that governs what happens to your software after launch — who fixes it when something breaks, how fast they respond, and what is included versus billed separately. Most Nigerian businesses sign these contracts without reading the terms closely, then discover the gaps only when something goes wrong and they are told it "falls outside scope." Understanding the standard terms before you sign protects you from that surprise.
What a Support Contract Typically Covers
Support contracts usually bundle a mix of bug fixes, security patching, hosting-related maintenance, minor updates, and a defined amount of support hours or response availability. What varies enormously between vendors is exactly where the line sits between what is included and what triggers an additional invoice.
Key Terms Worth Understanding
Response Time vs Resolution Time
These are not the same thing, and vague contracts blur them deliberately. Response time is how quickly someone acknowledges your issue — "we received your ticket." Resolution time is how quickly it is actually fixed. A contract promising "24-hour response" tells you almost nothing about how long you will actually be down. Ask for both figures, separately, in writing.
Uptime Guarantees
If hosting is included, look for an uptime percentage — commonly 99.5% or 99.9%. Understand what that actually means in downtime hours per month, and whether there is any compensation (service credit, fee reduction) if the vendor misses it. A guarantee with no consequence attached is not really a guarantee.
Scope of Support: Bug Fixes vs New Features
This is the single most common source of billing disputes. A bug is something that does not work as originally built and agreed. A new feature is something that was never part of the original scope. Vendors sometimes stretch the definition of "bug" narrowly to push more work into billable new-feature territory. A clear contract defines this distinction explicitly, with examples if possible.
Hosting and Security Patching
Confirm whether server updates, SSL certificate renewal, and security patching are included or separate. Unpatched software is one of the most common ways Nigerian business websites and systems get compromised — this should never be left ambiguous in a contract.
Renewal and Escalation Terms
Know how much notice you get before renewal, whether pricing can change at renewal, and what your escalation path looks like if the vendor becomes unresponsive. Contracts with automatic renewal at undisclosed future pricing are worth negotiating before you sign, not after.
Red Flags in Support Contracts
- No defined response or resolution times — everything is "as soon as possible"
- Vague scope language like "reasonable support" with no examples of what is and is not included
- No mention of what happens to your data or access if you decide to leave
- Pricing structures with hidden per-ticket or per-hour charges not disclosed upfront
- No named point of contact or escalation path beyond a generic support email
What a Fair Contract Looks Like
A well-structured support contract names specific response and resolution windows, clearly separates maintenance from new development, includes security patching as standard, and gives you a defined off-ramp if the relationship ends. It should read like an agreement between two parties with obligations on both sides, not a document designed to protect only the vendor.
At Harzotech, our IT support and maintenance plans are structured this way deliberately — clear tiers, defined response times, and no ambiguity about what a security patch versus a feature request costs. You can see how our support plans compare on our packages page.
If you are currently reviewing a support contract from another vendor and want a second set of eyes on the terms before you sign, book a consultation and we will walk through it with you honestly, whether or not you end up working with us.