Sync Licensing and Music Clearance Software: Why a Deal Dies Waiting for the Fourth Writer to Reply

Why sync deals fail on administration rather than on taste

An agency music supervisor needs a track for a campaign that shoots in nine days. The sync manager checks: the composition has four writers. Two are controlled by the publisher, one is with a responsive co publisher, and one is an independent represented by an administrator who takes four working days to answer anything. The master is with a label whose licensing contact left last month. The campaign is for a beverage brand, and one writer has a restriction against alcohol advertising recorded in a contract nobody has read since 2018.

Nine days is not long enough. The agency moves to a production music track that clears in an hour. The deal did not fail because the music was wrong. It failed because the clearance path was unknowable at the moment the decision had to be made.

This is the structure of the sync business. The creative selection is fast and emotional. The clearance is slow and administrative. Every hour spent establishing who owns what and who has to approve is an hour of deal risk, and the alternative options available to a supervisor are increasing. The rights holders who win sync business are not always the ones with the best catalogue. They are frequently the ones who can answer yes with confidence in an afternoon.

Problem 1: ownership splits are scattered and nobody trusts the number

A composition's ownership is a set of percentages across writers and publishers, and your copy of it may differ from the co publisher's copy, from the collection society's registration, and from what the writer believes. Master ownership sits separately with a label or an artist. For a catalogue of any size the splits data has been assembled over years from statements, registrations and contracts, and parts of it are stale.

Synchtank models rights and does it properly, and it is a serious product for rights holders. Disco and Source Audio are excellent at the pitching and delivery side, where the job is getting music in front of supervisors quickly. What none of them can do is make your splits accurate, because that data problem is yours, and the tools inherit whatever you feed them.

What a custom build does: hold splits with provenance and confidence rather than as bare percentages. Each share knows its source, whether a contract, a society registration or a statement, and when it was last verified. The clearance view then shows not just who owns what but how confident you are, and flags shares that do not total correctly, which happens more often than anyone admits. It also computes the most valuable question in sync, which is whether a track is one stop. A catalogue filtered to one stop tracks is worth disproportionately more to a supervisor on a deadline, and most rights holders cannot produce that list on demand.

Problem 2: clearance is a chase and the chase is invisible

Once a quote is agreed, every co owner has to approve. That means emails, follow ups, and a mental model of who has replied held by one person. If a co owner objects to the use or wants a different fee, the whole quote moves. Meanwhile the client is waiting and the shoot date is fixed.

Most systems track a licence as a record with a status. What they do not model is the approval as a set of independent parties each with their own state, their own contact, their own response history and their own typical response time. So the chase is manual and the sync manager cannot answer the question that matters, which is not what is the status but who are we waiting for and how likely are they to move today.

What a custom build does: model each required approval as its own object with party, share, state, contact and history, then automate the chase with escalation. The dashboard shows a deal as a set of parties with three green and one amber, and the amber has a name and a last contacted date. Response time history per party is genuinely useful: after a year you know which administrators take a week, which lets you triage a nine day deadline honestly instead of optimistically. Where an approval requires a decision from you rather than a third party, it should never sit in a queue at all.

Problem 3: restrictions live in contracts and surface at the worst moment

Writers and artists restrict uses. No political advertising, no alcohol, no tobacco, no gambling, no firearms, sometimes approval required for any advertising at all, sometimes restrictions specific to a territory or a competitor of an existing endorsement. These live in contract clauses, and in most organisations they live in someone's head backed by a document nobody rereads.

Rights systems tend to model restriction as free text if they model it at all. Free text does not block anything. So a quote goes out, work proceeds, and the restriction surfaces during approval, which is late enough to be embarrassing and sometimes late enough to be expensive.

What a custom build does: encode restrictions as structured rules against categories, then evaluate them at the point of search. A supervisor searching for a beverage campaign should not be shown a track that cannot clear for alcohol, and your team should see the restriction with its source clause before a quote goes out. Most favoured nation terms deserve the same treatment: if one party receives terms no less favourable than any other, that constraint must be enforced when fees are set, and doing it by hand across a multi party clearance produces quiet errors.

Problem 4: the licence is issued and then nobody tracks it

A sync licence has a term, a territory, a media scope, sometimes options to extend into further media or further markets. Options expire. Terms end. Campaigns get extended by the client, who may or may not remember to come back for a new licence. And usage that continues past the term is an infringement your writers will eventually notice.

