CEO peer group meeting topics for 2026, with a ready-to-run AI and company data block

Why AI and company data belongs on the 2026 agenda

A strong CEO peer group topic for 2026 is what a company's internal records are worth to AI developers, because every member has a decision to make about it, even if the decision is not yet. AI is shifting from models that answer questions to agents that carry out tasks, and training those agents takes records of real work: tickets and resolutions, deal histories with outcomes, approvals and project files. That material lives inside companies like the ones around your table.

Two public reference points help frame the discussion. Researchers at Epoch AI estimate the stock of human-generated public text at roughly 300 trillion tokens and project that language models could fully use it between 2026 and 2032 if current trends continue, a forecast with wide uncertainty. And Reddit's February 2024 IPO registration statement disclosed data licensing arrangements signed in January 2024 with an aggregate contract value of $203.0 million over terms of two to three years. That is a multi-year total for a large social platform, not annual revenue and not a benchmark for a mid-sized operating company, but it shows a market exists.

Topics that pair well with it in 2026

The retention topic has its own primer: should companies delete old emails. The rest of this guide is the data-as-an-asset block, ready to run.

What to prepare before the meeting

• Confirm the group's confidentiality norms cover a discussion of systems, contracts and records.
• If you are a referral partner of any provider in this space, say so in the pre-read and again at the meeting.
• Note which members run US companies with 50+ full-time employees at peak (contractors excluded); smaller members still gain from the records discussion, but only larger ones can act on it.
• Send a one-page pre-read covering what gets licensed, what does not, and the who qualifies baseline.
• Ask each member to bring a list of their systems and how far back each goes: names and years only, no data.
• Decide whether to invite an outside speaker, and if a provider presents, label the slot as a vendor presentation.

How to run the 60-minute block

1. The facts (10 minutes). Explain what is licensed (records of real work), how it works (a one-time payment for a license that is typically exclusive for AI training over an agreed term, with ownership kept by the company and nothing binding until it signs) and what is excluded (consumer personal data without a licensing basis, medical records without authorization or de-identification, and anything that belongs to clients).
2. The records walk (15 minutes). Each member names their three oldest systems and the years each covers, and you write them on the board. Strong companies tend to keep records across 10-15+ systems with 5-10+ years of history, so members with deep, connected histories stand out quickly.
3. The rights round (15 minutes). Put three questions to each member: did we create these records or do they belong to our clients; what do our customer contracts say about data use; have employees been told how work records may be used? The guide to customer contract data use restrictions is a good pre-read for this segment.
4. Explore, park or pass (15 minutes). Each member picks one. Explore means the company meets the baseline and the owner wants to learn price and terms. Park means maybe later, for example after a system migration or a contract review. Pass means the records are not theirs to license, the company is below the baseline or the owner will not consider an exclusive license.
5. The opt-in close (5 minutes). Pass round a sign-up sheet. You follow up only with members who tick the box.

Members will ask whether this is legitimate. Point them to how advisors vet an AI data licensing offer, which lists the questions to put to any provider. This is general information, not legal, tax or financial advice; members should confirm rights questions with their own counsel.

Questions that keep the discussion honest

• If a buyer offered a one-time payment for five years of your support tickets, what would you need to know first?
• Who in your company could export ten years of CRM history next month, and how long would it take?
• Which records would you never let leave the building, whatever the price?
• What did your last system migration leave behind?
• Would your biggest customer be surprised to hear you were considering this?

Common mistakes chairs make with this topic

Example (Illustrative)

Illustrative, fictional scenario: a regional group of eleven CEOs runs the block at its March meeting. In the records walk, an MSP founder lists fourteen years of ticket history across two help desks, an engineering firm CEO lists project files going back to 2011, and a staffing company owner realizes most of her records describe her clients' workers.

At the decision point, three members choose explore, four park (two are mid-migration and two want counsel to read customer agreements first) and four pass (two are below the baseline, one is the staffing firm and one runs a consumer brand). The chair sends one opt-in note to the three explore members and calendars a check-in with the park group after their migrations.

The opt-in follow-up note

For the mechanics of the handoff, see how to introduce a US company for an AI data partnership.

If the chair is a referral partner

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. Rewards become payable only after the buyer pays and SourceX receives its fee; a meeting, sign-up or signed agreement alone does not trigger payment, and no reward is guaranteed.

The bigger question for a chair is neutrality. The playbook for CEO peer group chairs covers disclosure and member confidentiality in more detail.

Next step

Add the block to an upcoming agenda and send the pre-read two weeks ahead. Once members opt in, register as a partner to get a referral link you can send them, or share sourcex.si/apply with members who prefer to apply directly.