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.
The most valuable parts of your business — your live database, customers, payments, and contracts, plus all your backend logic — are recovered and safe. Your website and app are running and accessible under accounts you hold. For most of the system this is a structured recovery and ownership transfer, not a rebuild from zero. One part — your app's source code — depends on a hand-off from the previous developer, covered below.
| Asset | Status | What it means for you |
|---|---|---|
| Production database | Secured ✓ | Your live database — every customer account, lead, payment, and signed contract — is already backed up and safe. Nothing was lost, and nothing can be lost now. |
| Backend functions | Secured ✓ | The complete set of payment, SMS, push, signature, and invoicing functions — all backed up and ready to migrate under your control. |
| Website | Recoverable | Your marketing site source is readable and reconstructed into a repository you own, redeployed under your own hosting. |
| Payment & subscription system | Live | Card and in-app subscription flows kept running through the migration. Webhooks re-pointed with cutover validated through test replays to minimize any interruption. |
| Lead & Job Management app (web + Android) | Depends on source | Your salesman app runs on both web and Android from one shared codebase. The running app is in hand; whether we recover or rebuild it depends on getting its source code back — see below. |
| Link & redirect services | Config in hand | Deployment configuration is captured. Source recovered if the repository transfers, otherwise rebuilt from its known behavior. |
The investigation is complete and your live database and backend functions are already backed up safely. We also confirmed the previous developer migrated your system to a newer version rather than deleting anything — so your older data was never lost either. The expensive assets — customers, payments, contracts — are safe.
Your salesman Lead & Job Management app (the one used daily, on web and Android) is built from a single codebase that lives in a separate repository held by the previous developer. The running app is in our hands; its editable source code is not. Getting that repository transferred to you is the single most valuable action right now — it's the difference between recovering your app (you own it, fully editable) and rebuilding it from scratch. We push hard to recover it first; the pricing below reflects both outcomes.
Fixed-price. The path depends on one thing: whether your app's source code is recovered or has to be rebuilt.
Optional add-ons: security hardening of the database access rules (+$500–800) · link/redirect service rebuild if its repo can't be recovered (+$1,000–2,500) · ongoing monitoring & changes retainer ($200/month).
Most likely path: Tier 2 — $6,000–12,000
Your backend and data are already secured. Tier 2 recovers everything else — website and app — under your full ownership, provided we get your app's source repository back from the previous developer. That single hand-off is what keeps this a recovery (Tier 2) rather than a rebuild (Tier 3), which is why securing it now matters. Ongoing infrastructure runs roughly $25–40/month on your own accounts.
Your live database and backend functions are already backed up. We confirmed the live version of your system and that no data was lost in the previous developer's migration.
Push to get the app's source repository transferred to you from the previous developer. This is the highest-leverage step — it decides whether your app is recovered or rebuilt.
Move the live database and backend functions under accounts you own, reconstruct the website into your own repository, rotate every key, and lock the previous developer out.
Re-point card and in-app subscription webhooks with the cutover planned to minimize interruption, validated through test replays before going live.
With the source recovered, redeploy the app under your ownership and republish on Android with a new upload key. If the source can't be recovered, rebuild it to match.
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 investigation and data backup are already complete, so the work starts from a known position.
| Milestone | Working days |
|---|---|
| Secure accounts & full backup | ✓ done |
| Recover app source repository from previous developer | depends on hand-off |
| Migrate backend & functions under your ownership | 2–3 |
| Website reconstructed & redeployed under your repos | 2–3 |
| Payment & subscription webhook cutover (test-validated) | 1–1.5 |
| App recovered & republished (Android upload key reset) | 1–2 |
| Handoff: docs, access inventory, walkthrough | 0.5 |
| If app source lost — full app rebuild instead | +15–30 |
Calendar time can run longer where it depends on you (the ownership confirmation, the app source hand-off) 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.