A rewrite has consumed budget without replacing the old application. Examine completed work against real journeys before commissioning another start.
Establish what works
Identify usable code and the assumptions it depends on. A polished interface may still lack permission checks or data migration. Separate these gaps.
Test a migration slice
Choose a small journey with representative historical data. Check whether it can run alongside the current application. Document incompatible rules and missing transitions.
Fund the next decision
Request a bounded assessment with reusable assets and remaining work. The partner should explain why each asset can be retained. Compare a limited recovery against a new rebuild using the same acceptance criteria, including the cost of running both systems during transition.
Related reading : Software rescue budgets: separate diagnosis from the repair commitment. Discuss your project scope with Sky Vaults.