# When a client contract restricts introductions | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-client-s-contract-restricts-third-party-introductions
Last updated: 2026-11-05

Stop before you mention SourceX, and escalate. A clause in your engagement letter, master services agreement or a policy it incorporates can restrict an introduction that your professional rules alone might allow: naming the client to an outsider, using what the engagement taught you, accepting value from a third party, or approaching the client about something outside your scope. Quote the clause in the escalation brief below, send it to whoever interprets contracts for your firm, and introduce nobody until it returns with one ending: a referral, an unpaid mention or no introduction.

A friendly disclaimer does not cure a contract problem. "No obligation, just an idea" in an email changes nothing you signed, and neither does a reward you plan to decline. The only safe order is clause first, conversation second.

## Your role, the contract and the four acts inside one introduction

An introduction feels like one act. Under a contract it is four, and different clauses reach different ones. Name your role and the agreement that binds you to the client, then test each act separately.

| Act | What you would actually do | Clause families that can reach it |
|---|---|---|
| 1. Mention | Tell the client's CEO that SourceX licenses business records directly from companies | Scope, non-solicitation, rules on offering other services |
| 2. Submit | Send SourceX the company's name, a CEO contact and why it may fit | Confidentiality, non-disclosure of the relationship, use of engagement information |
| 3. Be paid | Receive a reward if the company completes a paid license | Third-party payment, gifts, conflict and kickback clauses |
| 4. Promote | Mention SourceX in a client alert, seminar or newsletter | Publicity and name-use clauses, plus SourceX's own rule on naming partners |

The roles this guide is written for each sign different paper. A law firm alliance manager may find the restriction in a client's outside counsel guidelines attached to the engagement letter. A compliance consultant or fractional executive is more likely to find it in a master services agreement or a supplier code of conduct the contract incorporates by reference. A regulated adviser may face an advisory agreement plus firm policy. Read every document the contract pulls in, not just the one with the signatures.

Splitting the acts often rescues a decision. A contract that bars payments from third parties may leave act 1 untouched, and a confidentiality clause that stops act 2 may say nothing about a CEO who decides to apply on the company's own initiative.

## What SourceX's documents settle, and what they leave to your contract

SourceX's paperwork narrows what you would ever handle, which makes counsel's job easier, but it cannot release you from anything.

- **What travels.** SourceX's [process page](/how-it-works) says the introducer makes the introduction and need not export, upload or describe confidential records. Under section 4.2 of the sample Channel Partner Agreement, a partner has no right to pass on a supplier's records, raw data, inventory or personal information. So act 2 is a company name, a contact and a reason, never a file.
- **Who is bound.** The sample agreement says it "does not bind a contact that is not a party to it" (section 2.4). Your client takes on nothing when you sign it, and you are released from nothing you owe the client.
- **Naming.** Section 4.5 bars either party from publicly identifying the other as a partner without written authorization, which matters for act 4 whatever your client contract says.
- **What the client receives.** Section 4 of the terms (version 2026-10-22.2, since replaced by version 2026-11-04) says: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." SourceX pays any reward from its own share, so the company receives the same amount with or without you. That helps the disclosure conversation; it does not answer a clause that forbids third-party payments outright.

Nothing in the terms or the sample agreement mentions a partner's contracts with its clients. Whether a clause can be waived, by whom and in what form is a question for your firm's counsel, read against the actual text.

## The contract restriction escalation brief

One brief per client, filled in by the person who knows the relationship and handed to the person who reads contracts for the firm (general counsel, an ethics partner or outside counsel). It stays inside the firm. It carries the clause, never client files.

| Field | What goes in it | Why counsel needs it |
|---|---|---|
| 1. Client code | An internal reference, not the client's name in any message that leaves the firm | The brief may circulate before anyone knows whether naming the client is allowed |
| 2. Your role | Outside counsel, consultant, adviser, fractional executive; the engagement's scope in one line | Scope clauses read differently for a narrow project than for a general retainer |
| 3. Governing documents | Each agreement, its date and every policy or guideline it incorporates by reference | Restrictions often sit in the attachment, not the signed pages |
| 4. Clause text | Quoted word for word with its section number, one row per clause | Counsel reads words, not summaries |
| 5. Acts reached | Which of the four acts each clause may touch | A clause that reaches only act 3 still allows an unpaid route |
| 6. Origin of the idea | The CEO raised it; you saw public facts; or you inferred it from engagement work | Use restrictions turn on where your knowledge came from |
| 7. What SourceX would receive | Company name, CEO contact, a sentence on why it may fit; nothing else | Shows counsel the disclosure is small and defined |
| 8. Money | The default reward: the greater of $50,000 plus 5% and 15% of what SourceX actually pays the company, with no cap, paid by SourceX and never deducted from the company's payout | Third-party payment clauses need the exact basis |
| 9. Consent route | Who at the client the contract says can consent, and in what form; filled in by counsel | Contract consent and the CEO's licensing decision may sit with different people |
| 10. Ending and conditions | Referral, unpaid mention or no introduction, with any conditions and a review date | Turns the review into an instruction |

