01 / The approach
Publication is a beginning.
Not the end of the project.
Your content changes, software receives updates and new requests appear as your business develops. A maintenance plan gives those tasks a defined place instead of leaving them until something needs urgent attention.
We review the website and its dependencies, then agree what will be maintained, how requests are submitted and which checks are appropriate. The arrangement is based on the actual system, not a promise that every issue can be prevented.
A good fit for
- Businesses that want a clear point of contact after launch
- Teams needing regular content or technical updates
- Existing websites that need a structured support arrangement
02 / What we can build
What we can build.
Technical maintenance
Review and application of agreed updates, taking account of compatibility, access and the testing options available for your website.
Backups & recovery planning
An agreed backup approach and recovery responsibilities. Storage, retention and restore checks depend on your hosting and the support scope.
Content & small changes
A defined allowance or process for text, image and other agreed changes. New functions and larger redesigns are estimated separately.
Support & review
A channel for requests, agreed priorities and periodic review of key functions. Monitoring frequency and response times are written into the arrangement.
The exact scope, integrations and deliverables are agreed in your proposal. Not every project needs every feature.
03 / How we work
How we work.
Assess
We review the website, platform, hosting and available access.
Agree
We define covered tasks, request handling, priorities and responsibilities.
Maintain
We carry out the agreed work and check the functions affected by changes.
Review
We revisit the plan when the website or your business requirements change.
04 / Before we begin
Before we begin.
What we need from you
- The website address and a description of its platform and hosting.
- Authorised access and information about existing backups or support arrangements.
- Your priorities, expected request volume and a responsible contact.
What we agree together
We specify covered work, service hours, response targets and exclusions. A maintenance arrangement does not imply 24/7 availability, guaranteed uptime or unlimited changes. Third-party outages and major recovery work are assessed under the agreed terms.
05 / Questions & answers
Questions & answers.
Can you maintain a website you did not build?
We can assess it first. Acceptance depends on the platform, code condition, documentation and access available; a review or initial cleanup may be required.
Is emergency support included?
Only when explicitly agreed. Service hours, response targets and how urgent issues are handled are defined in the support arrangement.
Does maintenance include a redesign?
Not automatically. Routine updates and agreed small changes are distinct from new pages, new functions or a redesign, which can be scoped separately.
Are domain and hosting renewals included?
Only when they are part of the agreed service. We clarify who owns the accounts, who receives renewal notices and who is responsible for payment.