Managed care versus hourly support

Most WordPress site owners know they should not ignore updates forever. Fewer know what they are actually buying when they choose between a monthly care plan and an hourly developer on retainer — or on call.

The labels blur because both involve “someone technical watching the site.” The economics and expectations are very different. Picking the wrong model is how you end up with either surprise invoices or a false sense of safety.

What managed care is meant to do

Managed care — what Rescue 404 calls Website Care Plans — is ongoing supervision for a stable site:

• Scheduled updates with staging and rollback discipline when appropriate
• Verified backups — not just “a plugin says it ran”
• Uptime and error monitoring with someone who knows your stack
• A defined monthly allowance of support requests for small changes (hours, phone number, broken link, pixel install) — each typically about 30 minutes or less
• Managed hosting on eligible plans so resource limits and server config are not fighting the maintenance work
• Monthly or periodic health reporting so problems surface before they become outages

Care is preventive operations. It assumes the site basically works today and you want it to stay that way.

Care is not unlimited custom development, redesign, SEO campaigns, or emergency rescue at no extra charge. Those belong in other lanes — and saying that upfront saves arguments later.

Current Care tiers and what each includes are on Pricing and the Website Care Plans page.

What hourly support is meant to do

Hourly support bills time as tasks arrive:

• “Install this plugin”
• “Fix the contact form”
• “Something looks weird on mobile — take a look”
• “We are not sure what we need — start the clock and investigate”

Hourly work can be efficient when the task is small, named, and the site is otherwise healthy. It is a poor default when the site is down or access is missing — because the first hour becomes discovery and the invoice arrives before scope is clear.

Side-by-side expectations

Topic	Managed care	Hourly support
Billing	Predictable monthly plan	Per hour or per ticket
Best for	Stable sites needing supervision	Named tasks with clear scope
Updates	Scheduled, supervised, documented	Often on request only
Backups	Verified as part of the plan	Whatever exists — may not be tested
Emergency downtime	Care clients get prioritized response within plan terms; major rescue may still be scoped separately	Every minute billed; scope unclear until hours accrue
Small edits	Included within plan request allowance	Billed per task
Redesign / new pages	Out of scope — design lane	Sometimes sold hourly (often poorly scoped)
Hosting	Included on eligible Care enrollment	Usually client’s problem unless billed separately

Neither model is “better” in the abstract. They solve different problems.

When care is the better fit

Choose managed care when:

• The site is online and repair-complete — not mid-outage
• You want updates and monitoring handled without opening a ticket for each plugin release
• You would rather pay a known monthly amount than negotiate hours every quarter
• The business depends on the site for leads, bookings, or sales — downtime has a cost
• You are done with cheap shared hosting that breaks every update (Care-eligible sites normally migrate into managed hosting as part of enrollment)

If you are comparing care to “my nephew who knows WordPress,” the honest comparison is whether someone verifies restores and refuses bad updates on fragile themes — not the monthly price alone.

For the repair-then-care sequence, see Website repair versus website redesign — care assumes the foundation is sound.

When hourly is the better fit

Choose hourly when:

• The site is healthy and you need a single, well-defined task
• You already have competent internal ops and only need occasional specialist hours
• You are between agencies and need short-term help without a monthly commitment
• The stack is simple and you accept that nobody is watching it between tickets

Hourly can also be appropriate for agencies subcontracting a specific fix — as long as scope is written before the timer starts.

Be cautious with “hourly as pseudo-care”: paying someone five hours a month to “keep an eye on things” without defined deliverables often means updates happen when remembered, backups are assumed, and the first real outage becomes a rescue project at emergency rates.

What hourly support usually does not include

Unless explicitly contracted, hourly developers typically do not guarantee outage response times, run staging for every update, migrate you off bad hosting, or credit investigation toward a fixed repair when scope explodes. That is a different product — a transaction, not a care relationship.

What managed care usually does not include

Care plans also have boundaries. Rescue 404 Care does not replace:

• Emergency rescue on a site that is currently down (that starts with a paid diagnostic — see What a website emergency assessment includes)
• Full redesigns, new landing pages, or custom feature builds
• Marketing retainers, SEO guarantees, or ad management
• Access recovery when nobody can log into registrar, hosting, or admin (see How much access recovery can cost and why)
• Commerce-heavy store operations beyond brochure-level WooCommerce (that is a separate Commerce Systems product)

Clear excludes protect you as much as the provider. “Unlimited” care plans that secretly bill rescue hours are a billing trap.

The hidden cost of the wrong model

Care without eligibility — enrolling a fragile site on bargain hosting — produces theater: updates fail, backups cannot restore, and every month ends with “hosting is the problem” without a migration path.

Hourly without diagnostics — opening the meter on an unclear outage — produces invoices that feel random. That is why Rescue 404 starts new rescue work with a paid diagnostic credited toward repair when you proceed.

Redesign billed as maintenance — asking hourly help to “make the site modern” without a design scope — is redesign work wearing a maintenance label.

Before you enroll in care, ask what happens when an update breaks staging, how often backups are actually restored, and what occurs if the site is already down on day one. Before you open an hourly ticket, ask whether you can describe the task in one sentence — if not, you likely need a diagnostic first.

Putting it together

Use repair when something is broken. Use care when repair is done and you want supervised maintenance. Use hourly when the task is small, named, and the stack is stable.

Managed care is how you reduce the next emergency. Hourly support is how you execute a specific task. Confusing the two is how WordPress sites drift for years — updated just often enough to break, not often enough to be safe.

Rescue 404 sells Care for eligible stable sites and rescue for broken ones. We would rather tell you “this is a one-hour task” than enroll you in a plan you do not need — and we would rather tell you “this is down, start with diagnostic” than pretend a few monthly support requests will fix an active outage.