This week, senior leaders from across the media industry came together in London for the DPP Leaders' Briefing. If one question runs through this year's conversations, it's buy versus build. The DPP itself calls it one of the defining debates of 2026, driven by AI-assisted coding tools that give broadcasters far more in-house development power than before. Its European Media Trends report found that AI is reshaping the traditional buy-versus-build debate, and its Media Tech CEO Survey shows suppliers re-architecting around AI and connected platform ecosystems.

It's not buy vs. build. It's buy TO build
Hardware got replaced by software, and now software is being replaced by self-built tools. But is it really?
In every broadcast house I visit, the same debate comes up - do we buy or do we build it ourselves? Broadcasters usually choose to build because the way they work is what sets them apart. How a newsroom takes a story from first idea to on air is part of its identity, so very few broadcasters want a vendor to decide that for them.
Some broadcasters built their own tools and are now moving away from them, and others bought a platform and are now starting to build on their own. Both are right, for different reasons.
Building got easy, but owning is still hard
AI has made building much easier because you can get exactly the interface and workflow you want. Owning what you build is a different matter, though: you own every bug, every upgrade and every integration; you need a dev team to maintain it over the years; redundancy and hosting become your responsibility too.
Buying solves most of that, because the software is proven and supported. The catch is that SaaS makes you work its way, with its clicks and its screens. Your team ends up adapting to the tool, when the tool should adapt to your team. So why should you have to choose?
Headless: separating the engine from the head
This is why we believe in headless. In a headless setup, the engine and the interface are separate.
- The engine is the data, the logic, and the device control. We run it, and we keep it on air.
- The head is everything your people see and click, and you build it however you want.
Fluid Workflows
We call this approach Fluid Workflows. It gives you one core platform where the code and data stay fixed, with an interface on top that each team shapes to the way it works. In other words, you buy the core, and you build the experience.
A director in the gallery, an editor on the desk, and a producer on the rundown all need different screens. With Fluid Workflows, each team gets its own view, while the core underneath stays the same: tested, supported, and on air.
Already live in Cuez soft panels
This isn't a future promise, because it's already live in a new Cuez production control panel solution. You simply prompt what you want to see, what you want to connect, and how your workflow should run, and Cuez builds it on top of the core. This is only the beginning as we deepen our MCP integration across the Cuez suite.
The result is you get the best of both worlds.
We carry the reliability and the risk, and you build what you want within and on top of our platform, with Cuez as an expert innovation partner alongside you.
What comes next
This is what we're building at Cuez, end-to-end and fully in the cloud. Let's stop talking about what you buy, and start talking about what you'll build.
Want to continue the conversation? Send us a message!
