Back to Insights

Hourly Website Support Or A Monthly Plan?

31 Aug 20263 min read

An orange umbrella shelters a small white model house on a neutral surface.

You need a brochure replaced, an enquiry form checked or a problem investigated. Paying for the work as it comes up sounds straightforward.

But who is looking after the website between those requests?

That is the main question when comparing hourly support with a monthly maintenance plan. Both can be sensible. The difference is what someone has agreed to look after, and how the work is approved.

Separate Maintenance From New Work

It helps to divide your needs into three groups.

Maintenance keeps the existing website cared for. Depending on the platform and agreement, this may include software updates, backups and routine checks. For example, WordPress’s maintenance guidance covers updates, backups and broken links.

Support deals with questions and problems, such as an editor being unable to update a page or a form behaving unexpectedly.

Improvements change what the website does. Adding a new application process or connecting another business system is different from maintaining an existing page.

A proposal that simply says “website support” leaves too much open. Ask which of these groups it covers.

When Hourly Support Can Make Sense

Hourly work can suit occasional, clearly defined requests when someone already owns the routine upkeep.

You might need help adding a new office page while your internal team handles updates and checks. Or you may want a specialist to investigate one specific issue.

Before work starts, agree on the task, an estimate and a spending limit. Ask the provider to pause for approval if the investigation uncovers more work.

Also check whether time spent investigating, communicating and testing is included in the estimate. These are real parts of the job, not just the minutes spent making a visible change.

Hourly support does not automatically reserve immediate availability. If a deadline matters, confirm it before relying on it.

When A Monthly Plan Can Make Sense

A recurring plan can be useful when your website needs regular attention and your team does not want to arrange every routine task separately.

It may also suit a busy marketing calendar with frequent updates, provided those updates are actually included.

The value is clearer ownership and planned capacity, not an assumption that every request is free. A monthly fee can cover a defined list of checks, a time allowance, specific types of work or a combination.

Ask what happens to unused time, what happens when the allowance is exceeded, and which requests need a separate quotation.

“Unlimited requests” is not the same as unlimited work or immediate completion.

Ask About The Moment Something Goes Wrong

A quick acknowledgement is different from a completed fix.

Ask the provider to distinguish between receiving a request, starting an investigation and resolving the problem. Some issues depend on third-party services or require more investigation than others.

Useful questions include:

  • Which support hours apply?
  • How do we report an urgent problem?
  • What counts as urgent?
  • Who contacts the hosting or payment provider when needed?
  • What information will we receive while work is under way?

Do not assume a monthly plan includes round-the-clock support. Have the actual arrangements written down.

Compare The Work, Not Just The Price

Give each provider the same examples: a routine content update, a failed enquiry form and a new feature request. Ask how each would be handled and charged.

Then compare responsibility as well as cost. Who checks backups? Who keeps track of renewals? Who tests important journeys after an update? What does your own team still need to do?

A lower quote that leaves these jobs unassigned may not be a useful comparison.

Keep Control Of Your Website

Your business should know who owns the domain, hosting and website accounts, and how access will be handed over if the arrangement ends.

Ask for a clear record of completed work and outstanding issues. You should not need to understand the code to know what was checked, what changed and what needs a decision.

The right arrangement is the one that fits your workload and makes responsibility clear. Tell us what support you need, including what your team already handles, and we can discuss the scope.

Website MaintenanceWebsite Planning

Other Related Articles

View All