The offer

WordPress Technical Audit + Fix Sprint

The audit shows you what needs attention on your site and in which order. In the fix sprint I then work through the most important findings. Both have a fixed price, and you can book either one on its own.

  1. Free checkTwelve signals in seconds
  2. AuditFindings by risk and effort
  3. Fix sprintPull requests you merge
  4. ResultMeasured before and after

Step 1

The Technical Audit

A structured review of your WordPress: code, configuration, plugins, hosting and the way changes reach production. Remote and read-only.

What you get

  • A written report with every finding, its risk and the effort to fix it
  • A prioritized backlog you can hand to any developer
  • Quick wins marked as such, so you can start the same day
  • A walkthrough call with you and your team
  • The report stays yours, whoever does the fixing
#FindingRiskEffort
01Abandoned form plugin with a known vulnerabilitySecurityQuick winHighS
02Two admin accounts of a former agencySecurityQuick winHighS
032.4 MB of autoloaded options on every requestPerformanceMediumM
04No Content-Security-Policy headerSecurityLowM
Example from an audit report. Every finding comes with the reason, the fix and a priority.

Step 2

The Fix Sprint

A sprint with a fixed time frame that closes the most important findings of the audit. Scope and price are agreed before we start, and you follow the progress in the pull requests I open.

How a sprint runs

  1. We pick the findings with the best risk-to-effort ratio
  2. I work in your repository, on a branch, with your tooling
  3. Every change comes as a pull request with tests where it counts
  4. You review and merge, so nothing goes live without your approval
  5. We measure before and after, so the result is visible

Working with AI

What AI does in a sprint, and what it doesn’t

AI tools take over the repetitive part: reading large codebases, drafting refactorings, writing test scaffolds, checking hundreds of templates for the same mistake. That is why a sprint covers more ground than the same time spent by hand.

The decisions remain mine. I read every line before it becomes a pull request, and I am accountable for it. No agent works on its own in your production, and you get no code that I couldn’t explain to you.

What I need from you

Little, and only what the work requires.

  • Read access to the code repository, or a copy of themes and plugins
  • A staging environment or a recent database dump without personal data
  • Someone who knows the history of the site, for one call
  • For the sprint: write access to a branch, or a fork

FAQ

Questions I get asked.

Do I have to book the sprint after the audit?

No. The audit stands on its own. Many teams fix the findings themselves or with their agency. The report is written for exactly that.

Do you need access to our production site?

No. The audit works from code, configuration and a staging copy. Production stays untouched unless you explicitly want something checked there.

What about personal data and GDPR?

I work with anonymized data wherever possible and sign a data processing agreement where needed. Personal data is not part of the audit.

Which setups do you cover?

Single sites and multisite networks, classic and block themes, custom plugins and integrations, on managed hosting or your own servers.

Why fixed prices and not hourly rates?

Because you should know the cost before the work starts. Scope is agreed in a short call, and if it changes, we agree on it again first.

Tell me about your site.

A few lines are enough: what the site does, where it is hosted and what bothers you about it. If you are a web designer asking on behalf of a client, just say so. I reply personally, and if I think you don’t need an audit, I will say so.