Discovery and spec
We map user stories, data model, attribute schema, editor UX and render semantics. You get a written specification and fixed quote before any code is written.
Built for UK SMEs, charities, professional services firms and distributed teams around London, Manchester, Birmingham, Bristol, Edinburgh and teams working nationwide. Focused, documented functionality that fits the editor and can be maintained safely. We account for plain UK English with accessible, task-focused content, cards, Direct Debit and regulated Open Banking or Pay by Bank providers where they fit the journey, and practical delivery in GMT/BST.
UK organisations do not need a generic overseas template. They need custom WordPress plugin and block development shaped around a competitive market where credibility, accessibility and a low-friction enquiry or checkout journey strongly affect conversion, internal ownership and the tools their customers already recognise. The build includes namespaced code, capability checks, sanitisation, escaping, upgrade paths and documentation instead of hiding business logic in a theme.
Our output is production grade. block.json metadata, strict attribute types, dynamic render where state matters, deprecations for every shipped version. Your editors get a clean Gutenberg experience. Your developers get code they can read and extend.
A practical delivery process for UK teams, with decisions documented in GMT/BST and local operational requirements agreed before build work begins.
We map user stories, data model, attribute schema, editor UX and render semantics. You get a written specification and fixed quote before any code is written.
WordPress engineers build the plugin or blocks in clean PHP and TypeScript. block.json first, proper supports, sensible defaults. Weekly staging demos keep you in the loop.
PHPUnit, Playwright, WordPress coding standards, PHPStan and accessibility audits on every block. Deprecations tested against prior shipped versions so existing content never breaks.
We package the plugin, generate POT files, tag a release and hand over a README plus a video walkthrough. Optional retainer for updates and future blocks.
UK SMEs, charities, professional services firms and distributed teams operate in a competitive market where credibility, accessibility and a low-friction enquiry or checkout journey strongly affect conversion. We shape the custom WordPress plugin and block development around those buying habits, plain UK English with accessible, task-focused content, straightforward proposals, sensible estimates and pricing in pounds, and the systems already used by the team. The result is a practical service plan for teams building trust and sustainable growth across the UK.
Give content teams a controlled component with the right fields, variants and accessibility behaviour. For teams around London, Manchester, Birmingham, Bristol, Edinburgh and teams working nationwide, we define the local audience, ownership and follow-up route before implementation and account for cards, Direct Debit and regulated Open Banking or Pay by Bank providers where they fit the journey.
Turn a repeated manual task into a permission-aware WordPress workflow with a clear audit trail.
Package an external service or data source behind a stable WordPress interface.
We minimise unnecessary collection and document forms, analytics, processors and retention choices with the UK GDPR and Data Protection Act 2018, with security and privacy-by-design guidance from the ICO in mind. Technical implementation supports your compliance work; it does not replace legal advice.
The delivery plan can account for cards, Direct Debit and regulated Open Banking or Pay by Bank providers where they fit the journey, pricing in pounds sterling, plain UK English with accessible, task-focused content, and a UK region when contracts, latency or organisational policy make local hosting preferable. We only add local integrations that serve a real customer or operational need.
Planning, reviews and support are organised around GMT/BST. The build includes namespaced code, capability checks, sanitisation, escaping, upgrade paths and documentation instead of hiding business logic in a theme. Handover is written for the people who will publish, approve and support the site locally.
Local regulatory references are implementation context, not legal or regulatory advice. Your organisation remains responsible for confirming the obligations that apply to its sector and use of personal data.
Not all plugin work is equal. Here is how we stack up against a typical freelancer and a traditional agency.
Fixed quotes before work begins. Choose the tier that fits your scope or ask for a custom estimate.
One custom Gutenberg block with clean editor UX, dynamic render and full i18n.
Multi block plugin with patterns, variations and a small admin settings screen.
Full plugin product with REST routes, admin UI, migrations and PHPUnit coverage.
Commercial plugin build with licensing, update server and a dedicated engineer.
A plugin is not done until it passes our internal checklist. No shortcuts, no loose ends.
PHPCS with WordPress ruleset clean on every file. No silenced warnings, no selective excludes.
Static analysis at level 8 with WordPress stubs. Types on hooks, filters and REST responses.
Unit and integration tests for core logic, REST routes and migration paths. CI gates on green.
Real Gutenberg browser tests. Insert block, edit attributes, save, reload, assert output.
Keyboard flow in the editor, labelled controls, semantic output, contrast checked in all themes.
Every attribute change ships a deprecation. Existing content rendered against prior versions in tests.
Full text domain coverage, translator comments, POT generated on build, RTL friendly markup.
Inline docs, PHPDoc blocks, README and a changelog your team can read.
Build script, ZIP artifact, semver tag and release notes for every shipped version.
We are the silent engineering team behind dozens of design and marketing agencies. Your client sees your work, your invoice and your brand. Our name never appears in the plugin header or the editor.
Plugin header, readme and admin screens carry your brand, not ours.
One point of contact for all your plugin work. Shared Slack channel, weekly syncs, fast replies.
Retainer rates, bulk discounts and priority scheduling for agency partners.
We plug into your Linear, ClickUp, Notion or Jira. No tool switching, no friction.
You share the block or plugin specification in your stack. Linear, Notion, wherever you already work.
We write a detailed technical specification and send you a partner rate quote. Never shown to your client.
You mark up, brand the proposal and present it on your letterhead at your price.
Your client signs off on your terms, with your brand, and pays you directly.
Silent build on branded staging. No credits in the plugin header, readme or editor UI.
You review, accept handover and ship the plugin to your client under your agency name.
Yes. Planning, reviews and support can be organised around GMT/BST. We agree response expectations, meeting windows and escalation contacts before the project or care plan starts.
We apply data minimisation, secure handling and privacy-by-design practices to forms, analytics, integrations and hosting decisions. We document the technical choices clearly, while your legal or data-protection adviser confirms the obligations that apply to your organisation.
Yes. We map your existing shortcode attributes to block attributes, ship deprecations so old content keeps rendering, and provide a migration script where bulk content conversion is needed.
Yes. Our blocks use theme.json tokens and the standard block supports API, so they pick up your typography, colour palette and spacing scale automatically. No hardcoded styles that fight your theme.
A single custom block with editor and frontend takes 2 to 3 weeks. A multi block plugin with REST routes and admin UI takes 5 to 10 weeks. You get a firm timeline in your written estimate.
We build bespoke plugins for you. You own the code and the distribution. We can also help package, licence and ship a commercial plugin product if that is the goal.
Share your plugin or block requirements and a WordPress engineer will respond with a written estimate and timeline within one business day.