What should a data-sourcing referral agreement protect?

A data-sourcing referral agreement should define the introduction, authority to make it, permitted follow-up, attribution window, overlap rules, payment trigger and records needed to verify that trigger. “We will share leads and split revenue” leaves too much unresolved for either side to rely on.

This is a commercial checklist, not a contract form or legal opinion. Referral, agency, employment, data-protection and fee rules vary by jurisdiction and by the parties' actual conduct. Get qualified advice before signing, especially if one party will negotiate, make representations, receive confidential information or act for the other.

What counts as an accepted data-owner introduction?

Specify what must be delivered and accepted. Is it a named company, a named decision-maker, a description of a data category, or a meeting? Does the receiving party need to confirm in writing that the introduction is new and relevant? A record of the date, parties, scope and acceptance helps both sides distinguish a completed referral from a general lead or an old contact.

Before exchanging personal or confidential details, establish authority for the proposed disclosure, check the relevant privacy obligations and obtain any required permission. An introduction can be made at different levels: a non-identifying description, an authorized company name, or a direct contact. The agreement should say which level is allowed and who approves it. A referral partner's confidence that an executive is “interested” does not itself authorize disclosure or establish control of the data.

What may the referrer do or promise?

Record whether the referrer only identifies a potential source, arranges an introduction, or continues to help with qualification and communication. State who may describe the service, request information, discuss terms and make commitments. If the referrer is not authorized to negotiate or speak on behalf of the company, say so plainly.

Write down what the referral partner may do, what it may disclose, who approves each introduction and what makes a payment due. A document called a referral agreement should not be assumed to authorize negotiation, representation or data transfer. Compare the stated role with the parties' actual conduct and keep any wider mandate separate.

How should existing contacts and duplicate referrals be handled?

The company may already know the receiving party, another partner may have introduced it, or an existing discussion may concern a different business unit or dataset. Decide how to check for overlap before sharing names. Use a narrow, confidential process if needed, such as asking whether an introduction is already active without disclosing additional details.

Define what happens when there is a match. Possible approaches include no referral fee, a reduced fee for a documented contribution, or a written exception for a separate scope. These are negotiation options, not universal rules. Avoid broad claims over every future relationship with a company when the work concerned one specific introduction.

Which opportunity and period does attribution cover?

If attribution continues after an introduction, define the period, what activity qualifies, and which opportunity it covers. A time window alone does not answer whether a later, unrelated data category or buyer counts. Nor does a tracked-link visit prove that a referral caused a transaction. Keep evidence of actual introduction and agreed follow-up, and allow the parties to correct errors.

When is a referral fee earned and how is it checked?

State whether compensation is a fixed amount or a percentage, what the percentage applies to, when it accrues, and when it is paid. If it depends on money received, identify which receipt, currency conversion, refunds, taxes, deductions and timing count. If it depends on a signed agreement, define whether signature alone triggers payment or whether another event is required. A proposed fee is not earned cash; accounting should follow the contract and actual receipts.

Include a reporting mechanism that is proportionate to the agreement. For example, the parties might exchange a periodic statement showing the covered transaction, amount received, calculations and any adjustment, with a defined process to ask questions. An audit right, if included, needs scope, confidentiality safeguards, frequency and cost allocation.

Address confidential information and exit

Limit use of company information to the agreed purpose. Identify who may see it, what security and retention rules apply, how unauthorized disclosure is reported, and what must be returned or deleted when discussions end. Do not assume that an NDA grants authority to disclose the company's information or licenses it for onward use.

Set termination rights and clarify which obligations survive, such as confidentiality, payment already accrued, record retention and dispute handling. Define governing law and dispute process with counsel. An agreement should also address conflicts: whether either party may work with competing sources or buyers, and how those situations are disclosed and managed.

A compact pre-signing checklist

Before signing, both sides should be able to answer these questions:

• What exactly is an accepted referral, and how is it recorded?
• What authority does the referrer have, and what may not be promised?
• How are existing contacts and competing introductions checked?
• Which opportunity is attributed, and for how long?
• What is the fee base, trigger, payment timing and adjustment process?
• What information can be shared, with whose permission, and for what purpose?
• What records, reporting, confidentiality and audit provisions apply?
• What ends at termination, and what obligations continue?

A short agreement can still answer each point. The aim is not to burden a simple introduction with unnecessary process. It is to prevent the parties from discovering after a valuable discussion that they meant different things by “lead,” “exclusive,” “revenue” or “payment.”

Where Avelence fits

Avelence provides commercial advisory, buyer-market research, dataset positioning, licensing strategy and introductions. Any partner role, fee arrangement or authority to communicate for a company requires its own agreed scope. Written authority to lead discussions, work alongside the owner or identify opportunities does not automatically authorize company-name disclosure, data access or a particular recipient handoff.

For a prospective partner, the useful first step is to document the proposed role and the safeguards above. No introduction should be treated as permission to access or license company data.

For the role decision before those terms are drafted, see referral or sourcing partnership. A single handoff and ongoing qualification work should not inherit the same responsibilities by accident.