15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →15% OFF ON ANY PLANUse code 15off4everClaim now →
Templates / Contract

Free Retainer Agreement Template

A retainer agreement covers the ongoing scope of service, service levels, payment terms, access, responsibility, handover, and how either side can end the arrangement.

Retainer Agreement template preview

Language:

en

Last updated:

October 2026

Share template

A site stays online until the night it doesn’t, and then the awkward bit starts: who responds, how fast, and what happens while orders and support messages stack up. This retainer agreement gives that moment a written answer, covering ongoing hosting and maintenance work, how incidents get handled, and how the service keeps running month to month.

The contract starts by pinning down what the retainer covers, then separates routine work from changes that need a separate quote. The middle sections answer the questions clients actually ask when something breaks: how severity gets assigned, where response times come from, what access is required, and what happens if an update causes a fault. The pages use muted violet with a brass-olive call-to-action, under Raleway headings and Inter body text, so the client reads the obligations before they get to the signature.

  • Scope of work Defines the monthly managed hosting retainer and lists what’s included, then draws a clear line around out-of-scope changes that must be described and priced before work starts.
  • Service levels Explains severity levels and how issues get triaged, with response times and after-hours coverage tied back to the accepted proposal or onboarding notes.
  • Payment Splits payment between setup work and the ongoing retainer, sets the 30/70 setup schedule, monthly invoicing timing, the 7‑day payment term, and what happens if invoices go overdue.
  • Handover and exit Spells out what gets provided at the end of the retainer, including a handover plan, exports and backup point confirmation, access removal, and stopping monitoring.
  • Ending this agreement Covers notice, what remains payable on termination, and includes the Signature block for acceptance.

Once the terms match your setup, you fill in your names, dates, and rates, send it, and the client signs online. The signed contract becomes the shared reference for billing, notice, and the handover steps if the retainer ends.

We went from spending hours on every proposal to creating fully customized ones in under 5 minutes. That's not an exaggeration - we timed it.

Yazan & Mawaheb
Yazan & MawahebAgency Owners

What to include in a retainer agreement

PartWhat it covers

It covers hosting, monitoring, updates, backups

Opens with what the service includes and how the retainer runs week to week, with the site list and any add-ons tied back to an accepted proposal or statement of work.

Scope of work

Lists the ongoing hosting and WordPress maintenance included each month and flags feature or design changes as out of scope, so any extra work gets described and priced before it starts.

Service levels

Defines severity levels and how response commitments get set, with after-hours coverage and any service credit or fee adjustment if a service level is missed.

Payment

States how setup work and the ongoing retainer get invoiced, the 7-day payment window, and when non-urgent work may pause if payment and contact can’t be resolved.

Price review

Explains how the retainer price can be reviewed, how notice works for a change, and that past invoices don’t get altered by new pricing.

Access and logins

Says what access is needed to deliver the service and how credentials should be shared safely, plus what happens when access gets changed or removed without warning.

What we need from you

Sets expectations for a single point of contact, fast decisions during incidents, and advance notice when other changes or suppliers could affect hosting or WordPress.

Insurance

Notes the provider’s insurance for the work and points the client to covering their own business risks, with an option to request a short summary of cover held.

Putting things right

Describes how incidents get logged and communicated, the steps used to restore service when a change causes a fault, and the limit of control over third-party failures.

Our team

Explains that service cover comes from a team and includes a non-solicitation clause for staff during the agreement and for a defined period after it ends.

How the retainer runs

Covers monthly renewal and invoicing, how notice to end or pause works, and what still needs to keep running to avoid preventable incidents.

Handover and exit

Sets out the handover plan and deliverables at exit, including exports and backups, credential rotation where needed, and stopping monitoring alerts.

Responsibility

Clarifies what the provider takes responsibility for, what can still cause outages, and excludes liability for business losses while committing to share logs and timelines if there’s a dispute.

Ending this agreement

States how either side can terminate, what stays payable up to the finish date, and includes the Signature section the client signs.

Who it is for

Managed hosting providers, WordPress maintenance shops, and freelancers offering web hosting & maintenance on a monthly retainer, especially where after-hours incidents and handover need to be in writing.

The contract in full

