I step into codebases I didn't build all the time. These are starting prices based on how urgent and how tangled the problem is — not a vague 'contact for a quote.'
Think of these as a floor, not a fixed quote. The right number depends on how many issues there are and how familiar the codebase is.
One clear issue, handled without a big process.
Multiple issues, or code you didn't write yourself.
Site down, hacked, or breaking during business hours.
Once things are stable, a one-time rescue can turn into an ongoing safety net if you want it.
Site down, checkout or forms broken, a hack or security compromise, a plugin update that broke the site, or a deadline you can't move. If it's costing you business right now, it qualifies.
Yes — that's most of this work. I step into existing codebases regularly and I'm comfortable finding my way around code I've never seen before.
I'll tell you before it turns into a bigger bill, not after. If the real problem is deeper than the original ask, you'll hear about it and get a choice, not a surprise invoice.
Yes — a lot of urgent-work clients end up staying on for hourly support so the next issue gets caught before it's urgent.
Planning a new site instead of fixing an existing one? See starting prices for new builds.
See starting prices for technical SEO, local SEO, and ongoing content work.
See starting prices for accessibility audits, remediation, and ongoing monitoring.
Send me what's happening and how urgent it is. You'll hear back directly from me, not a support queue.
Share the website, system, issue, or idea. You'll hear directly from the developer doing the work.
A few details are enough to get the conversation started.
