# Legal compliance claims in an intro email | SourceX

Canonical: https://refer.sourcex.si/guides/what-not-to-promise-about-legal-compliance-in-an-intro-email
Last updated: 2026-11-05

Promise nothing about legality in an introduction email. Not that licensing is compliant, not that the company holds the rights, not that privacy law is satisfied, not that your firm has reviewed anything, and not that you are allowed to be paid. None of those is yours to confirm at the introduction stage. Run each sentence through one check: keep it if a published SourceX page or the CEO's own words support it, send it to the person who can answer it, or cut it. A disclaimer at the bottom repairs none of them.

This page is for law firm alliance managers, lawyers, compliance consultants and regulated advisers drafting one email that suggests a conversation with SourceX. It is not legal or ethics advice. Your own ethics counsel, employer or professional body answers the questions about you; the company's counsel answers the questions about the company.

## Who is writing, and what the email is for

Name the role before you draft, because the role decides who reviews the draft.

- **A law firm alliance manager** usually is not a lawyer, but works inside a firm whose lawyers carry professional duties. The ABA's comment on Model Rule 5.3, in our paraphrase, expects lawyers to give nonlawyer assistants instruction and supervision on the ethical side of their work, particularly on not disclosing information about a client's representation. In practice the alliance manager's draft goes to a supervising lawyer before it goes anywhere else.
- **A lawyer at the firm** writes under the version of the Model Rules their state adopted.
- **A compliance consultant or regulated adviser** writes under their employer's policy, their regulator's rules and their client contracts.

The proposed activity is narrow: one email to a company's CEO, or to someone who will take it to the CEO, suggesting a conversation with SourceX that the CEO controls. If you will submit the introduction as a partner, you sign the SourceX Channel Partner Agreement first. The email does not advise the company, assess its records or speak for SourceX. Everything below follows from keeping it that small.

## Why legal-sounding sentences creep into introductions

They arrive with good intentions. The CEO's first worry is often "is this allowed?", so the writer answers it. Firm marketing habits reach for reassurance. And a lawyer's name on an email lends weight to whatever it says, which is exactly the problem.

Three published facts set the outer limit before any professional rule applies:

1. **You cannot speak for SourceX.** Section 7.1 of the sample Channel Partner Agreement says the Partner "is not an agent of SourceX and may not commit SourceX to prices, licenses, payouts or other obligations."
2. **You cannot carry the company's material.** Section 4.2 says the agreement "gives Partner no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems."
3. **You cannot predict the outcome.** In our paraphrase of section 4.6, a partner must not tell a company that an estimate, positive interest, a signature or an upload assures it of a purchase or a reward.

For lawyers there is a further standard. Model Rule 7.1 bars false or misleading communications about a lawyer or the lawyer's services, and says: "A communication is false or misleading if it contains a material misrepresentation of fact or law, or omits a fact necessary to make the statement considered as a whole not materially misleading." A line such as "our firm has looked at this and it checks out" is a statement about the firm's services. Whether a given introduction falls within the rule, and which state's version governs, is a question for your firm's ethics counsel.

## The claim review and escalation checklist

Read the draft one sentence at a time and give each a color.

- **Green, keep:** a published SourceX page or the CEO's own words support it, and you can name the page or the conversation.
- **Amber, escalate:** someone can answer it, but not you and not now. Hold the sentence until they have.
- **Red, cut:** nobody can stand behind it at the introduction stage.

| Claim family | What drafts say | Who can stand behind it | Color | What the email says instead |
|---|---|---|---|---|
| Legality of a deal | "Licensing this data is fully compliant." | Nobody yet; the company and its counsel, after SourceX's review | Red | Nothing about legality |
| Rights to the records | "You own these records, so you're clear to license them." | The company with its counsel; SourceX runs a rights check in its process | Red | "SourceX's process includes a rights check before any deal." |
| Customer and vendor contracts | "Your customer agreements won't get in the way." | Only someone who has read them on the company's behalf | Red | Nothing; the company's counsel reads its contracts |
| Privacy and consent | "No employee or customer consent is needed." | The company, its counsel and any privacy officer | Red | "SourceX lists what a company must confirm, including that personal data was collected lawfully." |
| SourceX's handling | "SourceX anonymizes everything, so privacy risk disappears." | Only SourceX, in its own published words | Amber | Quote the published sentence and link it, adding nothing |
| Your firm's review | "Our privacy team is comfortable with this." | Your firm, only if an engagement exists and the review happened | Red unless engaged | Nothing; if the firm is engaged, the advice travels inside the engagement |
| Privilege | "Anything you share stays privileged." | Nobody at the introduction stage | Red | "Please don't send me any documents; SourceX's first step is a few questions and no files." |
| Your pay | "My bar rules allow me to accept this." | Your ethics counsel or employer, and only to you | Amber | After they answer: "SourceX may pay me a reward under its program terms." |
| Fit | "You qualify." | SourceX, after its review | Red | "SourceX decides fit after its own review." |
| Footer | "This email is not legal advice." | Your firm's policy | Green as a label | Keep it if required; it fixes no red sentence above it |

