The original developer is gone
You have code and business expectations, but no reliable picture of what works, what is missing or how to release it.
Software project rescue
Get a stalled software project moving again.
I turn an unclear codebase, unfinished release or failing delivery into a practical recovery plan and the next production milestone.
Work directly with the senior engineer responsible for delivery.
Recognizable situations
You may be here because
The project keeps absorbing time
Bugs, unclear priorities and changing estimates make it hard to decide whether to repair, reduce or replace the current solution.
A critical release is blocked
The team needs a senior engineer to isolate the constraint, reduce the scope and take ownership of a credible next milestone.
The outcome
A defensible next decision and a shipped milestone
Rescue begins by separating facts from assumptions. When the codebase is understood, the implementation sprint targets one recovery milestone with explicit acceptance criteria.
- Codebase, environment and delivery assessment
- Risk and dependency map
- Prioritized recovery options
- A reduced, testable next milestone
- Implementation and production release when feasible
- Handover notes and post-release support window
How the work runs
Clear decisions before code.
- 01
Establish the facts
I inspect the code, environments, known failures, release path and the business outcome the project was meant to support.
- 02
Reduce the uncertainty
You receive options, risks and a recommended milestone small enough to estimate and verify honestly.
- 03
Recover delivery
With scope agreed, I fix and release the milestone, document the state and make the next decision easier.
Why Cavendish
Senior ownership without the agency layers.
I have more than ten years of software engineering experience across agencies, established organizations and a global marketplace. I work directly in existing systems and stay responsible for the path from diagnosis to release.
- Experience
- 10+ years
- Delivery
- Direct with João
- Working hours
- US and Europe overlap
Commercial scope
Software Rescue Sprint
Implementation from US$4,000
If the technical state is not yet knowable, we start with Technical Discovery from US$1,500. You keep the assessment whether or not you hire me for implementation.
Clear boundaries from the start
- No fixed repair promise before code and access are assessed
- One prioritized recovery milestone per implementation sprint
- Rebuilds, vendor failures and new product scope are priced separately
Questions before we talk
Practical details.
Can you quote the whole rescue immediately?
Only when the codebase and failure are already clear. Otherwise a confident fixed quote would hide uncertainty. Technical Discovery creates the evidence needed for an implementation decision.
Will you recommend a rebuild?
Only when the evidence supports it. Repairing, reducing scope or replacing one component is often less risky than starting over.
What do we keep after discovery?
You keep the system assessment, risks, options, proposed acceptance criteria and implementation recommendation. It is useful even if another team performs the work.
Start with the real problem
Tell me what needs to work differently.
Share the current systems, the blocked workflow and the result you need. I will reply with questions, a sensible next step or a clear no-fit.