Should you share data licensing revenue with customers in the records?

Do customers have a claim on data licensing revenue?#

Customers have a claim on data licensing revenue only to the extent their contracts, your privacy notices or applicable law give them one, and that varies by record type. A distributor's notes on how it resolved a late shipment describe its own work; a customer's uploaded drawings or negotiated price list are that customer's information, held under confidentiality terms.

Start with the documents rather than the ethics debate. Look for clauses on data ownership, permitted use, aggregated or de-identified data, confidentiality and return or deletion at the end of the contract. Many B2B agreements let a supplier use service data to run and improve its own operations but say nothing about licensing to third parties, which counsel interprets deal by deal.

Keep payment and permission separate. A revenue share can be a reason for a customer to grant consent, but money paid without the right consent does not close the gap.

Which records change the answer?#

The records that change the answer are the ones whose value comes from the customer rather than from your own operations. Sort record families by whose contribution makes them useful before deciding anything about compensation.

Mixed records are the hard middle. A support thread contains the customer's question and your team's answer; removing the customer's identity usually leaves your team's expertise, which is often what a buyer wants.

Options for sharing, from none to opt-in revenue share#

Companies have five practical options, from no share at all to an opt-in revenue share, and each fits a different mix of rights and relationships. Most companies end up combining two, such as excluding sensitive accounts and giving notice to the rest.

Choose the lightest option your rights support. Heavier options create more consent evidence, but they also create obligations you will have to administer for as long as the license runs.

Public precedents for sharing come mostly from content businesses, where contributors' own work is the product. Getty Images, for example, stated in its Form 10-K for fiscal 2024 that contributors will be compensated for inclusion of their content in AI training sets and, in certain cases, share in revenue from AI tools trained on it. Operating records of your own staff's work are a different case, which is why the record-family sort above comes first.

What a customer revenue share takes to run#

A customer revenue share takes more administration than most founders expect, because every payment needs a formula, a record of who contributed and an accounting treatment. Settle these before offering it to anyone.

Credits often fit B2B relationships better than cash, because they run through existing invoices and reward continued business. Cash payments to customers who have since left raise their own questions about contact details and reporting.

• 1Define the pool: gross or net license proceeds, and which costs come off first.
• 2Define the allocation: by records contributed, by account, or an equal share per participating customer.
• 3Track contributions: keep a manifest that ties each licensed record to a participating account.
• 4Set payment mechanics: cash, credits against invoices or both, and when they are paid.
• 5Plan reporting: what each participating customer receives and how often.
• 6Confirm tax and accounting treatment with your accountants, including whether payments reduce revenue or count as an expense and what information reporting applies.

What customers are likely to ask#

Customers are likely to ask four things before they ask about money: whether they will be identifiable, whether a competitor could benefit, whether they can say no and whether anything about their own service changes. Clear answers to those questions often matter more to a business customer than a small payment.

Prepare a one-page explanation that names the record types, the details removed, the permitted use and how to opt out where that is offered. Route objections from key accounts to the executive who owns the relationship, not to a general inbox.

Mistakes that turn a license into a customer dispute#

The mistakes that turn a license into a customer dispute are usually about sequence and surprise rather than money. A customer who first hears of the license from a third party, or after records have shipped, tends to object regardless of what the contract allows.

Most of these are avoided by one discipline: decide the policy, write the explanation and brief account owners before any customer hears about the license.

• 1Offering payments before counsel has confirmed whether consent is needed.
• 2Announcing a revenue share program before deciding how it will be calculated and paid.
• 3Treating de-identification as the end of the analysis when confidentiality terms still apply.
• 4Including key accounts without telling the executive who owns those relationships.
• 5Promising customers a say over buyer selection that the license terms cannot honor.
• 6Letting sales staff describe the program informally before the written explanation is ready.

Illustrative: an industrial distributor offers credits to a subset#

Illustrative: a fictional industrial distributor runs Epicor for orders and inventory and a shared service inbox for backorders, substitutions and returns. A model developer is interested in how its inside sales team resolves supply exceptions: the original request, the substitute offered, the customer's response and the outcome.

Counsel's review finds that standard customer terms allow use of transaction data for the distributor's own business but are silent on third-party licensing, while a handful of large accounts negotiated confidentiality terms that cover pricing and order history. The distributor removes customer names, contacts, prices and account numbers from all records and excludes the negotiated accounts entirely.

For the remaining accounts, it sends notice with an opt-out and offers service credits to customers who opt in to a deeper package that keeps their industry classification. The package is smaller than the full archive, but every included record has a documented basis, and no customer learns about the license after the fact.

How SourceX handles customer records in a transaction#

SourceX reviews customer contracts and notices during the Rights step of the SourceX five-step transaction, before any preparation starts. The supplier decides whether to offer customers a share; SourceX does not set that policy. Privacy preparation then removes personal and confidential details from every record in the package.

The SourceX Evidence Packet records the licensing rights relied on, any consent or opt-out documentation, the permitted use and the privacy record, so the basis for including each customer's records is written down before release.