Website Maintenance Packages: What to Include and Charge

A local business website is not finished when it goes live. Opening hours change, contact forms need checking, and somebody must know how to restore the site if a change breaks it. A website maintenance package turns those recurring jobs into a bounded service that both the client and the designer understand.

The important distinction is between maintaining the site you delivered and promising to do whatever the client asks next month. Those are different products and should have different prices.

Quick answer

To sell a website maintenance package, specify the recurring checks, backup and recovery responsibility, a monthly allowance for small edits, response times, and what costs extra. Price it from your tools, hosting, expected hours, and a buffer for support rather than copying a competitor's monthly fee. Put the package on a separate line from the one-time build, and review its actual workload after a few months.

• Care: monitoring, backups or a tested rollback process, and periodic checks.
• Edits: a finite allowance with a definition of a small change.
• Projects: new pages, redesigns, integrations, and copywriting quoted separately.

What belongs in a maintenance plan?

Start with the stack you actually run. A WordPress site and a static brochure site do not need the same work. WordPress's maintenance guidance covers routine backups and updates; a static site may have no plugins or database to update. Do not charge for a monthly "plugin update" on a site without plugins.

For a typical local-business site, consider these deliverables:

1. Availability and contact checks. Confirm the home page, key service pages, phone links, and contact or booking form work. Specify how often and where alerts go.
2. Recovery. Identify who owns the hosting account, where backups live, who can restore them, and when a restore was last tested. For a deployment-based site, document the rollback steps instead of claiming a backup exists when it does not.
3. Software updates where applicable. For WordPress, specify responsibility for core, theme, and plugin updates, and test the critical pages afterwards. A static site needs a different checklist.
4. Content maintenance. Offer a defined number of small text or image edits, such as changing holiday hours or a service description. The client supplies approved text and rights-cleared images.
5. A short status note. Tell the owner which checks and changes were done, what failed, and which decisions you need from them. Do not promise a monthly analytics presentation unless it is part of the scope.

Google's Search Console guide explains how to inspect search performance and indexing issues. An occasional check can be useful, but ongoing SEO work, rankings, and new content are not interchangeable with technical maintenance.

Three package shapes you can adapt

These are illustrative offers, not market rates or guarantees. Adjust the work, price, and response window to your own costs and capacity.

Essential care: example $75 per month

For a small static brochure site: an availability and form check, a documented restore or rollback route, and one short status email. Content changes are quoted separately. This suits a client who wants someone accountable for basic site health, not a standing editor.

Care plus edits: example $175 per month

Everything in Essential, plus up to 45 minutes of client-supplied text and image changes per month, with a stated turnaround during business hours. Define whether unused time expires or rolls over. Test affected pages and forms after changes.

Managed care: quote per site

For WordPress, booking integrations, multiple locations, or frequent changes, add the platform-specific update process, a backup schedule and restore test, more editing time, and an agreed support window. Price the site after you inspect its plugins, traffic-critical forms, licenses, and hosting. Do not put an unexamined legacy site on the same flat fee as a new static site.

The first two examples assume you can deliver the work profitably. If hosting is included, name the host, who holds the account, renewal responsibilities, and whether third-party fees are part of the price. Do not imply that a site will never go down; name how you detect and respond to an outage instead.

How to set your monthly price without guessing

Write down the cost of fulfilling the promise before you set a public price:

1. Add monthly hosting, paid tools, licenses, and monitoring costs attributable to this client. Separate pass-through charges from your service fee if useful.
2. Estimate routine monthly time: checks, updates, reports, and administration.
3. Add an allowance for irregular support and the edit allowance you promised.
4. Multiply total expected hours by your sustainable internal hourly rate, then add direct costs. Check that the result leaves room for the margin and risk you want to carry.
5. Review time logs after the first few billing cycles and adjust the package for future renewals if reality differs from the estimate.

For example, if your direct costs are $20 per month and you expect one hour of work at a $70 internal rate, your illustrative cost floor is $90. A $75 plan with that scope would not cover those assumptions. Reduce the included work, change the tooling, or charge more. This is a worked example, not a recommended price for every designer.

The same cost-floor discipline applies to the initial project. The small-business website pricing guide shows how to scope and quote the build separately.

Put the boundaries in writing

A useful plan description answers questions before there is an urgent request:

• Small edit: for example, replace supplied hours, a paragraph, or one photo on an existing page; state the monthly time allowance and whether it rolls over.
• New work: a new page, new layout, booking integration, SEO campaign, and copywriting require a separate quote and approval.
• Response versus resolution: say when you will acknowledge a request and when work normally starts. Acknowledging an outage is not a promise to fix a third-party host instantly.
• Emergency path: define what counts as an emergency, contact hours, and whether after-hours work costs extra.
• Accounts and exit: record who owns the domain, hosting account, site files, content, and backups; explain the handover and any transfer fee if the client leaves.
• Payment: set billing date, third-party renewal treatment, and how the package changes or ends. Have the client approve changes to scope in writing.

The proposal template shows where to put this recurring offer next to, but not inside, the project price. Before offering it to an existing client, use the website audit checklist to document what you would actually be taking responsibility for.

A repeatable monthly checklist

For each client, keep a dated record of the check, result, and follow-up:

1. Open the live site and test the primary contact route with a safe test submission agreed with the client.
2. Check certificates, domain renewal status, and the owner of each account.
3. Confirm the documented recovery route still works; periodically test a restore or rollback without disrupting the live site.
4. Apply platform updates if included, then re-test key pages and forms.
5. Complete approved small edits and record the time used against the allowance.
6. Send a concise status note with unresolved items and the next action owner.

A deployment platform's rollback is not necessarily a complete backup of site data. For instance, Cloudflare Pages documents production deployment rollbacks, but a separate form backend or customer database needs its own recovery plan.

Where Opportunora fits

Opportunora helps an operator find local-business prospects, prepare a site for review, publish after approval, and draft an invoice. It does not replace the maintenance agreement you make with a client or guarantee their hosting uptime. If you sell both a build and a care plan, keep the recurring obligation explicit in your offer. See the product workflow or start a free trial to explore the build-to-invoice process.

Frequently asked questions

Is hosting the same as website maintenance?

No. Hosting keeps site files available; maintenance defines who checks the site, handles changes, and responds when something fails. Hosting can be part of a package, but name its cost and account owner separately.

Should I offer unlimited edits?

Not unless you have defined exactly which requests qualify and have priced for the capacity they can consume. A time or task allowance with separate quotes for larger work is easier to deliver consistently.

Does a static website need a care plan?

It can, especially when someone must monitor the live site, update hours or services, check forms, manage domain renewals, and retain a recovery path. Its plan should not claim WordPress-style plugin maintenance.

When should I offer the package?

Introduce it in the initial proposal as an optional, separately priced line item. Confirm the handover and account ownership before launch, then start recurring billing only on the date specified in the agreement.