Most plugins don't fail because they sound bad. They fail because nobody can tell, in the five seconds a producer spends deciding, why this one is worth it. After years building plugins with a dozen producer brands, the things that actually move a plugin off the page are almost never the things first-time developers obsess over. Here's what sells — and what's a waste of your time.
The sound needs an identity, not just quality
Quality is the floor, not the hook. Plenty of clean, well-coded plugins never sell a copy because they don't do anything you can't already do. What sells is a recognizable character — a plugin that nails one thing in a way nothing else on the producer's drive does. Producers don't buy "a better EQ." They buy the specific sound they keep hearing on records and can't reverse-engineer. Decide what your plugin is unmistakably for before you write a line of DSP, and let everything else serve that one identity.
The demo sells more than the sales page
People buy plugins with their ears, not their eyes. A 60-second clip of your plugin doing its thing inside a real beat will out-convert the most beautifully written feature list every time. The moment a producer can hear themselves using it — "oh, that's the sound I've been chasing" — the sale is basically done. If you can only invest in one piece of marketing, make it a short, honest demo where the plugin is the star and the talking is minimal.
A UI that photographs well
Plugins sell as thumbnails. On a marketplace, in a YouTube description, on your own store — the screenshot is the first thing a buyer evaluates, and often the only thing before they click. A UI that reads instantly at thumbnail size sells; a cluttered one doesn't, no matter how good the engine behind it is. Design the interface so the one thing your plugin is known for is the most visible thing on screen. If a stranger can't guess what your plugin does from a 400-pixel-wide image, the design isn't finished.
Positioning beats feature lists
"42 oscillators, 9 filter types, unlimited modulation" sells nothing. "The 808 that cuts through any mix" sells. A buyer doesn't want your spec sheet — they want one clear promise they can picture in their own music. Name the outcome, not the engineering. The features matter; they just belong in the second paragraph, after the producer already knows why they care.
Price is a signal, not just a number
New developers systematically under-price out of nervousness, and it backfires. A plugin priced too low reads as beta-grade — buyers correlate price with quality, and a bargain-bin number quietly tells them not to trust it. The same plugin priced where its peers sit reads as legitimate and frequently converts better. Price for the value the buyer perceives, not for your own doubt about whether you've earned it.
Social proof — being named, not just reviewed
What other producers say about your plugin in context — a quick mention in a YouTube tutorial, a Discord thread, an unprompted comment — does more than any claim you make about yourself. The first handful of genuine reviews and the creators who name you without being paid to are worth more than an ad budget. Build relationships with the people who'd actually use your plugin, give them something worth talking about, and let the proof come from their mouths instead of yours.
The name and the first five seconds
A plugin's name, its thumbnail, and its one-line hook do almost all the selling. Get those three right and the rest of the page just confirms a decision the buyer has already started making. Get them wrong and it doesn't matter how deep the feature set is, because nobody scrolls far enough to find out. Spend real time on the name and the hook — they're cheap to change and expensive to get wrong.
What doesn't matter (the myths that waste your time)
- More features. Bloat doesn't sell; clarity does. Every control you add is one more reason for a buyer to feel unsure.
- Being the cheapest. A race to the bottom just teaches the market that your work is cheap. Compete on identity, not price.
- A flashy website. A clean product page with a great demo beats a slick site wrapped around a confusing product. The plugin is the product, not the page.
- Going viral. A spike of attention rarely converts to a customer base. Steady, credible mentions in the right communities compound far past any single viral moment.
Where this fits
Building a plugin that works is maybe half the job. The other half — the identity, the demo, the UI grammar, the positioning, and the distribution that turn a finished plugin into something producers actually buy — is exactly what the VST Development Course walks through, end to end, with the real workflows behind plugins that have shipped to producers for years. Founders' pricing is open through June 1.
The plugin sitting finished on your hard drive and the plugin paying for your next month are often the same plugin. The difference is everything in this list.
