How to Make Money With a DaVinci Resolve Plugin You Sell to Your Own Audience

Build a DaVinci Resolve plugin once and the hundredth sale costs exactly what the first one did: nothing. That number does not exist in a day rate, a retainer, or a coaching call, no matter how good you are at any of them. It only exists on the other side of a product.

Most of what gets sold to editors right now is about speed: cut your edit time, take on more clients, post more often. That treadmill does not end, it just moves faster under you. This is about the other option: building something once that keeps selling without your hours attached to it, to the people who already watch what you make.

The service you already know the shape of

If you edit for other people, you already know this model from the inside. You trade hours for money. A good year means more hours or a higher rate, and both have a ceiling: yours. Miss a month of client work and that month's income is simply gone, because there was never an asset behind it, only your time, spent and paid for once.

A plugin does not have that ceiling, because it is not your time being sold. It is a file. Someone buys it at 2am in a time zone you are asleep in, and the transaction has nothing to do with your calendar.

What a marketplace seller pays for that you already have

Sell a plugin on a general marketplace and you are one listing among hundreds, competing on a search result you cannot control, for a buyer who has never heard of you. Most of what that seller pays for, in ad spend or in marketplace fees, is exactly the thing you already have if you have any audience at all: people who already trust your taste and your technical judgment, because they have watched you make things for a while.

That is the actual argument for selling direct. Not the commission a marketplace takes, though that is real too. It is that the expensive part, being a known and trusted name to the exact person who has the problem, is already done. A plugin sold from your own site to your own audience starts where a marketplace listing has to fight to get to.

The habit you repeat is the product

The plugin does not need to be invented from nothing. Look at what you already do the same way on every project: a caption style you always reach for, a bin structure you rebuild by hand every time, an export chain you run through three tools because no single one does the whole thing. If you have explained that habit to another editor more than once, it is not a quirk. It is a specification.

That is a different starting point from most software ideas, which begin with a guess about what a stranger might want. Yours begins with something you have already tested on the one project that matters most: your own, repeatedly, for free, for months.

Building it is the smaller half of selling it

Writing the plugin is not where most people stall. Packaging it so it survives on a machine you have never touched is. An installer that works on a client's Windows laptop and a stranger's Mac. A licence that says what they are actually buying. A way to rebuild the exact same release six months later when Resolve updates and someone asks why their copy stopped working.

That is the half of this that is not really about DaVinci Resolve at all, and it is the half that decides whether you have a product or a folder of files you are personally responsible for forever. It is also the half most tutorials on Resolve scripting skip entirely, because it only starts to matter once somebody else's money is involved.

Where The Forge fits

The Forge is the skill pack I built for exactly this, for Claude Code, and I covered what is inside each edition in detail in an earlier post about building it. The short version, for the money question specifically: Creator teaches your AI worker to build Resolve automation from plain English, which is where you prove a habit is actually worth productizing before you spend a cent on selling it to anyone else. Studio is the edition built for the sale itself. It adds real-time OFX effects in C for anything that touches pixels, and the packaging, installers, and release kit, a release script, an EULA template, a generated welcome guide, that turn a working plugin into something you can hand to a stranger and get paid for.

What this does not solve

None of this replaces having an audience in the first place. A plugin sold to nobody sells to nobody, however well it is packaged. It also will not sell itself from silence: you still have to tell the people who follow you that it exists, and answer the emails when something on their machine does not match yours. What it removes is the ceiling on your own hours, not the work of having something worth selling to.

Own the plugin. Stop reselling the same hour of editing work over and over just because that is the model everyone already has in place.