Your web app, database, payment system, and mobile app are all live and serving real customers. The goal of this engagement is to put every part of that system back under accounts you own and control — cleanly, without interrupting live traffic or payments.
Based on current evidence, the platform appears highly recoverable. Your production database and its business data, your backend functions, your web application, and your published Android app all still exist and are accessible under accounts you hold. This is not a rebuild-from-zero situation — the evidence points to a structured recovery and ownership transfer rather than a ground-up reconstruction.
| Asset | Status | What it means for you |
|---|---|---|
| Web application | Recoverable | Source reconstructed and redeployed under your own repository and hosting account. |
| Production database | Intact | All customer accounts, leads, appointments, quotes, payments, and signed contracts preserved. Nothing lost — the live business data is fully in hand. |
| Backend functions | Recoverable | The full set of payment, SMS, push notification, and invoicing functions — code intact and exportable, migrated under your control. |
| Payment system | Live | Stripe flows kept running through the migration. Webhooks re-pointed carefully, with cutover validated through test replays to minimize any interruption. |
| Android app | Recover & republish | The app connects to the same backend you already control. Store identity recovered, upload key reset, republished under your own account — not rebuilt from scratch. |
| Backend services (worker / redirect) | Rebuild if needed | The one area where source may need reconstruction from live behavior — see scope below. |
There are signs the previous developer had started moving the system onto a newer backend before stepping away. The very first step of this project is to check whether that newer version already exists and is the one your users are on. If it does, parts of the recovery are already done and the scope shrinks. We confirm this before finalising anything — so you never pay to recover something that's already in place.
Fixed-price, scoped to what you actually need. Choose based on which parts of the system you want recovered.
Optional add-ons: security hardening of the database access rules (+$500–800) · ongoing monitoring & changes retainer ($200/month).
Start with the Audit & Recovery Plan — $500–1,500
It's a small first step that resolves the open questions, confirms what's recoverable against real evidence, and produces a fixed price for the full build. The audit fee is credited in full toward the recovery if you proceed — so you're never paying twice. Ongoing infrastructure (hosting, payments, messaging) runs roughly $25–40/month on your own accounts.
Rotate passwords, remove the previous developer's access across every platform, and take a full read-only backup of the database, functions, and app binaries before any change is made.
Confirm whether the previous developer's in-progress migration produced a newer backend that's already live. This is what locks the final scope and price — and may shrink the work.
Reconstruct the web app into a repository you own, export the database with all its data, and redeploy everything under your accounts.
Re-point Stripe webhooks with the cutover planned to minimize interruption, validated through test replays before going live.
Documentation, a full access inventory, and a walkthrough call. You leave owning every key to your own business.
Working days, full-time focus. Some steps overlap. The audit is already largely complete — the inspection of your platforms is done, so the recovery starts from an informed position.
| Milestone | Working days |
|---|---|
| Secure accounts & full backup | 0.5–1 |
| Resolve newer-version question & lock scope | 0.5–1 |
| Web app reconstructed & redeployed under your repos | 2–3 |
| Database & backend functions migrated, secrets rotated | 1.5–2 |
| Stripe webhook cutover (test-replay validated) | 0.5–1 |
| Android: confirm backend, reset upload key, republish | 1–2 |
| Handoff: docs, access inventory, walkthrough | 0.5 |
Calendar time can run slightly longer where it depends on you (the authorization confirmation, access to the newer project) or on Google's upload-key reset, which can take a few days on their side. Those are flagged up front so nothing is a surprise.
A short written confirmation that you own these accounts and assets and that the previous engagement has ended. This protects both of us and is standard for any ownership-recovery project.