Core engagement
Focused App Recovery Sprint
Bounded implementation work that repairs the specific things diagnosis identified as mattering most — with acceptance criteria agreed before any code changes.
The implementation engagement
Bounded repair, with the boundary written down
This is where diagnosis becomes repaired software. The defining feature is not speed — it is that the edges of the work are agreed in writing before anything is implemented.
Looking for the broader category, the situations we handle, and our position on rewrites? That is App Recovery. This page is the specific engagement that implements the fixes.
Who this is for
- Founders who have a diagnosis and want the important findings fixed
- Teams who need senior help closing a specific set of defects
- Anyone who wants their existing application repaired rather than replaced
What you receive
- A written scope with explicit acceptance criteria and exclusions
- Repair of the agreed findings, in small reviewable changes
- Automated tests covering the behaviour that was repaired
- Verification in a real deployed environment, not only locally
- A delivery report covering what changed, what was preserved, and what was not verified
- Handoff documentation for whoever maintains it next
What this does not include
Stated plainly so there is no ambiguity later. Anything here can be scoped separately if you need it.
- Open-ended "fix my whole app" work
- Unlimited scope or unbounded hours
- New feature development unless explicitly scoped and quoted
- Ongoing support after handoff unless separately agreed
The outcome
The agreed findings are repaired, proven by tests, and documented — with the working parts of your codebase left intact.
Scope control
How the boundary is set and held
Most engagements go wrong not because the work was hard, but because nobody agreed where it ended.
Findings become scope
The sprint addresses named findings from diagnosis — not "the app". Each one is listed, so both of us can point at the list.
Acceptance criteria come first
Before implementation, we agree what "repaired" means for each finding, in terms that can be objectively checked rather than argued about.
Exclusions are explicit
What we are not doing is written down alongside what we are. Silence is where scope disputes grow.
Changes are raised, not absorbed
If something new surfaces mid-sprint, you hear about it and decide. We do not quietly expand the work and present it later.
Small reviewable changes
Work arrives in commits that can be read and reversed individually — not one enormous change nobody can review.
Milestones for larger work
Beyond a single focused sprint, work is split into funded milestones with acceptance at each, so neither side carries the whole risk.
Verification
“Fixed” means proven, not asserted
Every repaired finding gets an automated test that fails against the old behaviour and passes against the new one.
Verification runs in a real deployed environment as well as locally. That is not ceremony — in our own demonstration, an entire class of permission defect existed only once the application was hosted, and the full local suite passed the whole time.
You can read exactly how that played out in the ClientFlow case study, including the finding we did not expect to have.
About this price
From $1,750 reflects that recovery work varies with what diagnosis found. The starting figure is real, and the specific number is quoted from the actual scope — not estimated before anyone knows the cause.
If a Triage has already been completed, the quote comes from its findings, and you will recognise every line item in it.
After handoff
You receive a delivery report covering what changed, what was deliberately preserved, and what remains unverified — plus documentation aimed at whoever maintains it next, on the assumption that person is not us.
Ongoing involvement is available as Technical Stewardship, but it is optional. A recovery that leaves you dependent on the person who did it has not really succeeded.
Discuss a Recovery Sprint
Tell us what you are dealing with. If this is not the right fit, we will say so and point you at what is.