the 48-hour clock starts the day you sign. hours 0 to 4: triage call, we take the domain, the last known login, the name of the developer or agency, and a straight answer on whether anything public facing is down right now. hours 4 to 24: access recovery, registrar lookup, dns trace, hosting-provider trace, and if the old developer is still reachable we send the handover request on your behalf, worded to get a reply instead of a fight. hours 24 to 40: we open every codebase, cms and platform we can reach and build the risk map line by line, keep, patch or rebuild. hours 40 to 48: access checklist, risk map and a fixed-scope quote land in your inbox. in writing, every time, never a verbal estimate.
no blame is a policy, not a tone. we never ask you to justify the contract you signed. we never demand proof the old developer was at fault before we move. we never bill you for the hours it takes us to be annoyed at someone else's code. the report states the current position and the path out. you already know whose fault it was. what you need from us is a number and a plan, and you get both inside two days.
salvage and rebuild are two different verdicts, and the risk map gives one per system, never one vague verdict for the whole project. reachable repo, a stack we already run in production, a database you control: that gets a patch or a repair sprint and you keep everything you paid for. a wordpress install with 40 unlicensed plugins and no recoverable admin, a private github repo the freelancer never transferred, a page builder with no export path: those get a rebuild verdict, stated plainly with the reasoning next to it. you are never left guessing, and you are never sold a repair that quietly becomes a rebuild three weeks in.
a quote, not a guilt trip. most rescue conversations in bangkok happen over line or a coffee and end with someone telling you what you should have done differently. we skip that entirely. the diagnostic gives you four assets you own outright, whoever you hire next: the access checklist, the risk map, the fixed-scope quote, and the handover email that actually gets your old developer to reply. take all four to another studio if you want. almost nobody does, because we are the team that already mapped the mess, and the code lands in your own repo from day one.