Add-ons on request.
A tool that does not exist yet, or one of these bent to your workflow — built to order and delivered as a plain Blender add-on. No catalogue, no subscription: one job at a time.
Three kinds of job.
Most requests fall into one of these. If yours does not, describe it anyway — the scope is where that gets sorted.
Four steps, no surprises.
Nothing gets built before both sides know what is being built.
- 01
Describe the job. What you do by hand today, how often, and a
.blendif the shape of the scene matters. - 02
Get a written scope. What the add-on will do, what it will not, which Blender range it targets, and what it costs — quoted per job, before anything is built.
- 03
See it work early. Short iterations. You get a working version to try on your own files, not a demo at the end.
- 04
Take it with you. The ZIP, install notes and the source. Whether it stays yours alone or joins this page is your call.
Built like the rest of them.
Good to know
On request only, and one job at a time. Small tools are often a matter of days; anything larger is split into stages you can stop after. Pricing is per job and stands in the scope — no hourly meter running in the background.
Describe the job.
Two or three sentences are enough to start. The scope comes back in writing.
