Support and maintenance

An agreed approach to issues, updates and new needs after your software is released.

Request an initial conversation

When you need it

Going live is a milestone, not the end of the work. A product evolves alongside workflows, integrations and people. You need to know who owns a request, how it is assessed and what happens next.

  • You want to organise support and maintenance after a release.
  • You have a product to update or evolve over time.
  • You need clearer handling of issues and priorities.

How we approach it

  1. Agree on the scope

    We define covered systems, contact channels, hours, priorities and request handling.

  2. Organise requests

    We distinguish incidents, updates and new features, making assessments and progress visible.

  3. Validate changes

    We plan testing and releases, updating documentation when product behaviour changes.

What you receive

These are typical service outputs. Scope, timing and responsibilities are defined in the proposal for your project.

  • Agreed support scope and responsibilities.
  • Request handling and prioritisation process.
  • Maintenance activities covered by the agreement.
  • Documentation of updates and changes.

Before we begin

Is support always available 24/7?

No. Coverage, on-call availability and response times depend on the agreement and service priority. They are defined before activation.

Can you maintain software built by others?

We assess code, documentation, access and dependencies before taking it on. The findings determine which activities we can cover.

Let’s start withwhat’s holding you back.

Tell us which product you want to maintain and how requests are handled today. We assess the systems before proposing a support agreement.

Request an initial conversation

The first conversation helps us understand the context. Audits, development and support each have their own scope and proposal.