Custom WordPress plugins, built to outlive the update.

A single-purpose plugin typically costs £1,500–£4,000. One with an admin interface, settings and a third-party integration runs £4,000–£12,000. A WooCommerce extension changing pricing, checkout or fulfilment is £8,000–£25,000. A commercial plugin with licensing starts around £20,000. After a free scoping call we give you a written quote, with scope and exclusions agreed up front.

Typically two to four weeks for a focused plugin, four to eight for one with an admin interface and integrations, and eight to sixteen for a commercial plugin with licensing and update delivery. Every sprint ends with an installable build on a staging site you can test yourself.

Yes. Ownership transfers to you on full payment, as set out in your contract. The repository sits in your organisation, there is no licence back to us, no obfuscation and no phone-home. WordPress plugins are GPL by nature and we do not pretend otherwise.

Yes, and it is a large part of what we do. We audit it first and tell you honestly whether it is worth keeping: usually it is. Where possible we extend it from a small companion plugin using its own hooks, so the original keeps receiving updates rather than being frozen by your edits.

That is a design decision rather than luck. We use documented hooks and APIs, never edit core, never write directly to core tables, and test against the current and previous major versions. Built that way a plugin is designed to keep working through updates; built with core hacks it is not, which is exactly what most rescue jobs we see turn out to be.

Yes. That means licence key validation, an update server so customers upgrade from their own dashboard, seat limits, a customer-facing account area and a support process. The software is roughly half of it: the rest is onboarding, billing and support, and we will be straight with you about that before you commit.

Use an existing one whenever a mature plugin covers most of it: we recommend that often in first conversations, by name and with no affiliate arrangement. Build when your logic is genuinely specific to how you trade, or when the stack of subscriptions faking the feature already costs more than a build.

We can, and we will tell you whether it is worth it. The directory brings reach and also a support obligation, a review process and a GPL-only distribution model. For most business plugins the answer is to keep it private; for a product, a free tier alongside a paid one is often the right shape.

Yes. WooCommerce extensions are built for High-Performance Order Storage rather than reading orders from post tables, plugins are tested on PHP 8.1 to 8.4, and where you run a network we build for multisite with per-site settings. Every plugin is reviewed against the WordPress Coding Standards with PHPCS.

A written review of a plugin you rely on or inherited, covering security (capability checks, nonces, sanitisation, escaping, prepared statements, file handling), performance, standards, dependency currency and maintainability. Each finding comes with a severity and a recommended fix. It costs £800–£2,500, takes under a week, and the report is yours whatever you do next.

We investigate and fix issues traceable to our code under a maintenance retainer or as separately agreed work, prioritised by severity as agreed in your support plan. On a retainer we also test against each WordPress, WooCommerce and PHP release before it reaches you rather than after.

An experienced in-house lead engineer runs your project, with additional developers on larger builds. You meet the team during scoping, and the people involved are agreed with you before the build starts.