The platform is the books
Rights management at a Middle East broadcaster or distributor is the intellectual-property accounting system for the business. Every title carries a rights window, an availability map by territory, a window-by-platform exclusivity, a revenue split with the licensor, a marketing rights specification, a residuals obligation, and a renewal calendar. Each new licence deal lands as a structured rights record. Each window expiry, each option exercise, each renewal negotiation, each platform-extension request modifies the record. The platform that holds the records is, structurally, the books of the IP business.
The platforms that hold these records at Middle East broadcasters today are typically one of three things. A legacy product that the broadcaster has been operating for a decade or more, often the same product the global tier-one broadcasters started from. A vendor-led modernisation that the broadcaster signed during the last technology cycle. A spreadsheet-and-document-management hybrid that the rights team has built around the gaps in whichever vendor product the broadcaster chose. Each of these has the same structural issue. The records that determine the broadcaster's commercial reality live inside a system the broadcaster does not own outright.
This piece is the REFORGE pattern for the rights management platform.
What the rights workflow actually contains
The rights workflow at a Middle East broadcaster covers six structural surfaces.
Acquisition. The broadcaster acquires content from external licensors — studios, distributors, sports rights-holders, independent producers, the regional content suppliers. Each acquisition is a deal record with structured terms.
Cataloguing. The acquired title enters the catalogue with the structured rights specification — territory, window, platform, language, subtitle and dubbing rights, marketing rights, residuals obligations, renewal mechanics.
Programming and exploitation. The programming team works against the rights specification to schedule the linear broadcast, the OTT availability, the cross-platform release sequence. Every programming decision is constrained by the rights specification.
Renewal and option management. Each window has a renewal calendar. Each deal has option mechanics — first refusal, output-deal commitments, volume-discount triggers. The rights team manages the calendar against the commercial relationship with the licensor.
Licensing-out and distribution. The broadcaster's owned content is licensed to external buyers — international broadcasters, OTT platforms, theatrical distributors, ancillary-rights buyers. Each licence-out is a separate deal record with its own structured terms.
Royalties and revenue accounting. The revenue from the licensed content is reconciled against the deal terms. The royalty calculation, the revenue split, the residuals payment, the regulatory reporting — each is a structured workflow that the finance and rights teams operate jointly.
Each of these surfaces is currently served by a combination of the legacy platform, working spreadsheets, document-management systems, and the institutional knowledge in the rights team's senior staff. The platform's coverage of each surface varies.
What the alternative architecture looks like
The replacement is not a single platform purchase. It is the deliberate building of a rights-management substrate the broadcaster owns, with workflow surfaces on top that respect the structural reality of the IP business.
The substrate has three components.
The rights data layer. Every deal, every title, every right specification lives in a structured data layer the broadcaster operates. The schema models the rights specification with the fidelity the rights team needs — territory rules with the precision the deal terms require, window rules with the date-arithmetic precision the calendar workflow needs, platform rules with the granularity the streaming-experience design demands. The data layer is queryable from any engine, exportable in standard formats, and portable to any infrastructure the broadcaster chooses.
The deal-document layer. Every contract is held against the deal record, with the structured terms extracted, the original document preserved, and the relationships between contracts modelled explicitly. The document layer is searchable against the structured deal taxonomy.
The workflow layer. The rights workflow runs on owned software against the data layer. The cataloguing workflow, the programming-against-rights workflow, the renewal calendar, the option-exercise workflow, the licensing-out workflow, the royalties reconciliation. Each is a structured workflow the rights and finance teams operate against the data they own.
The AI agent layer sits on top. The agents absorb the synthesis work the rights and finance teams perform manually today. The renewal-calendar agent watches the calendar against the operational reality and surfaces the upcoming expiries that warrant attention. The option-exercise agent reads the option terms against the current commercial reality and prepares the structured recommendation. The licensing-out agent watches the catalogue against the external-buyer interest and surfaces the deals that the licensing team should pursue. The royalties agent reconciles the revenue against the deal terms with the auditable structured evidence base attached.
The REFORGE sequence
The replacement runs as a sequence of workflow-led sprints. The legacy platform stays in place during the parallel-run period the rights team needs to validate the new substrate.
Sprint one — the data layer migration. The deal records, the title catalogue, the rights specifications, the deal documents, and the historical revenue ledger migrate to the owned substrate. The legacy platform continues to operate as the production system during the validation. The parity report against the legacy platform is the artefact the rights leadership signs off on before the cutover.
Sprint two — the cataloguing and programming-against-rights workflow. The cataloguing team and the programming team move to the new workflow surface. The legacy platform's cataloguing function retires for the new acquisitions. The historical catalogue lives in the new substrate.
Sprint three — the renewal and option management workflow. The rights team moves to the new surface for the calendar workflow. The agents that absorb the synthesis work go live with the supervised pilot pattern we run at every regulated estate.
Sprint four — the licensing-out and royalties workflow. The licensing and finance teams move to the new surface. The structured evidence base for the royalty calculations is the auditable artefact the external auditor reviews.
The legacy platform retires at the end of the sequence. The broadcaster owns the books of the IP business.
What this changes commercially
Three things change for the broadcaster running the workflow-led replacement.
The IP-management cost trajectory bends. The legacy platform's recurring cost, the integrator's retainer on the configuration, and the rights team's manual work all reduce.
The institutional capability matures. The rights team owns the substrate that the entire IP business reads from. The team's productivity reflects this.
The strategic optionality grows. The broadcaster who owns the rights substrate can pursue the strategic moves — content acquisitions, licensing-out deals, distribution expansions — without the vendor relationship being the gating factor.
The Middle East dimension
Three dimensions matter at a Middle East broadcaster specifically.
The cross-jurisdiction rights architecture is the operating reality. The Middle East content-licensing environment, the broader MENA territorial mapping, and the international rights relationships require the substrate to handle the territorial precision the deal terms demand.
The Arabic-language content lifecycle is the substrate the cataloguing operates against.
The Ramadan-cycle programming workload is the highest-stakes annual moment for the rights and programming teams.
The saasinator perspective
The IP business runs on the rights substrate. Hosting the substrate inside a vendor's commercial perimeter is the procurement decision worth revisiting. The broadcaster who owns the substrate is in a different commercial conversation with every vendor in the broader stack.
What to bring to the diagnostic
Bring the legacy rights-platform deployment scope, the integrator retainer, the deal-document inventory, and the rights team's working-files catalogue. The diagnostic is ten working days. The output is the workflow recommendation, the architecture sketch, and the first-quarter scope. Book a diagnostic at /diagnostic.