Blog / Web management /
Retainers or projects: how I structure website maintenance work
“How many hours do you want per month?” It’s the question everyone reaches for first, and it’s usually the wrong one.
Website maintenance can be a monthly retainer or a defined project. Neither is automatically fairer. It depends on how often the site changes, how fast someone needs to respond and whether there’s a clear backlog of work.
When I pick up a client site, the better opening question is this: what needs to stay healthy, what work recurs, and what happens when something unexpected breaks? Answer that and both sides avoid mismatched expectations.
When a retainer fits
A retainer suits a site that needs regular updates, monitoring, reporting or ongoing advice. The client gets a predictable relationship and the provider gets a planned window to do the work. The scope should say what’s included, how requests are prioritised and what happens when the workload outgrows the agreed capacity.
I’d never sell a vague bucket of hours with no account of what the client gets. Define the tasks, the response expectations and the exclusions. Be careful about emergencies, too: monthly support doesn’t automatically mean 24/7 cover.
When a project fits
A project suits work with a clear start and end: a migration, a redesign, an audit, a one-off cleanup. Be clear on the deliverable, assumptions, dependencies and what counts as done. If the work uncovers a bigger issue, document it and agree whether it becomes a new project or ongoing support.
Projects are easier to budget, but they need enough discovery to avoid underestimating the unknowns. A site full of undocumented custom code may need a review before anyone can quote a reliable scope.
Separate maintenance from development
Routine maintenance covers things like update reviews, backups, monitoring and small content or configuration changes. New features, redesigns, migrations and major integrations are different work. Write down where the line sits, so every request doesn’t become a negotiation.
Name the third-party costs too: hosting, domain renewals, premium plugins, email services, licences. Say who owns the accounts and who pays. A client shouldn’t discover that a critical plugin licence sits on an employee’s personal account.
Set expectations for requests and incidents
Agree the request channel, what to include and how work is prioritised. A broken checkout isn’t the same as a footer typo. Give the client a way to flag urgency, but define how you assess and respond.
State response times separately from resolution times. You can acknowledge an incident quickly without being able to fix a third-party outage straight away. Don’t promise anything that depends on a host, an app developer or client approval.
Make work visible
Keep a task log: request, decision, status, outcome. A short monthly summary can show work done, upcoming renewals and risks needing client input. If a month was quiet, say so. I’d rather admit that than invent activity to justify the retainer.
Use reports to support decisions. If the same issue keeps coming back, explain the root cause and propose a lasting fix. Maintenance should make the site more reliable, not bill repeatedly for the same avoidable incident.
Choose a model together
Ask how often the site changes, what downtime would cost, what skills the client has in-house and how quickly decisions get made. A small static site may need the odd project and a clear emergency contact. A store with live campaigns and integrations needs a continuing relationship.
Some clients need a hybrid: a maintenance retainer for routine work and separately scoped projects for larger changes. Put the distinction in writing and review it when the site or business changes.
FAQ
Is a retainer cheaper than project work?
It depends on scope, capacity and frequency. Compare what is included and the cost of unplanned work, not just the monthly fee.
Should unused retainer hours roll over?
That is a commercial decision to agree in advance. Make the treatment of unused capacity clear in the contract.
Does maintenance include emergencies?
Only if the agreement says so. Define coverage, response expectations and dependencies explicitly.
Define the boundaries of maintenance
Before work begins, agree what’s included, how requests are prioritised and what counts as urgent. A retainer may cover scheduled reviews and a set amount of ongoing support, while a project has a fixed scope and handover. The labels don’t settle the details. Put response expectations, approval steps, access ownership and out-of-scope work in writing, so nobody guesses when something unexpected happens.
A maintenance agreement should also say what the client is still responsible for, such as supplying approved content or looking after third-party accounts. Keep the process in proportion to the site: a brochure site and a shop taking orders have different needs. Review the arrangement when the site changes. Last year’s scope may not fit this year’s business.
Choose a model the relationship can sustain
A retainer isn’t automatically better for the client or for the person doing the work, and a project isn’t automatically more efficient. Does the site need regular attention? Can tasks be scoped in advance? How quickly are decisions made? A predictable review cycle suits an ongoing relationship, while a migration or rebuild is clearer as a project. Either way, leave room to talk about work outside the original agreement. A short review at the end of each period shows whether the arrangement still fits.
Related reading
- Client website handover documents: what I include
- Uptime isn’t enough: monitoring forms, checkout and email
- A client onboarding checklist for website handovers
Before you agree a maintenance plan, write down what happens in a normal month and what happens when something breaks. Do both sides give the same answers? If not, fix the scope first.