A useful maintenance service should reduce operational risk, keep the site understandable and create a clear record of what changed. The work depends on the system, its age, its traffic and the cost of failure.
Website maintenance services / Observe → repair → verify
Website maintenance and support that starts with the real cause.
I handle one-off fixes and ongoing website maintenance with the same discipline: inspect the live behaviour, make the smallest safe change and prove that the important paths still work.
Practical maintenance
Maintenance is not a monthly list of unexplained tasks.
One-off or ongoing
Choose the relationship that matches the problem.
- 01
One-off technical work
A focused repair, deployment issue, integration problem, small feature or measured performance task. Current pricing starts from £250.
- 02
Ongoing maintenance
Monthly coverage for updates, planned improvements and recurring technical responsibility. Current pricing starts from £150/month.
The working scope
What website maintenance can cover.
- 01
Diagnosis and incident repair
Find the cause before changing production code or configuration.
- 02
Updates and dependency care
Apply relevant framework, plugin or package changes with compatibility checks.
- 03
Backups before material changes
Create a usable rollback point before work that can affect live data or behaviour.
- 04
Performance and reliability
Investigate slow paths, heavy assets, failing jobs and fragile integrations.
- 05
Security and access hygiene
Reduce obvious exposure, review permissions and handle sensitive configuration carefully.
- 06
Planned improvements
Deliver small features and technical refinements without turning maintenance into an undefined rebuild.
Custom and WordPress sites
Different systems need different maintenance plans.
I can support custom Laravel applications and WordPress websites, but the scope depends on access, hosting, current dependencies, previous customisation and the quality of the existing codebase.
Clear expectations
Support terms should match the system and the risk.
Response expectations, monitoring and emergency coverage are agreed around the actual site. I do not advertise an invented 24/7 support desk or promise a response window that has not been contracted.
Safe changes
Inspect, protect, change, verify.
- 01
Access and baseline
Confirm the environment, current health and the paths that cannot be interrupted.
- 02
Cause and scope
Separate the visible symptom from the underlying problem.
- 03
Rollback point
Create the minimum useful backup before material production work.
- 04
Implementation
Make the smallest change that solves the agreed problem.
- 05
Verification
Check the affected path and any connected service that could regress.
Common questions
Before I take responsibility for a live site.
How much does website maintenance cost?
Ongoing maintenance currently starts from £150/month, while focused one-off technical work starts from £250. The real range depends on the system, access, risk and expected coverage.
Can you maintain a WordPress website?
Yes, where the hosting, plugins, theme and previous customisation can be reviewed. WordPress maintenance is handled inside the wider support service rather than through a thin separate package.
Can you take over a site built by another developer?
Yes, after access and a focused technical review. I need to understand the deployment, data, dependencies and existing failure risks before making promises about ongoing support.
Do you offer emergency support?
Urgent work can be assessed individually, but guaranteed emergency availability only exists when it has been explicitly agreed as part of the support arrangement.