Focused fixes: often 1–3 hours
Examples include correcting one production route, repairing a mobile overflow, connecting a real form handler, fixing one callback value, or removing a duplicated script. At US $150 per hour, a 1–3 hour example is US $150–$450. This is a planning range, not a quote for a project that has not been reviewed.
Cross-layer repairs: often 3–6 hours
A symptom that crosses browser code, a server handler, a connected provider, and stored data usually needs reproduction, evidence from each boundary, the repair, and regression checks. A 3–6 hour example is US $450–$900. The written estimate explains which boundaries are included.
Rescue work: often 6–12 hours or a staged scope
Generated code with duplicate implementations, inconsistent environments, broken authentication, or payment provisioning may need a short diagnostic stage before a responsible repair estimate. A 6–12 hour planning example is US $900–$1,800; larger work is divided into approval points instead of becoming an open-ended invoice.
How to get a useful estimate
Send the live or preview URL, the exact user action that fails, the builder used, when it last worked, and any safe build or browser error. Do not send credentials. The initial review determines whether the issue fits a focused fix, cross-layer repair, diagnostic stage, or repair-versus-rebuild decision.