Services / Project rescue

Your software project is late, over budget or abandoned. We take it over.

We assess what is there in 2-4 weeks: what works, what does not, what it would take. Then we stabilize, re-plan and deliver. Where needed we step into product owner and technical lead roles until the project is back on track. We have done this inside a bank, on a delayed project nobody wanted to own.

Describe it in writing Prefer to talk? Book a 30-minute meeting

Rescue requests get a written reply within one business day, from an engineer.

16 engineers, available fastEU-based teamIT-liability insuredNDA before you tell us anything

How a rescue works

Assess, stabilize, deliver, hand over.

Step 1

Assess, 2-4 weeks

We read the code, the backlog, the contracts and the deployment, AI-assisted, and talk to the people who know. Output: a written picture of what exists, what is salvageable, the real risks, and a plan with an effort range. Duration and cost agreed before we start.

Step 2

Stabilize

Stop the bleeding: builds that work, environments that can be recreated, backups that restore, a specification of what the system does today extracted from the code. Time-boxed, with a clear exit criterion.

Step 3

Deliver

Re-planned scope delivered in 2-3 week iterations against the specification. Demo every iteration, releases tested and reversible. You see progress in software, not in status reports.

Step 4

Hand over, or run

The project goes back to your team with a current specification and documentation. Or we keep running it under an SLA. See application maintenance.

Signs it is time

If two of these are true, write to us today.

The go-live date moved twiceAnd the new one has no plan behind it that anyone can explain.
The vendor has gone quiet, or goneInvoices arrive, demos do not. Or the company no longer exists.
Nobody can say what the system doesThe spec is a folder of old decks; the truth is in the code and in one person's head.
The key people are leavingThe two developers who understand it have handed in their notice.

What we need from you

Access, a decision maker, and honesty.

Access

Read access to the repository, the backlog, environments and contracts. An NDA first, if you prefer; we sign yours.

One decision maker

Someone who can say yes or no within a day. Rescue projects die of committees.

The real picture

What was promised, what was paid, what was delivered. We have seen it before; nothing you tell us will surprise us.

Reference

Rescues we can talk about.

Rescue engagements are rarely publishable; clients do not advertise that they needed one. We share more in conversation and under NDA, within what our clients' own confidentiality agreements allow.

Is a project on fire right now?

Describe it in two or three sentences. An engineer replies, not a sales desk, within one business day for rescue requests.

Prefer to talk? Book a 30-minute meeting

Describe it in writing