Once the money is in, attention moves to the next deal. Tracking the tail is nobody's priority until a writer asks why their song is still running in a market that expired last year.

What a custom build does: treat the licence as a live object with dates that generate work. Expiring options surface as commercial opportunities, because an option about to lapse is a conversation worth having. Term ends surface as compliance checks. Cue sheet obligations are tracked, since performance income depends on correct filing and that step is frequently dropped after delivery. Sync fees then allocate across writers and publishers by share, feeding statements without the manual re entry where allocation errors get introduced.

Problem 5: search is built for cataloguers, not for supervisors under pressure

A supervisor does not search for a title. She searches for something that feels like the second half of a scene, in a tempo range, with no vocal in the last thirty seconds, available for a national broadcast campaign in two territories, one stop. Every part of that query is real and most catalogue search tools answer only the first part.

Disco and Source Audio have done good work here on the discovery experience and pitching side, which is why they are widely used. Where a rights holder's own build adds value is joining discovery to clearance, because a beautiful search that returns tracks you cannot clear for this use is worse than no search at all.

What a custom build does: make clearability a search facet. Filter by one stop status, by restriction compatibility with the brand category, by territory availability and by whether required approvals come from parties with fast response histories. Audio similarity search is genuinely useful and now cheap to implement: a supervisor uploads a temp track and gets your closest matches, which is exactly how briefs arrive. Stems availability matters too, since a supervisor needing an instrumental at short notice takes the track that has one. All of it converts catalogue depth into an advantage rather than a search problem.

What this costs and how long it takes

In our delivery experience a first release covering catalogue and ownership data with provenance, one stop determination, search with clearability facets, and quote to licence workflow with multi party approval chasing runs $55,000 to $115,000 and ships in 10 to 14 weeks. A full platform adding structured restriction rules, most favoured nation enforcement, licence lifecycle with option and term tracking, cue sheet generation, income allocation to shares, and a client facing pitch and approval portal runs $140,000 to $320,000 phased across 6 to 12 months.

What drives price up in sync specifically: the state of your splits data, which is the single largest variable and is usually worse than the client expects. Whether you administer both composition and master or only one, since a master and publishing operation carries two ownership models. Multi currency and withholding if you licence internationally. Integration with society registrations and statement ingestion, which is valuable and fiddly because formats differ by territory. Audio analysis features such as similarity search and automatic tagging, which are affordable individually and add up. And a client facing portal, which brings access control and secure streaming requirements.

What keeps it down: starting with your top earning catalogue rather than everything, and accepting that splits verification is an ongoing programme running alongside the build rather than a prerequisite for it.

Build versus buy in sync licensing

Buy if you control your catalogue outright, which is the common case for a production music library. If you own both composition and master and clear everything yourself, the clearance problem this category exists to solve simply does not apply to you, and Disco or Source Audio for pitching plus a licence template will serve you well. Buy also if your sync volume is low enough that the manager holds every deal comfortably in her head, because that person is faster than any system until she is overloaded.

Build when two or more of these are true. Your catalogue is co owned, so most deals require third party approvals. Your splits data lives across several sources and nobody fully trusts it. Restrictions exist in contracts but not in any system that can block a quote. You handle enough concurrent deals that the chase is a full time job. Or you have lost deals to speed, which is the one that usually gets the project funded, because it is measurable and it recurs. If your team can name three deals in the last year that went elsewhere while you were waiting on clearances, the arithmetic makes itself.

How to choose a developer for sync licensing software

Ask them to explain the difference between master and publishing rights and what one stop means. It takes thirty seconds and it filters heavily. A developer who has not built in music will treat a track as an item with an owner, and the entire difficulty of this domain is that it has many owners with different powers.

Ask how they would model an approval chain where parties respond independently and one can veto. You want per party state with history, not a single status field marching through a workflow.

Ask what they would do about splits that do not add to one hundred percent. The right answer is that the system surfaces it as a data quality exception with provenance rather than silently normalising, because a quiet correction in ownership data becomes a payment error later.

Ask who owns the code, the catalogue data and the infrastructure accounts, and put it in the contract before kickoff. At Digital Heroes the client owns the repository from the first commit. Ownership and restriction data is the operating asset of a rights holder, and it should never live somewhere you cannot take it from.