Care plan tiers that don't confuse anyone

A café owner opens the care plan page her web designer sent over. Three columns, fourteen lines each. Uptime monitoring. Plugin updates. Malware scanning. Staging site. Priority support. The words are different in each column, but she can't tell what she would notice. She picks the cheapest, then emails a month later asking for the new winter menu to go up, and is surprised it isn't "included".

Nobody did anything wrong. The tiers just described the designer's work instead of the café's needs.

Care plan tiers work when there are two or three of them, when each one is described by what the business gets, when the differences fit on one line, and when you recommend one. The safety work stays the same in every tier. What changes is what the owner can feel: how many changes they get, how fast you answer, and what you take off their plate.

How many care plan tiers should you offer?

Two or three. If you're just starting, one plan is enough: one price, one list, one promise you can keep.

Every extra tier is another thing to explain on a sales call and another boundary to hold every month. Three is about as many as a busy owner will compare on a phone. Four or five usually means some tiers differ by a line nobody reads.

A quick test: can you say the difference between each tier in one sentence, out loud, without looking at the page? "The second one includes up to four small changes a month." If you need a table to explain it to yourself, the client will need a meeting.

What should change between tiers?

Change the things an owner notices. Keep the base identical.

The same in every tier. Backups, updates, a check that the site loads, a monthly test of forms and booking links, and a working security certificate. WordPress's own documentation recommends taking a backup before you update, so the site can be restored if something goes wrong. That order belongs in every plan, not only the top one. The certificate matters more each year: Let's Encrypt announced in December 2025 that it will shorten its certificates from 90 days to 45 days by 2028, with a 45-day option open to early adopters from May 2026. If you're weighing the Let's Encrypt 45 day opt in for your clients, the check that renewal works belongs in every tier.

What can change. Pick one or two of these:

• How many small changes a month.
• How quickly you reply on a working day.
• Whether hosting is included.
• Whether you look after their Google listing, including holiday hours.
• A short monthly note, or a short call each quarter.

Here's how that looks for a small café:

	Care	Care and changes	Care, changes and hosting
Backups, updates, security certificate check	Yes	Yes	Yes
Forms and booking link tested monthly	Yes	Yes	Yes
Small changes each month	One	Up to four	Up to four
Reply time on working days	Two days	Next day	Next day
Hosting	Client's own	Client's own	Included
Google listing hours kept up to date	No	Yes	Yes
Monthly note	Yes	Yes	Yes

Notice what isn't in the table: security as an upgrade. Selling safety as an extra leaves your cheapest clients with the riskiest sites, and it's still your name on the work when something breaks.

How should you name care plan tiers?

Name them by what the client gets. "Care", "Care and changes" and "Care, changes and hosting" are plain, a little dull, and impossible to misread. Bronze, Silver and Gold tell the café owner that one costs more than another, and nothing else. Names built on your tools, such as "Managed WordPress Pro", tell her even less.

Put the one-line difference right under each name, in the client's words: "for when the menu changes most months", "for when you'd rather not deal with hosting at all".

How do you price each tier?

Price each tier from your own time and costs, then check the gaps between them make sense.

• The base tier covers your monthly routine and your fixed costs per site.
• Each step up covers the real extra work: the extra small changes, the faster replies, the listing you now keep current.
• A hosting tier adds the hosting cost and the time you spend on it. Pricing a website hosting and maintenance package goes through that in detail, including what happens to the hosting if the client leaves.

If the step between two tiers is small, most clients will take the higher one and you'll be doing more work for little more money. If it's large, nobody moves up. Aim for a gap that matches the extra work, and let the client see why.

Avoid pricing from someone else's price list. Care plan prices vary so widely that copying one tells you little about your own costs.

What goes in writing for each tier?

Each tier needs its own short page the client can read on a phone: what's looked after, what happens each month, how many changes, how fast you reply, and what isn't included. The "not included" list matters most. New pages, new features, online shops and redesigns are quoted separately, whatever the tier.

The clearest way to keep tiers consistent is writing a service recipe for each one: the same headings every time, filled in with that tier's promises. When a client asks "is this covered?", you check the recipe, not your memory. The same "covered or extra" line is what separates website maintenance vs retainer work, so if some clients really want a set number of hours for bigger jobs, that's a retainer and it's worth pricing separately.

When the client picks a tier, send it with the quote, so the price, the tier and what's included arrive together. Keeping quotes, deposits and payments in one place means you can find what they agreed to when the first "is this included?" arrives.

How do you help a client choose?

Ask three questions, then recommend one tier:

1. "How often does something on your site need to change?" Seasonal menus, new staff, price updates.
2. "Do you want to deal with hosting, or would you rather we did?"
3. "If something breaks, how soon do you need an answer?"

For the café with a new menu most months, the answer is the middle tier, and you should say so. A recommendation isn't pushy; it's the job. Most owners are relieved to be told.

Then set the rule for moving. A client can move up or down from the next billing date, and unused changes don't carry over. If a client regularly asks for more than their tier covers, suggest the next tier up rather than quietly absorbing the extra work.

What about add-ons that don't fit any tier?

Sooner or later a client wants something that belongs to none of the tiers: a monthly blog post, a newsletter, extra help before a big event. Resist adding a fourth tier for one client. Offer it as an add-on with its own line and its own price, on top of whichever tier they're on.

Keep add-ons few and written the same way as the tiers: what's included, how often, and what's extra. If three clients ask for the same add-on, it may deserve a place in the middle tier. If only one does, it stays an add-on, and your tiers stay simple for everyone else.

The same goes for one-off jobs. A new page for a spring promotion isn't a reason to move up a tier. Quote it as a one-off, do it, and leave the plan as it was.

Care plans bring an AI agency recurring revenue, and they're only one of the services to sell after the website. Whatever else you add later, the same rule holds: plain names, one-line differences, the same safety work for everyone, and one tier you'd recommend to a friend.