The amber row on SourceX's handling deserves care. SourceX's how-it-works page says that once SourceX gives the go-ahead, the data is "extracted, transferred and de-identified through approved processing routes." That sentence, quoted and linked, is safe. "Anonymized," "completely private" or "no risk" are words SourceX has not published, and the [privacy promises guide](/guides/what-not-to-promise-clients-about-data-privacy) explains why absolute privacy wording fails.

Escalation has an order. Questions about the company's legal position go to the company's own counsel, never to you. Questions about your conduct go to your supervising lawyer, ethics counsel or employer. Questions about SourceX's process go to SourceX in writing, and you pass on its answer word for word. If the company already has a rights question you can see, the [counsel handoff for an unfinished rights question](/guides/how-to-refer-a-client-whose-data-rights-need-legal-review) keeps that question with the people who can answer it.

## Settle confidentiality, conflicts and pay before drafting

Run these before the draft exists, not after.

**Confidentiality.** Does any sentence rest on something you learned while acting for this company or for anyone else? If so, it comes out, whatever its color. Keep the email to public facts and what the CEO has told you directly. Matter details, privileged material and client documents never appear in an introduction; the [guide on assessing contract materials without sharing privileged work](/guides/how-to-assess-contract-process-materials-without-sharing-privileged-work) goes further.

**Conflict.** Is your firm advising this company now on anything the introduction touches: its data, its contracts, a dispute, a sale? Does the firm act for anyone whose interests run against the company here? Those questions go through your firm's conflicts process before a word is drafted.

**Compensation.** Has your ethics counsel or employer answered whether you may be paid, on what terms and to whom? The sample agreement names the Partner as "an individual, or entity type and jurisdiction," so a firm can sign as the partner. How a firm's partner account relates to its people's personal accounts is not settled by the published terms; SourceX decides it. On the company's side, section 4 of the terms is plain: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." Any reward is worked out as the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, with the USD 50,000 floor applying once per referred company on its first qualifying transaction, and becomes payable only once the section 5 conditions are met.

Your firm's approval route for the arrangement itself is set out in the [compliance approval guide](/guides/compliance-approval-outside-referral-arrangement).

## Three drafts, three endings (Illustrative)

Illustrative. Each draft, firm and company below is made up, and the endings show routes, not results.

**A referral.** An alliance manager at a 90-lawyer firm meets the CEO of a 310-person claims administrator at a bar association event; the company is not a client. Her draft says the arrangement is "fully compliant" and that "our privacy group is comfortable." Both rows are red. The supervising partner strikes them, adds the quoted SourceX process sentence and a one-line disclosure, and confirms the firm signed the Channel Partner Agreement as an entity. The CEO asks for a call, and the introduction goes in.

**An unpaid introduction.** A compliance consultant whose employer will not approve outside compensation tells the CEO of a 140-person freight broker, a current client, that SourceX exists and how to apply. The email carries no claim of any color because it makes none: a link to SourceX's how-it-works page and a sentence that the company would decide everything with its own counsel. The company applies on its own with no partner named.

**No participation.** A firm represents a 220-person software company in a dispute over a customer data clause. The conflicts partner says no introduction while the matter is open, and none is sent. The file records the date and the reason, without client detail.

## Record the permitted next step and the expert handoff

Keep a short file note for each email you send or decide not to send:

| Field | What goes in it |
|---|---|
| Date and draft version | The version that went out, or "not sent" |
| Sentences cut or changed | The claim family only, never client facts |
| Who cleared it | Supervising lawyer, ethics counsel or employer, by role |
| Disclosure given | The exact sentence the CEO read |
| Handoffs named | The company's counsel for legal questions; SourceX in writing for process questions |
| Next step | Introduction submitted, company applies itself, or no participation |

That note is the record of what you did not say, which is often the part that matters later.

## Where this checklist falls short

- **It is not a legal review.** It sorts sentences; it cannot tell you whether a rule applies to you. Your state's version of the Model Rules, your employer's policy and your regulator decide that.
- **It cannot see a conflict.** Only your firm's conflicts process can.
- **Published pages change.** Re-read any SourceX sentence you quote on the day you send it, and quote the [how-it-works](/how-it-works) page as it then reads.
- **No evidence on readers.** Nobody has published how CEOs react to compliance language in introductions; the color scheme is a review discipline, not a finding.

## 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 every sentence in your draft is green and your own adviser has answered the pay question, [register as a partner](/register), confirm the company's fit facts on [who qualifies](/who-qualifies) and keep the [program terms](/terms) beside the draft as you send it; more professional-boundary guides sit in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://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_7_1_communication_concerning_a_lawyer_s_services/
- https://www.americanbar.org/groups/professional_responsibility/publications/model_rules_of_professional_conduct/rule_5_3_responsibilities_regarding_nonlawyer_assistant/comment_on_rule_5_3/
