Employee announcement and FAQ template for a data license

This template gives a company a fill-in employee announcement and a ten-question FAQ for licensing historical records to AI developers. It states what is and is not included, how identifiers are handled, how to raise concerns and request exclusion, and avoids promises the company cannot keep. Have counsel review it before sending.

When to use this template

Use it when a company has decided to explore or sign a license of historical business records with AI labs and data buyers, and wants staff to hear it from leadership first. Send it before any scoping work reaches employee mailboxes, chat channels or shared drives, and before outside coverage can reach your people ahead of you.

This is a starting draft, not legal advice. Employment and privacy rules vary by state, so have your counsel or HR adviser review it before it goes out. The guide to common concerns about licensing company data lists the questions staff tend to raise.

The announcement

Replace the {placeholders}. Keep the voice plain and keep every sentence something the company can stand behind.

The employee FAQ (ten questions)

Paste these under the announcement or on your intranet. Edit each answer to match your actual scope and terms.

How to personalize it

Placeholder	What to fill in	What to avoid
{systems_in_scope}	Real systems and record types	Vague words like "all data"
{start_year} and {end_year}	The actual date window	Years you are unsure about
{exclusions}	Your real exclusions, including small teams	Promises you have not decided
{one honest reason}	The true business reason	Reasons you would not say aloud
{next_step_and_date}	A concrete next event	A date you may miss
Question 8	The decision actually taken	Hinting at a payout no one approved

If the company is reducing headcount, read whether licensing during layoffs is insensitive and consider whether the announcement should wait or be paired with other communication. The page on whether to wait before licensing covers timing in more depth.

Follow-up timing

Day 0: send the announcement from the CEO or owner, not from a no-reply address.
Day 1-2: hold a short live session or leave a staff-channel thread for questions.
End of the comment window: summarize what was asked, what changed and what remains open.
Before delivery: confirm exclusions were applied and tell staff who asked.
If a former employee writes in: follow the steps in how to handle a former employee complaint.

What never to include

Confidential records, extracts or screenshots from the data itself.
The name of a buyer who has not authorized disclosure.
Dollar figures, price or any reward amount.
Promises that no one can ever be identified or that the company will never license again.
Statements about legal rights you have not cleared with counsel.

What this means for referral partners

Partners never write or send this announcement and never see the records. If you introduced the company, you can point the owner to this template. Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. The reward is paid only after the buyer pays and SourceX receives its fee; an introduction, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. The referral earnings calculator shows how the formula works, and the FAQ answers program questions. Sponsors planning for several holdings can also read portfolio data licensing and reputational risk.

Next step

If you know a US company with 50+ full-time employees at peak (contractors excluded) that is ready to explore a license, register as a partner and make the introduction. Owners can apply directly at sourcex.si/apply.

Step 1Share your linkSend your personal link to a company you know.
Step 2Company appliesThe company applies itself at /apply.
Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Should we announce a data license before or after signing?

Many companies announce before delivery, once the scope is clear enough to describe honestly and while exclusion requests can still be handled. Announcing after delivery leaves no room to act on objections. Your counsel can advise on timing for your state and facts.

Can we name the buyer in the announcement?

Only if the buyer has agreed and the contract allows it. During a process, the safer wording is the buyer type, such as AI developers and data buyers, with a promise to share more once terms are signed.

Do we have to offer employees a share of proceeds?

That is a company decision, not a program requirement. Whatever you decide, state it plainly in the FAQ and do not hint at a payment that has not been approved.

Who should send the announcement?

The CEO, owner or another visible executive, from a named account rather than a no-reply address. Staff read the sender as a signal of how seriously the company takes questions.

Is this template legal advice?

No. It is a drafting starting point. Notice and consent rules for employee communications and data use vary by state and contract, so have counsel or an HR adviser review the final text before it goes out.

Free resources

MCP ROI calculator — Estimate hours saved, implied savings and first-year ROI from MCP.
Business exit readiness assessment — A preliminary exit readiness score and checklist for advisors.
SDE vs EBITDA calculator — Seller's discretionary earnings next to market-rate EBITDA.
All free tools · MCP resource center

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment