services
Engineering standards first. AI makes them faster, not optional.
I build custom WordPress applications and make sites readable to search engines and AI assistants. Every change, whoever or whatever wrote it, goes through the same pipeline: version control, review, static analysis, tests and staged deploys. That pipeline is what lets me use AI to deliver more without lowering the bar.
- review
- every change, before merge
- analysis
- PHPCS, PHPStan level 8
- tests
- on every push
- budgets
- performance and accessibility in CI
- ai
- drafts and checks; never merges
how ai fits
More output, same bar.
Google’s DORA research for 2025 found that AI amplifies what a team already has: it speeds up teams with strong engineering foundations and exposes the weaknesses of teams without them. These are the foundations it amplifies here.
AI drafts, the pipeline decides
Code from a model passes the same linting, static analysis, tests and review as code I type. Nothing reaches the main branch because a tool was confident.
one pipeline · no exceptions
Tests define done
Generated code is only as trustworthy as the checks it has to pass. Where behaviour matters, the test is written first and the change has to satisfy it.
PHPUnit · Playwright · axe-core
Context is written down
Coding standards, architecture decisions and project rules live in the repository, so assistance follows this codebase instead of the internet’s average.
decision log · project rules
A person owns every merge
I decide the architecture, read every diff and answer for every line that ships. AI speeds up the typing, not the accountability.
review required · signed merges
Quality is measured, not assumed
Performance budgets, accessibility rules and contrast ratios run in CI on every change, so faster delivery can’t quietly erode them.
Lighthouse CI · contrast checks
Your code and data stay yours
Client code and data only reach the tools we have agreed on in writing, under terms that don’t train on them.
written agreement · no training use
Custom WordPress applications and development
Plugins, block themes, integrations and headless builds, written to a standard and delivered faster with AI-assisted engineering inside a strict pipeline.
best for: product teams, in-house web teams, agencies needing a senior engineer
scope
- Custom plugins and domain logic
- Block themes and custom Gutenberg blocks
- REST, GraphQL and headless front ends
- Legacy code audits and refactors
you receive
- Repository with CI from the first commit
- Test suite and coding-standard config
- Architecture notes and written decisions
- Deploy pipeline with rollback
Technical SEO and answer engine optimization
Making a site readable to search engines and AI assistants: crawl access for every bot that matters, content in the HTML, structured data, and pages that answer the questions buyers actually ask.
best for: sites with good content that search results and AI answers don’t surface
scope
- Crawl and indexation audit, AI crawlers included
- Structured data built into the theme
- Content structure for answers and citations
- Core Web Vitals and accessibility
you receive
- Written audit with prioritised fixes
- Fixes shipped as reviewed, tested code
- AI visibility baseline across assistants
- Re-measurement on a fixed schedule
Platform migrations
Moving between platforms without losing content, URLs or search equity. Scripted, repeatable and verified before DNS changes.
best for: sites outgrowing a hosted builder or a page builder, or leaving WordPress
scope
- Crawl, inventory and content model
- URL map and redirects tested in CI
- Scripted content import
- Cutover and 60-day monitoring
you receive
- Fixed-price audit and written scope
- redirects.csv and import logs
- Signed pre-launch QA checklist
- Launch report
Site maintenance and care
Updates, monitoring and small changes on a fixed monthly scope, handled through the same review and deploy process as new work.
best for: sites in production that need an owner, not a ticket queue
scope
- Core, plugin and dependency updates via staging
- Security and dependency audits
- Uptime, error and performance monitoring
- Monthly hours for small changes
you receive
- Written monthly changelog
- Tested, restorable backups
- Incident notes when something breaks
- Quarterly performance and accessibility report
included in every engagement
The baseline isn’t an upsell.
- Git repository you own, from day one
- Pull requests reviewed before merge
- WPCS / PSR-12 linting and PHPStan in CI
- Automated tests on every push
- Sanitize, validate, escape; nonces and capability checks
- Staging environment that mirrors production
- Atomic deploys with one-command rollback
- WCAG 2.2 AA and performance budgets checked in CI
- AI-assisted changes held to the same review and checks
how to engage
Ways to work together
Fixed-scope project
A defined build or migration with a written scope, milestones and acceptance criteria.
fixed price · after a paid audit
Contract engineering
Embedded with your team, working in your repo, your tickets and your review process.
weekly rate · 3-month minimum
SEO and AEO audit
A written audit of how search engines and AI assistants read your site, with every fix prioritised and priced.
fixed price · yours to keep
Monthly care
Ongoing maintenance with a fixed set of hours and a predictable invoice.
monthly retainer · cancel with 30 days
Not sure which one fits?
Send a short description and a link to the repo or site. I’ll tell you which service applies, or if none do.