An EOS IDS example: should we license our operating records?

How do you run an IDS on whether to license company records?

Run it as a normal IDS: identify the real issue in a sentence or two, discuss until the facts are on the table, then solve with one next step and one owner. For this topic the real issue is rarely "should we do AI?" It is usually rights, sponsorship or archives, and the solution is usually a small, reversible step such as a fit check, not a decision to license.

This guide walks through the three steps with a fully fictional example, then lists the mistakes that make this IDS drag on. It is written for EOS implementers who facilitate Level 10 meetings and want a worked case beyond people and process issues. SourceX is the data licensing platform behind the fit check: the company keeps ownership, licenses records to AI labs and data buyers, and nothing is binding until the company signs.

What do you need before the meeting?

Put the issue on the Issues List with a short title, then bring a few facts. The facilitator does not need legal answers, only enough to keep the discussion honest.

• The issue stated as a question: "Should we explore licensing our operating records?"
• A rough headcount at peak, full-time only (contractors excluded) and the number of years of documented operations.
• A short list of systems that hold records, with any that are archived or about to be retired.
• The name of the person who could authorize a license: owner, CEO, CFO or authorized representative.
• Whether any records belong to clients, partners or patients rather than to the company.

If the team cannot answer the last two, that is itself useful information for the Identify step.

How do you handle each step of the IDS?

Illustrative IDS: a 180-person logistics software company

This scenario is fictional. The company, names and details are invented to show the mechanics.

Identify. The Visionary opens with "We should sell our data to AI companies." After a few questions the Integrator restates the issue: "We don't know whether we have the right to license our support tickets and shipment records, and we don't know who inside the company can say yes."

Discuss. The team lays out the facts:

1. The company has about 180 people today, has operated for 11 years and keeps records in a ticketing tool, a CRM, shared drives, Slack and a finance system, plus an older ticketing system that was archived after an acquisition.
2. The CFO notes that some customer contracts restrict how customer information is used. The head of support adds that shipment records include customer-supplied data.
3. The Visionary is willing to consider a one-time payment but not a long exclusive commitment. The Integrator points out that deals are typically exclusive for AI training for an agreed term, so that preference needs to be tested early.
4. Nobody has checked who can export the archived ticketing system.

Solve. The team does not decide to license. The solution is a To-Do list: the CFO reviews customer contract language by Friday; the IT lead confirms the archived system can still be exported; the Integrator runs the company fit checker and brings the results to the next Level 10. A Rock for the quarter, if the answers are positive, follows the wording in the EOS Rock examples.

What are the common IDS mistakes on this topic?

What can the facilitator say to keep the discussion on track?

Short prompts keep the Discuss step to its time box and stop the room from debating AI in general.

Capture each unknown on the whiteboard as it appears. At the Solve step, turn the biggest unknown into the To-Do, and leave the others for the following week.

When is the right answer to drop the issue?

Some IDS sessions should end with "not now". Drop it when:

• The company has fewer than the baseline of 50+ full-time employees at peak (contractors excluded).
• The records mainly belong to clients or other third parties who have not consented.
• The data is mostly consumer personal information or protected health information without a licensing basis.
• The archives have been deleted and nobody can export anything.
• The owner will not consider an exclusive license.

Write the reason on the Issues List so the team does not relitigate it next quarter. The operations audit checklist is a quick way to re-check the records picture later.

How do you follow up after the IDS?

Review the To-Dos at the next Level 10 under the To-Do list segment. If all three come back positive, convert the work into a Rock. If the sponsor says no, close the issue. Either outcome is a clean result.

What does this mean for a 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, payable only after the buyer pays and SourceX receives its fee. No reward is guaranteed, and the reward is a share of SourceX's fee, never deducted from what the company receives. If you facilitate for clients, keep your facilitation neutral and check your own client agreements before accepting any fee; the management consultant page explains the partner role.

Next step

Choose one client whose leadership team has an open question about records or archives and offer to run this IDS at their next Level 10. If the result is a fit check, register as a partner to introduce them, or use the network opportunity finder to think through which client to approach next. The company baseline is on the who qualifies page.