36. A Maintenance Retainer Written in Plain Language

A maintenance retainer is a monthly promise that the website will not be abandoned after launch. For a Malaysian SME it usually covers small edits, a watchful eye on the contact form, and the unglamorous work of updates and backups. It goes wrong when the document is written like a software licence. The founder signs because they want peace, then discovers that peace does not include the banner they need before a sale. A retainer in plain language says what is included, what is extra, and how fast you will hear back.

Plain does not mean casual. The agreement can still name the site, the fee, the term, and how either side can stop. It should be readable by the person who pays, not only by the person who built the site. If your coordinator cannot explain the retainer to a client without opening a glossary, rewrite it. The monthly fee is buying clarity as much as hours.

<>

List the work in verbs a founder recognises

Included might mean updating holiday hours, swapping a photograph, changing a phone number, and checking that the enquiry form still arrives. It might include software updates and a backup you have actually restored once, so you know the backup is not a rumour. Say the number of small requests you will do in a month, or say that you will do a reasonable set of text and image edits and that a new page is a separate quote. Vague unlimited editing invites unlimited arguments.

Excluded deserves the same plain list. A new shop section, a photoshoot, a campaign page, copywriting from scratch, and work on a different domain are not maintenance. Emergency help on a public holiday is not silently included unless you priced it. If you will try to help and will bill the time, say that. Surprises belong in the excluded list more than in the included list, because surprises are where relationships crack.

Put response time next to the fee

State office days and a response window you can keep. We reply on business days within one working day is a promise. As soon as possible is not. Say what counts as urgent, such as the site being down or the payment page failing, and how to reach you for that. A WhatsApp message at midnight should not be the official urgent channel unless someone is paid to read it. Match the promise to the footer of the website so the client does not publish a faster claim than you agreed.

• The monthly fee and whether SST is added.
• The edits and checks that are included.
• The work that always needs a separate quote.
• The hours and the response window.
• How to pause or end the retainer.

Say how requests should arrive. One email address, or one shared board, beats a mix of voice notes and forwarded chats. You can still be friendly. You can ask that the request includes the page link and the sentence they want changed. That single habit saves more time than a clever clause. If the client has several approvers, name one person who may send work. Maintenance dies when three relatives all think they are the client.

<>

Write the money so a bookkeeper can post it

The fee, the invoice date, and the payment term should look like your other invoices. If the retainer starts mid-month, say whether the first invoice is pro-rated. If a month has no requests, say whether the fee still stands, because the watching and the updates are the work. Clients accept a quiet month when you told them the fee is for availability and upkeep, not for a pile of visible edits. They resent it when the proposal talked only about changes.

A retainer people keep is one a founder can explain back to you without looking at the PDF.

Renewal should be dull. A yearly reread, a fee that changes only with notice, and a short report of what you actually did. The report can be five lines. Updated plugins, restored one backup test, changed Raya hours, added two photos. That note justifies the next invoice better than a dashboard. It also reminds both sides when the scope has quietly grown into a new website.

<>

Review the words after the first three months

The first quarter shows which requests were really maintenance and which were new projects in disguise. Adjust the list together. Do not wait for a dispute. If every month includes a new landing page, you are not on a maintenance retainer. You are on an underpriced design arrangement. Rename it and reprice it while the relationship is still polite.

Keep the signed version and the current version in the same folder as the site access notes. When a staff member leaves, the next person should not have to infer the deal from old chats. Plain language is not only for the day of signing. It is what lets a small company hand the promise to someone else without a week of archaeology.

Bring the retainer to the person who answers the phone, not only to the person who signs. They are the ones who will promise a homepage change during a busy Saturday. If they do not know what is included, they will promise a new section and you will either do it free or disappoint a customer. A ten-minute briefing after signing prevents that Saturday promise.