Which parts of the technology and AdTech stack should an audio company own?
The short answer
An audio company should retain control over its audience relationships, data use, commercial rules and technology decisions. It does not need to develop every system that supports them. Proprietary development is most defensible where it creates a distinctive business advantage. Standardised capabilities, particularly those connecting to advertising buyers and third-party systems, often benefit from specialist providers with the resources to maintain those integrations. The right architecture combines proven internal systems, external technology and selective custom development. Its purpose is to keep the business competitive, commercially accessible and capable of evolving without making every market change an internal development project.
Does owning technology mean controlling your future?
The instinct to build and own technology is understandable. It promises independence, flexibility and control over priorities. Internal teams may also know the requirements of the existing business better than an external provider.
But ownership and strategic control are different things.
A company can own its code and still be constrained by a development backlog, scarce expertise or interfaces that no longer meet buyer requirements. Equally, it can use external technology while retaining contractual control over data, pricing decisions and the ability to change partners.
The question is which ownership model gives the business the strongest position, not how much software it can call its own.
Where does in-house development make commercial sense?
Custom development deserves consideration when it supports a capability that differentiates the business: a distinctive listener experience, proprietary audience intelligence, commercially valuable decision logic or a workflow that materially improves performance.
Even then, the comparison must include the cost of keeping that capability effective over time.
Building the first version is only the beginning. Security, reliability, documentation, recruitment, partner integrations and changing market requirements all create continuing obligations.
For many individual publishers, matching the development capacity of specialist international technology providers across the entire stack is not an economically credible ambition. Scale, resources and a genuine differentiating use case should determine where exceptions make sense.
Which capabilities are usually better sourced externally?
Components that connect the company to the wider advertising market are often strong candidates.
Depending on the business, these may include ad serving, supply-side access, demand-side integrations, measurement connections and parts of audience-data activation.
Their value depends heavily on interoperability, operating reliability and continued support for the systems buyers use. Maintaining those connections can require substantial work without making the publisher’s own content or audience proposition more distinctive.
Specialist providers can spread that investment across customers. But buying a system does not automatically make it future-proof. Device support, integration depth, product roadmaps, service commitments and total costs still need to be tested.
A vendor’s promise of compatibility should be verified against real campaign requirements.
What should remain under the company’s control?
The technical implementation may be external, but accountability stays with the publisher.
| Area | What the company should control |
|---|---|
| Audience relationships | Product priorities, listener experience and the terms governing access to audience information |
| Data | Permitted uses, access rights, appropriate portability and restrictions on partner reuse |
| Commercial policy | Pricing rules, inventory allocation, sales commitments and approval authority |
| Architecture | How systems connect, which dependencies are acceptable and how components can be replaced |
| Performance | Visibility into delivery, costs, revenue, service quality and operational failures |
| Continuity | Documentation, access arrangements and credible migration or exit options |
These controls need to be reflected in contracts, operating processes and technical implementation. They cannot be assumed merely because a provider describes its platform as open.
Why does compatibility matter beyond the audio industry?
A technology stack can work well within the broadcaster’s own processes and still make the business difficult for advertisers to buy.
Agencies and advertisers operate across media channels, markets and buying platforms. They need inventory, audience information, creative delivery and reporting to fit into those workflows.
Industry specifications such as OpenRTB and VAST provide part of the shared technical language for programmatic transactions and ad delivery. They are a foundation for integration, not proof that two systems will work together without additional implementation. [1][2]
This makes cross-media compatibility a commercial issue. A buyer’s willingness to include audio can depend on how easily it fits into the rest of the campaign.
The relevant benchmark is the advertising market’s buying process, not only the technical practice of other radio companies.
What does agnostic programmatic access mean in practice?
It means giving buyers appropriate access through the systems they use, without unnecessarily tying the publisher’s proposition to a single buying platform.
That may involve multiple supported demand-side platforms, suitable deal structures and reporting that can be understood alongside other media. It does not require connection to every platform, nor selling every impression through an open auction.
The publisher still needs to protect yield, avoid unnecessary intermediaries and maintain appropriate quality and data controls.
Agnostic access is therefore a deliberate commercial design choice: broad enough to reach relevant demand, selective enough to preserve value.
Should legacy systems be replaced completely?
Not necessarily. Proven systems may still perform important functions reliably and economically.
The problem arises when their limitations determine what the business can offer, how quickly it can respond or which buyers it can serve.
A staged approach can preserve useful systems while adding standard interfaces, replacing restrictive components and connecting previously separate processes. Each step should improve a business outcome: less manual work, faster activation, more reliable reporting or access to relevant demand.
This is especially important where broadcast and digital audio workflows need to converge. Common booking access can connect the two, while recognising that their inventory, targeting and delivery mechanics remain different. RMS has publicly documented a real-time programmatic radio implementation involving automated exchanges of terrestrial inventory information and broadcast confirmations. [3]
Modernisation should progressively digitise commercial operations without putting current revenue at unnecessary operational risk.
How can management avoid missing the next industry standard?
Monitor developments in Europe and the United States, including shared infrastructure, emerging specifications and the platforms gaining practical adoption among buyers.
The aim is to recognise when a common approach is becoming a condition of market access. Waiting until every integration is commercially urgent can leave a publisher funding expensive catch-up work.
Equally, an emerging technology does not deserve investment simply because it attracts attention. Assess actual adoption, buyer relevance, interoperability, switching costs and the consequences of waiting.
The architecture needs room to respond without forcing a complete rebuild each time.
How THE AUDIO SHIFT can help
THE AUDIO SHIFT draws on Matthias Schenk’s experience in the development of RMS’s audio technology and commercial capabilities, including the convergence of terrestrial radio and digital audio advertising.
That perspective connects internal operating requirements with the expectations of agencies, advertisers and international buying platforms. It brings practical experience of the dependencies and implementation choices involved in making audio inventory digitally accessible.
The work evaluates which existing systems should be retained, where external solutions offer stronger economics and where proprietary development creates a genuine advantage. It also assesses partner dependencies, integration requirements and the path towards convergent programmatic booking.
The outcome is a prioritised technology roadmap, with clear build, buy and partner decisions, commercial evaluation criteria and a migration sequence designed around the business.
Matthias Schenk · Founder, THE AUDIO SHIFT
Sources
[1] IAB Tech Lab, OpenRTB: https://iabtechlab.com/standards/openrtb/
[2] IAB Tech Lab, VAST: https://iabtechlab.com/standards/vast/
[3] RMS, Echtzeit-Programmatic Radio: https://rms.de/pressemitteilungen/2023/RMS_Programmatic_Radio
