website rescue / 48-hour diagnostic
a stalled bangkok build gets a calm, 48-hour diagnostic before anyone touches a line of code.
your developer went quiet, your agency has been two weeks from done for four months, or you inherited a site nobody on your team can log into. we do not ask how it got this way. we spend 48 hours mapping exactly what you own, what is salvageable, and what a fixed-scope repair or rebuild costs, then hand you the quote and the access checklist either way.
book the 48-hour diagnostic (usd 2,150 / thb 77,400)01 . what it is
a rescue is not a greenfield build with a delay. a greenfield build starts from a known state: empty repo, your domain, your accounts. a rescue starts from an unknown state. you do not know what code exists, whether it is finished, who has admin access to the domain, or whether the last invoice you paid bought you anything you can legally point to. that unknown state, not the missing features, is the actual problem, and it is why a rescue needs a diagnostic phase before anyone quotes a rebuild.
the 48-hour clock starts the day you sign and pay for the diagnostic. hours 0 to 4: a triage call, we get the domain, the last known login, the name of the developer or agency, and a plain answer to "is anything public-facing broken right now." hours 4 to 24: access recovery, we run a registrar lookup, a dns lookup, a hosting-provider trace, and if the old developer or agency is still reachable, we send a handover request on your behalf, worded to get a reply, not a fight. hours 24 to 40: we open whatever code, cms, or platform we can reach and build the risk map, line by line, keep, patch, or rebuild. hours 40 to 48: you get the access checklist, the risk map, and a fixed-scope quote for whatever comes next, in writing, no verbal estimate.
no shaming means specific things, not a tone of voice. we do not ask you to explain the contract you signed before we start. we do not require proof the old developer was at fault before we act. we do not bill you for the time it takes us to be annoyed at someone else's code. the diagnostic report describes the current state and the path forward, it does not narrate whose fault it is. you already know that part. what you need from us is a number and a plan.
salvage and rebuild are two different verdicts, and the risk map states one per system, not one for the whole project. a codebase in a repo you can access, on a stack we know, with a database you control, usually gets a patch or a repair sprint. a wordpress install with 40 unlicensed plugins and no admin login recoverable, a private github repo the old freelancer never transferred, a site built on a page builder with no export path: those get a rebuild verdict, and we say so plainly, with the reasoning next to it, so you are not guessing.
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 part. the diagnostic produces four things you can act on regardless of who you hire next: the access checklist, the risk map, the fixed-scope quote, and a handover email template that gets your old developer or agency to actually respond. if you take the quote to someone else, that is a fine outcome. most clients do not, because we are the ones who already mapped the mess.
02 . who it is for
archetype 01
hired a freelance developer off a facebook group eight months ago for a booking platform. he answered fast for the first six weeks, then the replies slowed, then stopped. she has a half-built next.js app on an unknown host, a domain registered under his personal godaddy account, and no idea whether the code she paid for legally belongs to her. the diagnostic tells her what she owns, what he still controls, and what it costs to finish either way.
archetype 02
her agency has said "two weeks from done" every two weeks for four months, and the retainer invoice keeps arriving on schedule regardless. she does not know if the site is 20% done or 80% done, because every demo shows a different broken thing. she needs someone outside that relationship to open the actual codebase, put a number on the remaining work, and tell her whether to keep paying or walk.
archetype 03
inherited a wordpress site from a contractor who left the country, running 40-plus plugins, three page builders layered on top of each other, and a checkout that fails on line pay roughly one order in twenty. she has two years of google search console history and a google analytics property she cannot afford to lose. she needs someone who can take the site over without resetting her seo back to zero.
03 . what you receive
01
access and credential checklist. domain registrar, dns provider, hosting account, cms admin, source repo, analytics (ga4, search console, clarity), and the business email tied to each one, verified one by one, not assumed.
02
risk map. every system component gets a keep, patch, or rebuild verdict, with the specific reason next to it: repo access, code quality, licence status, host stability, plugin sprawl, whatever applies.
03
fixed-scope rebuild or repair quote. a single itemised number for whatever the risk map recommends, no hourly line, no "we'll know more once we start."
04
handover request template. a ready-to-send email to the old developer or agency asking for the access list and the outstanding files, worded to get a reply instead of silence.
05
migration plan without losing seo. 301 redirect map for every url that changes, canonical tags carried over, sitemap resubmission to search console, and continuity for the existing ga4 and clarity properties so the historical data does not reset to zero.
06
a 30-minute walkthrough call. we go through the risk map and the quote together before you decide anything, plain english, no jargon, no pressure to sign the follow-on engagement.
04 . timeline
phase 0
hours 0 to 4
one call. the domain, the last known login, the name of the developer or agency, and a plain read on whether anything public-facing is broken today.
phase 1
hours 4 to 24
registrar lookup, dns trace, hosting-provider trace. if the old developer or agency is reachable, the handover request goes out on your behalf, worded to get a reply.
phase 2
hours 24 to 40
we open whatever code, cms, or platform we can reach and score each system component: keep, patch, or rebuild, with the reasoning attached.
phase 3
separate engagement, 2 to 10 weeks depending on scope
hours 40 to 48 deliver the fixed-scope quote and the full written report. execution only starts once you sign, billed separately from the diagnostic.
05 . pricing
step 01
usd 2,150 / thb 77,400
one-off, fixed 48 hours
step 02
from usd 4,500 / thb 162,000
fixed scope, when the risk map says salvageable
step 03
usd 9,500 to 24,500+ / thb 342,000 to 882,000+ per phase
fixed scope per sow, priced like the equivalent service
thb shown at approximately 36 to the dollar, bot reference rate at invoice date is what actually bills. the diagnostic fee is credited in full toward step 02 or step 03 if you sign within 30 days of the report. usd or thb both accepted. stripe usd, wise usd, or thai bank transfer in thb all supported.
06 . proof
case study
full migration off wordpress, elementor, wpml and a tangle of plugins to a custom next.js storefront, three locales, live in one week. the same access-recovery-then-rebuild sequence a stalled bangkok build needs, compressed into days once the risk map is clear.
case study
a 154-page wordpress and elementor pro site exported to cloudflare pages with five years of seo history kept intact and hosting cost taken to near zero. proof that migration does not have to mean losing what a site already earned in search.
07 . questions
01
what if the old developer will not respond?
we send the handover request on your behalf during hours 4 to 24, worded to get a reply. if there is still no response, we move to the recovery paths that do not need their cooperation: registrar-level account recovery, hosting-provider support tickets, and a from-scratch rebuild priced into the risk map. you are never blocked on someone else answering an email.
02
what if we do not own the domain?
this comes up more than you would think. if the domain is registered under the old developer's personal account, we document the registration history and initiate a registrar transfer request, which most registrars honour once you show proof of payment or a service contract. if the domain genuinely cannot be recovered, the risk map prices a new domain plus a 301 redirect plan from the old one, so you do not lose the inbound links pointing at it.
03
can you save our existing seo rankings?
in most cases, yes, if we can reach the analytics and search console properties during the diagnostic. the migration plan carries over canonical tags, maps a 301 redirect for every url that changes, resubmits the sitemap, and keeps the existing ga4 and clarity properties running instead of resetting them. rankings can dip for two to four weeks after any migration, that is normal, but the historical data and the link equity do not have to reset to zero.
04
do you need the old developer's cooperation?
no. cooperation helps, and the handover email template is built to get it, but the diagnostic is designed to work without it. registrar lookups, dns traces, hosting-provider support, and code recovery from whatever access you do have are all part of the process. the risk map states plainly which parts depend on their cooperation and which do not.
05
what if the code is a mess?
that is exactly what the risk map is for. a messy but reachable codebase, on a stack we know, usually gets a patch or a repair sprint, not a full rebuild. genuinely unreachable or unrecoverable code, an unlicensed page-builder export, or a plugin stack nobody can safely update gets an honest rebuild verdict instead of a repair quote that quietly turns into a rebuild three weeks in.
08 . further
ready for the diagnostic?
book the 48-hour rescue diagnostic. access checklist, risk map and a fixed-scope quote delivered in writing, credited toward the repair or rebuild if you sign within 30 days. line official account fallback for thai-first contact.