It covers hosting, monitoring, updates, backups, incident response, and security patching for the site(s) listed in the accepted proposal or statement of work, plus any agreed add-ons.

If there is an accepted proposal, it sets the plan, pricing, and any setup work like migration and cutover. This agreement sets how we run the service week to week, how we communicate when something breaks, and how billing and handover work.

Scope of work

Each month we run the managed hosting retainer on an ongoing basis: we host your site, watch uptime and key checks, apply routine WordPress maintenance in an agreed monthly window, and keep backups and security work running in the background.

The retainer includes the items listed below. Anything that changes features or design is not included, like new pages, new integrations, or checkout changes. If you ask for out-of-scope work, we will describe what we propose to do and price it before we start, so there are no surprises.

* Managed web hosting * WordPress updates * Uptime monitoring * Incident response * Daily backups * Security patching

Service levels

We treat issues by impact. When you report a problem, or monitoring alerts us, we reply using the response times for the severity level we assign. We will tell you the level we have assigned and why.

Severity levels: Critical (site down or checkout broken), Major (key functions degraded), Minor (non-blocking bug or content issue). Response times and after-hours coverage are set out in the accepted proposal or onboarding notes for your account. Monitoring runs continuously and pages our on-call rota after hours for urgent incidents.

If we miss a service level, we will explain what happened, what we changed to prevent a repeat, and agree a fair service credit or fee adjustment for the affected period.

Payment

There are two parts to payment: any one-time setup work, and the ongoing managed hosting retainer.

Setup work, where included, is invoiced 30% to start. The remaining 70% is invoiced when migration and cutover are complete. The ongoing managed hosting retainer is invoiced at the start of each month.

Every invoice is payable within 7 days of its date. If an invoice becomes overdue, we will contact you to fix it quickly. If we cannot reach you or payment does not arrive, we may pause non-urgent work until the account is back up to date. We will keep you informed before taking any step that could affect service.

Price review

We review the managed hosting retainer price at a regular interval, normally once per year, to reflect changes in platform costs, security workload, and the support load of your site.

If we propose a new monthly price, we will tell you in writing before it applies. The notice period is one we choose and confirm with you in writing at the time. If you do not want to continue on the new price, you can end the retainer by giving notice, and we will follow the handover steps in this agreement.

Price changes do not affect invoices already issued. Any one-off out-of-scope work is always quoted and agreed separately.

Access and logins

To run the service we need the right access. This usually includes admin access to WordPress, access to your current host during migration, and domain DNS access for cutover and SSL validation.

We will only accept logins through a safe method. Use your password manager sharing feature, or a one-time secure link that expires. Do not paste passwords into forms, tickets, or ordinary email. If you cannot share access safely, tell us and we will agree another route.

If access is removed or changed without telling us, it can delay fixes and planned maintenance. We will tell you what is missing and what we need restored.

What we need from you

This retainer works best with one named contact on your side. That person collects input internally, approves maintenance windows, and is the route we use for urgent decisions.

You agree to: keep your contact details up to date, reply to time-sensitive questions promptly during incidents, and tell us before you make changes that affect hosting or WordPress, like switching DNS, adding a proxy, changing payment providers, or installing major plugins. If another supplier is working on the site, you will introduce us so we can coordinate.

You are responsible for your store operations, products, and customer communications. We are responsible for keeping the hosting and maintenance service running as agreed.

Insurance

We carry business insurance that fits the kind of work we do, including cover for mistakes and accidents in the course of providing hosting and maintenance.

You are best placed to insure your own business risks. That usually includes cover for loss of revenue, stock and fulfilment issues, customer claims related to your products, and any contractual commitments you have to your customers.

If you need us to confirm the type of insurance we hold, ask and we will provide a short summary. If your business or a third party requires specific cover to be in place, tell us before we start so we can confirm whether we can meet it.

Putting things right

If something goes wrong, we deal with it openly and quickly. As soon as we become aware of an incident, we will log it and tell you what we know, what we are doing next, and what we need from you, if anything.

If our work causes a fault, like an update that breaks the site, we will prioritise getting you back to a working state. Depending on what is safest, we will roll back the change, restore from a known good backup, or apply a fix, then verify key journeys like login, checkout, and admin access.

If there are third-party failures involved, we will help with diagnosis and coordination, but we cannot control third-party response times.

