How to answer employees who fear their work will train an AI replacement

The honest answer: the records train outside models, not a replacement

Say it plainly. The company is licensing a copy of past records, for example six years of closed support tickets and project threads, to AI labs and data buyers who use them to train and evaluate general-purpose models and agents. The license does not install software in the company, does not create a model the company owns, and SourceX does not train AI models itself.

Then add the part employees will respect: nobody, management included, can promise how AI will change work over the next decade. What management can promise is what it controls, which is the scope of the license, what stays out and how people are protected.

What are employees actually worried about?

"Are you training AI to replace us?" usually bundles several separate worries. Answer each one on its own rather than with a single reassurance.

When each answer is specific, the bundled fear usually shrinks to the one or two concerns that deserve real attention.

Why do AI buyers want old work records at all?

Training an agent to do multi-step work takes examples of multi-step work actually done: a ticket escalated, a fix proposed, a reply sent, an outcome recorded. Those sequences exist inside companies and are thin on the public web. The value lies in the workflow and its result, which is why identifying details can usually be removed without destroying what the buyer needs. If staff want the background, the primer on what AI training data is is written for non-specialists.

What will management do, and what will it not do?

Commit only to what the signed scope supports. Write the two lists down before the announcement.

Management will:

• Decide scope before telling staff, and share the list of systems and years included.
• Put exclusions in writing, such as direct messages, HR and medical files, and social or personal channels.
• Settle the redaction rules with SourceX before any work begins.
• Release nothing until an agreement is executed and the company authorizes delivery.
• Name one person who answers questions, with a stated response time.

Management will not:

• Introduce monitoring or ask anyone to create new records for the license.
• Include material that belongs to clients unless those clients agree.
• Promise outcomes it cannot control, such as how AI will affect a given role.

Expect contact-center and sales teams to ask about call recordings, because their calls are among the most personal records a company holds. Federal law (18 U.S.C. 2511(2)(d)) generally allows a private party to record a call when one party consents, but California Penal Code 632 requires the consent of all parties to a confidential communication. Recordings made without the notices the law required should stay out of scope, and other states have their own rules.

This is general information, not legal, tax or financial advice. Confirm with your own counsel before acting.

What to say: a script for the announcement

Use it at the all-hands, then give managers the same words for team meetings. Fill the braces before you speak, and cut any line that is not true for your company.

For a team lead in a one-to-one, three sentences are enough:

A five-step rollout that keeps trust intact

1. Settle scope and exclusions with SourceX and your counsel before anyone outside leadership hears about the license.
2. Brief managers first, with the script and a short FAQ, so the first question in a team meeting does not catch them cold.
3. Announce to everyone on the same day, in writing and in person; the employee announcement template gives a starting draft.
4. Open a named inbox or channel for questions, and publish answers to the common ones within a week.
5. After signing, confirm in writing what was delivered and what was excluded.

When the fear is justified

Sometimes the worry points at something real that has nothing to do with the license. If the company is planning to automate roles, say so separately and on its own timeline; folding it into a data-license announcement makes both look worse. If layoffs are under way, consider waiting. If most of the value sits in recordings made without proper notices, or in conversations employees reasonably believed were private, narrow the scope or step back.

Sponsors weighing these trade-offs across several companies can use a sponsor's view of reputational risk in portfolio data licensing. If a current or former employee objects after the announcement, the guide on when an employee objects to a data license covers the next steps.

For the adviser who made the introduction

If you introduced the company, your job is to point the owner to these resources, not to speak for the company to its staff. Partners never export, upload or describe confidential records. Advisers preparing a sale can pair this page with how M&A advisors answer seller objections to licensing data.

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, paid only after the buyer pays and SourceX receives its fee. Because the reward comes out of SourceX's fee and never out of the company's proceeds, it changes nothing in what employees are told about the money.

Next step

If you advise owners who will face this question, register as a partner and make the introduction once the owner is ready to talk scope. Owners can apply directly at sourcex.si/apply, and the FAQ covers the questions that come after the announcement.