Audit
Code, architecture and dependency review.
Taking over someone else's codebase blind is how migrations blow their budget. We audit first, so both sides know exactly what state it's really in before agreeing a plan.
Code, architecture and dependency review.
Findings and a costed rescue or migration plan.
Get the existing app back to a shippable state.
Phased move to Flutter where agreed.
Feature parity testing against the original app.
Documentation and a maintenance plan going forward.
The parts that matter when you don't fully trust the codebase you're inheriting.
No commitment until both sides know the real state of the code.
Migration happens in stages, so the app stays shippable throughout.
User data migrates without disrupting people already on the app.
You get documentation, not just a working build and a shrug.
Common. The audit is designed to work from the codebase alone, without needing input from the original team.
No — many rescues just need stabilisation and targeted fixes, not a full rebuild. The audit tells us which one applies.
Depends on codebase size and complexity — the audit gives a realistic estimate before you commit to anything.
Tell us what you know about it. We'll tell you what an honest audit would find.