Software Maintenance Contracts, Explained Plainly

"Maintenance included" means different things to different vendors, and the gap between expectations and the fine print is where most disputes start.

What should be covered

Security patches, bug fixes for existing functionality, and compatibility updates when a third-party service or OS changes underneath you — this is the baseline of keeping a system healthy, not a bonus.

What's usually a separate line item

New features, design changes, and scope expansions are typically billed separately from maintenance — a good contract makes this distinction explicit so there's no argument later about what counts as "a fix" versus "a new feature."

Response time matters more than people think

A maintenance contract should specify actual response time commitments for critical issues (a payment system down) versus minor ones (a typo in a footer) — vague "we'll get to it" language isn't a real commitment.

What to ask before signing

What's the escalation path if something breaks on a weekend? Is there a cap on included hours, and what happens once you exceed it? Get these answered in writing.

Reviewing a maintenance contract, ours or someone else's? Ask us — we're happy to explain what's reasonable to expect.