What a website maintenance retainer really pays for

A maintenance retainer is not automatically wasteful. A busy WordPress store, membership site, or booking system genuinely needs updates, backups, security monitoring, and someone responsible when integrations fail. A five-page static brochure site does not have the same moving parts.

The problem is paying a recurring fee without knowing which risk or workload it covers.

What legitimate maintenance includes

For a dynamic site, a useful plan may include:

• tested core, theme, and plugin updates
• off-site backups plus a documented restore test
• uptime and security monitoring
• malware cleanup responsibility
• a staging copy for risky changes
• a defined number of content edits
• response times for ordinary and urgent requests
• monthly evidence that the work happened

“Keeping the site online” is not a deliverable by itself. Hosting, software maintenance, and content changes are separate jobs even when one supplier bundles them.

The static-site alternative

A static site has no database, admin login, or server-side plugins. Cloudflare serves finished files. That removes most of the recurring update surface behind traditional maintenance plans.

It does not remove every task. Someone still needs to own the domain, renew it, update content, monitor forms, keep account recovery current, and preserve the source files. Those tasks are usually periodic, not a monthly retainer.

Fair versus inflated

A fair retainer answers five questions in writing:

1. What exact work happens every month?
2. What is excluded?
3. What response time is promised?
4. Who owns the accounts, source code, licences, and backups?
5. How can either side end the arrangement?

Warning signs include bundled “SEO” with no named work, a refusal to provide administrator access, backups that only the agency can restore, unlimited-change claims with hidden queues, and a domain registered in the supplier’s name.

Do not judge the plan by its monthly figure alone. Judge the workload, the business impact of downtime, and whether an independent provider could take over using the assets you receive.

When the paid option is justified

Pay for ongoing support when at least one of these is true:

• the site processes orders, payments, memberships, or sensitive records
• several plugins or third-party systems must remain compatible
• downtime has an immediate measurable cost
• staff make frequent content changes and need a service desk
• regulations or contracts require tested recovery controls

For a brochure site changed a few times a year, buy changes as needed or learn the simple publishing workflow. The free route is static hosting plus a quarterly ownership and recovery check.

Exit checklist

Before ending a retainer, collect:

• registrar and DNS access
• hosting administrator access
• source repository or a complete source archive
• a current database and media backup where applicable
• licences and a list of renewal dates
• analytics, form, email, and payment ownership
• the build and deployment instructions
• an inventory of open problems

Use the full digital ownership checklist. If the supplier cannot hand over what your business paid to create, resolve ownership before cancelling the only account that keeps the site running.