Scheduled updates
Platform, dependency, and plugin updates applied on an agreed cadence with a verification pass afterwards.
Website Maintenance
Websites decay quietly. Dependencies fall behind, forms stop delivering, images bloat, and nobody notices until a customer does.
Keep a published website current through scheduled updates, monitored delivery of critical paths, and a predictable route for small content and design changes.
Overview
Small, regular work prevents large, urgent work
Most website emergencies are the accumulated cost of skipped routine work: an unpatched dependency, an expired integration credential, or a contact form that has been failing silently for weeks.
Maintenance turns that into a rhythm — a review cadence, an agreed change route for content and small design work, and verification that the paths that matter still work after every update.
What this includes
Website Maintenance capabilities
A maintenance arrangement can stay narrow or include content and design changes; scope follows how much the site changes month to month.
Content and design changes
A predictable route for copy edits, new sections, and small design adjustments without ad-hoc escalation.
Critical-path verification
Regular checks that navigation, forms, search, and key conversion paths still behave as expected.
Performance and media upkeep
Reviewing page weight, image handling, and caching as content is added over time.
Backup and restore expectations
Documented backup coverage and a tested understanding of what restoring actually involves.
What you receive
Concrete deliverables
- Maintenance scope and cadence agreement
- Update, verification, and change log
- Periodic performance and link review
- Documented escalation and restore path
Why it matters
Practical outcomes
Fewer urgent incidents
Routine updates keep small problems from compounding into outages.
Changes have a route
Content and design requests follow a known process instead of individual favours.
Visible state
A change log makes it clear what was updated, when, and why.
Protected critical paths
The pages and forms that generate enquiries are the ones that get verified.
Scope and third parties
Maintenance covers the website and the parts of its stack you own. Availability of the underlying hosting, CDN, and third-party services remains subject to those providers’ own terms; no independent uptime figure is offered.
How maintenance works month to month
From an unmaintained site to a predictable routine.
-
Baseline the site and its risks
Record the current platform, versions, integrations, and the pages the business cannot afford to lose.
-
Agree the update and backup routine
Agree the update cadence, the backup arrangement, and who approves changes that carry visible risk.
-
Apply scheduled updates
Apply platform, plugin, and dependency updates on a known schedule rather than in reaction to a problem.
-
Verify the critical paths
Check the pages and forms that matter after each update instead of assuming nothing moved.
-
Report and handle change requests
Report what changed and handle small content and design requests through one predictable route.
What we hold ourselves to
Maintenance is the work that prevents the emergency.
These are the commitments behind an arrangement that is quiet because it is working.
- 01
Updates applied before they are urgent
Routine currency keeps upgrades small, because a deferred update becomes a migration.
- 02
Verify the paths that earn money
Contact forms, checkout, and key landing pages are checked explicitly after every change.
- 03
Restores that have been rehearsed
A backup counts only once a restore has actually been performed and timed.
- 04
Changes that are reversible
Every change has a way back, so a bad update is an inconvenience rather than an outage.
- 05
Written record of what changed
Work is documented so the site never depends on one person remembering how it was configured.
Relevant technology
What keeps a live site healthy
The content platform being maintained, the monitoring that notices problems, and the checks that catch regressions.
Capability domain
5 tools
CMS
- WordPress
- Joomla
- Headless CMS
- Contentful
- Strapi
Capability domain
8 tools
Frontend
- TypeScript
- JavaScript
- Angular
- React
- Next.js
- Vue.js
- Nuxt
- Tailwind CSS
Capability domain
5 tools
Monitoring
- Sentry
- OpenTelemetry
- Grafana
- Prometheus
- Application logging
Capability domain
7 tools
Testing
- Pest
- PHPUnit
- Playwright
- Cypress
- Vitest
- Jest
- Postman
Scope boundaries
Where this work hands off
Keeping a site current borders on rebuilding it, on running its infrastructure, and on supporting real software; these are the dividing lines.
-
Application Maintenance & Support
A published site and a piece of software with a domain model, permissions and integrations need different attention. Applications are supported under the engineering engagement.
-
Website Development
Maintenance keeps the current site healthy. A redesign, a migration, or a new section is project work with its own shape.
-
Managed Hosting & Infrastructure
We look after the site; provisioning and operating the infrastructure underneath it is a separate arrangement under your own accounts.
-
CMS Development
Routine content and design changes are included. Changing the content model itself — new types, new editorial workflow — is a CMS engagement.
Questions
Useful context before a consultation
Maintenance questions usually concern response expectations, what counts as a small change, and how backups are proven.
Do you offer a fixed monthly package?
Scope and cadence are agreed per site. We do not publish a package or a service-level guarantee that has not been scoped against an actual site.
Can you maintain a site you did not build?
Usually, after a review of its platform, dependencies, hosting access, and current condition. That review establishes what can be maintained responsibly.
Does maintenance include hosting?
It can be combined with managed hosting, but the two are separate services and can be engaged independently.
What counts as a small change?
Copy edits, image swaps, new pages built from existing components, and minor styling adjustments. Anything that changes the content model or introduces a new template is quoted as project work rather than absorbed quietly.
How quickly do you respond?
Response expectations are agreed per engagement against what the site does and what an outage would cost. We do not publish a standard response time we have not committed to.
Start a conversation
Keep a live website in good condition
Tell us what the site runs on, who changes it today, and what has been neglected.