How we work

From “nobody agrees what’s wrong” to an operational system.

A structured route with a clear decision point. You can stop after any step. We would rather you did than continue something that no longer makes sense.

  1. Recovery Conversation

    One conversation

    A confidential conversation with executive management to establish whether the situation is appropriate for intervention. We listen, ask the awkward questions and tell you honestly whether we can help. If we can’t, we’ll say so.

    What you getA clear view on whether an assessment makes sense.

  2. Software Recovery Assessment

    Normally 5–10 working days

    A focused, independent assessment of everything between the investment and operation. We talk to people on every side — management, users, the project team, the implementation partner and the vendor — and look at the evidence. It is deliberately not another enormous consulting report.

    • Original business objectives
    • Expected operational outcomes
    • Current implementation status
    • Contractual and project scope
    • Business requirements
    • Critical functionality
    • Integrations
    • Data readiness
    • Testing
    • User acceptance
    • Go-live criteria
    • Project governance
    • Decision-making
    • The customer–supplier relationship
    • Organisational dependencies
    • Commercial dependencies
    • The genuine blockers to operation

    What you getAn answer to one question: what prevents go-live?

  3. Recovery Decision

    Presented in person

    Management receives an executive-level Recovery Decision. It answers the questions that matter and reaches one of four conclusions. The aim is not to force every project into go-live. Independent judgment matters more.

    1. Is the implementation recoverable?
    2. What is actually preventing delivery?
    3. Which issues genuinely prevent go-live?
    4. What decisions are required — and from whom?
    5. What must be delivered before go-live?
    6. What can safely be deferred?
    7. Who needs to do what?
    8. What is the shortest credible route into operation?
    • Recover

      The foundation is sound. Focus, decisions and a tighter go-live scope will get it live.

    • Restructure

      Recoverable — but not in its current form. Scope, plan, governance or contract need resetting first.

    • Replace

      Part of the solution, or the delivery model, cannot get you there. Replace it deliberately, not in anger.

    • Stop

      Sometimes the honest answer. Stopping well costs less than failing slowly.

    What you getRecover, restructure, replace or stop — with the reasoning and the route.

  4. Executive Intervention

    As long as it takes — and no longer

    Where recovery is viable, we lead it. A temporary role across everyone involved, restoring focus, decisions, accountability, alignment and momentum. We separate true go-live requirements from improvements and backlog. The existing implementation team stays if it can deliver.

    Executive managementBusiness ownersUsersThe customer organisationThe implementation partnerThe software vendorTechnical teamsExternal specialists

    What you getDelivery that moves again, towards a date people believe.

  5. Go-live

    The point of it all

    The objective is not a prettier project plan. It is an operational system, used by real people for real work.

    What you getA system in operation.

  6. Stabilise & Exit

    Then we leave

    We stay until the solution is stable and your organisation can carry it on its own. Then we leave. We don’t build consulting dependency — our success is measured by how little you need us afterwards.

    What you getAn organisation that runs its system without us.

How we behave

Five principles.

  1. Problem, not blame.

    Finding fault is easy and changes nothing. We look for what blocks delivery.

  2. Independent judgment.

    No software, no partner and no answer to sell. We say what we see.

  3. Decisions over documents.

    A short, clear decision beats a long report nobody acts on.

  4. Must-have versus nice-to-have.

    Go-live needs what operation needs. Everything else can wait.

  5. Temporary by design.

    We are there to make ourselves unnecessary.

Have a project that should have been live by now?

Let’s establish what’s actually preventing it.

Start a confidential conversation

Initial conversations are confidential and exploratory. No obligation, no sales pitch.