Think about the clients you built sites for two or three years ago. How many of them still talk to you? For a lot of agencies the honest answer is “a few”. The rest drifted off after launch, and when they needed a redesign, a new feature or help with a broken plugin, they asked whoever answered first. Often that was a competitor, or a cousin who “does websites”.
Ongoing maintenance is one of the simplest ways to keep those relationships alive. Not because a monthly invoice locks anyone in, but because regular, useful contact keeps you in the client’s mind as the people who look after their website. This post looks at how to use that contact well, so retention comes from service rather than inertia.
Why clients drift after launch
Clients rarely leave because they are unhappy. They leave because nothing reminds them you exist. A typical pattern:
- The project ends with a handover and a thank-you email.
- Months pass without contact. The client’s team changes; the person who hired you moves on.
- Something breaks. The new contact does not know who built the site, or assumes you are expensive, busy or no longer interested.
- They find someone else, who then quotes the redesign a year later.
The fix is not more sales emails. It is a reason to be in touch that the client values, and maintenance provides one every month.
Plan the transition before launch
Retention starts during the project, not after it. Raise ongoing care early, ideally in the proposal, so it is part of the plan rather than an upsell at the end. Something as simple as a line in the timeline helps: “Launch, then ongoing maintenance from the following month.”
At handover, make the transition concrete:
- Walk the client through what will happen in the first month after launch.
- Tell them who to contact and how, and what counts as urgent.
- Agree what you will send them each month.
- Confirm who holds which accounts: hosting, domain, analytics, licences.
Our handoff checklist for finished sites covers the access and documentation side of this step.
Make every month useful to the client
A maintenance relationship that only shows up as an invoice will be cancelled at the first budget review. To keep it, each month should leave the client with something they can see or understand.
A short report they actually read
Keep it to the essentials: what was updated, what was checked, anything unusual, and one or two observations. Write for the person who will read it, not for another developer. “We updated the booking plugin and tested a booking on mobile” beats a list of version numbers.
One useful observation
Each report is a chance to notice something. A page that has become slow, a form that gets a lot of spam, a plugin that is no longer maintained, a contact page with an old phone number. These observations are where future projects come from, and they show that someone is paying attention.
Problems raised before the client finds them
If monitoring shows the site went down overnight and you brought it back, say so. Clients rarely remember the months when nothing happened, but they always remember the time you spotted something first.
Respond to small requests well
The quickest way to lose a maintenance client is to make a small request feel like a burden. If your offer includes a few edits a month, handle them cheerfully and quickly, and confirm when they are done. If a request is outside what is included, say so politely and offer a quote, without making the client feel they asked something wrong.
Small requests are also how clients test whether you still care. An image swap handled smoothly earns more goodwill than a perfectly run update that nobody saw.
Schedule a review, not just maintenance
Once or twice a year, offer a short review call or written summary. Look back at what happened on the site, what changed in the client’s business, and what might be worth doing next. Keep it honest: if the site is in good shape and needs nothing, say that too.
Questions worth asking in a review:
- Has anything changed in how you sell or who you sell to?
- Which pages do customers ask you about, or complain about?
- Is there anything you find awkward to update yourself?
- Are there new services or products the site does not mention yet?
- Is anyone else on your team now involved with the website?
The last question protects you against the most common reason for drift: the person who hired you has left, and the new contact does not know you.
Keep your contact list current
Ask, at least once a year, who should receive your reports and who to contact in an emergency. Add a second contact where you can. If your monthly email starts bouncing or going unread, find out why. A maintenance relationship with nobody on the other end is a cancellation waiting to happen.
Handle the first problem like it matters
Every maintenance relationship eventually meets its first real problem: an update that breaks a layout, a host outage, a form that stops sending. How you handle that moment shapes how the client sees the whole arrangement.
Tell them early, before they discover it. Explain in a sentence or two what happened, what you are doing, and when you will update them next. When it is fixed, say what caused it and what you have changed so it is less likely to happen again. Keep the tone calm and factual; clients take their cue from you.
A problem handled openly often strengthens trust more than a year of quiet months. It shows the client what they are paying for. If you are unsure how to word that kind of message, our post on what to tell a client when their site is down has examples you can adapt.
Explain what happens without maintenance
Some clients will question the value after a quiet few months. That is fair, and it deserves a straight answer rather than scare stories. Explain what the work prevents: outdated plugins becoming security holes, backups that do not exist when they are needed, an expired domain taking the site offline. Our post on what happens when a site stops being maintained sets this out calmly, and it is something you can share.
If, after an honest conversation, a simple site genuinely does not need monthly care, it is better to say so and offer ad hoc support instead. A client who trusts your advice is more likely to come back for the next project than one who feels they were kept on a plan they did not need.
Treat cancellations as information
When a client cancels, ask why, briefly and without pressure. Common answers include cost, not seeing the value, a change in business, or moving to a different supplier. Each tells you something about your offer or your communication. Make the exit clean too: hand over access, backups and notes promptly and politely. Clients do return, and the ones who left on good terms are the ones most likely to.
Deliver it without overloading your team
Retention through maintenance only works if the maintenance actually happens, every month, for every client. That is routine work, and it competes with project deadlines for the same people. When a launch is due, updates get postponed and reports go out late. Clients notice.
Options that agencies use:
- A fixed maintenance day each week that project work cannot take over.
- One person in the team owning maintenance, with a backup for holidays.
- Tooling that handles updates, backups and monitoring across sites centrally.
- A partner who does the routine work under your agency’s name, while your team keeps the client conversations and reviews.
Whichever you choose, the client should see the same consistent service. For more on turning this into a reliable income line, see our post on building recurring revenue beyond projects.
Measure what matters
You do not need a dashboard, but it helps to keep track of a few things over time:
- How many launched clients move onto ongoing maintenance
- How long maintenance clients stay
- How many new projects come from existing maintenance clients
- Why clients cancel, in their own words
Look at these once a quarter. If few clients join after launch, look at how you introduce maintenance. If they leave after a few months, look at what they receive each month.
A retention checklist
- Maintenance mentioned in the proposal, not just at handover
- A clear first month after launch, explained to the client
- Short monthly reports in plain language, with one useful observation
- Problems reported before the client notices them
- Small requests handled quickly and confirmed
- A review once or twice a year
- Contacts checked and a second contact added
- Honest advice when a site does not need monthly care
- Clean, polite exits
- A routine that survives busy project months
For the bigger picture of how outsourcing can support this kind of work, see our outsourcing guide for agencies and freelancers.
If the routine part is what slips when projects get busy, our page on maintenance we carry out under your agency’s name describes how we take it on while you keep the client relationship.
Next in this series: How to Sell Website Maintenance to Clients
