Ace8 is the modernization practice of AceMQ.24/7 support from AceMQ after go-live
Book an Assessment
GuideBuyer's guide

How to choose a team for software rescue: nine questions before you hand over the code.

You are about to give a stranger the keys to a project that already went wrong. Ask these before you do.

AceMQ engineering team4 min readEngineer-reviewed

Stacks we work in

  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions
  • Java
  • Spring Boot
  • Kubernetes
  • PostgreSQL
  • Kafka
  • Docker
  • Terraform
  • GitHub Actions
The short answer

Choose a software rescue team by what it will look at before it quotes. A good team audits the code first, tells you what it found in writing, proposes a small first phase at a fixed price, and says plainly when a rebuild is the better answer. Score every proposal against the same nine questions below. This guide supports our software project rescue offer.

Next stepFixed-price assessmentInventory, risk score and a phased roadmap with a fixed price for phase one.Book a fixed-price assessment

01 · The questions

What should you ask a team that wants to take over your project?

Ask the nine questions below of every team and write down the answers, including ours.

#QuestionA good answer sounds like
1What do you do before you quote?Read the code, or run a paid audit, then quote the next phase
2What will the audit report contain?Findings ranked by risk, what to fix first, and a fix or rebuild view with reasons
3Will you say if a rebuild is the better answer?Yes, with the evidence, even though it changes the scope
4How do you stop things getting worse while you learn the code?Freeze risky changes, add tests, then change
5Who will work on it?Named engineers, with location and time zone stated
6Who owns the code, accounts and keys during and after?You do, from day one; you hold the repository and cloud accounts
7How is the work priced?A fixed price for a first phase; later phases agreed after it
8What happens at the end?A handover you can run without them, with documents and a deploy anyone can repeat
9Who runs it after launch?A plan agreed before launch, or a clean handover to your team

02 · Order of work

Why should a rescue start with an audit?

Because nobody can price a rescue honestly without reading the code.

  1. 01

    A team that quotes a full fix from a demo and a conversation is guessing, and you carry the cost of the guess.

  2. 02

    A code audit turns the unknown into a ranked list, and it is a cheap way to test a team before you commit to a larger phase. If you cannot get an audit first, ask for a first phase small enough to stop after. Ask also for the report in a form your next team can read, so the work is not trapped with the firm that wrote it.

03 · Warning signs

What are the red flags in a rescue proposal?

how-to-choose-a-software-rescue-team-review.mdEngineer review
Findings
F-01A fixed price for the whole job quoted before anyone has seen the code.
F-02A promise to fix everything without a fix or rebuild decision.
F-03No testing phase, and no plan to protect what already works.
F-04The team keeps the repository, hosting accounts or keys.
F-05A rebuild proposed by default, because rebuilds are bigger contracts.
F-06No named engineers, or a team that changes after signature.
F-07References you cannot name or check, and claims of results with no source.
Illustrative sample, not a real client report

04 · Types of team

What kinds of team take over failing projects?

Each type suits a different job, and none is best for all.

TypeTends to suitWatch for
The original vendorSmall fixes where the team still exists and knows the codeAn incentive to defend earlier decisions
Freelancers and small studiosSmall apps and tight budgetsOne person's availability; handover depth
Specialist rescue and engineering firmsAudits and takeovers with senior reviewSmaller capacity; fit with your stack
Large integratorsVery large programs with many workstreamsCost and junior staffing
Your own engineersLong-term ownership once the code is stableTime to recruit and onboard while the problem keeps growing

05 · Proposals

How do you compare rescue proposals fairly?

Give each team the same access and the same question, ideally a read-only copy of the repository and one page describing the problem, then compare scope lines, not totals.

  1. 01

    Two proposals at the same price can cover different work, so check what each includes: tests, deploy pipeline, documents, handover.

  2. 02

    Check what happens at each phase boundary and who carries the risk if a phase runs over. Ask whether a phase can be stopped without a penalty, and what you receive if you stop. For price context, see software rescue cost. Before you start, collect the items on the vendor handover checklist.

06 · Disclosure

How would Ace8 answer these questions?

Ace8 is the modernization practice of AceMQ, and we sell this service, so treat this as one set of answers among others.

  1. 01

    We audit first. The rescue audit has a fixed price agreed after a scoping call, and later phases are agreed once we have read the code. We tell you when the finding is a rebuild. You own the repository and accounts throughout.

  2. 02

    AceMQ engineers do the work, and AceMQ supports the result 24/7 after go-live if you want that; see supported after migration. Ace8 has no published rescue case studies of its own yet, so ask us for the audit sample rather than a client reference.

07 · Next step

What is the first step to take?

Send the repository and a short description of what went wrong.

  1. 01

    We scope an audit on a call, with no obligation to continue. Start at software project rescue.

FAQ

Frequently asked questions

Short answers to what buyers ask first. Something else on your mind? Ask an engineer.

Score each team against the same questions: what it does before it quotes, what the audit report contains, who owns the code, how the work is priced and what happens at handover.

Start here

Know the cost before anything moves.

A fixed-price assessment gives you the inventory, the risk score and a phased plan. Scope and cost are fixed before the migration starts.

Inventory
Every application, its stack and what it depends on.
Risk score
Where a change is likely to break, ranked.
Phased plan
What moves first, which tools lead, and the fixed price.

Get in touch

Talk to a modernization engineer.

Tell us what you run today. An engineer, not a sales script, replies within one business day.

305-204-2607info@ace8.io

66 W. Flagler St. 9th Floor
Miami, FL 33130

What are you moving off? *

Fixed price. Scope and cost before any migration starts.