Digital development · Consulting · AI automation
MAINTENANCE & SUPPORT
A clear plan for ongoing digital care.
Keep your website, application or software supported through an agreed scope for maintenance, updates and issue handling.
Defined coverage
Planned maintenance
Clear escalation
Ongoing review
Support Services
Website Maintenance
Plan platform updates and compatibility checks.
Application Support
Review issues and changes affecting mobile applications.
Software Maintenance
Maintain agreed features and integrations.
Updates & Enhancements
Prioritise useful improvements within a defined scope.
Monitoring Requirements
Agree what needs monitoring and how issues are reported.
Support that is defined before you need it.
Your proposal confirms covered systems, support channels, availability, response expectations, exclusions and any third-party costs. Report issues by email with a description, affected URL and the steps that produced the problem; do not send passwords.
Setting Up Ongoing Care
01 · Review the System
Assess the platform, condition, dependencies and access needed before agreeing coverage.
02 · Define Coverage
Confirm covered systems, service hours, reporting channels and exclusions.
03 · Plan Maintenance
Agree update windows, backup responsibilities and checks before changes.
04 · Apply & Validate
Make agreed changes and check the affected workflows.
05 · Document Changes
Record the work completed, outcomes and any unresolved issues.
06 · Review the Plan
Revisit priorities, recurring issues and support needs as the system evolves.
Maintenance Plans
Scope, response arrangements and pricing are agreed after reviewing your systems.
Essential Care
For a defined website or application: planned updates, routine checks and an agreed issue-reporting process.
Professional Care
For active systems: Essential Care plus agreed performance reviews, prioritised improvements and a scheduled maintenance plan.
Tailored Support
For connected or complex environments: define application coverage, infrastructure responsibilities, escalation and reporting around your needs.
How Support Requests Are Handled
| Step | What happens |
|---|---|
| 1. Report | Describe the issue, affected page or system and its impact. Do not send passwords or sensitive records. |
| 2. Assess | Review the request against the support scope and agree its priority. |
| 3. Resolve | Investigate, propose a fix and apply the approved change. |
| 4. Review | Confirm the result and record any recommended follow-up. |
Support Questions
A technical review is needed first to check the platform, condition, access, dependencies and support requirements.
Coverage, frequency, retention, alerts and restore responsibilities are specified in the selected support agreement.
Availability, service hours, escalation and response targets must be agreed in the support scope; they are not assumed for every plan.
Use your agreed reporting channel. Include the affected address, what happened, when it started and the impact. Do not send passwords in an ordinary support message.
Yes. Enhancements are reviewed separately from issue resolution and assessed for scope, effort and dependencies.
Hosting, licences and provider subscriptions are included only where the written proposal explicitly says so.
Support Channels
Use the channel agreed for your service. Availability and response arrangements depend on your support scope.
Ready to turn your ideas into reality?
Tell us what you want to achieve. We will help define the right scope and next steps.
