Software Maintenance

Software maintenance for the system you already run.

When production breaks, know where to report it, who takes the ticket and when you’ll hear back. The Wavect Maintenance SLA pairs ongoing software care with written response targets for your system.

DIRECT ANSWER

The Wavect Maintenance SLA is a written support schedule for an ongoing software maintenance retainer. It sets the systems covered, the working hours and first-response targets by severity. Maintenance also covers agreed patches, bug fixes and small changes.

Best for

  • Owners of a production system that can be built and released, and needs a reliable maintainer
  • Teams whose developers have moved on to new work and want routine care handled

Consider another approach

  • A change of provider that needs access recovery and knowledge transfer first
  • 24/7 on-call operations or a contractual uptime guarantee

Start from a system someone can maintain

Maintenance assumes we can build, test and release the system. If access, documentation or the previous provider are the problem, that is a Software Takeover first; its handover, recovery and dependency upgrade offers keep their own scope and terms. If the onboarding check finds the system cannot be released safely, we say so before agreeing a maintenance scope. Structural change, such as replacing a framework or splitting a monolith, is Legacy Modernization.

What routine care includes

The agreement lists the systems and environments covered. Work outside that list is quoted before it starts.

Updates and security patches

Keep runtimes, frameworks and libraries on supported versions. Security advisories are triaged and patched in an agreed order of priority.

Bug fixing

Reproduce, fix, test and release defects reported by your team or found in logs and error tracking.

Small enhancements

Minor changes within an agreed monthly budget. Anything larger is quoted separately before work starts.

Monitoring hygiene

Keep error tracking, logs, certificates and alerts useful. Alerts route to a named person during agreed hours.

What does the Wavect Maintenance SLA include?

After onboarding, we quote a monthly maintenance retainer and agree a written support schedule. It names the systems and environments covered, the support channel, service hours and time zone, who can escalate, and how we measure response.

Critical incident

A core production workflow is unavailable and there is no workable alternative. We acknowledge the ticket, begin triage and agree when you’ll get the next update.

Degraded service

A production workflow is impaired but users can still work. We assess impact and confirm a workaround or the next action.

Routine request

Minor bugs, updates and small improvements enter the maintenance backlog and are scheduled within the agreed scope.

Response clock and reporting

The clock uses the agreed support channel and staffed hours. The monthly report shows ticket severity, first-response times, missed targets and follow-up actions.

Illustrative record: one month of maintenance

An illustrative monthly report lists dependency updates applied and deferred (with reasons), security advisories checked, bugs fixed with the release that contains each fix, small changes delivered against the agreed budget, open items and the decisions you need to take. This is an example format, not a customer result or a service-level commitment.

Onboard, maintain, review

The onboarding check is scoped and quoted on its own. The maintenance agreement follows from what it finds.
  1. Onboarding check

    We build, test and release the system once in an agreed environment. You receive a version inventory, known risks and a proposed maintenance scope.
  2. Ongoing maintenance

    A monthly agreement covering the agreed systems, working hours, request channel and response targets per contract.
  3. Periodic review

    Review what was done, what aged and what keeps breaking. A recurring structural problem becomes a separate modernization or security decision.

Bring access, the version list and the people who report problems

We need repository, CI and hosting access, the current version list, known issues, error tracking, the people who report problems and a person who can approve releases. Larger features belong to Software Development. For budgeting, the software maintenance cost guide explains typical cost drivers; its model is not a quote or a support commitment.

Choose a focused next step

These engagements cover specific needs within this service. Follow the scope that matches your decision.

Recurring monitoring and staffed response, including a separately agreed 24/7 arrangement, belong in Managed Cloud Operations; ordinary maintenance or migration does not activate that coverage.

// proof

Ongoing care in existing engineering work

IKB: Wavect worked inside IKB’s Smart City build on infrastructure and devices, handed the platform over to IKB’s in-house team completely, and stayed on as external support for new device integrations, the Grafana stack, field connectivity and manufacturer calls. MyMerch documents a multi-year engagement improving a working Shopify business in targeted steps without a rewrite. Polity documents long-running QA ownership with flakiness reduction and bug triage across services. None of these cases documents 24/7 coverage or an uptime commitment.

These are selected projects, not our full portfolio. We have shipped 100+ products since 2018.

Questions before you start

The Maintenance SLA covers first response within agreed working hours. For 24/7 monitoring, on-call staffing or a contractual availability target, scope Managed Cloud Operations separately after readiness and staffing are confirmed.
The signed schedule sets the target by severity and defines when the clock starts during staffed hours. First response means we acknowledge the issue and begin triage. The time needed to restore service or ship a fix depends on the incident.
Yes, if it can be built and released. The onboarding check shows that. If the previous provider is leaving and access or knowledge must be recovered first, that is a Software Takeover.
Small enhancements fit inside the agreed monthly budget. Larger features are quoted separately or handled as a Software Development engagement, so routine care does not quietly turn into an open-ended build.
As a monthly agreement for the agreed scope. Work outside that scope is quoted before it starts. We do not publish a price before the onboarding check, because the cost depends on the system.
List the systems covered, known issues, access, request priorities and response windows. Name who approves releases and unexpected costs. Distinguish routine care from new features and emergency coverage so a maintenance request has a clear route and commercial basis.

Scope your maintenance SLA

Describe the system, its stack, who maintains it today and what keeps slipping. Keep credentials and confidential data out of the first enquiry.