Plugin development

Custom WordPress plugins, built to be maintained.

We build plugins that do one job well, pass a security review and can be handed to another developer without a decoder ring.

What a project includes

  • Discovery: the problem, the users, the edge cases and what already exists on the site.
  • Architecture: data model, migrations, capabilities and the Free/Pro boundary if there will be two editions.
  • Implementation with PSR-4 autoloading, no logic in the bootstrap file and WordPress Coding Standards.
  • Security review of every write path: capabilities, nonces, prepared queries and escaped output.
  • Tests with PHPUnit and wp-phpunit, plus an end-to-end pass of the flows that matter.
  • Documentation, changelog and the release itself: WordPress.org, Envato or a private zip.

Constraints we state up front

  • GPL. The code is GPL-compatible and the repository is yours at handover.
  • No page builders. Blocks and theme code stay portable and readable.
  • PHP 8.1+ and WordPress 6.6+. We do not carry compatibility weight that stopped being supported years ago.
  • Reversible migrations. Every schema change ships with a versioned upgrade and a documented downgrade path.
  • No obfuscation. Nothing is hidden, and nothing in the free edition is disabled on purpose.

Questions we get asked

Who owns the code?

You do, under the GPL. The repository, the build scripts and the release process are handed over at the end of the project.

Can the plugin be sold on Envato or WordPress.org?

Yes. We have shipped to both and can prepare the submission, the documentation and the support policy. Free and paid editions are separate packages, never one package with features switched off.

What happens after handover?

You can take it in-house, give it to another agency or keep us on a maintenance plan. Nothing in the code depends on a server we control.

Do you work with existing plugins?

Yes, including plugins that started in a theme or in a page builder. We write tests around the behaviour that must not change before refactoring anything.

Have a plugin in mind?

Tell us what it has to do and who will use it. We answer with a scope and a date.