EOS Integrator responsibilities in a data licensing project

What does the EOS Integrator do in a data licensing project?

In most EOS companies the Integrator is the natural project sponsor: they run the leadership team, resolve cross-functional issues and hold the Accountability Chart together. In a data licensing project that means owning the inventory, coordinating rights review and keeping the timeline moving. The Visionary or owner still decides whether to license and signs if the terms work.

This guide maps SourceX's steps (inventory, rights review, price and terms, buyer review, delivery) to the Integrator seat and says when the Visionary, CFO or another authorized representative has to act. It is written for EOS implementers coaching leadership teams. Data licensing here means the company keeps ownership and licenses operational records to AI labs and data buyers through SourceX; nothing is binding until the company agrees price and terms and signs.

Which steps belong to the Integrator and which to the Visionary?

The pattern is simple: the Integrator runs the work, the Visionary or authorized sponsor owns the decision and signature. If the Visionary has stepped back and the CEO or CFO holds signing authority, name that person in the first meeting.

What exactly does the Integrator own day to day?

The Integrator's role is to make the project boring. Concretely:

1. Name the sponsor and the steward. The sponsor is the owner, CEO, CFO or authorized representative who can say yes. The steward is the person who knows where records live. Put both on the project plan.
2. Hold the inventory. The inventory lists each system, years of history, what can be exported and who can export it. It is metadata only. A Rock is a sensible container; see EOS Rock examples.
3. Run the weekly cadence. Add the project to the Level 10 Issues List or To-Do list; do not create a parallel meeting.
4. Guard the boundary. Staff do not export, upload or describe confidential records until the company has agreed terms and de-identification rules.
5. Escalate rights questions. Anything involving client data, trade secrets or personal information goes to counsel. The guide on trade secrets in AI training data licenses lists what attorneys tend to flag.

When must the Visionary or owner step in?

The Integrator should not carry these alone:

• Exclusivity. Deals are typically exclusive for AI training for an agreed term. If the owner will not consider an exclusive license, that is a stop sign.
• Price and terms. The company receives one all-in price, SourceX's fee included, with no separate charges. The owner or authorized representative approves it.
• Signature. Only an authorized representative signs; an Integrator without signing authority cannot commit the company.
• Risk appetite on rights. If counsel flags a client-contract limit, the owner decides whether to carve those records out or stop.
• Sale or financing events. If the company is preparing to be sold or refinanced, the owner and advisors decide timing so a license fits the transaction.

What does the Integrator need from IT and the CIO?

The Integrator rarely knows every system, so a good first meeting includes the IT lead. Ask three questions per system: how many years does it hold, can someone still export it, and is it archived or about to be retired. For help framing technical conversations, see CIO peer groups and discussing data licensing with IT leaders.

What goes wrong when the Integrator seat is misused?

What should the Integrator say in the first sponsor meeting?

Keep it to the facts the sponsor needs to decide whether to continue, and ask for the decisions only the sponsor can make.

Then agree a date for the first checkpoint. A realistic first checkpoint is the inventory draft, not a price. Price follows the inventory and buyer review, and the company approves it before anything goes further.

Which companies fit this approach?

It suits EOS companies that meet the baseline: US-based, 50+ full-time employees at peak (contractors excluded), several years of documented operations, rights to license the data and an authorized sponsor. Records spread across email, Slack or Teams, CRM, finance, support, engineering and operations, with long histories or archived systems, are the strongest. The who qualifies page has the full list, and the company fit checker gives a preliminary, non-binding screen.

How do partner rewards work for implementers?

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 becomes payable only after the buyer pays and SourceX receives its fee; a lead, meeting or signed agreement alone does not trigger payment, and no reward is guaranteed. It is a share of SourceX's fee and never reduces what the company receives. Management consultants and implementers should disclose any referral arrangement to clients and check their own engagement terms; the management consultant page explains the adviser role.

Next step

Ask the Integrator at one client to draft the sponsor and steward names this week. Then register as a partner and use the network opportunity finder to plan which other EOS companies to approach.