Software Project Rescue: What to Do When Your Developer Fails to Deliver

Your developer disappeared. Or delivered something broken. Or your agency went quiet three months past the deadline. You have a half-built product, invoices paid, and no working software. Here is what to do: stop, assess, and rescue --- in that order. According to the Standish Group, 45% of software projects are delivered late and 7% are never delivered at all. McKinsey research shows that 17% of large software projects fail so badly they threaten the company's existence. Most failed software projects can be salvaged. The ones that cannot are usually cheaper to restart with the right team than to continue throwing money at the wrong one.

We have rescued 20+ projects at SystemForge. I am Pedro Corgnati, Founder and Full-Stack Developer, and this is the exact playbook we follow when a client calls in crisis. We assess your situation in 48 hours.

Need help right now? Message us on WhatsApp --- we respond within 2 hours on business days.

Step 1: Assess the Damage Before You Do Anything Else

Do not hire a new developer, do not try to fix things yourself, and do not make any changes to the codebase. First, secure your assets and understand what you are working with.

Get all source code into your own repository immediately. If you do not have access to the GitHub, GitLab, or Bitbucket repository where the code lives, that is your first priority. If the developer controls the repo, request a transfer or a complete export. If they are unresponsive, check your contract for source code ownership clauses. Every hour you do not control your code is a risk.

Request all documentation, passwords, and credentials. Server access, database passwords, third-party API keys, deployment configurations, domain registrar login, SSL certificates. Make a list and check every item. Missing credentials can add weeks to a rescue timeline.

Get a code audit. A senior developer can assess a codebase in 2-4 hours and tell you: Is the architecture recoverable? Is the code readable and maintainable? What percentage of the stated features actually work? How much of the code can be reused? A code audit costs $500-$3,000 depending on the size of the codebase. It is the single most valuable thing you can spend money on right now.

The hard question: rescue or restart? A codebase is worth rescuing when the architecture is sound, the code is readable (even if incomplete), and more than 40% of the features work. A codebase should be restarted when the architecture has fundamental flaws (wrong database design, no authentication framework, monolithic code that cannot be extended), the code quality is so low that fixing bugs creates new bugs, or the technology choices are outdated or inappropriate. The honest truth: rescue costs 40-60% of the original project if the architecture is sound. Restart is faster and cheaper if it is not.

The 4 Most Common Ways Software Projects Fail

1. Freelancer or agency disappeared or went bankrupt. The most traumatic scenario. One day they respond to messages; the next, silence. This happens more frequently with solo freelancers and small agencies without financial reserves. The Upwork freelance project abandonment rate without a formal contract sits around 60%.

2. Scope creep killed the budget mid-build. The project was $50,000. Then it was $75,000. Then $100,000. And it is still not done. Without milestone-based payments and a locked scope document, scope creep can consume any budget.

3. Technical debt so severe the product cannot be launched. The app "works" in demos but crashes in production. Performance degrades with real data volumes. Security vulnerabilities are baked into the architecture. The developer did not build for production --- they built for screenshots.

4. Product was built but does not work as specified. It exists, it runs, but it does not do what was agreed upon. Features are missing, workflows do not match the spec, and the UX is unusable. This usually results from poor communication during development and lack of regular demos.

Have you experienced one of these? Talk to us now --- we will tell you within 48 hours whether your project can be rescued and what it will cost.

How to Take Over a Half-Built Codebase

What a good rescue agency does first. We do not start writing code. We read code. The first 2-5 days are spent on assessment: running the existing application, reviewing the database schema, mapping what works versus what does not, and documenting every gap between the spec and the current state.

Estimating how much is done versus how much is left. Never trust percentages from the original developer. "80% done" often means "the easy 80% is done and the hard 20% will take longer than everything before it." We estimate based on working features, not lines of code.

Setting a new timeline and budget. A rescue project starts with a fixed-scope assessment (2-5 days, $1,500-$5,000). The assessment produces a detailed report: what can be kept, what must be rebuilt, estimated cost, and estimated timeline. This report is yours regardless of whether you proceed with us.

Working with the original developer's knowledge. If the original developer is still reachable, we include a knowledge transfer session before they disengage. Even a 2-hour call can save weeks of reverse engineering.

Your Legal Options (Briefly)

Review your contract. What was actually promised, in writing? Milestone deliverables, timelines, acceptance criteria --- these are enforceable. Vague statements like "build a custom web app" are not.

