Skip to content

Custom plugins, built properly.

When nothing off the shelf does what your business needs, I’ll build the plugin that does. I’m a WordPress developer in Norwich with over 20 years on the platform, building for single sites, WooCommerce shops and the WordPress.org directory.

Built around how your business works.

Off-the-shelf plugins are built for everyone. Yours is built for you.

Off-the-shelf plugins try to suit thousands of businesses at once. So you bend your process to fit them, pay for features you’ll never use, and juggle three plugins that don’t quite talk to each other.

A custom plugin does exactly what your business needs, the way your team already works, and nothing else. Less code means a faster, safer site, with nothing in it you don’t control.

And if the plugin is the product, something you want to give away or sell on the WordPress.org directory, I’ve been through that process myself.

What I build.

  • Business logic

    Quotes, bookings, pricing rules, membership levels: anything your business does that WordPress doesn’t do out of the box.

  • WooCommerce extensions

    Custom checkout fields, delivery rules, trade pricing, and connections to your stock or accounts system.

  • Integrations

    Connecting WordPress to the other software you use, such as a CRM, booking system or email platform.

  • Admin tools

    Dashboards and reports that save your team time.

  • Products for WordPress.org

    Free plugins with an optional Pro version, built to pass the directory’s review.

BoxCart: one I built for myself.

BoxCart is my own click and collect plugin for WordPress. I designed it, built it, and prepared it for the WordPress.org directory, whose review is stricter than most people expect.

Everything I learned doing that goes into the plugins I build for clients.

The BoxCart website

What “properly” means.

The difference between a plugin that works today and one that’s still working in five years.

  1. 01

    WordPress’s own standards

    Written to the platform’s coding standards, so the next developer can read it.

  2. 02

    Secure by default

    Everything sanitised on the way in and escaped on the way out.

  3. 03

    It survives updates

    A plugin that breaks every time WordPress moves isn’t finished.

  4. 04

    It’s your code

    Documented, and yours to hand to anyone.

How a plugin project works.

  1. 01

    Describe the problem

    In plain English. No technical brief needed.

  2. 02

    I map it out

    How it fits with your site and the tools you already use, so nothing is built twice.

  3. 03

    Fixed price and spec

    A short spec of what it will do, and the number.

  4. 04

    Built on staging

    On a copy of your site, so the live one is never at risk.

  5. 05

    You test it

    I fix anything that needs it, then it goes live.

  6. 06

    Looked after

    Updates and support as needed, or through a care plan.

Fixed One number, agreed before anything starts.

What you’d pay.

Priced to the job. A small plugin that does one thing for one site is a world away from a product headed for the directory with its own updates and support.

Describe what it needs to do and you’ll get a fixed number before anything starts.

A Norwich developer you can actually talk to.

I’m based in Norwich and have worked with businesses across Norfolk since 2005. You talk to the developer writing your code, not an account manager, which makes a real difference on custom work, where small details matter.

Norwich London Colorado Tel Aviv

Questions people ask.

Who owns the code?

You do. It’s documented and yours to take to any developer.

What happens when WordPress updates?

Plugins I build are written to WordPress standards, so they keep working through updates. If an update ever needs a change, a care plan covers it, or I’ll quote it.

Can you change a plugin we already use?

Usually it’s better to extend it than edit it, so your changes survive the plugin’s own updates. I’ll tell you which approach makes sense.

Can you build a plugin to sell?

Yes. I can build the free version for WordPress.org and a paid Pro version, with licensing and updates.

Do you do WooCommerce development?

Yes. Custom WooCommerce features are a big part of my plugin work, from checkout changes to trade-only shops.

How long does a plugin take?

A small plugin can take a few days. A bigger one, or a product for the directory, can take several weeks. You’ll get a timeline with the price.

Do you work with agencies?

Yes, I do a lot of this white-labelled, under your name. There’s a page for that.

Got something your website should be doing?

Tell me what it needs to do, and I’ll come back with how I’d build it and a fixed price.