Music rights contracts have a property that makes them unusually hard for conventional document search: the number that matters is almost never in the document you are holding.
A publishing agreement sets a revenue share. A later amendment adjusts it for a particular catalogue. A sync licence carves out a territory. A side letter changes the accounting period for one label. The share actually payable on a given track, in a given territory, this quarter, is the result of the whole chain — and getting it wrong is not a filing error, it is a payment to the wrong party.
The situation
A US music rights company approached us with a growing catalogue and a legal function that had become the bottleneck on every deal. Sync licensing requests arrived with short deadlines. Each one required somebody to establish what rights were actually available, under what existing commitments, before anyone could respond.
The contracts existed. They were organised. They were simply not answerable at the speed the business moved at.
What makes this domain specific
Three things distinguish music rights work from general contract management, and all three shaped the build.
Splits are cumulative and conditional. Royalty and revenue-share clauses are not replaced wholesale; they are adjusted, carved out and reinstated. Representing them as a single current value loses the reasoning, which matters when somebody queries a statement two years later.
Territory and term interact. The same work may be licensed differently in different territories with different expiry dates. A question about availability is always a question about a specific combination.
Counterparty paper arrives constantly. Sync deals come on the other side's template. Reviewing each against the company's own position was manual, and it was where deadlines were lost.
What we built
The deployment uses iLeaf's CLM platform, with the amendment and version-control layer doing most of the load-bearing work.
Amendment versioning that preserves the chain. Every amendment is generated and stored as a formal Amendment No. X, mapped clause by clause against the original. The platform can therefore answer both "what is in force now" and "what was in force on this date", which is the question that arises when a historical statement is queried.
Extraction tuned to the domain. Royalty and revenue-share clauses, territory grants, term and expiry, and the accounting provisions are extracted as structured fields rather than as text, so availability questions become queries with filters rather than searches over prose.
Counterparty redline review against a playbook. When a sync agreement arrives on the counterparty's paper, every deviation from the company's approved position is flagged, with a compliant fallback clause suggested. The reviewer reads what changed, not the whole document.
Obligation tracking on the commitments that bind. Exclusivity periods, option windows, reversion dates — extracted from the contracts and surfaced before they matter rather than discovered afterwards.
What we deliberately did not do
The platform does not calculate royalties and does not issue statements. It establishes what the contracts say, with citations, and hands that to the people and systems that do the accounting.
That boundary was set early and it was the right call. Rights administration has its own systems of record and its own reconciliation processes, and a contract intelligence layer that started producing numbers would have created a second source of truth for figures that must agree exactly. What the business needed was not another calculation — it was the contractual position, established quickly and traceably, feeding the calculation that already existed.
The same reasoning applies to advice. The platform extracts, cites and flags. Whether a proposed carve-out is acceptable is a commercial judgement, and it stays with the people whose job that is.
The result
The change the team describes is not in any single feature. It is that a sync request can now be answered within the window it arrives with, because establishing the rights position is a query rather than an afternoon.
Every answer carries the clause it came from, which matters more here than in most domains — in rights work, the ability to show why a position was taken is frequently the whole point.
Have a system that needs to do this?
500+ systems shipped since 2011, and we still maintain most of them. Tell us what you are trying to move.
