Compare support retainers and ad hoc development using reserved capacity, response expectations, preventive work, rollover rules and change control.
A maintenance retainer and pay-as-you-go development solve different scheduling problems. A retainer may reserve capacity and recurring attention; ad hoc work is purchased when a task arises. Neither label guarantees availability, response time or unlimited work. Compare the actual obligations and the cost of waiting when an important system fails. The right choice depends on how predictable your workload is and how much interruption the business can tolerate.
Describe the work you actually need
Review recent incidents, dependency updates, content changes and feature requests. Separate preventive maintenance from reactive support and planned development. Identify work that requires continuous familiarity with the system, such as release ownership or integration monitoring. Then estimate the arrival pattern, not just total hours. Several urgent requests in one week create a different capacity problem from the same effort spread across a quarter.
Read the capacity terms
For a retainer, establish reserved time, response coverage, included work, priority rules and what happens when demand exceeds the allowance. Clarify unused capacity, rollover, cancellation and reporting. For ad hoc work, ask how requests are queued, estimated and approved, and whether an urgent request has any guaranteed availability. A low hourly rate can be poor value if the needed engineer cannot start when the business requires help.
Compare three realistic months
- A quiet month with preventive updates and routine checks: what work occurs without an incident?
- A normal month with small changes and one defect: how are priorities and approvals handled?
- A difficult month with an outage and a provider upgrade: which capacity is reserved and what becomes additional work?
- For each scenario, include internal coordination time and the consequence of waiting, not only the supplier invoice.
Choose a reviewable arrangement
A hybrid agreement can reserve a small operating capacity while quoting larger projects separately. Make the boundary explicit so new features do not consume all preventive work unnoticed. Review usage, unresolved risks and response outcomes after a meaningful period. Adjust capacity to evidence rather than buying an arbitrary bundle forever. The best arrangement gives the business a predictable way to keep the system healthy and obtain help, with clear visibility into what the recurring commitment does and does not purchase.
- Maintenance and support
- Software Support SLA: Response, Resolution and Exclusions
- Software Handover to a Maintenance Team: An Acceptance Checklist
Compare the full cost of two options
Model implementation, migration, recurring operations and exit costs over the same horizon. Enter your own quotes and assumptions for each option.
Enter all costs for both options. Use 0 for costs that do not apply.
Your inputs are planning assumptions, not market prices. Contingency applies to implementation and migration only. Recurring costs increase every 12 months; exit cost occurs at the end. Discounting assumes month-end payments. Taxes, revenue, financing and currency conversion are excluded. Cost crossing is not a return-on-investment forecast.
Frequently asked questions
Does a retainer mean unlimited support?
No. Capacity, coverage, included work and overflow rules must be stated explicitly.
Is pay-as-you-go always cheaper?
Not necessarily. Consider availability, coordination and the business cost of delay alongside hourly charges.
Can unused hours roll over?
Only if the agreement allows it. Clarify expiry, limits and whether capacity rather than hours is being purchased.
Can we combine both models?
Yes. Reserved maintenance can coexist with separately scoped features or larger improvements.
When should we review the arrangement?
After enough operating history to compare planned capacity with actual demand, response outcomes and unresolved maintenance work.
Bring the scope. We will help make it buildable.
Share the user journey, integrations and launch constraints. We can clarify the scope and prepare an estimate with assumptions and exclusions.
Further reading
Software support SLA: define response and restoration
Write a practical software support SLA with severity examples, coverage windows, response obligations, restoration goals, exclusions and escalation.
Software maintenance handover: prove the team can operate
Transfer software maintenance with verified access, reproducible releases, dependency ownership, recovery exercises and a signed exception register.
Website maintenance checklist for business-critical sites
Organise website maintenance around critical journeys, recoverable backups, controlled updates, access reviews and evidence of completed work.