Ongoing Maintenance.
Scheduled site care, content updates and a defined route for support.
Ask about this package Tailored scope. Price on enquiry.
Your next
chapter.
Teams that need a dependable way to maintain their site and handle regular improvements.
A documented maintenance routine, named responsibilities and visibility of changes and outstanding issues.
Know who looks after the site after launch.
Sites change after launch: service information is updated, software dependencies evolve and integrations need attention. A maintenance plan gives those tasks a schedule, an owner and a record. It also gives your team a defined way to request changes or report a problem.
We review the platform, hosting setup, access and existing issues before proposing the plan. That establishes what we can support, which responsibilities sit with another supplier and whether any separate repair work is needed. Routine maintenance is distinguished from a redesign or a substantial new feature.
The agreement specifies the check schedule, supported hours, content-change allowance and response expectations. Completed work and unresolved issues are recorded. If a request falls outside the plan, we assess it and explain the additional scope before work proceeds.
Connected.
Considered.
- 01Initial site and dependency review
- 02An agreed update and backup routine
- 03Routine functional and availability checks
- 04A defined allowance for content changes
- 05Issue triage and a clear support channel
- 06Maintenance notes and improvement recommendations
One scope.
Connected workstreams.
A supported technical baseline
We review the system, access and existing dependencies, then agree the update and backup responsibilities appropriate to the setup. Any problems that require separate remediation are identified before ongoing care begins.
Routine checks and changes
Follow the agreed schedule for functional checks, updates and content changes. Record completed work and issues so the business can see the current state of the site.
Issue handling and next improvements
Support requests follow a clear route, with priority and response expectations specified in the agreement. Larger improvements are assessed separately, including their dependencies and effect on the existing experience.
Review the current system and agree the supported scope.
Establish access, backups and the maintenance schedule.
Review completed work and plan the next improvements.
A good brief.
A shared understanding.
We agree the supported scope, operating hours and request process before starting. Maintenance reporting records relevant work and open issues. Hosting costs, third-party licences and development beyond the allowance remain explicit items in the agreement.
What to bring to the first conversation
- The website and details of its hosting and platform
- Appropriate access and the current backup arrangements
- A description of routine change needs and important site functions
Bring what you have. We can work through the open questions together.
Good questions.
Clear answers.
Is round-the-clock support included?
Support hours, response targets and any urgent coverage are defined in the agreement. They are not assumed to be 24/7.
Can you maintain a site built by someone else?
Often, after an initial technical review. We confirm the supported platform, access requirements and any existing issues before proposing a care plan.
Are redesigns included in maintenance?
A defined allowance can cover routine changes, but a redesign or a substantial new feature needs its own scope. We assess the request before it becomes an unplanned commitment.
How are backups and recovery handled?
The plan identifies who owns backups, which parts of the system they cover and the agreed recovery process. The arrangements depend on the platform and hosting environment rather than a universal assumption.
Let's shape the right scope.
Tell us about the business, the problem and the outcome you want. We will discuss where to start.