What a Fair Website Support Retainer Should Include
Short answer: A fair website support retainer covers the routine care that keeps a site safe and working: software updates, backups, uptime and error monitoring, a set number of small edits each month and a stated response time for faults. It should also name the hours or edits included, the rate for anything beyond them and the things it does not cover. Be wary of plans that promise unlimited edits or "whatever you need" without limits, because those terms usually shift the cost onto the client later. Ask for a monthly report so you can see what was done.
Start with what the site runs on
A retainer should match the technology underneath your site. A static brochure site built with a basic content tool needs fewer updates than a shop with a payment gateway, a booking system and a customer login. Before you compare plans, list the parts: the content management system, the theme or template, the plugins or extensions, the hosting, the email provider, the payment service and any custom code.
Picture a bakery in Dunedin (Kiln Street Bakery, an invented name) that runs an online order form with a payment provider and a weekly newsletter. Its retainer must cover the order form's updates, payment provider notices and email authentication settings. A plan written for a simple five-page site would miss most of that.
What routine care should include
Routine care is the work you should not have to ask for. A fair plan includes the following tasks, repeated at a set frequency.
- Software updates for the core system, themes, plugins and extensions, tested on a copy before they go live.
- Security checks such as reviewing login attempts and confirming the site certificate renews.
- Backups that run daily or weekly, are stored away from the host and can be restored within a stated time.
- Uptime and error monitoring that alerts the provider when the site is down or a form stops working.
- Performance checks each month, such as page load time for the main pages.
Ask whether each item is performed or simply available. A backup that exists but has never been restored is a risk, so ask for a restore test at least once a year.
Response times and fault bands
Faults are not all equal, so a fair retainer sorts them into bands. A typical structure is an urgent band for a site that is down or taking payments incorrectly, a standard band for a broken page or form, and a planned band for cosmetic changes. Each band should have a target response time and a target fix time, written in hours or business days.
The response time is a promise to reply, not a promise to fix. Ask the provider to state both, and to explain what happens if the fix needs a third party, such as a payment provider.
Monthly hours, edits and the fine print
Most plans include a set number of hours or a set number of edits each month. A small text change might take fifteen minutes, while a new page with images may take two hours. Ask the provider to define an edit in writing, and check whether unused time carries over. Many providers allow it to expire, which is worth knowing before you plan a seasonal campaign.
Watch for vague terms. "Unlimited edits" often has a fair-use clause that the provider can enforce at any time. "Priority support" may only mean the provider will answer first, not that the fix happens sooner. "Basic SEO" can mean anything from meta description checks to a full audit, so ask for a list.
Ask for a monthly report
A monthly report makes the retainer visible. It should list the updates applied, the backups taken, any incidents and their fix times, the edits used and the hours left. Ask for it to be sent on a fixed date, such as the first working day of each month. If a provider cannot produce one, you have no way to judge whether the money is being well spent. Read the first report closely in the first two months, and compare it with the plan. Gaps between what was promised and what appears in the report are the cue to raise the issue early, while it is still easy to fix.
A simple comparison of plan features
| Feature | What to look for | Warning sign |
|---|---|---|
| Updates | Tested before going live | "We update when we can" |
| Backups | Stored off the host, restore tested | No mention of restores |
| Response time | Stated for each fault band | "As soon as possible" |
| Edits | Defined, with a monthly allowance | "Unlimited" with no fair-use terms |
| Reporting | Monthly, dated and itemised | Reports only on request |
| Exclusions | Listed in writing | Not mentioned |
Typical prices and what they buy
Prices for retainers vary by region, technology and the size of the site, and this article does not quote specific vendors. As a planning guide, compare plans by what each includes over a year, not by the monthly fee alone. A low fee with no monitoring, few hours and no restore testing may cost more when something breaks. A higher fee with clear hours, fault bands and a monthly report may be better value if it prevents one lost weekend of sales.
Questions to put to the provider
Ask them to walk through a real example: a payment form stops working on a Friday evening. Who gets the alert, what is the response time, what is the fix time, and is that covered by the monthly fee or billed separately? A clear answer shows that the plan has been used before. A vague answer suggests the plan has never been tested.
FAQ
Do I need a retainer if my site rarely changes?
Yes, for security and backups. A site that never changes can still be attacked, and the software behind it still needs updates.
Is a retainer the same as hosting?
No. Hosting provides the server and often the domain. A retainer covers the care of the site running on it. Some providers bundle both, so check which parts you are paying for.
What if I want to cancel?
Ask for the access, backups and documentation to be handed over on request, in a usable format, and confirm the notice period in writing.
Our enquiry form is the place to send a plan you are unsure about, and we will read it line by line.