inMusic, the parent company of Akai, Moog and Native Instruments, has decided to work with the people who mod its instruments instead of fighting them. In an interview with The Verge published on 6 November 2026, CEO Jack O’Donnell said the company is “going to provide a toolbox to the community” and will “provide the inner workings of, say, an MPC” so that people can build on them. The full interview is in the source below. The news part is short, so I will keep it short.

What the excitement is about

Musicians have modded hardware for as long as hardware has existed. What changed is that writing a small program for your own sampler no longer needs a programmer. You describe what you want, you get working code, you load it. The reaction to the story treats inMusic’s move as generous, or brave. I read it as practical. They looked at what their customers can now do for themselves and stopped standing in the way.

Is there a real need? Yes, and it was always there

Every owner of a sampler wants one thing it doesn’t do. A custom export. A different way to name files. One button that does three steps. Those wants are too small and too personal for a product team to prioritise, so they sat unmet, or got solved by a third-party utility sold for a few dollars.

What changed is that the owner can now build that utility themselves. This is the part of vibe coding I take seriously. A normal person can build fairly competent software for their own use. The fallout from a mistake is small because the tool only touches their own data. I do this myself. I have replaced many of the tools and scripts I used to buy or patch together with ones I build this way.

What didn’t change is the instrument. The sound engine, the hardware, the firmware, the distribution into shops, the service network and the name people trust all stayed where they were. A toolbox for the edges doesn’t touch the core.

The small utilities are the first casualty

If I sold a companion utility for a sampler, I would be worried. Consumer utility software is going to be hit hard, because the individual utility is now the easiest thing to build. inMusic has read this correctly. If the utilities are going to exist either way, it is better that they run on your toolbox, on your platform, built by your customers, than against you.

The same thing is coming for a clinic, a shop and a marketing team

Take a clinic. It pays for a handful of small tools around its practice system. A reminder script. A reporting export. A waiting list in a spreadsheet with macros. The vendor of the practice system probably sells or resells some of those. Within a year the clinic manager builds the export themselves in an afternoon, because it only reads their own data and only has to work for them.

What that vendor should do is what inMusic did. Stop defending the small stuff. Publish the data and the hooks. Keep the system of record, the compliance work, the connections into payment and the relationship with the clinic.

A shop is the same. A merchant will vibe-code their own stock-count checker or margin calculator. They will not vibe-code a payment gateway agreement or a logistics contract. A marketing team will build its own reporting dashboard. It will not build the ad platform’s data or the agency’s judgement about what to do with it.

Where a prompt still can’t reach

Vibe coding collapses the distance between a thought and working output, and that is the only distance it collapses. What decides commercial success sits outside it: real-world testing, user feedback, marketing and customer acquisition. Every build still needs back-and-forth on alignment, strategy, approach and security, and that context comes from a person with experience, not from a single prompt. B2B software still has a gap here that vibe coding can’t close.

At AeroChat the part a prompt can’t produce is each market’s payment processors and logistics partners. Global vendors skip them. You can’t vibe-code your way into those relationships, and that is where the time goes.

What to do

Split what you sell into the core and the edges. The core is the hardware, the platform, the system of record, the integrations into money and delivery, and the relationship with the customer. The edges are the small utilities, exporters, calculators and companion apps.

Expect revenue from the edges to fall, and stop spending money defending it. Give the edges away on purpose. Publish an API, documentation and a toolbox, and let customers build what they want on top. Put the freed-up effort into the core and into the relationship, which is where you are still hard to replace.

If you are the customer, do the reverse. Build the small tools yourself, and keep your core systems with vendors who hold the relationships you can’t.

Source: The Verge: How Akai and Moog are embracing vibe-coded mods