Deposit recovery. If milestone deliverables were not met, you may have grounds to recover payments. Small claims court handles disputes up to $10,000 in most US states. For larger amounts, a demand letter from an attorney ($300-$500) often prompts resolution without litigation.

IP ownership. If your contract includes a work-for-hire clause, the code is legally yours regardless of the developer relationship status. If it does not, consult an attorney before using or modifying the code.

When a lawyer is worth it. If the failed project cost exceeds $25,000, if there is no work-for-hire clause, or if the developer is withholding access to your code or servers. Below $25,000, the legal costs often exceed the recovery.

How to Avoid This Next Time

Five contract clauses that would have prevented most project failures:

1. Milestone-based payments. No more than 30% upfront. Each subsequent payment tied to approved, working deliverables.
2. Weekly demo requirement. The developer shows you working software every week. No demo, no next payment.
3. Source code access from day one. You have full access to the repository at all times. Non-negotiable.
4. Defined acceptance criteria per milestone. Written, specific, testable. Not "build the dashboard" but "dashboard displays X data from Y source with Z filtering."
5. Termination with deliverable handover. If either party terminates, all work product, documentation, and credentials are transferred within 48 hours.

These are not aggressive contract terms. They are standard practice for any professional agency. If a developer pushes back on any of these, that is your clearest red flag. See our full guide on how to hire a reliable development company from the start to avoid this situation. And read about why a fractional CTO prevents project failures if you want technical oversight without hiring a full-time CTO. For finding a replacement developer who can start immediately, that guide covers urgency hires. Also see what a proper web app development process looks like contrasted with what failed projects typically miss.

Rescue Readiness Checklist

Complete these 10 items in 30 minutes to prepare for a rescue call:

• Do you have access to the source code repository?
• Do you have all server and database credentials?
• Do you have the original scope document or contract?
• Can you list which features work, partially work, and do not work?
• Do you have access to the domain registrar?
• Do you have access to the hosting account?
• Do you know what technology stack was used?
• Can you access the database directly?
• Do you have copies of all invoices and payment records?
• Is the original developer still reachable (even if unresponsive)?

The more items you can check, the faster and cheaper the rescue will be. Missing repository access or credentials adds 1-3 weeks to any rescue timeline.

How SystemForge Handles Project Rescues

Our rescue process has three phases:

Phase 1: Assessment (2-5 business days, $1,500-$5,000). We review the codebase, run the application, map working versus non-working features, and produce a written report with a rescue-or-restart recommendation. You keep this report regardless of next steps.

Phase 2: Stabilization (1-3 weeks). If the project is rescuable, we fix critical bugs, secure vulnerabilities, and get the application to a stable baseline. The goal is not new features --- it is a foundation that does not break.

Phase 3: Completion (timeline varies). We build the remaining features according to the original spec (or a revised spec if the original was unrealistic). Milestone-based payments, weekly demos, and your full access to the codebase from day one.

Typical rescue cost: 40-60% of what the original project should have cost, assuming the architecture is sound. For projects where restart is the better option, we provide a complete rebuild proposal.

Message us on WhatsApp now. We respond within 2 hours on business days and can begin assessment within 48 hours of engagement.

Frequently Asked Questions

How much does a software project rescue cost?

Assessment costs $1,500-$5,000 and takes 2-5 business days. Full rescue typically costs 40-60% of the original project budget if the architecture is sound. If a restart is needed, expect 70-90% of what a clean build would cost, offset by existing design work and validated requirements.

Can any codebase be rescued?

No. Codebases with fundamentally flawed architecture, severe security vulnerabilities baked into the core, or technology choices that are obsolete or inappropriate are often cheaper to restart than to rescue. The assessment phase determines this before you commit.

How do I know if the new agency will not do the same thing?

Demand the five contract protections listed in this article: milestone payments, weekly demos, repository access from day one, defined acceptance criteria, and termination with handover. Any professional agency will agree to all five without hesitation.

How long does a typical project rescue take?

Assessment takes 2-5 business days. Stabilization takes 1-3 weeks. Completion depends on how much work remains, but most rescues we handle are completed in 6-12 weeks after the assessment phase.

Should I try to recover money from the original developer?

If the contract clearly defines deliverables that were not met, and the amount exceeds $10,000, a demand letter from an attorney ($300-$500) is worth trying. For amounts under $10,000, small claims court is an option. For amounts under $5,000, the time and stress often outweigh the recovery.