What a website care plan leaves out
Most care plans list updates, backups and security checks. Two things are often missing: who renews each domain, hosting plan and licence, and what happens to the small requests that fall outside the plan’s hours. Write both into the plan, and record them per client.
What the common guides cover
Most care plans are built from the same list: core, theme and plugin updates, backups, security scans, uptime checks and a set number of support hours. The Admin Bar’s guide, What is a “Website Care Plan” and What’s Included?, is a good version of that list, and I would start there. It tells you what work to promise. It was not written to answer two other questions, and those are the ones that cause trouble a year later.
Renewals: who handles each one
A client’s site depends on a domain, a hosting plan, often a certificate, an email service and a few licences. Each has a renewal date, and most care plans say nothing about them. The client assumes you are watching. You assume the registrar will email. Nobody checks.
Write a short renewals clause into the plan. For each service, settle three things:
- Managed by. Who logs in to the account and acts on a renewal: you, the client or a third party.
- Paid by. The client pays the provider directly, you pay and rebill, or you pay and absorb it. These are the three arrangements in Yven, and they are the three you have in real life.
- What happens on the date. Do you tell the client a month ahead, and who decides if a service should be allowed to lapse?
Then record the answer per client, so it is not in your head. The rebilling guide goes through the three models and the risks of each, and the markup calculator helps if you rebill. One thing a care plan should not do is promise to prevent a lapse. It can promise to tell the client in time, and to check the date on a stated schedule. That is a promise you can keep.
The small jobs: what happens to the extra request
Every plan has a number of hours or a list of tasks. Clients still ask for things outside it: a new page, a changed phone number, a banner for a sale. If the plan is silent, you will do some of these for free, bill some, and argue about a few.
Put the rule in the plan and say it before the first request. For example: the plan covers a stated number of hours each month. Work inside it is logged and not billed again. Work outside it is logged and billed monthly at a stated rate, with a stated minimum. This is an example of wording, not legal advice.
Whatever the number, log the work. A plan with 3 hours a month only means something if you know whether the client used 1 or 5. The guide to billing small website changes covers what to record for each job and how to handle the month end. In Yven, a fixed-fee project can have an hours budget, and you choose whether time over the budget is billed to the client or absorbed. Work covered by the plan can be marked plan-included so it does not add to what the client owes.
A section list for a care plan
This is a list of headings, not a legal document. Have the agreement text checked by someone qualified.
- What is covered. The recurring tasks, each in a line.
- What is not covered. New features, redesigns, content writing, and anything caused by a third party’s change.
- Hours. How many each month, whether unused hours carry over, and what happens when you go over.
- Renewals. The managed by, paid by and notice rules above, listed per service.
- Small requests. How they are logged, how they are billed, and when to quote instead.
- Response times. How fast you reply, and what counts as an emergency. Only promise what you will actually do.
- Price and billing. The monthly fee, the invoice date, and how to cancel.
- Handover. What the client receives if the plan ends, which is the handover document.
A month-end routine for a plan client
The plan is a promise, and a routine is how you keep it. Once a month, for each client on a plan:
- Check the hours used against the budget. If a client is regularly over, that is a pricing conversation, not a favour.
- Look at the renewals due in the next 60 days and tell the client about any that need a decision from them.
- Send the invoice, with the logged work visible. A client who can see what was done questions less. The shared work log shows them the entries you mark as client-visible, grouped by month.
Fifteen minutes per client is a realistic target once the records exist. It is a lot longer if you have to rebuild them each month from email.
Pricing the plan
The two clauses above change what a plan costs you. Renewals you rebill add a monthly line and a margin. Renewals the client pays directly add nothing to the price, but they add a small amount of your time each month, because you still watch the dates. Small requests are the larger variable: a plan with two hours that is regularly three hours is underpriced, and you only know that if you log the work.
If you want a way to work out the number, the guide to how much to charge for website maintenance gives a method with worked examples. It does not give a price, because yours depends on your costs and your rate.
What to tell a client who asks what they get
Clients rarely read the agreement, and they ask in plain words. Have a short answer ready. Something like: the site is kept up to date and backed up, the domain and hosting renewals are watched and you hear about each one in good time, and small changes are logged and billed once a month, with a set number of hours included. Three sentences are enough. Anything longer belongs in the agreement.
The renewals sentence is the one clients remember. A domain that expires is a visible, embarrassing failure, and they will not blame the registrar. Saying early who watches it, and who pays, is a small promise that makes the plan feel worth the fee.
Review it once a year
Plans drift. Services get added, a client changes hosts, and your own rate goes up. Once a year, on a fixed date, read each plan against the client book: does the renewals list match what exists, and do the hours match what the log shows? Fix the plan, tell the client, and move on.
Where this leaves the plan
A care plan that lists updates and backups, and also names who renews each service and how extra work is billed, is easier to sell and easier to run. The client knows what they are paying for. You know what you promised. Neither of you finds out at renewal time that the domain was on a card that expired.
Where another tool is the better choice
For the technical side of a plan, such as updates, backups and uptime across many WordPress sites, a dedicated maintenance tool does the work and Yven does not. Many shops will use both: one tool to run the maintenance, and the client book to record the renewals and the money behind it.
Where to go next
- The client book, for what to record about each client and site.
- Who pays for the domain? The money side of renewals and rebilled services.
- How to bill small website changes.
- All guides.