When a thin care plan is not enough for your site

A thin care plan keeps the lights on. Updates get applied. Backups get taken. Someone glances at uptime. That is useful when the site is mostly static and nothing much changes week to week.

It is not enough when the site is the business. Stores, agency builds, SaaS dashboards, booking tools, membership areas. Those need room for real changes, not a monthly checklist that runs out of oxygen the moment something breaks or sales ask for a tweak.

What a thin care plan actually covers

Care plans exist for a reason. Core and plugin updates. Backup checks. Security glances. A quick look after updates so the homepage is not quietly broken. On WordPress and WooCommerce that still matters a lot.

What they usually do not cover is product work. New landing pages. Checkout tweaks. A Laravel feature that sales promised. An integration that broke when the third party changed an endpoint. Two hours of "can you just" that eats the whole month's care budget before Tuesday.

If your site rarely changes and you mainly want updates and backups handled, a care plan is often the honest fit. If you are forever buying emergency hours on top of it, you already know the plan is too thin for how the site is actually used.

When you have outgrown updates-only

I see the same pattern with store owners and agencies. The site is live. Customers rely on it. Someone is always asking for a small change. Care tickets stack up, get deferred, or turn into separate quotes that slow everything down.

Typical signs:

• You open more change requests than the care plan can absorb.
• Production issues keep costing ad-hoc support hours.
• The site is a store, SaaS, or booking tool, not a brochure.
• Your previous developer left and nobody owns the codebase day to day.
• Agencies need overflow capacity that stays under their brand without a full hire.

At that point you still want hygiene (updates, backups, uptime). You also need someone with diary time for the awkward fixes and small builds, or a scoped project when the brief is bigger than a care ticket.

What I offer on the maintenance page

On my side, website care and support starts from the published care plans on the website maintenance page. WordPress care from £99 a month. WooCommerce care from £149 a month. Those cover the updates, backups and health checks that stop boring breakage becoming a customer problem. Small changes can sit inside the plan as limited hours, depending on the package.

If you need more than that (steady feature work, Laravel ownership, white-label overflow, or a living app that changes every week), we scope the extra hours or a retainer separately. I do not invent a higher "maintenance floor" price on this page. Bigger rebuilds, new websites, SaaS builds and vibe-code rescues stay as project work, with their own starting prices.

Care plan, extra hours, or project

Three different jobs. Mixing them up is how people get frustrated.

A care plan is hygiene. Keep the site patched and recoverable. Good for quieter marketing sites and smaller stores that barely change. Details and the live prices sit on website maintenance.

Extra hours or a scoped retainer are for when the site earns money every day and needs steady attention beyond updates. We agree the hours properly rather than pretending they fit inside a thin checklist.

A project is when the brief is a rebuild, a new website, a SaaS or app build, a vibe-code rescue, or a proper redesign. Do not try to squeeze that into a care ticket. It will not fit, and everyone will be annoyed.

If something is already on fire, one-off WordPress and WooCommerce support still exists for the awkward rescue jobs. That is separate from monthly care.

Want a straight conversation about which lane you are in? Use the form on dawsony.com and tell me what the site does, how often it changes, and what keeps breaking. I will say if care, scoped hours, or a project is the honest answer.

Website care from £99/month

Paying for reliability is cheaper than paying for weekends of emergency work. A thin plan is fine until it is not. When the site needs more than updates, buy the right shape of help. Cheers.