Inventarisatie en scope
We bespreken doel, contentmodel, gebruikersrollen, integraties en randvoorwaarden. Scope en technische aanpak leggen we schriftelijk vast.
Maatwerkplugins en Gutenberg-blokken voor organisaties die betrouwbare, onderhoudbare WordPress-functionaliteit nodig hebben.
We bouwen WordPress-functionaliteit die past bij je contentmodel, workflows en technische stack. Geen generieke uitbreiding die je later moet repareren, maar duidelijke code met aandacht voor performance, beveiliging en beheer.
Van een custom post type tot een uitgewerkt Gutenberg-blok: iedere oplossing wordt getest, gedocumenteerd en zo ingericht dat je team ermee kan werken.
A practical delivery process for Dutch teams, with decisions documented in CET/CEST and local operational requirements agreed before build work begins.
We bespreken doel, contentmodel, gebruikersrollen, integraties en randvoorwaarden. Scope en technische aanpak leggen we schriftelijk vast.
We ontwerpen de interface en ontwikkelen plugin- of blokfunctionaliteit volgens WordPress-standaarden.
Code review, functionele tests, toegankelijkheidscontrole en performancecontrole vóór staging.
We deployen gecontroleerd, leveren documentatie en leggen je team uit hoe de nieuwe functionaliteit werkt.
We bouwen voor Nederlandse teams die duidelijke workflows, betrouwbare integraties en onderhoudbare WordPress-code nodig hebben.
Give content teams a controlled component with the right fields, variants and accessibility behaviour. For teams around Amsterdam, Rotterdam, Utrecht, Eindhoven and teams serving the wider Benelux, we define the local audience, ownership and follow-up route before implementation and account for iDEAL, SEPA and the payment service provider used by your organisation.
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 EU GDPR and guidance from the Autoriteit Persoonsgegevens, including data minimisation, retention and responsible handling of personal information in mind. Technical implementation supports your compliance work; it does not replace legal advice.
The delivery plan can account for iDEAL, SEPA and the payment service provider used by your organisation, pricing in euros, plain English with a structure that can support Dutch copy without duplicating layouts, and an EU data region when your processing, contracts or internal policies require it. We only add local integrations that serve a real customer or operational need.
Planning, reviews and support are organised around CET/CEST. 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.
Neet 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. Nee shortcuts, no loose ends.
PHPCS with WordPress ruleset clean on every file. Nee 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, Neetion or Jira. Nee tool switching, no friction.
You share the block or plugin specification in your stack. Linear, Neetion, 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. Nee credits in the plugin header, readme or editor UI.
You review, accept handover and ship the plugin to your client under your agency name.
Ja. Planning, reviews and support can be organised around CET/CEST. 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.
Ja. 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.
Ja. Our blocks use theme.json tokens and the standard block supports API, so they pick up your typography, colour palette and spacing scale automatically. Nee 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.