AI strategy workshop agenda and questions on proprietary data

An AI strategy offsite agenda should include a 45-minute data assets segment after the use-case discussion. Facilitators ask about long-running systems, who created the records, who can authorize a license and who can run an export, then record internal use, licensing or both for each record set.

When to use this agenda

Use it when you run an AI strategy workshop or leadership offsite and the agenda is heavy on use cases and tools but silent on the company's own records. It adds one 45-minute data assets segment and a facilitator question bank. The segment surfaces which records exist, who holds the rights and who can decide, without anyone sharing a single confidential file in the room.

Management consultants are well placed to run it because you already sit with the CEO, CFO and heads of operations in one room, which is the combination a data licensing decision needs.

The half-day agenda with a data assets segment

TimeSegmentOutput
0:00-0:30Where AI already touches the businessList of current tools and owners
0:30-1:15Priority use casesRanked shortlist with a named owner each
1:15-1:30Break
1:30-2:15Data assets: what do we hold and who decides?Systems list, rights flags, decision owner
2:15-2:45Internal use, licensing, or bothOne of three positions per record set
2:45-3:15Risks, policies and vendor termsOpen questions for counsel and IT
3:15-3:30Actions and ownersDated next steps

Place the data segment after use cases, not before. By then the room knows which AI projects need internal records, so the question "who else might value those records?" lands naturally.

Facilitator question bank for the data assets segment

Ask these in order. They are built to produce answers a participant can give from memory, with no screen share and no documents.

Records

  • Which systems has the company used for more than five years, including ones we no longer log into?
  • Where do decisions get recorded: email, Slack or Teams, a CRM, tickets, a wiki?
  • Which of those records show an outcome, such as won or lost, resolved or escalated, approved or refused?
  • Has any system been retired, migrated or cancelled in the last three years, and was an export kept?

Rights

  • Did our own people create these records, or were they created for clients under their contracts?
  • Do client agreements, employee notices and privacy policies say anything about reuse?
  • Is any of it mainly consumer personal data or health information?
  • Has any of it already been licensed to a vendor or data buyer for AI training?

Decision owner

  • Who is authorized to grant a license: the owner, CEO, CFO or another authorized representative?
  • Who can actually run a full export, and how long would it take?
  • Would the owner consider an exclusive license for an agreed term in return for a one-time payment?

How to capture the answers

Use a three-column grid on the flipchart or shared board and fill it live.

Record setPositionNext action
Support tickets, 6 years, closed reasons keptBoth: internal tuning and a license reviewCFO to ask the help desk admin to confirm a full export
Old CRM, archived at migrationLicensing review onlyIT lead to locate the archive
Client project filesInternal use onlyCounsel to confirm client consent

Those rows are Illustrative and fictional; replace them with the room's own. The three positions are internal use, licensing, or both. If the answer is "both", record that the license scope and any vendor terms need to be reconciled before anything is signed. The guide on what happens to a ticket archive when support moves to an AI agent shows how those two uses differ.

A script for the bridge to a referral

When two or three record sets land in "licensing review", the facilitator can close the segment in one breath.

The introduction email builder helps you draft the follow-up once the sponsor agrees. For the demand side, the page on the race for proprietary training data gives you background reading to circulate beforehand.

How to adapt the agenda

SettingChange
Sponsor-backed companyInvite the operating partner for the data segment; the fund's exit story may shape timing
Company preparing for a saleBring in the M&A advisor; see the referral opportunities for M&A advisors
Company that has shrunkAsk about records from the larger years; see whether a downsized company still qualifies
Company with EOS rhythmAdd the item to the Issues List; see EOS annual planning
Company closing an officePair with the office closure checklist

What never goes in the room

Do not ask participants to open, paste, screenshot or describe confidential records. Partners and consultants make introductions and capture basic fit information only: size, years of operation, which systems exist, and who the sponsor is. Do not promise a price, a buyer or a timeline, and never quote a reward in the invitation or the deck. The program facts are on the rewards page.

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. Check your firm's own policies on referral fees and client disclosure before you register.

Next step

Add the data assets segment to your next workshop and bring the grid. If a company comes out with a record set in "licensing review", register as a partner and introduce the sponsor, or have the company apply at sourcex.si/apply. To check fit beforehand, send the sponsor to the who qualifies page.

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

Common questions

How long should the data assets segment be?

Plan 45 minutes for the questions and 30 minutes for the internal-versus-licensing discussion. If time is short, run only the records and decision-owner questions; those two are enough to decide whether a company is worth a follow-up screen with the sponsor.

Who needs to be in the room for the data segment?

The CEO or owner, the CFO, and whoever runs IT or operations systems. Add counsel if client contracts are in question. The point is to have a person who can authorize a license and a person who can run an export present together.

Can we run this segment remotely?

Yes. Use a shared board with the three-column grid and keep documents out of the call. Participants answer from memory, which is why the questions ask about systems, years and outcomes, not about file contents.

What if the room says licensing is not for them?

Record the position and the reason, such as client rights or a vendor clause, and move on. A no today is useful: it can change after a migration, a leadership change or a sale process, and the notes make the question easy to revisit.

Does licensing records conflict with building our own AI agents?

Not necessarily. Internal use and a license are separate grants. Record 'both' when the room wants both, then have counsel and the relevant vendors confirm the scope and any exclusivity before a license is signed.

Free resources

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