"10% of WHAT? Why Revenue Splits Break When Contracts Get Complicated"
"You're getting 10%." Ten percent of what? This is the question that breaks most revenue-sharing arrangements. Not because anyone is dishonest, but because a percentage without a defined base is not a number. It is a shape. And shapes don't pay rent. The Problem Every revenue split you've ever seen looks simple on paper: Artist gets 18%. Producer gets 3 points. Platform takes 5%. But run the math…
Ten percent of what? This is the question that causes most revenue-sharing arrangements to break down. Not due to deceit, but because a percentage without a defined base is not a number; it is an undefined shape. Ambiguity left unchecked leads to wildly different payouts. Contracts should specify the base – net receipts, published price to dealers, or wholesale price in music, gross bookings or net revenue in SaaS.
The base is a contract term, not an afterthought. Most payment-splitting tools apply every percentage to the remaining pool at the time the rule runs, leading to ambiguous bases. Real agreements need multiple bases: gross (before any deductions), net (after processing costs), qualifying (after all deductions), and remaining (current pool after higher-priority rules).
A revenue graph may require all four bases. Change the base and the payout changes dramatically. Using a tool that lets you define the base for each rule and see the arithmetic for every entitlement helps prevent disputes.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
