← All services

Software stabilisation and maintenance

The software exists. Make it reliable again.

We take over existing applications, including those built by others: diagnosis, verified fixes and agreed ongoing support.

Discuss this project

When it makes sense

  • Errors and fragile integrations interrupt work.
  • The application is incomplete or every release is difficult.
  • The previous supplier no longer supports the project and ownership is unclear.

The outcome to agree

A clear technical picture, prioritised issues and verified interventions on agreed problems. Then, if needed, a maintenance agreement.

What we deliver

  • Inventory of code, dependencies, access, data and environments.
  • Reproduced issues, risks and an action plan separating verified and unverified items.
  • Agreed fixes and regression checks on affected workflows.
  • Release and recovery procedures, documentation and a follow-up backlog.

The first step

Software stabilisation and maintenance

Start with a takeover diagnosis. The inventory, priorities and plan remain useful even if you do not continue with LuCz. Stabilisation and maintenance are separate next steps.

Discuss this project

A clear scope

  • Stack compatibility and access are checked before promising coverage or timing. React, Next.js, TypeScript and Node.js are the main stack.
  • Major rewrites, new features, urgent work and support coverage require a specific agreement.

Price and timing are defined for your case after the brief. Deliverables, access, ownership, licences and support are explicit in the proposal.

How we get there

  1. 01

    Reproduce the issues and reconstruct the project’s technical state.

  2. 02

    Work through milestones with checks before and after fixes.

  3. 03

    Verify release and recovery and agree any ongoing support.

What we need from you

  • Legitimate access to repositories and environments.
  • A contact who knows the expected behaviour.
  • Reproducible examples, logs and necessary data, shared through agreed channels.

Relevant experience

Development and delivery experience

Matteo’s professional experience includes code review, maintenance and releases. His background is on the Founder page; the plan for your application starts with its diagnosis.

Explore the experience →

Before we start

  • Yes, after checking the stack, access and code. How it was built does not replace a diagnosis of the application.

Discuss this project

Price and timing are defined for your case after the brief. Deliverables, access, ownership, licences and support are explicit in the proposal.

Let’s discuss your project