# Companies with internal knowledge base data for AI licensing

Canonical: https://refer.sourcex.si/data-types/internal-knowledge-bases
Last updated: 2026-11-05

An internal knowledge base is the collection of articles, how-tos, and answers that a company's staff use to do their jobs.

## What it is
An internal knowledge base is the collection of articles, how-tos and answers that a company's staff use to do their jobs.

## A hypothetical example
*Illustrative:* a US IT services firm has 4,000 internal articles built up over eight years, organized by product and problem type.

## What makes it useful
For AI developers seeking to license data, internal knowledge bases offer:
- Breadth and depth across real-world problems
- Maintenance and evolution over time
- Structured organization such as categories and links

## Rights and sensitivity questions
SourceX settles these questions with the company in its rights check; a partner never opens or evaluates the knowledge base:
- Does any content include client confidential information or credentials?
- Was any content licensed from a third party?

## How to recognize it without exporting it
Ask the CEO (in an owner-run company, usually the owner): *"Where does your team look things up, and roughly how many articles are in there?"*

## Related
- [Which businesses qualify](/who-qualifies)
- [Industries](/industries)


> Rewards are calculated as the greater of $50,000 plus 5% and 15% of the compensation SourceX actually pays the company you refer, with no cap. A lead, meeting or signed agreement alone does not trigger payment. See the [program terms](/terms).

## When a portfolio company centralizes its knowledge base, is that the moment to mention SourceX?

Sometimes, and only as timing. Moving scattered wikis, shared drives and help-center articles into one knowledge base can leave the CEO with spare attention and one person who knows what sits where. It improves nothing SourceX screens on: headcount, rights and who decides stay as they were, and the years of records the company created can stay the same or shrink, never grow. Nor does it give a fund's engagement lead any reason to view, sample or export the knowledge base. Wait until the company says the move has settled, then ask the CEO one question; the company states what it holds, and SourceX reviews it.

The overview above defines the record type. This part is for a VC portfolio engagement lead who hears, in a board update or a portfolio check-in, that a company is consolidating its knowledge. A broader records cleanup is covered in [the documentation cleanup timing guide](/guides/the-referral-moment-after-a-long-documentation-cleanup), and a company feeding its knowledge base into its own AI assistant raises the questions in [the internal AI project guide](/guides/when-an-internal-ai-project-raises-external-licensing-questions).

## What a centralization project is, and what it proves

A centralization project gathers knowledge that grew up in several places, often team wikis, document folders and a support help center, into one platform with one structure. Most run through recognizable phases: deciding what moves, moving it, switching staff over, then retiring the old tools.

Some of these projects have a vendor date behind them. Atlassian says end of life for its impacted Data Center products, Confluence among them, "will take place on March 28, 2029", when subscriptions expire, "making Data Center products and apps read-only." A date like that is a documented reason a company may plan a move. It is not a reason for anyone outside the company to hurry one.

What the project proves is narrow: the company cared enough about its own knowledge to organize it. It does not prove that the knowledge is the company's own, that it runs back many years, or that it suits a current SourceX program. SourceX's glossary notes that a knowledge base is often considered in review alongside the tickets that reference its articles; whether those links survived the move is something the company knows and can state if asked, never something a partner checks.

## The milestone comparison: five phases, one moment to ask

| Phase | What the company is busy with | What you might hear | Your move |
|---|---|---|---|
| Scattered, before any project | Running the business across several tools | Usually nothing | Nothing on this account; any other reason to ask stands on its own |
| Planning and sorting | Deciding what moves, what is archived and what is deleted | A line in a board update | Hold; never offer to help sort spaces |
| Moving and cutover | Migrating pages, fixing links, retraining staff | Complaints about broken search | Hold: the worst moment for a new topic |
| Old tools retired | Read-only archives, contract end dates | A shutdown date | Hold; mention a shutdown date to the CEO once, as a records point, with no mention of SourceX |
| Settled | Normal work in one place | The CEO says the move is behind them | One question to the CEO, naming that change |

Across all five phases, the screening facts stay fixed:

- full-time headcount at peak, 50 or more, with contractors excluded;
- the years of records the company created, which a move can keep or lose but never add to;
- the company's rights: pages that came from a vendor, a client or an acquired business are as borrowed after the move as before;
- an earlier AI-training license of the material, which rules it out;
- earlier contact between SourceX and the company, which SourceX finds itself: section 3 of the terms says "SourceX checks its own records before inviting an introduced company";
- the CEO as the person who decides;
- location, read exactly as SourceX publishes it. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

## Centralization-context referral questions

Five questions, asked only once the company calls the move settled, and only of the CEO. Each can be answered in a sentence, and each has a twin that must never be asked.

