Software Project Rescue Consulting Services: How to Hire One and What You Should Get Back

A software project rescue consultant is an outside expert you pay to find out why your software is stuck or breaking, and to get it launched and stable. Judge one by what they hand back: a written diagnosis, options with costs and dates, and a system that developers who weren't on the rescue can maintain.

What a rescue consultant does

The Project Management Institute describes a rescue in five phases: mandate, assessment, definition, intervention and transfer.^[1] The assessment rests on documents, questionnaires, checklists and interviews. In software, that means someone reads your code and your plans and talks to the people who wrote them.

The definition phase then sets a new scope, schedule and budget.^[1] That is the answer to the question most owners start with. What will fixing it cost, and how long will it take? A consultant who names a price before looking at the code is guessing. One who can't name a price when the assessment ends isn't finished.

Five questions to ask before you hire

1. Whom have you rescued projects for, and can I call them? PMI advises anyone hiring outside experts to check credentials carefully. It says references from completed projects carry more weight than certifications.^[2]

2. What will you need to see? PMI says an assessment needs open access to all project information and team members. If the real state of the project is hidden, no one can form an accurate view.^[3] Expect to open your repository, your hosting accounts and your contractors to the consultant.

3. How will you find the root cause? PMI warns that recovery aimed only at restoring speed, without finding the causes, is unlikely to last.^[4] A consultant who promises a launch date in the first call hasn't looked for them.

4. What will you fix first? For a troubled project, PMI says stabilizing the product can matter more than making progress. The team should push forward only once the product is fairly stable. If an unstable or unfamiliar technology is causing the defects, it suggests switching to one the team knows.^[1] If your software keeps breaking, a new feature list is the wrong first step.

5. Who will do the work, and how did you choose them? Joel Spolsky, a software company founder, argues that developers are not interchangeable and that the best ones get ten times as much done as average ones.^[5] He also points out that a company hiring the top 0.5% of its applicants is not necessarily hiring the top 0.5% of developers.^[6] So "we hire the top 1%" tells you little. Ask how the consultant interviews and tests the people they bring in.

What you should get back

PMI describes a recovery report that lists the people interviewed, the documents reviewed, the issues found and their causes. It sets out the options with the pros and cons of each, and recommends one. If the report advises going on, it states the conditions for success and the corrective actions.^[7]

Ask for that. It lets you choose with the facts in front of you, and it lets you take the report to another developer for a second opinion. It should also say plainly when the right answer is to stop.

The rescue itself needs an end point. PMI notes that without completion criteria, it is hard to tell when normal work can resume.^[4] Ask what "done" means in writing, such as a launched product, a set number of open defects or a handoff date.

A system cheaper developers can maintain

Many owners hope a rescue will let them spend less on developers afterward. That depends on the quality of the code inside the product, which customers never see. Martin Fowler argues that internal quality lowers the cost of adding features. He cites a study that found fixing issues in low-quality code took more than twice as long, and that such code had 15 times the defect density.^[8] The Consortium for Information & Software Quality found in 2022 that technical debt, the cost of reworking weak code, had become the biggest obstacle to changing existing code.^[9]

So ask the consultant a test question: could a developer who wasn't part of the rescue change this system safely? Ask for the architecture written down and for a handoff. PMI treats the transfer of responsibility as the last phase of a rescue.^[1] Ask, too, what the system will cost to host each month once it is stable.

If your project is stuck or keeps breaking, a direct conversation with Robert Lara III is the quickest way to learn whether it can be saved, and what that would cost.