Review before taking over
Understand the platform, access, hosting, backups and current issues. We identify initial fixes separately from the ongoing maintenance scope.
Maintenance & support
Keep it working. Know who to call.
Websites and business systems need attention after launch. We agree a practical care plan for updates, backups, checks and support, with clear responsibilities and a route for issues that need more work.
THOUGHTFUL SYSTEMS. PRACTICAL PEOPLE.
A practical approach
Care that matches the system you run.
Make routine care routine
Agree an update schedule, backup responsibilities and checks for important pages, forms and workflows. Test changes before applying them where the setup allows.
Keep support clear
Define how to report an issue, what the plan covers and when a change needs a separate quote. Support hours and response expectations are agreed in the plan.
Care for the connections.
Keep the whole system in view.
Understand the dependencies, check the changes and keep people informed.
- Observe
- Maintain
- Improve
What is included
Clear work. A usable handover.
A useful starting point: a website or system that needs a care plan. We confirm the final deliverables in your scope.
- An initial website or system review
- Agreed updates and compatibility checks
- Backup and recovery responsibilities
- Checks for key pages, forms and integrations
- Monitoring and issue reporting within scope
- A clear process for support requests
- Documentation of important changes
- A handover route if you change provider
Scope & investment
A clear quote for the work you need.
Maintenance is agreed after a review.
The plan depends on the platform, its condition, the systems covered and the agreed support scope. Initial repairs, larger changes, hosting and third-party charges are identified separately.
You receive the scope, responsibilities and costs before work begins.
Before we begin
A few practical questions.
Can you maintain a website you did not build?
We can assess it first. Access, platform condition, hosting and existing problems determine whether we can take it on and whether initial remedial work is needed.
Does a care plan include redesigns and new features?
Only where they are explicitly included. Larger changes, migrations and redesigns are scoped separately so the ongoing plan stays predictable.
Is support available around the clock?
Support hours, response expectations and escalation arrangements are agreed before the plan starts. We do not assume a 24-hour service.
Do you also maintain AI workflows and open systems?
Yes, where agreed in the scope. That can include integration checks, workflow monitoring, source updates, backups and small improvements, with responsibilities matched to the system.
One useful place to start
Let’s look at what needs looking after.
A website or system that needs a care plan. A conversation can help define the scope and next step.