First, understand it.
Then put it right.

1. Understand the project and the pressure.

The first conversation establishes what the system was meant to do, what has gone wrong and what a successful recovery would mean. We also discuss what is already live, who depends on it and any immediate concerns.

This is the free initial assessment. Its purpose is a high-level view and a useful next step. It does not replace a technical investigation.

2. Agree the investigation.

If a closer look is needed, we scope the work, access and expected output. Depending on the problem, that may involve the application, AI workflow, data, infrastructure or integrations.

The aim is to establish the actual blockers, separate causes from symptoms and make a defensible recommendation about what to retain, repair or replace.

3. Scope and carry out the recovery.

We agree the implementation work, responsibilities and acceptance criteria before proceeding. Your existing developers or delivery partner can remain involved where that supports the recovery.

Costs and timing reflect the project. A launch-blocking backend gap, an insecure application and a poor RAG answer are different engineering problems.

4. Check the outcome and hand over.

The checks should match the problem being fixed and the outcome agreed. We establish those checks during scoping, then make the changes and their operating implications clear to the team taking the system forward.

What to bring to the first conversation

• A plain-language description of what the product or system should do.
• One or two examples of what currently fails.
• Its stage: prototype, pre-launch or live.
• The result you need and any deadline that matters.
• Who owns the code, infrastructure and relevant accounts.

Please keep credentials, source code and sensitive production data out of the initial enquiry. Any necessary access can be agreed separately.