Maintenance retainer or pay as you go? Compare what is actually covered
A small-site decision guide with break-even arithmetic, exclusions and a recovery checklist.
| Question | Monthly retainer | Pay as you go |
|---|---|---|
| Predictability | A regular bill for the stated scope. | Spending varies with the work requested. |
| Response | Use the written response commitment. | Availability may depend on current workload. |
| Included tasks | Check updates, backups, edits and limits. | Agree each task and estimated hours. |
| Unused time | May expire; check rollover terms. | There may be a minimum charge per request. |
Define maintenance before pricing it
Maintenance can mean software updates, uptime checks, backups, content edits or emergency recovery. A plan called “complete care” may include only some of those. List the jobs your site needs and assign an owner to each. For a small service site, checking the enquiry form and keeping business details correct may matter as much as a software update. Neither a recurring invoice nor an occasional payment proves the work has been completed.
Worked example: the arithmetic threshold
Imagine a retainer of $40 per month and an hourly alternative of $25, with identical scope and no minimum charge. The retainer costs $480 per year. Dividing $480 by $25 gives 19.2 hours per year, or 1.6 hours per month. If you use ten hours, hourly spending would be $250; at 24 hours it would be $600. These invented figures demonstrate the method, not typical rates. The comparison stops being equivalent if the retainer excludes work, caps hours or includes monitoring that is not included in the hourly option.
Response time can matter more than hours
A retainer may reserve support capacity, but only rely on the commitment written into the agreement. Distinguish acknowledgement time from resolution time. Ask what happens outside normal working hours and who pays for an incident caused by an unsupported extension or hosting outage. A brochure website and a transaction-heavy service may reasonably choose different levels of response coverage.
Look for evidence of routine work
Ask for a short maintenance record: updates completed, checks performed, issues found and the date of the latest successful recovery test. Confirm whether backups cover files and databases, where they are kept and how long restore points remain available. A report containing only “all good” is difficult to evaluate. Request enough evidence to understand the work without expecting sensitive logs or passwords in an ordinary email.
Keep access and handover clear
The business should retain control of its domain and hosting accounts. Agree the access a maintainer needs and how it is removed at the end of the relationship. Record whether backup exports and documentation will be handed over, and whether the plan renews automatically. If your site uses paid software, establish who owns its licence and what happens when the maintenance arrangement ends.
Choose a plan you can review
Estimate likely tasks over a year, compare equivalent scope, and identify the consequences of waiting for help. If the work is genuinely occasional, hourly support can be practical. If predictable coverage and routine checks are valuable, a retainer may fit. Review actual use after a few months rather than treating either option as permanently best. Our maintenance calculator separates cash spending from the value of your own hours.
Our examples use the assumptions stated on this page. Read our calculation methodology and editorial policy, or send a correction.