Compare a small business website maintenance plan by asking who does the work, what evidence you receive, and what happens when a request falls outside the agreement. A useful proposal names responsibilities for backups, updates, content edits, inquiry checks, incidents, and account handover. “Ongoing support” needs those details before you can judge whether the plan fits your business.
For a local-service owner, begin with the website functions your office relies on. A simple informational site and a site with booking or connected intake tools may need different support scopes. Ask providers to explain their recommendations using your actual setup rather than a standard activity list.
Start with a responsibility matrix
List the work you want covered and ask each provider to complete the same matrix. Keep the owner’s responsibilities visible too: someone in the business must approve service information, report operational changes, and authorize work beyond the agreed scope.
| Work area | Responsibility to name | Evidence or boundary to request |
|---|---|---|
| Backups and recovery | Who maintains copies and handles restoration? | What is covered, where the record lives, and how recovery is checked |
| Software updates | Who reviews and applies relevant changes? | Components included, exclusions, and checks after a change |
| Content edits | Who receives and publishes approved revisions? | Included edit types and what becomes a new assignment |
| Inquiry delivery | Who checks the route from website to office? | A test record and the person handling failed receipt |
| Incidents | Who assesses an issue and coordinates correction? | Contact route, escalation, and approval rules |
| Account handover | Who documents access and transfers working knowledge? | Account inventory, usable records, and responsibilities at exit |
Have the provider identify items that another company controls. Hosting, domain registration, booking tools, and email delivery may have separate owners in your setup. A maintenance agreement should say how those dependencies are coordinated.
Axon Media’s website design and development service is a relevant starting point for discussing the site’s structure and ongoing needs. Whatever provider you choose, ask for a scope your office can use when an issue occurs.
Ask what a backup commitment actually includes
A proposal should identify which website materials its backup arrangement covers. Depending on the setup, ask about content, files, configuration, and data needed to restore the functions you rely on. Do not assume every account or connected service is included.
Request the proposed backup process, retention arrangement, and location of the records. Ask who can access the necessary materials if the support relationship ends. Record any platform limits the provider identifies.
Then ask how recovery is checked. A provider should be able to explain the proposed restoration process, who performs it, and what would be verified afterward. If a recovery exercise could disrupt the live site, agree on a suitable way to test it separately.
Treat a backup record and a recovery plan as distinct deliverables. The business needs to understand what was saved and what still depends on another account, supplier, or missing input. Avoid accepting a promise that every possible incident can be reversed.
Define updates and content edits separately
For software maintenance, ask the provider to name the relevant components it manages and those it does not. The plan should describe how changes are reviewed, applied, and checked, including what happens if a problem appears.
Match the checking scope to your business functions. If inquiries are essential, include that path in the proposed check after a relevant change. A statement that an update was applied does not explain whether the functions your office needs were examined.
For content support, agree on the kinds of revisions included. Updating approved hours or replacing a supplied photograph is a different assignment from planning a new service section, writing its copy, or building a new integration.
Use examples to clarify the boundary:
- Is a correction to an existing service description included?
- Who prepares the wording and approves its accuracy?
- Does adding a service require a new page or fit an existing section?
- Who handles image permissions and descriptions?
- What happens when a request needs design or development work?
Ask the provider to flag a new scope before starting it. The office should receive a description of the work, its dependencies, and the proposed commercial terms rather than discovering the boundary afterward.
Include inquiry checks and an incident route
Describe the contact path your business wants checked: the visitor submits a request, the system reports its state, and the intended person receives usable information. Agree which parts the provider checks and which parts your office must confirm.
For a test inquiry, ask for a record of the route used, the observed result, and any exception needing action. Keep real customer details out of routine test material. A visible success message alone should not serve as the office’s receipt check.
Incident handling needs a similarly clear route. Specify where staff report a problem, what information they supply, and who decides the next action. Distinguish acknowledgment, investigation, and correction in the provider’s commitments; these are different stages.
Ask how the provider handles an issue in a connected service it does not manage. Who contacts that supplier? Who keeps your office informed? Who can approve a temporary workaround or additional work?
For local businesses, an incident plan should reflect the way staff actually use the website. Choose practical reporting and escalation arrangements they can follow.
Require an exit handover and compare the final scope
Ask for an account inventory that identifies what the business controls, what access the provider uses, and any unresolved dependency. Keep credentials out of the comparison worksheet; use the agreed secure access process.
The exit plan should state which records, approved assets, website materials, and outstanding issue notes will be supplied. Confirm who will explain the current setup to a replacement provider and what remains outside the handover.
Compare proposals by reading across the matrix. A narrower plan can be appropriate if your business or another supplier owns the remaining work. A broader plan can be useful when it closes specific responsibility gaps. Neither is easier to assess when its exclusions are hidden.
Your next action is to mark each work area as provider-owned, business-owned, separately supplied, or unresolved. Resolve the consequential gaps before accepting the plan. If you need help turning that matrix into a workable support scope, discuss your website with Axon Media.