Stop Building a Second Product After You Ship

Building the instrument is only half the job. The other half (licensing, delivery, updates, user management) is where many teams quietly burn months and headcount on a “second product” they never meant to build.
We sat down with Calum Minuti-Goold, a guest developer from ebbandflow who has worked with leading software companies on developing, authoring, and launching software instruments. Against the competitive backdrop of Kontakt, UVI / FL Studio, and newer toolchains like ImaginePlugins, Calum walks through what post-ship infrastructure looked like before Product Hub, which capabilities actually move the needle for clients, and why ownership of the full pipeline is the line that closes the pitch.
This is a longform interview: fourteen questions across six chapters, about a nine-minute read. Settle in.
Key Takeaways
- Fragmented post-ship stacks cost ownership first: different contacts at every failure point, and rebuilds that stop being worth pursuing.
- Delivery is the overlooked lever. Bandwidth fees mount fast; putting installers and downloaders in the post-build flow sends teams back to building.
- Versus Kontakt- and UVI-class incumbents, the closing argument is pipeline ownership from ideation through sales, without waiting on another team’s schedule.
- Product Hub is framed as control without large overhead: licensing in your hands, subscription-ready without growing the team, and a collaborative roadmap with UJAM.
In this article
- The Real Cost of a Fragmented Workflow
- Delivery Is the Feature Developers Forget to Budget
- Scaling Catalogs Without Menu Diving
- Ownership Over the Pipeline
- When Licensing Stops Being an Afterthought
- Tried, Tested, and Built With Your Roadmap in Mind
The Real Cost of a Fragmented Workflow
Gorilla Before Product Hub, what did licensing, delivery, updates, and user management actually look like, and what did that patchwork cost you in time and money?
Calum Prior to the Gorilla Engine environment, development consisted of far more isolated and administrative tasks. This ranged from needing multiple third-party tools to map basic instruments, to complex and unmonitored terminal tasks running from text-based files that could take hours to remotely process before being able to test any deliverables.
The problem of a fragmented workflow is ownership. At any stage where something went wrong you could have a different point of contact, a different manager, a different engineer. And all those components are not partnered to feel like part of the same flow.
In general, this means time lost in purely communicative tasks, engineer-led hotfixes to make things work as expected, and an overall result where rebuilding plug-ins, content, or updates could consume enough resources that it is no longer efficient to pursue.
Calum Minuti-GooldThe problem of a fragmented workflow is ownership.
Gorilla How much engineering time were you burning on that “second product,” the stitched-together stack that had nothing to do with the instrument itself?
Calum Generally, it would be three full teams, in addition to actual development. One to handle conversion and delivery, one to handle web, and, due to that separation, another to handle communication between all the teams. That scale would remove the agility needed to be competitive in the market today.
Delivery Is the Feature Developers Forget to Budget
Gorilla Product Hub covers bandwidth-free installer delivery, branded downloaders with resume support, and webshop connections that create licenses after purchase. Which of those moved the needle most for your clients, and why?
Calum Delivery is something that is frequently overlooked by us all, and those who have delved in will know just how quickly fees can mount. Having these aspects included in the overall post-build flow allows developers to get back to developing and stop worrying about how to get their products online, secured, and downloadable.
Gorilla There’s also a JavaScript client for login and activation inside the plugin. How does that embedded activation experience compare to the usual Kontakt / iLok / Native Access gauntlet?
Calum Having used this latest client on a recent large release, I noticed how it not only reduced the need for customer support, but also gave me the tools and access to help when a customer did need assistance.
Calum Minuti-GooldDelivery is something that is frequently overlooked by us all, and those who have delved in will know just how quickly fees can mount.
Scaling Catalogs Without Menu Diving
Gorilla Working with catalogs like Westwood Instruments (dozens of SKUs, multiple builds, large assets), what does scale look like inside Product Hub?
Calum Simply put, it works exactly as you would expect. No complex systems or menu diving. It’s a simple, intuitive, and searchable database for licences and products, allowing you to track versions, push uploaded items for release, allocate licences, and see which licences are attached to which customers.
Calum Minuti-GooldNo complex systems or menu diving.
Gorilla Resume support for large downloads still feels rare. For a catalog-heavy shop like Ebb & Flow, what support burden does it remove?
Calum Large downloads are an unavoidable part of working with samples, especially when catering to a global audience, so adopting a system that makes this part as streamlined as possible reduces friction for someone wanting to use the tools they purchased as quickly as they can.
And when something local and uncontrollable does go wrong, allowing for that larger download to pick up right where it left off can certainly help people get back to making music as quickly as possible.
Ownership Over the Pipeline
Gorilla Kontakt has 20+ years of ecosystem; UVI is deep in FL Studio. When you pitch Gorilla Engine + Product Hub to a client like CrowHill, what closes the argument?
Calum For me, it’s always been about ownership over the pipeline. You can go from product ideation and creation all the way through to distribution and sales without needing any handholding, sign-offs, or manual intervention from the Gorilla Engine team.
Almost every other system I have encountered has a blocker in one way or another where another team has to handle a stage of the process. Those unknowns, and the reliance on another team’s scheduling, are often enough to derail even the sparsest of roadmaps.
Calum Minuti-GooldFor me, it’s always been about ownership over the pipeline.
Gorilla Gorilla Engine opened to third parties as Native Instruments entered insolvency proceedings. Do you use that timing in sales conversations?
Calum Almost every developer, both established and starting out, spent the majority of that period looking ahead for alternatives without any need to be pushed. Less because of the uncertainty itself, and more because it was a moment to reflect and identify other points of friction.
It was an opportunity that many service providers took to launch their offerings, but few looked to improve on what predecessors already had.
Gorilla Newer tools like ImaginePlugins aim at smaller teams with simpler workflows. Where does GE + Product Hub fit when someone asks, “Is this too much platform for me?”
Calum Like all great platforms, GE offers scalability. You can make a simple single-dial effects unit or a multi-page, surround-sound, 100GB orchestral collection. That ability to scale matters.
Starting small almost always leads to growth, and having to change platforms multiple times during that growth cycle can delay opportunities, or distract and pull teams away from innovation.
When Licensing Stops Being an Afterthought
Gorilla Subscription-ready licensing is built into the delivery workflow now. Are clients like Ebb & Flow or Westwood actually moving that way, and can a small team support it?
Calum Subscription adoption is something many brands are unfamiliar with, simply because the tools available on the market haven’t been able to offer it. Now that it is achievable without any increase in team resources, it is an option many companies may look to, in order to make larger collections even more accessible.
Gorilla How do you frame Product Hub as an investment rather than a cost, especially for developers who’ve never priced backend infrastructure?
Calum As with distribution, licensing (and protecting both a developer’s and a purchaser’s investment) is often an afterthought, despite being one of the most crucial aspects of the delivery flow. Other solutions from competing services in the market have always attributed a direct cost to licensing products.
These costs are almost always an upfront fee based on projections, or a recurring, point-of-sale cost based on total RRP. So there has always been substantial risk involved in offering that level of security, but more so there has always been the need for those third-party handovers and reliance on other teams’ timelines, or allowing monitoring access to internal systems.
The Product Hub puts that integration and control in your team’s hands, and is structured in a way that is substantially more friendly towards those starting out and looking to get their first few products released without a large overhead.
Calum Minuti-GooldThe Product Hub puts that integration and control in your team’s hands.
Tried, Tested, and Built With Your Roadmap in Mind
Gorilla Release 26.03 shipped 50+ changes from community feedback. Working with UJAM for clients like Crow Hill and Westwood, does it feel like a vendor relationship or a partnership?
Calum The Gorilla Engine team has always been incredibly collaborative, from actively looking for feedback to implementing changes or fixes reported to them, often taking into account your own roadmap to ensure they provide what you need, when you need it. For a company of this scale, this is generally unheard of, and is frequently the first thing I mention to a new team looking for a way to build and release their ideas.
Gorilla For a developer with a great instrument who’s dreading licensing and delivery, what’s the one thing to understand about Product Hub before building something custom?
Calum The tools already exist, and the support is there. The ideal scenario is always to use something tried, tested and well maintained. The head start the Product Hub gives you allows for more time to build great tools for your community.
Calum Minuti-GooldThe tools already exist, and the support is there.
Gorilla Where do you see Product Hub in two years?
Calum In the time the Product Hub has been out, there are already great features being worked on, from a wider range of compatible e-commerce integrations to third-party reseller support. I see the future of the Hub blurring the lines between a client’s purchase flow and licensing even further.
Removing or reducing the requirement for log-in authorisation tools outside the Product Hub, as well as making deeper analytics available within the Hub to help determine use and friction points, such as download times, installation counts, and activation counts.
The information developers need to better understand what happens after someone leaves their website, so they can have ownership or at least oversight over the full experience.