Services

Website maintenance retainer

A fixed monthly budget instead of an invoice per change. Scheduled work on a calendar and a contractor who remembers your project.

Timelinemonthly

What's included

  • Monthly allowance of hours
  • Scheduled routine work
  • Small changes without new contracts
  • Unused hours partially roll over
  • Predictable budgeting
  • One accountable contractor
  • Monthly time report

A maintenance retainer and technical support are related but genuinely different things, and confusing them costs money. Support answers the question of what happens when something breaks: on-call cover, response times, incidents. A retainer answers a different question — who looks after the site during ordinary life: routine work, regular edits, gradual improvement.

The difference shows up in how the money works. Hourly billing looks cheaper, but every trivial change needs an estimate, an approval and an invoice, and that paperwork takes longer than the change itself. The result is that small tasks pile up for months because nobody wants to bother anyone over something minor. A retainer removes that friction: there's an allowance of hours and a person you can simply message.

How we work

  1. Size the work. We look at the site and talk through what a normal month contains: how many edits, which routine tasks, whether there's ongoing development. Then we pick an allowance that matches reality rather than padding it.
  2. Build the schedule. What happens regularly and when: updates, backup verification, certificate renewals, database cleanup. These run on their own without you having to remember them.
  3. Take in tasks. As a list, by email, or in chat — whatever suits you. Small items need no separate approval; larger ones get estimated first.
  4. Track the hours. Every task is logged with the time it took. At month end you can see exactly where the allowance went.
  5. Roll over what's left. Unused hours don't simply evaporate — a portion carries into the following month, so a quiet period offsets a busy one.
  6. Report. Once a month you get a summary: what was done, what it cost in hours, and what we suggest for the next period.

What you get

A predictable budget — one line in your accounts instead of unpredictable invoices. Small tasks stop accumulating because the barrier to asking disappears. And most valuably, a contractor who remembers the project: no explaining from scratch every time what this site is, where things live, and why something was built the way it was.

If you need guaranteed response times for outages — an on-call engineer, an SLA, round-the-clock monitoring — that's technical support, priced by response speed. Plenty of clients take both: a retainer for routine work and a support plan for incidents. If most of your tasks are content — products, copy, promotions — see content support.

Timeline

We start with a trial month, which is what reveals the true volume and lets the allowance be adjusted. After that it runs month to month with automatic renewal. Tasks within the allowance are delivered to an agreed window, typically one to three working days depending on complexity. Scheduled work follows its own calendar regardless of what you send in.

A typical scenario

Consider a company sitting on a backlog of small things: fix the phone number in the header, swap three photographs, add a careers page, update the price list. Each is twenty minutes of work, but commissioning them individually is awkward — approval and invoicing take longer than the job. The list sits untouched for six months while the site slowly goes stale. Under a retainer that backlog clears in a single session within the allowance, and new small items stop accumulating because sending them became easier than postponing them.

FAQ

How is this different from technical support?
A retainer is about routine work and a predictable budget: scheduled tasks, small edits, an allowance of hours. Support is about incidents: on-call cover, response times, an SLA. Many clients take both, but they're different services with different logic.
What if the hours run out early?
We talk it through: either remaining tasks move to next month, or you top up at a fixed rate. What we won't do is silently exceed the allowance and send a surprise invoice — you'll hear from us before that point.
What if we don't use the hours?
A portion carries into the following month. It can't accumulate indefinitely, or the retainer stops making sense, but a quiet month offsetting a busy one is fairer than burning everything to zero.
How many hours do we need?
Only the first month of working together really answers that. We normally start with a modest allowance and adjust against actual usage. Buying a large package up front rarely pays — topping up later beats paying for unused time.
What's included and what isn't?
Anything that fits the hours: edits, publishing, scheduled work, small development tasks. Not included: building substantial new sections or a redesign — those are separate projects with their own estimates and timelines.
Can we pause the retainer?
Yes, if the site isn't needed for a while. Give us notice — bear in mind scheduled work pauses too, so updates and backup checks won't be running during that time.
Who will actually work on our project?
An assigned specialist who knows your site. That's the whole point of a retainer: not re-explaining every time what the project is and why it works the way it does.
Other services