guides

Software maintenance and support models explained

Support contracts are often bought on price and judged on the one day something breaks. The tier should be chosen against what an hour of downtime costs you.

Get project estimate Request a consultation

Outcomes

Define response time and resolution time separately
Match the tier to the cost of downtime, not to the build price
Security patching should be continuous, not on request
Include a monthly allocation for small improvements
Agree escalation paths and named contacts

Problems this solves

Support and improvement confused

Keeping the system running and making it better are different budgets with different response expectations.

Nothing monitored

Without alerting, users become the monitoring system and problems are found late.

Dependencies drift

Frameworks and libraries move; deferring updates creates a forced upgrade project later.

How delivery runs

01
Handover and baseline
Access, documentation and a documented current state including known issues.
02
Stabilise first
Security and reliability items before new features.
03
Monthly rhythm
Patching, dependency updates and a small release each month.
04
Quarterly review
Incidents, costs and the improvement queue reviewed together.

Realistic timeline

Weeks 1–2

Handover, access and monitoring in place.

Month 1

Security and stability backlog cleared.

Ongoing

Monthly releases and quarterly reviews.

What moves the price

Response target

The single biggest driver of a support contract price.

System complexity

More integrations means more failure modes to monitor and handle.

Retained development capacity

Hours reserved each month for changes rather than fixes.

Where projects go wrong

Single supplier dependency

Documentation and your own account ownership keep switching possible.

Unbounded scope creep in support

Separate the support agreement from the change budget explicitly.

FAQ

Questions buyers ask

What is a typical annual cost?+

12 to 20 percent of build cost for an actively used system, including patching and small changes.

Can we change tier later?+

Yes, usually at any renewal point or with 30 days notice.

Software Maintenance Cost

You already have the idea. Let's define what comes next.