Services Build and fix
no plugin does the thing i need
Custom WordPress plugin development services
from $500WordPress plugin development services: one plugin that does your job properly, instead of a stack of half-fitting ones. I ship my own plugin and my own tooling.
What's included
- A plugin that does your specific job, without the settings pages you will never open
- Replacing three overlapping plugins with one that fits
- Admin tooling: bulk operations, custom fields, editorial workflow
- REST API endpoints and integrations with the systems you already run
- WP-CLI commands for the jobs that should never be done by hand
- Clean uninstall, no orphaned tables, no options left behind
- Code handed over with documentation, yours to keep or take elsewhere
Price
Cost follows how many places the plugin has to touch, not how many features it has. A plugin that owns its own data is small work; one that has to stay in step with another plugin's data or a third-party API is not.
Most WordPress sites end up running four plugins to get one behaviour, because no single plugin did quite the right thing. Each one brings its own settings page, its own scripts on every page load, and its own update schedule. The site gets slower and more fragile every time somebody solves a problem by installing something.
When building is the right call
Not often, and that is worth saying on a page selling it. Off the shelf is cheaper, better tested and maintained by somebody else, and the first thing I do is check whether something already covers your job.
Building earns its place in three situations. Nothing fits and the closest option needs so much configuration and glue that it becomes a maintenance problem of its own. You are running several plugins to produce one behaviour, and the stack is now the reason the site is slow. Or the plugin that does fit charges a yearly licence that will, over the life of the site, cost more than owning the thing outright.
Outside those, installing something is the better answer and I will say so.
What a small plugin looks like when it fits
No settings screen you will never open, no upsell banner in the admin, no scripts loading on pages that do not use it. It hooks in where it needs to, does its job, and cleans up completely if you ever remove it. No orphaned database tables, no options left behind years later.
That last part sounds like a detail and is the difference between a plugin and a liability. Most of the mess I clean up on client sites was left by software that was uninstalled and did not take its data with it.
Why I build these
Because I already build tools for myself. SiteHelm is my own plugin, a WordPress MCP server with 111 free operations and 51 pro ones across content, media, menus, Elementor, and custom fields, at version 0.14.0. The free tools on this site and the Search Console MCP server behind them are mine too.
Writing this kind of code is what I do when I am not doing SEO, which is why the quote is realistic and the code is clean. It also means the plugins tend to be built by somebody who will later have to do SEO on the site, so they do not ship the things that quietly cause indexing problems: duplicate URLs, unwanted archive pages, markup that fights the theme.
Afterwards
The code and documentation are yours, with no licence key and no dependency on me. If it needs keeping alive, maintenance covers that; if you would rather handle updates yourself or hand it to another developer, nothing in the build stops you.
Tell me what the plugin would have to do and I will start by checking whether one already does it.
- step 1 · check nothing already does itThe best outcome is often that an existing plugin already covers it and you save the money. I check first and say so if that is the answer.
- step 2 · scope in writingWhat it does, what it does not do, where it hooks in, and what happens on uninstall. Fixed price and timeline before anything is written.
- step 3 · build and hand overBuilt against WordPress coding standards, tested on a staging copy, then installed with the code and documentation handed to you. No licence, no phoning home, no dependency on me.
before you ask
Common questions.
Why build a plugin instead of installing one?
Usually you should not. Off the shelf is cheaper and better maintained. Building makes sense when nothing fits, when you are running three plugins to get one behaviour, or when a plugin that fits costs more per year forever than a build costs once.
Do I own the code?
Yes. You get the source and the documentation, and there is no licence key or subscription to me. If you want a different developer to take it over later, they can.
Have you actually shipped a plugin?
Yes. SiteHelm is mine, a WordPress MCP server currently at version 0.14.0 with 111 free operations and 51 pro ones, covering content, media, menus, Elementor, ACF and Meta Box fields, and system tasks. I also run a public Search Console MCP server and the free indexing tools on this site. The tooling here is the portfolio.
What about maintenance after it ships?
WordPress changes and plugins rot. Ongoing updates and compatibility work sit under maintenance, or you can take the code and handle it yourself. Either is fine.
What actually drives the cost?
How many places it has to touch, not how many features it has. A plugin that reads its own data, does one job and renders one screen is small work however clever the job is. Cost climbs when it has to stay in step with things outside its control: another plugin's data, a third-party API, a page builder's rendering, or the WordPress editor itself. So the useful question at the scoping stage is not what should it do, it is what does it depend on, and I will push on that before quoting.
Can you take over a plugin somebody else built?
Often, and it is worth asking rather than assuming a rewrite. Inheriting code is slower per change than writing it, so if the existing plugin is close to right the sensible move is to fix and extend it. If it stores data in ways that will not survive contact with a WordPress update, or nobody can say what half of it does, a rewrite is cheaper than the second year of patching it. I will look and tell you which one you are holding before either of us commits.
Everything else I run.
Get found
Build and fix
Keep it healthy