No products in the cart.
A business website needs attention after launch, even when its content rarely changes. Customers rely on it to find information, send inquiries, or make purchases. Keeping those everyday tasks working is part of owning the site.
For a small business owner, the question is how much of that upkeep to handle yourself and when to bring in help. A website maintenance plan can take recurring work off your hands and give you someone to contact when problems come up. Before committing to a monthly fee, you need to understand what your platform already handles, what the provider will manage, and what you’ll still need to handle.
What Is a Website Maintenance Plan?
A website maintenance plan is a recurring service for looking after an existing website. It may cover software updates, backups, monitoring, checks of important features, and help with errors or content changes. The work depends on how the site is built and what the agreement includes.
On a self-hosted site, someone must manage the website software alongside hosting. With a hosted website builder or e-commerce platform, the platform handles more of the underlying infrastructure and software. A maintenance provider may instead focus on content, forms, connected services, and the customer experience.
Coverage varies by provider. One plan might include scheduled checks and notifications when something needs attention. Another might cover investigating and repairing certain problems for a flat fee. The agreement should distinguish the provider’s work from responsibilities already covered by your platform or host.
Hosting may be included, too. It provides the infrastructure that runs the website, while maintenance covers the agreed work of looking after it. Larger changes, such as adding a booking system or rebuilding page layouts, generally need a separate scope and estimate.
What Should a Website Maintenance Plan Include?
A maintenance plan should state what gets done and how often. The schedule should reflect how much your business relies on the site, how frequently it changes, and which features customers need to use.
Software and Integration Updates
The software work depends on your platform. A self-hosted site may need updates to its content management system, themes, and plugins. A hosted platform may handle its own updates, while connected apps, custom code, and third-party services still need attention.
The provider should explain which parts they maintain and how they check changes. Where they control updates, that may involve creating a recovery point, applying the changes, and testing important pages and features. More complex changes may need testing on a separate copy of the site before they reach customers.
The plan should also explain how urgent security fixes and compatibility problems are handled. If the platform controls an update, establish what the provider can investigate or adjust and when the platform’s support team needs to get involved.
Backups and Recovery Options
Find out how your website can be recovered after an error, accidental deletion, or other disruption. Depending on the platform, recovery may involve a full backup, saved versions, or restoring particular types of content. The plan should explain what it can recover and what it doesn’t.
For a self-hosted site, backups may need to include both website files and a database. On a hosted platform, ask what its recovery tools cover and whether you need separate exports or backups. An export of content or products may not be enough to recreate the whole website.
Establish how often information is saved, how long it’s retained, and who handles restoration. Recovery needs should follow the pace of changes on your site. A rarely updated portfolio has different needs from a shop receiving orders throughout the day, where restoring older information could affect recent transactions.
Security and Downtime Monitoring
Downtime monitoring checks whether a site is reachable. Security checks may flag known vulnerabilities in installed software, suspicious changes, or signs of an intrusion. A proposal should identify which checks are included rather than grouping everything under “website protection”.
Monitoring can reveal problems that would otherwise go unnoticed, but it won’t catch every fault. A site may load normally while a customer-facing feature fails. That’s why monitoring and functional testing both belong in the maintenance scope.
Checks of Forms, Bookings, and Purchases
Testing should follow the actions customers take on your website. For example, a contact form might display a success message without delivering the inquiry. Checking that process means submitting a test message and confirming that it reaches the intended destination.
Work with the provider to identify a short set of essential actions, such as completing a booking, placing an order, or accessing a purchased download. The plan should record what gets tested and when, including checks after updates that could affect those features.
Performance Checks
Ask whether the plan includes checking for slow pages and investigating noticeable changes in loading time. Establish which fixes are included and when further work needs a separate estimate. Routine checks may reveal a problem, while resolving it could involve changes to hosting, images, plugins, or page design.
What Support Is Included When Something Goes Wrong?
You should know how to reach the provider and what help is available before you need it. Support terms should cover working hours, urgent requests, and when additional work requires your approval.
Response Times and Urgent Problems
A promised response time may mean someone will acknowledge your message or begin investigating. It doesn’t necessarily mean the problem will be resolved within that period. The provider should explain the commitment and how they’ll keep you informed while work continues.
Monitoring hours and support hours can also differ. Automated checks may run around the clock while someone reviews alerts only during business hours. Find out who receives those alerts and what happens when a serious problem occurs outside normal hours.
The definition of an emergency should reflect the effect on your business. A fault that prevents customers from completing transactions needs a different response from a cosmetic issue. State any extra charges for urgent or after-hours work in advance.
Repairs and Additional Charges
Repair coverage needs more detail than “support included”. A provider might cover problems caused by their maintenance work while charging separately for an existing fault or a failure involving another service. The agreement should explain whether the fee includes investigation, repair, or both.
For problems involving a hosting company or another software provider, establish who coordinates the work. Your maintenance provider may handle those conversations, or they may give you findings to take to the other company.
Backup restoration and malware cleanup also need stated terms. Storing backups and running security checks don’t necessarily include the labor required to recover a site. No plan can guarantee that an incident will never happen, but it should explain what assistance you’ll receive if one does.
Small Changes and Support Allowances
Some plans include time for edits to existing content, such as updating business hours or replacing a staff photo. Ask for examples of eligible requests, how the time is measured, and whether unused time carries forward.
You may need to supply finished copy or suitable images before an edit can begin. If a request exceeds the allowance, the provider should explain the additional cost and get your approval before proceeding.
What You’ll Still Need to Handle
Agree on who manages domain renewals, hosting payments, and software licenses, especially when those costs sit outside the plan. You’ll also need to provide content changes, approve additional work, and tell the provider about changes others make. If you edit the site yourself, establish which changes need a quick check with them first.
How to Compare Maintenance Plans
Give prospective providers the same description of your site, including its main features, connected services, and known problems. Their proposals should explain how they’ll support that setup. A generic package description may need a few written clarifications before you can compare it with another offer.
Compare the full cost, including any required setup work and separately billed services. Use these categories to check each proposal:
| Cost | Details to compare |
|---|---|
| Recurring fee | Scheduled work and included support |
| Initial assessment or cleanup | Required work and one-time charges |
| Hosting and software | Included services and separate renewals |
| Additional requests | Rates, estimates, and approval process |
| Emergency help | Covered hours and additional fees |
More complex sites can justify a higher fee because they take longer to test and troubleshoot. A membership site with payments and custom integrations involves more work than a small informational site. The proposal should connect the price to that work.
A sample maintenance report can help you judge how well a provider communicates. Request one with client information removed. It should show completed work, check results, and unresolved problems. If something needs your approval, you should understand the decision without interpreting a software log.
Keep promises about search rankings or lead generation separate from the maintenance comparison. Those goals may require content, SEO, or design work beyond routine upkeep. Choose a maintenance plan based on the work and support it commits to delivering.
Do You Need Ongoing Maintenance Support?
An ongoing plan is worth considering when your website supports daily business, and nobody has time to maintain it consistently. Having someone familiar with the site can also reduce the time spent explaining its setup whenever you need help.
The consequences of an interruption matter. A consultant with a small portfolio may be comfortable handling routine tasks and occasionally hiring help. A business that relies on online bookings needs to consider how quickly it could get assistance if customers couldn’t book.
If your current approach covers upkeep, testing, and recovery, you may not need another service. Check for gaps before adding a monthly expense, especially where your host and developer already share the work.
A recurring fault may need a focused repair before you choose a maintenance plan. Paying someone to check an unreliable feature more often won’t resolve its underlying problem. Unsupported software may need replacing, while custom features may need documentation or repairs before a provider can maintain them reliably.
Frequently Asked Questions
Before starting a plan, settle how access, hosting, and any future handover will work. These details can affect both the initial setup and your ability to change providers later.
Confirm the start date and whether the provider needs to complete an assessment or initial repairs first. Ask who handles urgent problems during that setup period and whether the work costs extra. If you’re switching providers, coordinate the handover so responsibility for the site stays assigned throughout the transition.
Not necessarily. Some providers support your existing setup, while others require their own hosting. If you use a hosted website builder or ecommerce platform, hosting is part of that service, so moving to another platform could involve rebuilding parts of the site. Ask whether the proposal requires any move, why it’s needed, and what it would involve.
Yes, although they may need to assess it before agreeing to ongoing support. Share any documentation, known problems, and details of custom features. The assessment should identify what needs to be done before maintenance begins and anything the provider can’t support.
Your business should control its domain registration and retain access to the accounts it owns. Give the maintenance provider a separate login where possible. If hosting or paid software comes through the provider’s account, establish how you would move or replace it when the arrangement ends.
Check the notice period and handover terms before signing. Before support ends, arrange a current backup, relevant documentation, and access to any accounts you’ll need. Confirm when bundled hosting or software licenses expire so you can make other arrangements in time.
Putting This Into Practice
Write a short maintenance brief before requesting quotes. Include your website address, the customer actions it needs to support, who currently handles upkeep, and any recurring problems. Note which tasks you’re comfortable keeping and where you need help.
Ask providers to explain how their proposed service covers those needs, including any work required before the plan starts. That gives you a concrete basis for comparing the fee and deciding whether the arrangement fits your business.
Work With TCB Studio
If you need help with an existing website, explore TCB Studio’s Web Development services. Send your website address, current hosting details, and a short description of the upkeep or problems you need help with so we can discuss the scope of work. Have questions? Contact us to get started.
