# Catalog rollout data introduction email | SourceX

Canonical: https://refer.sourcex.si/resources/catalog-rollout-introduction-email
Last updated: 2026-11-04

Send the email only after the owner opts in, and let it describe record groups the way the rollout taught the company to see them: where each group comes from, which business decision it records, and what contracts permit. Three short paragraphs do the job: what the stewardship work found, what SourceX does with your referral interest stated plainly, and an offer to introduce that asks only for a description. Below is a draft to adapt, followed by notes on every line and what to leave out.

The draft belongs to the [catalog rollout guide](/guides/moment-catalog-rollout-data-governance-advisors). It assumes the [15-minute meeting agenda](/resources/catalog-rollout-meeting-agenda) closed on "introduce now".

## Ready-to-adapt draft

Replace the braces from your meeting card. Under 200 words.

> Subject: {company} record groups after the catalog rollout: a possible introduction
>
> Hi {first_name},
>
> Thanks for {meeting_date}. As part of the catalog work, we walked through {group_count} record groups. For {strongest_group}, covering {years} years, the team can name the source system, the decision each record documents ({decision_type}) and who answers for permitted use. {scope_status}.
>
> You asked whether that kind of history has a use beyond governance. SourceX licenses approved business data directly from companies for AI training and evaluation, and manages the agreement, rights review, data preparation, delivery and payout. For transparency: I am a SourceX referral partner and may receive a reward from SourceX if a qualifying license completes. SourceX funds it separately; it never reduces what {company} would receive, and it has no effect on the catalog program.
>
> If you would like, I will introduce you. SourceX would ask first for a description: which record groups, roughly how large and how old, and who can approve a discussion. No catalog exports, lineage graphs or records. Reply "go ahead" or "not now".
>
> {your_name}

## Annotation, sentence by sentence

| Sentence | Why it is there | Never put in it |
|---|---|---|
| Subject line | Names the company and the program, and frames the email as an option | "Monetize", "opportunity" or any amount |
| "We walked through {group_count} record groups" | Shows the email grows out of governance work the owner commissioned | Asset counts, schema names or classification labels pulled from the catalog |
| "{strongest_group}, covering {years} years" | Leads with one concrete group rather than a vague "lots of data" | A list of every dataset in the estate |
| "Name the source system, the decision each record documents" | Uses the rollout's own three-part language, so the owner recognizes it | A claim that lineage is complete when parts were entered by hand |
| "{scope_status}" | States honestly whether counsel has reviewed permitted use | "Cleared for AI", or any legal conclusion you are not entitled to make |
| "SourceX licenses approved business data..." | One accurate line on what SourceX does | Buyer names, demand claims or price ranges |
| The disclosure | Puts your interest in writing before any introduction | Phrases such as "a small fee may apply" that hide who pays whom |
| "No effect on the catalog program" | Keeps the consulting mandate separate from the referral | Any link between the referral and your fees or scope |
| "SourceX would ask first for a description" | Sets the metadata-only boundary in writing | A request to export, sample or share a screen |
| "Reply go ahead or not now" | Two easy answers, one of them a no | A reminder schedule or a reward figure |

**On the decision sentence.** Catalogs tend to describe the record and the system well and the business judgment poorly. In Microsoft Purview, scans fill the Data Map and stewards curate the Unified Catalog as the business layer, but the decision a record documents is something a person writes down. The W3C PROV model names the missing pieces precisely: an entity is generated by an activity and associated with an agent. If you can name the activity (say, a disposition decision) and the agent (an inspector, an adjuster), put it in the email. If you cannot, leave the sentence out rather than guess. The [data lineage vs data provenance comparison](/compare/data-lineage-vs-data-provenance) explains the difference.

**On the disclosure.** The FTC's Endorsement Guides ask for clear and conspicuous disclosure of a connection between an endorser and a seller that the audience would not expect and that could affect how much weight they give the recommendation. Whether those guides govern a private email is a question for your advisers; a plain sentence removes doubt, and the owner's counsel will expect it.

## Choosing the scope sentence

The `{scope_status}` placeholder carries most of the risk. Pick the line that matches what counsel actually said.

| What counsel said | Sentence to use |
|---|---|
| Reviewed customer terms and recorded reuse limits | "Counsel has reviewed the customer terms for this group and recorded the reuse limits." |
| Reviewing, with a date | "Counsel is reviewing permitted use and expects to finish by {date}." |
| Not yet asked | "Permitted use has not been reviewed yet; {counsel_name} would own that question." |
| Some groups excluded by policy | "HR and payroll records are excluded by policy and are not part of this." |

Never write that the records "can be licensed". That conclusion belongs to the company, its counsel and then SourceX's own rights review.

## What stays out of every version

- **Catalog artifacts.** Exports, screenshots, lineage diagrams, glossary extracts and sensitivity labels all reveal more than a description should.
- **Records or samples.** Not one row, even anonymized.
- **Names from inside the data.** Customers, employees, approvers.
- **The reward as a forecast.** A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. The reward rate is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout. There is no cap per referred company. Illustrative only: a $250,000 payout to the company would mean a $62,500 reward. That number is for your own understanding, not the owner's inbox.
- **A copy to SourceX** before the owner replies.

## Before sending: fit, authority and attribution

Fit: 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. 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.

Authority: the email goes to the owner or an executive who can open a licensing discussion. A steward describes; an owner decides. What remains unknown until SourceX reviews an application: whether current dataset demand fits these groups, the rights review outcome, preparation work and any offer.

Sign the Channel Partner Agreement before submitting. The first valid introduction within the 90-day window is credited when the company submits a verified application, with one partner per company. If milestones are still open, finish the [archive context checklist](/resources/catalog-rollout-archive-context-checklist) first. The [introduction email builder](/tools/introduction-email-builder) and the [introduction email worksheet](/resources/a-reusable-worksheet-for-introduction-email-preparation) help collect placeholders, and [licensing customer support data](/resources/license-customer-support-data-for-ai) shows how one record type is assessed.

## 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.

When the owner replies "go ahead", [register as a partner](/register), confirm the company on [who qualifies](/who-qualifies) and check the [program terms](/terms) so your disclosure matches them.

## Sources

- https://learn.microsoft.com/en-us/purview/unified-catalog
- https://www.w3.org/TR/prov-o/
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.5
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/rewards
