the off-ticket work
Every site accumulates jobs that do not fit a sprint: the migration nobody wants to own, the security incident at the worst possible time, the performance that decayed one plugin at a time. That work is a service here, not a favour.
what you get
Migrations planned so the risky step is reversible: hosts, stacks, multisite splits, and the content moves where nothing is allowed to go missing. Security work from hardening through incident response, including the calm plain-English write-up your client actually reads. Accessibility and performance audits that end in a prioritized fix list with honest effort estimates, not a hundred-row spreadsheet of shame.
how it works
Audits are flat-rate and start from real data: server logs, waterfalls, and the site as it behaves in production. Migrations get a written plan with a rollback path before anything moves. Incidents get triage first and paperwork after.
proof
The Ace Hotel migration is the shape of it: four languages of professionally translated content living only in a translation proxy that was being decommissioned, reconstructed into content the client owns, on the same URLs, with a launch that was reversible in minutes. Behind that sit a decade of quieter rescues, from forensic cleanups of compromised sites to rotating credentials across dozens of production projects during a supply-chain incident.
the questions that come with this one
Yes. Most care work starts on someone else’s build.
Get in touch and say so. Triage comes first, scope after.
Audits are flat-rate. Migrations and incident work are quoted from the written plan.
have a project in mind?
Describe it and I’ll tell you how I’d build it.