Tangensys • Plan, deliver, measure
Website maintenance
Keep routine updates, backups and small changes organised. Maintenance works best when the responsibilities and limits are written down before a problem occurs.
The work to plan together
A scope shaped around this requirement.
- Updates and security patchesScope
- Backups and uptime monitoringReview
- Monthly small changesCheck
- VisitorArrives on a phone or desktop
- NavigationFinds the right page quickly
- Form or integrationEnquiry, booking or order
- Your teamReceives it in the right place
In short
What does Website maintenance involve?
Website maintenance keeps a site secure, updated and working: updates, backups, monitoring, fixes and small changes each month.
When Website maintenance is a useful fit
Businesses without in-house developers
Agree which routine updates and incident responses require external help.
WordPress and Shopify sites
Check the platform’s actual update, backup and access arrangements rather than assuming identical needs.
Sites after launch
Define the handover, monitoring and change allowance before the build team steps back.
Problems worth addressing first
Use these situations to identify the work that deserves attention before expanding the scope.
- Plugins and core are out of date
- There are no backups
- Small changes wait weeks
A practical example
A plugin update is tested on staging, a recoverable backup is retained and the contact form is checked after release instead of assuming the update succeeded.
This is an illustrative scenario to explain the approach, not a claimed client project.
The work we can include
The final quote identifies the deliverables, quantities, approvals and exclusions. Select the work that serves your goal rather than assuming every item is required.
- Updates and security patches
- Backups and uptime monitoring
- Monthly small changes
- Issue fixes
Where we usually begin
Included hours, response targets, backup retention and emergency coverage are agreed in the plan. A new feature or redesign is separately scoped.
Practical detail
A maintenance record that shows what happened
An illustrative update log should let the owner distinguish routine maintenance from an incident or a new feature request.
| Part of the work | Example output | How to review it |
|---|---|---|
| Routine update | Component, previous/new version, date and staging checks | The agreed critical journeys still work after the change. |
| Backup check | Backup date, contents and a restore test record | A backup is considered usable only after the agreed recovery check. |
| Incident | Observed failure, effect, action and remaining issue | The owner can see whether the service was restored or only investigated. |
| New request | Feature description and separate scope decision | A redesign or integration is not silently treated as a routine update. |
Response times, coverage hours and included update volumes depend on the actual maintenance agreement. A log should report evidence rather than imply every issue has been prevented.
Separate routine upkeep from emergency repair
Website maintenance needs an agreed list of responsibilities. Updates, backups, content changes and incident response have different effort and access requirements. A monthly plan should say what is monitored and which issues become separately quoted work.
First establish the current website condition and restore route. Backups are useful only when someone can access and restore them. An inherited website with unresolved failures may need initial repair before it can reasonably enter routine maintenance.
Keep change notes and review important contact or purchase journeys after relevant updates. Agree how urgent issues are reported and who approves a rollback. Response windows and availability belong in the contract; they should not be implied by a maintenance label.
Free technical review
Start with a clear scope and a practical next step.
Tell us what you want to improve and share the relevant website or project details. We will review the starting point, recommend a suitable scope and provide a custom quote.
The initial review is free. Delivery, third-party charges and ongoing support are quoted separately.
Process
How the work is delivered
Review the starting point
Review the current setup, examples of the problem and the information needed to agree the work.
Agree scope and sign-off
Discovery covers existing code, users, data and external systems. We turn the main workflow into sign-off checks, then agree milestones and responsibilities.
Deliver and review
Changes are reviewed on a test environment before release. Handover includes agreed documentation, access and a maintenance route; ongoing support is separately defined.
Hand over the next steps
Review the agreed outputs together. Confirm what your team maintains and what needs a separate ongoing arrangement.
What progress should mean
Measures that match the work
Record updates, incidents, recovery checks and completed requests. Uptime alone does not show whether checkout, forms and key journeys are working.
A record of delivery
See what was completed, reviewed and still dependent on access or approvals. Project delivery and business results are reported separately.
Clear limits in the data
We explain what can be verified and where a result is only an estimate. Contact clicks, conversations and sales are different actions.
Scope and responsibilities
You keep ownership of your business accounts and approved deliverables under the agreed contract. Any third-party licences, subscriptions or usage fees are identified before you commit.
Are all future website changes covered by maintenance?
No. Specify the included updates and small changes, with limits where appropriate. New features, major redesigns and third-party failures may need additional scope. A clear plan distinguishes ongoing upkeep from development and incident investigation.
Does having a backup guarantee recovery?
No. Its completeness, age and restoration process matter. Agree what restore testing is included and what data may need reconciliation.
Are new pages and features included?
Only when stated. Maintenance, content changes and feature development are different workloads and should be separated in the proposal.
Do you maintain sites you did not build?
Yes, after an initial review.
How is Website maintenance priced?
We quote against your goals, current setup and agreed scope. The quote separates delivery from third-party costs and ongoing support. You receive a custom quote within 2 working days.
How long does the work take?
The timeline follows the size of the agreed scope, access, content and approvals. We confirm milestones in the quote; a simple change and a full implementation need different schedules.
How will we communicate?
Your point of contact agrees a review rhythm with you. We use email, WhatsApp and scheduled calls, with decisions and scope changes recorded clearly.
What do you need to get started?
Share your current website or system, your main goal and examples of what is not working. We then agree the access and information needed for discovery.
Is everything included in the free review?
No. The free initial review helps define the next step. Detailed research, design, implementation and ongoing support are included only when stated in your quote.
Explore the related services
Let’s agree the right next step.
Tell us your goals and current setup. We’ll recommend a practical starting point and provide a custom quote.
Custom quote within 2 working days