Our team

The people who deliver this service are part of what you are paying for. We recruit, train, and retain the team so you have cover when someone is on leave and you are not dependent on one individual.

While this agreement is running, you agree not to hire or contract directly with our staff, or ask them to work for you outside this agreement. This also applies for a period after the agreement ends. The length of that period is one we choose and confirm with you in writing.

If you want extra support beyond the retainer, ask us. We can usually scale the plan or quote project work without pulling people away informally.

How the retainer runs

The managed hosting retainer is a recurring monthly service. It renews automatically each month and we invoice at the start of the month, so the service stays continuous.

Either side can end the retainer by giving notice. The notice period is one we agree and confirm in writing, and it starts when we acknowledge your notice in writing. During the notice period we keep monitoring, backups, and routine maintenance running as normal, unless you ask us to start handover earlier.

If you want to pause instead of end, tell us. We will explain what can and cannot be paused safely, because some tasks, like security patching, are there to prevent avoidable incidents.

Handover and exit

When the retainer ends, we will help you leave in a usable state. We will agree a handover plan in writing that covers hosting, DNS, backups, and any important credentials.

We will provide you with the site files and database export we hold, and we will confirm the last backup point available. If you are moving to a new host, we can share guidance on what they need. If you want us to perform a migration out as a one-off piece of work, we will quote it separately.

Once handover is complete, we will remove our access where we can, rotate shared credentials if needed, and stop monitoring alerts for your site.

Responsibility

We take responsibility for running the managed hosting retainer with care and for following the agreed processes around updates, backups, monitoring, and incident response.

We cannot promise that your site will never fail. Outages can be caused by third-party services, upstream providers, theme or plugin defects, traffic spikes, and changes made by others with access. When that happens, our job is to respond, communicate, and restore service as quickly as we reasonably can.

We are not responsible for your business losses such as lost sales, lost profit, or reputational harm. If there is a dispute, we will start by sharing logs, timelines, and the steps we took, so we are working from the same facts.

Ending this agreement

You can end the managed hosting retainer by giving notice. We can also end it by giving notice. We will confirm notice in writing and agree the finish date and handover plan.

You pay for: the retainer up to the finish date, and any agreed one-off work completed up to that date. If setup work is underway, the 30% start invoice remains payable, and the 70% completion invoice becomes due when migration and cutover are complete.

On termination we will keep the service stable during the notice period, then complete handover as set out above. If we have to end the agreement quickly for safety or non-payment, we will still act reasonably and help you recover access to your site and data.

Signature

Legal Notice: Please consult legal advice and carefully review the content of this contract template before implementing this template in your business.

Questions about this contract template

What should a retainer agreement include?

A retainer agreement usually covers what’s included month to month, what counts as extra work, how payment works, and how the relationship ends. This one also covers service levels, access and logins, incident response, responsibility, and handover.

How do you define what’s included vs extra work on a monthly retainer?

The agreement needs a written scope for the recurring service and a clear line around changes that don’t fit inside it. This template lists the included hosting and maintenance items, then says feature or design changes get described and priced before work starts.

How should response times work for after-hours incidents?

Response commitments work best when they follow severity levels, so “site down” doesn’t get treated like a minor content issue. This contract defines critical, major, and minor severity, and ties response times and after-hours coverage to what’s agreed for the account.

What payment terms make sense for a managed hosting retainer?

Many retainers split one-time setup from the recurring monthly fee, and then set a clear due date for invoices. This agreement uses a 30/70 schedule for setup where included, invoices the retainer at the start of each month, and makes invoices payable within 7 days.

What access should a hosting and maintenance provider ask for?

Access usually needs to cover the site admin area, the current host for migration, and DNS for cutover and SSL validation. This contract also spells out safer ways to share credentials and notes that missing access can delay fixes and planned maintenance.

What happens when a retainer ends and the site needs to move?

A good exit section should cover hosting, DNS, backups, and credentials, plus what files and exports get handed over. This agreement commits to a handover plan in writing, provides the site files and database export held, confirms the last backup point, and then removes access and stops monitoring.

Start free today

Your entire business, one login away

No credit card required. No contracts. Just the tools you need to run, grow, and automate your business with Super Work AI.

No credit card required

Plutio - Your entire business, one login away