| Ask the CEO | What the answer tells you | Never ask instead |
|---|---|---|
| "Is the knowledge base move finished, as far as you are concerned?" | Whether the timing signal is real | "Can you share the migration plan?" |
| "Is anyone still cleaning up after it?" | Whether the team has room for anything new | "Who has admin rights now?" |
| "Would a conversation with SourceX about licensing records the company created be welcome now, later or not at all?" | Permission, in the CEO's words | "Can I see the new space list?" |
| "If later, what would make it a better time?" | A follow-up date the CEO sets | "Could we get a page count for SourceX?" |
| "If you go ahead, is there anyone besides you SourceX should speak with?" | A contact the CEO names, often whoever ran the move | "Shall I call the knowledge manager directly?" |

The right-hand column is not a list of harmless shortcuts. Each item asks for the company's information on SourceX's behalf, which no partner does: SourceX's referral overview says a partner introduces without exporting, uploading or describing confidential records, and its screening page says these questions are answered in conversation, never from files, samples or logins.

## A badly timed ask, and the same company four months later (Illustrative)

Illustrative: a generic fund and company with invented facts; no outcome is implied.

A fund negotiated a group price on a knowledge platform for its portfolio, and its platform team helps companies onboard. One of them, a 240-person IT services firm, is midway through moving three team wikis, a document drive and its help center onto the new platform.

**The bad version.** A platform analyst helping with onboarding sees in the admin console that the firm's spaces already hold thousands of pages. He emails the CEO the same week: "Your new knowledge base looks like a great fit for SourceX, it's huge." That one line uses access granted for onboarding, offers a fit verdict nobody can give, quotes a figure the company never chose to share and arrives during cutover. The repair: an apology to the CEO, the analyst's admin access removed once onboarding ends, and a dated entry in the fund's log that nobody raises the subject until the CEO does.

**The better version.** Four months later the CEO mentions at a portfolio check-in that the move is finally done. The engagement lead asks the third question. The CEO says next quarter, after a product launch. In the new quarter the CEO writes back yes and names the knowledge manager who ran the move. The engagement lead signs the Channel Partner Agreement, introduces the CEO with the yes attached and nothing else, and the firm applies itself. In its application the firm describes its own systems and years of history, and flags pages that arrived with an acquisition; SourceX's rights check decides what is in.

## Who decides, and who still has room

- **The CEO decides.** The knowledge manager who ran the project may be the most useful person to talk to once the CEO says so; that person carries information, not the decision. The board and the fund do not decide either.
- **Capacity is real.** The people who ran the move may be the tiredest in the company. An introduction asks nothing of them until the company applies, and SourceX's process page puts the first step at listing systems and years of history, with no records shared.
- **One credit, one route.** If both the engagement lead and an operating partner know the CEO, agree inside the fund who asks. Credit is decided from dated records, and a link click alone does not decide it (terms, section 2).

## Where the centralization signal misleads

- **Moves lose history.** A migration that carried only current pages may leave the old versions in a read-only archive or nowhere. The company knows; you do not guess.
- **Tidying with AI tools.** sourcex.si has each supplier confirm its data was not created or altered with AI for the sale. A company that rewrote pages with an AI assistant during the move says so in review; a partner never suggests rewriting anything.
- **A move ordered for a sale or a dispute.** Counsel or the deal timetable leads; the company's own CEO decides until any sale closes, and the buyer's CEO once it has.
- **No outcome data.** SourceX has published no figures on knowledge-base introductions after a centralization, and this playbook has not been tested. To test it, log each company's phase when first mentioned, the date of the question and the CEO's answer, and compare answers given in the settled phase with any given earlier.

**Methods note.** The comparison applies SourceX's screening page, program terms (version 2026-10-22.2, since replaced by version 2026-11-04), referral overview, process page and glossary, all read on 27 October 2026, with Atlassian's end-of-life page used only as an example of a dated vendor event.

## 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.

When the CEO has called the move settled and said yes in writing, [register for a partner link](/register), sign before you submit, compare the company once more with [who qualifies](/who-qualifies), and keep the [program terms](/terms) open while you write the introduction; [how referrals work](/how-it-works) covers what follows, and more timing playbooks are in the [guides library](/guides). If the company goes ahead and SourceX later pays it, any reward comes from SourceX's own share and the company's payment is unchanged.

Weighing SourceX itself as an investment is a separate exercise from any introduction; materials for that are requested on the [SourceX investor page](https://sourcex.si/investors).

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.

## Sources

- https://refer.sourcex.si/how-it-works
- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/glossary/knowledge-base
- https://sourcex.si/how-it-works
- https://sourcex.si/investors
- https://www.atlassian.com/licensing/data-center-end-of-life
