When an internal AI project raises external licensing questions: an eight-question map that separates what the build settled for the company's own use from what a license would ask again, with the CEO deciding and no partner touching a record

Short answer

An internal AI project raises external licensing questions when building it forces the company to ask who owns its records, what its contracts permit and what an outside AI service may do with what it receives. Every answer the build reached was for internal use; a license would put each question again, for a different use. The referral moment comes when the CEO links the project to the records, not when you first hear about the build. Then ask the CEO once, and never see, review or export a record.

Visual briefFull-size diagram
A Venn diagram marked Illustrative: one circle reads allowed for our own AI tool and holds client project files; the other reads could be licensed for AI training and holds an archived CRM; the overlap holds the company's own support tickets and is labeled a licensing question; outside both circles, records licensed for AI training before are struck through in orange, and a footer reads the CEO decides, partners never see, review or export records.
Illustrative record sets, not a real company. Permission for internal use and permission to license are separate questions.

This page is for portfolio engagement leads who hear of an AI build at a company they know and wonder whether it is a reason to mention SourceX.

What the project settled, and for which use

A company that builds its own AI tool, whether search across its documents, an assistant for support staff or a model tuned on its tickets, makes decisions it may have deferred for years: which systems the tool reads, whether customer contracts allow reuse across teams, what the AI vendor's terms say. Those are genuine governance milestones.

None of them settles licensing, because licensing is a different use. An internal tool keeps records inside the company; a license for AI training gives an outside party rights in a prepared copy. Permission for the first says nothing about the second, and SourceX does not pretend otherwise. Its FAQ describes the step this way: "We ask structured questions about where data came from and what contracts or policies apply. We don't give legal advice."

A build also leaves every published check where it was: 50 or more full-time employees at the company's peak with contractors left out, years of records the company created itself, the rights to license them, a CEO who authorizes the discussion, and relevance to a current program, which SourceX assesses in review. A tidy AI project shows an organized company, not a fitting one.

Two of SourceX's supplier confirmations touch AI work directly. Its how-it-works page lists what a company confirms before a deal: "You have the rights to license the data, personal data was collected lawfully (GDPR/CCPA), it hasn't been licensed for AI training before, and it wasn't created or altered with AI for the sale." An internal project can bear on the last two clauses, and only the company can say how.

A badly timed email, and what the build actually changed

Illustrative. At a board meeting, the CTO of a 210-person freight software company shows the internal support assistant going live next month, built on eight years of the company's tickets. That evening a board member writes to the CTO: "Since the tickets are already cleaned up for the assistant, now is the moment to license them through SourceX." Four things are wrong. The CTO does not decide outside use; the CEO does. What the board member learned in the boardroom may prompt one question to this CEO and goes nowhere else. "Already cleaned up" suggests the records are ready to send and the company fits, and nobody has established either. And a launch month leaves the people who would answer any review with no time. The repair is a short apology, then silence until the CEO raises the subject.

What the build changed, set beside the period before it:

What you look atBefore the projectAfter the project
A list of systemsKnown to whoever runs each systemWritten down inside the company for the build, and kept there
Reuse of records across teamsNever askedAnswered, for internal use only
Outside use for AI trainingNever askedStill never asked; it is a different permission
Outside AI servicesNone connectedA vendor contract whose training terms counsel has read
Records the tool producesNoneDrafts or summaries the company can keep apart
Published checks: peak size, own records, rights, CEOAs they wereUnchanged
Who decides outside useThe CEOThe CEO
Leadership attentionWherever it wasOften absorbed by the launch

The internal-project referral question map

The map takes the questions a build usually raises and asks of each: what did the project answer, what would a license ask instead, and who inside the company answers it.

Question the build raisedWhat the project answeredWhat a license would ask insteadWho in the company answers
1. Which systems hold the records?Which systems the tool readsWhich records the company created itself, and since whenWhoever runs each system, reporting to the CEO
2. Do customer contracts allow reuse?Reuse inside the companyUse by an outside party for AI trainingThe company's counsel, then SourceX's rights review
3. Is personal information in scope?Which staff may see itWhether it should be left out before anything is sharedCounsel and whoever handles privacy
4. What may the AI vendor do with what it receives?The settings and contract for the buildWhether anyone already holds rights to train on the recordsThe IT lead and counsel, reading the vendor contract
5. Did the tool create or rewrite records?Whether its output is good enoughWhether any records were created or altered with AI for a saleThe project lead
6. Was any of it licensed for AI training before?Not askedWhether it ever was, since the company confirms it was notThe CEO
7. Who owns the project, and who decides outside use?The project sponsorThe CEO, and no one elseSettled: the CEO
8. Does the team have room?The project's own roadmapWhether anyone can field outside questions this yearThe CEO

There is no partner column, because it would be empty in every row. You do not ask for the system list, counsel's reading, the vendor terms or a sample, and you do not offer to look. On row 3, SourceX's own FAQ says only this much: "Depending on the data and law, some records may be better excluded entirely."

Row 4 deserves care because vendor defaults differ. OpenAI's business data page, for example, says "We don't train our models on your organization's data by default", and it also describes data a customer explicitly chooses to share, such as feedback, which OpenAI may then use for training (our paraphrase of the page). Whether anything like that touched this company's records is a question of its contracts and settings. Whether it matters for a license is for counsel and SourceX's review, never for a partner's guess.