Field 9 deserves care. Under the program, the client's CEO alone decides whether the company discusses licensing its records and signs for it. A contract may separately require that some named office at the client consent before you disclose the relationship. Those are two different questions, and the brief keeps both visible so nobody mistakes one yes for the other.

## Three review questions behind every ending

Counsel's reading usually comes down to three questions. Put them in the brief's covering note so the answer addresses each one.

**Secrecy.** Would act 2 disclose the relationship or something learned in it? If the contract or a professional rule calls for the client's consent, ask which standard applies. In the ABA's model terminology, informed consent means agreement after the person has received adequate information about the material risks and the reasonable alternatives, and a consent can be confirmed in writing either by the person or by a prompt written confirmation of an oral consent (our paraphrase of Rule 1.0(e) and (b)). Your own jurisdiction's adopted text governs, and counsel says which applies.

**Divided loyalty.** Would you be advising this client on the same records, contracts or rights that a license would touch? If so, the clause may be the smaller problem; the [client conflict check](/guides/the-client-conflict-check-before-a-data-introduction) covers that run.

**Money.** Does any clause restrict value received from third parties in connection with the engagement? A reward exists only if the company completes a paid license, and section 5 of the terms says "A lead, meeting or signed agreement alone does not earn a payable reward." Counsel decides whether the clause reaches a payment that contingent, and whether declining it would help. On declining, the published terms are silent; SourceX would decide how it is handled, so ask in writing first.

## Three clauses, three endings (Illustrative)

Illustrative. Generic firms, clients and clauses, invented for this page; each ending is that firm's counsel reading its own contract, and none says what any contract or rule allows.

**A compliance consultant and a supplier code of conduct.** The consultant's master services agreement with a 240-person logistics operator incorporates the client's supplier code, which bars accepting anything of value from third parties in connection with the services. The CEO mentioned years of exception records in a steering meeting. Counsel finds act 3 blocked and acts 1 and 2 untouched by that clause. Ending: an unpaid mention. The consultant tells the CEO that SourceX exists, the company applies on its own, and nobody on the consultant's side is credited or paid.

**A law firm and outside counsel guidelines.** The client, a 600-person claims administrator, attaches guidelines to the engagement letter forbidding disclosure of the representation without written consent from its legal department. Its CEO tells the relationship partner she wants to explore licensing. Counsel finds act 2 needs that written consent and sets conditions for act 3 under the firm's ethics review. Ending: a referral, made only after the legal department's written consent is on file and the CEO has confirmed she wants the conversation.

**A regulated adviser and a scope clause.** The adviser's agreement with a 150-person distributor limits the engagement to defined services and forbids offering the client other services during the term. Counsel reads act 1 as falling inside that restriction. Ending: no introduction. If the CEO asks directly, the adviser answers only as counsel has approved and points to SourceX's public pages.

## Writing down the ending, the signatory and the credit rule

Whatever the ending, write down one line per item and keep it with the brief:

- **The ending and its conditions**, in counsel's words, with the date.
- **Who tells the CEO what.** For an unpaid mention, the company applies itself. Once it has, the terms treat it as already known to SourceX, so a later introduction from you would be reviewed as a duplicate (section 3).
- **For a referral, who signs.** The sample agreement names the partner as "an individual, or entity type and jurisdiction", so the firm or a person can sign; the published terms do not say how a firm's account relates to its people's own accounts, which SourceX decides. Sign before submitting anything (section 1).
- **The credit rule you are relying on.** Section 2 credits one partner per company, decided from dated records once the company files a verified application inside the 90-day window. A click on your link does not settle credit by itself, so keep your dated written introduction.
- **A review date**, tied to the contract's renewal or the next version of SourceX's terms.

## Where the escalation brief stops

The brief organizes a decision about your contract; it cannot make it. Contracts renew, guidelines get reissued and a clause that permitted an act last year may not this year. Confidentiality promises often outlast the engagement, so a former client can still be covered. Contract law and professional rules differ by jurisdiction, and a disclosure, however clear, may not make a payment permissible; that is counsel's call.

The brief also leaves fit untouched. SourceX looks for companies that reached 50 or more full-time employees at their peak (contractors do not count), that hold years of records they made themselves and the rights to license them, and whose CEO wants to talk. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

A different contract question sits on the company's side: whether its own customer agreements let it license records at all. That belongs to the company's counsel and SourceX's rights review; [customer contract data use restrictions](/guides/customer-contract-data-use-restrictions) and the [DPA checklist](/resources/data-processing-agreement-checklist) map it, and [what first-party data means in AI licensing](/proof/what-is-first-party-data) explains why records the company created itself matter. If your ending is an unpaid mention, consent can still be needed, as [an unpaid introduction can still require client consent](/guides/an-unpaid-introduction-can-still-require-client-consent) explains. More partner decisions are in the [guides library](/guides).

## Next step

> **Refer a company. No cap on rewards.** Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Once counsel's brief comes back with a referral ending, [register as a partner](/register) under the signatory it names, check the company's public facts against [who qualifies](/who-qualifies), and put the current [program terms](/terms) beside the brief so the conditions and the terms are read together.

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://refer.sourcex.si/how-it-works
- https://refer.sourcex.si/who-qualifies
- https://www.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/rule_1_0_terminology/
