← Services

02

Plugin development

We build the plugin the off-the-shelf one nearly does. Written to WordPress conventions, tested, documented, and handed over with the repository — so a future developer, including one who is not us, can pick it up.

Start a briefAsk a question first

01What you get

What you actually receive

  • A plugin that passes the WordPress.org Plugin Check and PHPCS with the WordPress ruleset.
  • Tests where behaviour matters, and a build that produces the distributable package.
  • Capability and nonce checks on every write path, and escaping on every output.
  • Documentation aimed at the next developer, not at us.
  • Release tooling, so shipping a version is one command rather than a ritual.

02The decision

What "follows the platform" actually means

Most plugin problems are not bugs. They are a plugin deciding it knows better than WordPress.

Data
Post types, taxonomies and options where they belong, not a private table that nothing else can read.
Security
Capability check, nonce, sanitise on the way in, escape on the way out. Every write path, every time.
Compatibility
Filters and actions where extension is likely, so the next developer does not have to fork you.
Performance
Background work through Action Scheduler or the cron API, not a long request that times out half-finished.

03Limits

What this is not

  • We do not ship code that writes to the database without a capability check.
  • We do not bundle a licensing SDK, telemetry or a phone-home into your plugin.
  • We do not take work that depends on breaking another plugin’s licensing.
Typical duration
2 to 10 weeks
Engagement
Fixed scope, or a retainer for ongoing work
Proof of approach
Accessibility Remediation is ours, and open

04How it runs

Four stages, start to handover

  1. 01

    A brief, then a conversation

    You send four short answers. We read them and reply within one working day, either with questions or with a straight answer about whether we are the right studio for it.

  2. 02

    Scope written down

    What is being built, what is not, what it costs and when. If we cannot describe it clearly enough to price it, that is a sign the scope is not ready — and we will say so.

  3. 03

    Build, in the open

    Work lands in your repository from the first week. You see progress as commits and working previews, not as a status meeting.

  4. 04

    Handover that survives us

    Documentation for the next developer, the accounts in your name, and a walkthrough with whoever has to run it. Then a support window while you settle in.

Ready when you are.

Four short questions, about two minutes. A reply within one working day.

Start a brief