Tools built for your pipeline, not sold off a shelf.
A Figma plugin, a build and preview pipeline, an automated delivery step. Scoped to the way your team actually works, and yours to keep.
from €7,500
Per tool, fixed price, quoted once the shape is clear.
Why bespoke
A generic script solves a generic problem
Production bottlenecks are specific. They sit in the gap between the way your files are named, the platforms you deliver to and the approvals you have to pass. A tool bought off a shelf fits none of that, so it gets used twice and abandoned.
Everything here is built against your library, your naming and your delivery targets, then handed over with the source and documentation.
What gets built
Five kinds of tool
Most requests land in one of these. The named packages are the open-source display toolchain I maintain, which is usually the starting point rather than a blank page.
Figma plugins
Enforce the rules a library depends on: character limits per field and size, export presets per channel, bulk theme and surface switching, naming conventions checked before handoff.
Built against your own library
Build and preview pipelines
Local dev server for display units, multi-vendor compilation, and a preview anyone can open. One command instead of a folder of per-vendor builds.
display-dev-server, display-temple
Automated delivery
Push finished units to ad platforms and storage from the command line rather than through a sequence of upload forms.
display-upload
Video and GIF variants
Record HTML units to video and animated GIF, which is what social and Performance Max placements need from the same master.
display-ads-recorder
Feed generators
Turn a campaign spreadsheet into the feed your templates read, with the column map and validation that stops a bad row reaching production.
Built per feed spec
The toolchain
Published, and kept working
I maintain a distribution of the open-source display toolchain on npm under the @whoisxavier scope: the dev server, the unit templates, the uploader and the ads recorder. They are MIT forks of the toolchain MediaMonks released, kept current and extended where client work needs it.
That matters for two reasons. Your tool usually starts from working code rather than a blank repository, and the person building it has been inside that toolchain long enough to maintain it in public.
Keeping it working
Tool care, €4,800 a year
Optional, renewable, cancellable. It buys a working tool rather than my availability, so there is no retainer and no commitment to be on call.
Why a tool needs it
Ad platform specifications change, the Figma plugin API changes, and the Node ecosystem underneath moves constantly. A tool built this year stops working next year without anyone touching it.
What it covers
Keeping the tool running against those changes, dependency and security updates, and a defined budget of small changes across the year. Larger additions are quoted as their own build.
Priced at roughly a quarter of a build per year, which is the usual band for software maintenance. Decline it and the tool is still yours, with the source and the documentation.
Not sure which tool you need?
That is what the audit is for. One week inside the process, a written report naming where the time actually goes, and a scoped proposal. The fee comes off whatever gets built within 60 days.