I take on a small number of side projects for small businesses and teams: websites that need to be fast and easy to run, AI tooling that has to work with your own data, and systems that should talk to each other but don’t. The work is the same kind I publish on this site, so the articles and modules are the clearest sample of what you get.
What I take on
WordPress sites that stay fast
Block themes, custom plugins and the unglamorous parts that decide whether a site is still pleasant to run a year later: page speed, image delivery, security headers, search-engine and AI-crawler visibility, and an editor that non-developers can actually use.
The site you are reading is the reference. It went from 86 to 99 on PageSpeed Insights, serves WebP/AVIF without PHP in the image path, and pings search engines on publish via IndexNow. See the image optimizer and IndexNow for WordPress.
MCP servers and AI tooling
Connecting Claude, Cursor or other MCP clients to the systems you already run, such as your CMS, your shop backend or an internal API, with a small set of well-described tools instead of a raw endpoint dump. Content on this site is published through one of these. See brocode-content-mcp and WordPress and MCP.
Making two systems talk
The form that should land in the CRM, the shop orders that should reach the accounting tool, the spreadsheet someone copies by hand every Monday — whether the shop runs on WooCommerce, Shopify or Magento. Small integrations, webhooks and scheduled jobs that remove a manual step and log what they did, so you can tell when something went wrong.
What I don’t take on
- Large shop builds and replatforming. Multi-month shop projects need a team with an on-call rotation, not a side project.
- Retainers with response-time guarantees. Side work can’t promise a two-hour reaction at 3 a.m., and I’d rather say so up front.
- Design from scratch. I build from an existing design, a theme or a clear brief. Branding is somebody else’s craft.
How it works
1. You describe the problem through the contact page: what exists today, what should change, and by when.
2. I reply in writing, usually within a few days, with questions or a first take on the approach.
3. Fixed scope, fixed price. Before any work starts you get a short written scope: what is included, what isn’t, and what it costs. No open-ended hourly billing.
4. Handover, not dependency. The code lives in your repository, comes with a README that explains how to run and change it, and doesn’t need me to keep working.
Availability
This runs alongside a full-time engineering role, so I take on one or two projects per quarter and say no when a project isn’t a good match. Projects that fit best are well-defined pieces of work with a clear finish line, measured in days or weeks rather than months.
If that fits what you have in mind, get in touch.