Reading the map. It scores nothing. It shows whose question each row is, and it marks the one event that changes the referral moment: the CEO, rather than a slide or a vendor announcement, saying that the build raised a question about outside use.

The project's owner is not the decider

AI builds are usually run by a CTO, a head of data or a COO. That person knows which questions came up and may be the CEO's best adviser if outside use is ever weighed. They do not decide it: the CEO authorizes a licensing discussion and signs for the company. Taking the idea to the sponsor first either asks them to decide what is not theirs, or turns them into a messenger carrying a pitch upward.

Capacity is the second check, and it comes from the CEO alone. The people who would answer outside questions are the people finishing the tool. Before anything else, ask yourself whether the launch has settled: staff using the tool, the vendor contract signed, the project team back at its normal work. If not, nothing you say will land well.

A board or advisory seat adds a limit of its own. What you learned there about the project may prompt one question to this company's CEO; it never travels to anyone else, and it never reaches a different company.

Wait for the CEO's own words, something like "counsel says our contracts let us use the tickets internally, and nobody knows about anything else", or "could anyone outside use this?" Then ask, in your own words:

You mentioned the assistant made you look at what the tickets can be used for. Some companies at that point look at licensing records for AI training, which needs a separate permission from internal use. SourceX licenses business records directly from companies and decides in its own review whether a company fits. If you went ahead after an introduction from me, SourceX could pay me a referral reward, separately from anything it pays the company. Would you like to hear more, or shall I leave it?

Log the date, the CEO's words and the step the CEO chose. On a yes, sign the SourceX Channel Partner Agreement before submitting anything; the company applies and answers SourceX itself, and you never receive its inventory. Section 2 of the terms credits one partner per company, decided by SourceX from dated records once the application is verified. Any reward comes from SourceX's side: section 4 says it "is paid separately by SourceX and is never deducted from the supplier's agreed compensation", so the company's payout does not move either way.

Two projects at two companies (Illustrative)

Illustrative: both companies are invented, and neither story predicts what SourceX would decide.

A. The CEO connects the two. A 260-person claims administrator built internal search over eleven years of adjuster notes. Reading client agreements for the build, counsel found they allow internal analytics and are silent on outside licensing. At a scheduled check-in the CEO tells her investor, unprompted, that the project made her wonder whether the notes could be used outside the company. The investor asks the question above. She wants to hear more and applies herself; the investor never sees the index, counsel's notes or a single record, and never says the company fits.

B. Pride, not a question. The CEO of a 140-person engineering firm describes its new drafting assistant with obvious pride; nothing touches outside use or the records behind it. Raising licensing would be steering, not answering. The partner congratulates the team, writes one dated line, "AI drafting tool launched; no licensing question raised", and stops.

The relevance-and-consent calendar sorts events like these before anyone asks; neighboring milestones have their own guides, from a documentation cleanup to a founder's first CFO hire.

What the internal-project signal cannot tell you

  • Fit. The published checks decide fit, and SourceX's screening page says it checks relevance to current programs in review.
  • Rights. Contracts that allow internal reuse may be silent, or restrictive, about outside use; SourceX's FAQ leaves legal questions to the company's counsel.
  • Vendor history. Defaults and opt-ins differ by service, as OpenAI's own page shows; only the company's contracts and settings say what was shared.
  • Records made with AI. A tool that writes or rewrites records can raise a question under the confirmation that data "wasn't created or altered with AI for the sale".
  • Demand. Programs change, and a well-timed question can still end in no.
  • Your own interest. A partner who could be paid sees every build as an opening; disclose the reward and let the CEO set the pace.

Method note. The map and the comparison draw on SourceX's terms in version 2026-10-22.2, since replaced by version 2026-11-04, its screening, FAQ and how-it-works pages, and OpenAI's business data page, all read on 2026-10-27. They assign questions to the people who answer them; they measure nothing. SourceX has published no figures on how often companies with internal AI projects are introduced or accepted, and this page implies none.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

Once the CEO has linked the project to the records and asked for a conversation, register as a partner, set the company against the published screening profile and read the program terms before you introduce anyone; more timing guides are in the guides hub.

Watching for the right moment at a portfolio company is one job; judging SourceX as a possible investment is another, and the SourceX investor overview is where materials for that second job can be requested.

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does an internal AI project make a portfolio company more likely to fit SourceX?

No. SourceX screens on full-time headcount at peak, years of records the company created itself, its rights to license them, a CEO who authorizes the discussion and relevance to a current program. A build shows an organized company, not a fitting one, and it can add questions of its own about vendor terms and records made with AI.

Can I ask the project team which records the tool uses?

Not for SourceX. The system list, counsel's contract reading and the vendor terms belong to the company, and a partner never sees, reviews or exports records. If the CEO wants a conversation, the company answers SourceX's questions itself.

What if the company's AI vendor was allowed to train on the records?

That is for the company's counsel to work out from the vendor contract and, if the company applies, for SourceX's review; a supplier confirms its data has not been licensed for AI training before. A partner should not guess at the answer or ask to read the contract.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/how-it-works
  4. sourcex.si/faq
  5. openai.com/business-data
  6. sourcex.si/investors

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment