What happens in the first two days?
You give me access to the repository and the store accounts, and I read the code alongside the crash reports and the rejection messages. Within two days you have a written verdict: what works, what is broken, what it costs to fix and what it costs to rebuild.
Should I fix it or rebuild it?
Fix it when one thing is broken and the rest behaves. Rebuild it when every change is guesswork, or when the repair quote approaches the rebuild quote.
| The situation | Fix it | Rebuild it |
|---|---|---|
| One flow is broken, the rest behaves | Yes | No need |
| It crashes often and nobody knows why | Only if the cause turns up quickly | Usually cheaper in the end |
| The original developer left no notes | Risky, because every change is a guess | Often the honest option |
| You want a feature the design cannot hold | You pay for it twice | Yes |
| The repair quote is close to the rebuild quote | No | Yes |
What does a rescue cost?
The first call is free, and on that call I will tell you whether I can give you a verdict from what you can show me or whether I need paid time to read the code. Small jobs start at $50. Everything after the read is quoted as one fixed price, so you are never paying for guesses.