Protect the important journeys
Identify forms, checkout, sign-in and other business-critical flows. Updates should be verified against those dependencies instead of judged only by whether the homepage opens.
Website Maintenance & Support
Keep the website useful after launch.
Website maintenance and support for businesses that need dependable updates, content changes and a clear technical owner. We define the website’s dependencies, recovery needs and support scope before ongoing work begins.
An ongoing care cycle
- 01
Review
Know the site, accounts and important journeys.
- 02
Maintain
Apply agreed changes with a recovery path.
- 03
Verify
Check the pages and functions affected by the update.
An example journey, shaped around your requirements.
Start with the real need
Maintenance should have a scope people can understand.
Content editing, dependency updates and incident response are different types of work. A useful maintenance plan states what is included, how requests are prioritised and which systems remain the responsibility of other providers.
Keep recovery practical
Backups need to cover the relevant files and data, with an agreed restore process. Account ownership and release documentation help the business recover without relying on one undocumented setup.
A maintenance plan should explain what gets checked, who responds and how to recover.
Scope shaped around your business
What the work can include.
The final deliverables depend on the brief. These are the areas we review together before the build starts.
01
Website onboarding
Review the platform, accounts, hosting and current known issues.
A dependency and responsibility map.
02
Content update support
Handle the agreed copy, image and page changes.
A defined request and review flow.
03
Dependency maintenance
Plan supported software or plugin updates with appropriate checks.
Update responsibilities stated.
04
Backup and recovery review
Confirm what is backed up and how restoration is handled.
A practical recovery procedure.
05
Journey and performance checks
Review the agreed critical functions and recurring issues.
Evidence of affected behaviour.
06
Reporting and prioritisation
Keep a record of completed work, unresolved dependencies and recommended improvements.
A useful maintenance summary.
Before we begin
Decisions that shape the result.
A useful conversation resolves the requirements, responsibilities and trade-offs before they become surprises.
What counts as routine work?
A content edit and a new feature should not be treated as the same request.
Discuss before build: Define included work and escalation.
Who owns the hosting and providers?
Support depends on access and the responsibilities of external services.
Discuss before build: Identify the account and technical owners.
What response expectations are realistic?
Coverage and urgency should be explicit rather than implied by the word support.
Discuss before build: Agree hours, priorities and response targets.
From brief to working release
A clear path through the work.
The scope and milestones are agreed around the project. Each stage has something concrete to review.
- 01
Discover
Understand the audience, objective, content and current systems.
A shared brief. - 02
Design
Review the information, interface and important journeys.
A concrete design to assess. - 03
Build & verify
Implement the agreed scope and check the complete journeys.
A release with acceptance evidence. - 04
Launch & improve
Plan the switch, handover and ongoing responsibilities.
Ownership after launch.
Good questions
A clearer starting point.
Answers to the practical questions that often come before a project brief.
Can you maintain a site built by another team?
Yes, after an onboarding review of the code, hosting, dependencies and current issues. Access and documentation affect the initial scope.
Does maintenance include unlimited changes?
Only if explicitly agreed. The plan defines routine updates, request capacity and work that requires a separate estimate.
Are backups enough to guarantee recovery?
No. The backup scope, retention and restore process need to be checked. A useful plan documents the recovery procedure and its practical limits.
Can you fix performance problems?
Performance work can be included as a defined task or scoped improvement sprint. It should begin with an evidence-based diagnosis.
Read moreCan support include a redesign?
A major redesign is normally a separate project because it changes the page system and migration scope. Maintenance can support the existing site during that transition.
Have an idea worth building?
Let’s turn it into something your customers can actually use — and your business can grow with.