Who to involve first in a data licensing decision, including HR
Tell the people who must decide first: the owners, the board where there is one, and the authorized signer. Bring in counsel and IT next, HR before scope is final, then managers, and staff once scope and exclusions are clear. A short RACI table keeps the order from drifting.
What is the right order?
Start with the people who can say yes or no, then the people who can say "that is not allowed", then the people who run the work, and finally everyone else. Reversing that order is how a promising idea turns into an internal rumor before anyone has decided anything.
The sequence below suits a company with 50+ full-time employees at peak (contractors excluded) that is considering a license of its operational records. Adapt the names to your structure.
Step-by-step sequence
- Authorized sponsor and co-owners. The owner, CEO, CFO or authorized representative decides whether to explore at all. If there are several owners or a board, settle approval rights before telling anyone else.
- Counsel. Ask whether contracts, privacy notices, open disputes or lender covenants restrict a license. This costs little and saves the most.
- IT lead. Learn which systems exist, how far back they go and who can export from them. The IT lead also tells you what is technically impossible.
- HR lead. HR shapes exclusions for employee communications, advises on notices and knows which channels contain sensitive personnel material. Involve HR before scope is final, not after.
- Finance lead. Check the effect on lender terms, tax treatment and revenue recognition with your own accountants.
- Department heads. Tell them what is in and out of scope, who to send questions to, and what changes for their teams.
- All staff. Communicate only when scope, exclusions and the decision process are clear. Say what is licensed, what is excluded and where to ask questions.
Who does what? A simple RACI
R is responsible for doing it, A is accountable for the decision, C is consulted before it, and I is informed after it.
| Decision or task | Owner or sponsor | Counsel | IT lead | HR | Finance | Managers | Staff |
|---|---|---|---|---|---|---|---|
| Decide to explore | A | C | I | I | C | ||
| Confirm rights to license | A | R | C | ||||
| Systems inventory | A | I | R | C | |||
| Exclusions for employee communications | A | C | C | R | I | ||
| Agree redaction rules | A | R | C | C | |||
| Sign agreement | A | C | C | I | |||
| Staff communication | A | C | R | R | I | ||
| Export and handover | A | C | R | I |
Why does HR come in before the scope is final?
Employee messages, performance notes and complaints sit in the same systems as business records. HR knows where they are, what notices employees received and how employees will react. Rules about employee monitoring, recording and notice differ by state, so ask counsel what applies to your company.
HR also helps with tone. A line such as "we are exploring licensing certain business process records; personal and HR channels are excluded; nothing is final" lands better than silence followed by a surprise.
What to say at each stage
| Audience | What to say | What not to say |
|---|---|---|
| Co-owners or board | Option, scope, approval rights, how it is reversible before signing | A price or a date |
| Counsel | Systems, record types, contracts you suspect matter | That the decision is made |
| IT lead | Inventory only; no copying yet | Promises about timelines |
| HR lead | Draft exclusions; ask which channels are sensitive | Reading content aloud |
| Managers | Scope, exclusions, who answers questions | Anything about employee monitoring |
| Staff | What is licensed, what is excluded, and how to ask | Estimates of what the company will earn |
What does the first conversation sound like?
Keep the first message short. Avoid asking the whole leadership team to react in a group email.
Common sequencing mistakes
| Mistake | Why it hurts | Fix |
|---|---|---|
| Telling staff before counsel has reviewed contracts | You may have to retract scope | Counsel first |
| Asking IT to start exporting during the first meeting | Copies spread before rules exist | Inventory only until rules are agreed |
| Skipping HR | Sensitive channels slip into scope | HR before scope is final |
| One manager hearing it from a rumor | Distrust grows | Brief managers together |
| Holding a staff Q&A with no written scope | Answers drift | Share a short written scope note |
For the redaction side of the conversation, see when redaction rules are agreed. The stakeholder objection map lists what each group tends to ask, and the delivery manifest template records what was handed over once the work is done.
What about outside parties?
Lenders, major customers and investors may need to hear before or after. Whether they must be told depends on your contracts, so ask counsel. A sponsor's concerns about reputation are covered in the portfolio reputational risk guide, and the buyer side of document requests is explained in whether licensed data can be subpoenaed. Understanding what first-party data means in AI licensing helps explain to staff why the company's own records are the point.
What does a realistic timeline look like?
The calendar below is a planning aid, not a program commitment. Timing depends on how quickly counsel and the owners respond.
| Week | Who is told | Output |
|---|---|---|
| 1 | Owners or board, authorized signer | Decision to explore, approval rights written down |
| 1-2 | Counsel | List of contract and notice constraints |
| 2 | IT lead | Systems list with age and export owners |
| 2-3 | HR lead | Draft exclusions and a staff note |
| 3 | Finance lead and outside accountants | Questions on tax and lender terms |
| 4 | Department heads | Scope note, escalation contact |
| 4-5 | All staff | Short announcement and Q&A channel |
Example: a 90-person distribution company
Illustrative and fictional. The CEO of a 90-person distributor is curious about licensing years of order and support records. She first asks the company's outside counsel whether any customer contract restricts new uses. She then meets the IT manager to list systems, and the HR director to flag the chat tool that employees use for personal conversation. Only after the HR director drafts an exclusion for that tool does she brief the department heads. The staff note goes out last, with the scope in two sentences and a contact for questions.
Nothing is final at any point in the example. The CEO signs only if the terms work.
When not to start the conversation
Wait if ownership is contested, if a sale process or financing is active and advisers have not been consulted, or if no one at the company can run an export. Records that belong to someone else, such as an outsourcer's clients, need those clients' consent before anything moves forward.
Next step
If you advise an owner who is ready to take the first step, register as a partner and make the introduction. The referral FAQ explains how the process runs, and partners never handle the company's records.
- 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 the board hear about it before the management team?
If the board or co-owners must approve a license, yes: settle approval rights first. Otherwise the authorized sponsor decides who to tell. Either way, avoid letting management hear second-hand before the decision-maker has agreed to explore.
When is it too early to tell employees?
Before scope, exclusions and the approval process are clear. Early notice without those details invites speculation. Tell staff once you can say what is licensed, what is excluded and where to take questions.
Does HR have a veto?
HR advises rather than decides, but its input should shape exclusions for employee communications and notices. The authorized sponsor remains accountable. If HR or counsel raises a legal concern, treat it as a reason to pause and resolve it.
Do we need to tell customers or lenders?
It depends on your contracts and covenants, which counsel should check before anything is signed. Some agreements require notice or consent for new uses of data. Do not assume silence is allowed.
Who signs the agreement?
An authorized sponsor: the owner, CEO, CFO or another authorized representative. Confirm signing authority with counsel and any co-owners before you start, so the right person is at the table.
Related pages
- When are redaction rules agreed, and can we review a sample first?
- Stakeholder objection map for a data licensing decision
- Delivery manifest template for licensed records
- Portfolio data licensing and reputational risk: a sponsor's guide to doing it cleanly
- Can data licensed to an AI buyer be subpoenaed from the buyer?
- What is first-party data in AI licensing?
Free resources
- Client data licensing eligibility checker — A transparent preliminary screen for one company.
- Enterprise value calculator — Enterprise value from equity value, debt and cash.
- Earnout scenario calculator — Probability-weighted earnout value and its present value.
- 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