Website onboarding
An inventory of the CMS, hosting, themes, plugins and integrations, with access ownership and existing issues recorded.
Service inquiryWebsite maintenance services
Website maintenance your team can rely on.
Keep your business website maintained and give routine fixes an owner. We provide website maintenance and WordPress support around your CMS, integrations and publishing needs, with a defined work scope, reporting and response arrangements.
- WordPress and business websites
- Maintenance and development scope
- Named ownership and reporting
01 / The operating gap
A live website still needs someone to look after it.
We start with the point where value, trust or control is being lost. That keeps the project tied to a business decision instead of a generic list of deliverables.
Updates wait until something breaksUnreviewed dependencies and compatibility issues make changes harder to plan.
Small fixes have no ownerBroken forms, publishing errors and slow pages stay in a backlog while the business continues using the site.
Support coverage is unclearTeams do not know who receives alerts, what a support fee covers or how a serious incident is escalated.
02 / What you get
What website maintenance can include
We assess the site before agreeing a maintenance plan. Routine care, content changes, development capacity and incident response are listed separately so responsibilities and limits are clear.
WordPress maintenance
Core, theme and plugin updates with compatibility checks, backups and a recovery path appropriate to the site.
Monitoring and issue handling
Agreed availability and functional checks, an alert recipient, severity levels and an escalation route. Coverage and response times are written into the scope.
Fixes and ongoing development
Bug fixes, publishing assistance, performance work and agreed development capacity. Larger features and migrations receive a separate estimate.
Work log and reporting
A record of completed changes, checks, unresolved risks and proposed next work. You retain a visible view of what was done and why.
03 / Delivery path
Start with the estate, then agree the service
- 01
Review the website
Check the current CMS, hosting, integrations and support history. Identify urgent issues and onboarding needs.
- 02
Agree coverage
Define included websites, work capacity, update cadence, backup requirements, support hours and escalation.
- 03
Maintain and improve
Prioritise requests, make controlled changes and verify the affected website journeys.
- 04
Review the backlog
Report completed work and agree what comes next, including changes that need a separate project.
04 / Fit and boundary
For teams that need continuity after launch
A strong starting scope is specific enough to verify and important enough to change an operating or commercial result.
Good starting conditions
- A company needs an owner for website updates and technical fixes.
- An existing WordPress site needs regular maintenance and publishing support.
- A marketing team needs retained development capacity alongside routine care.
Scope considerations
- A major rebuild or migration is scoped as a project alongside maintenance.
- An active security incident needs an explicit incident-response scope.
- Infrastructure-wide DevOps and on-call coverage require separate service responsibilities.
05 / Questions
What buyers usually need to clarify before scoping the work.
The answers below define the normal starting boundary. The final scope follows your systems, evidence, risk and operating constraints.
Can you maintain a website built by another agency?
Yes, subject to an onboarding review of the code, access, licences, hosting and integrations. We identify any prerequisites before accepting ongoing responsibility.
Does WordPress support include unlimited changes?
Included work, capacity and exclusions are agreed in the proposal. Maintenance, small fixes and feature development are different types of work; larger requests receive an estimate.
Are hosting and paid plugin licences included?
Only when listed in the agreed scope. Ownership, renewal costs and third-party subscriptions are made explicit so your team can plan them.
Do you provide emergency or 24/7 support?
Support hours, incident severity, response targets and escalation are agreed for the engagement. A maintenance request does not automatically create round-the-clock coverage.
What does website maintenance cost?
The estimate depends on the website estate, current condition, integrations, update and backup needs, development capacity and support coverage. We can discuss those requirements in a free consultation.
Next useful step
We will help define the support your website needs.
Start with a free consultation. We will review the website, recurring requests and current support gaps, then propose a suitable scope.
Project request
We will propose the first practical step.