Its readers are partners who watch these projects from close by: process consultants, knowledge-base implementers, technical writing agencies, IT partners and accountants.
What a write-down project tells you about the CEO
Companies run documentation projects for ordinary reasons: a founding team nears retirement, new hires take too long to learn the work, a wiki is replacing a decade of shared drives. Whatever the reason, three things become true at once.
- The CEO has put a value on know-how. Someone approved time and money to capture how the company works, so a conversation about what that work is worth to others is no longer strange.
- A named person now holds the map. The project owner, often an operations manager, knowledge manager or head of training, learns which teams know what and which systems hold the history.
- Dates appear. Old drives get archived and legacy wikis switched off. A dated end state is real timing, unlike a quarter-end.
Knowledge capture is not a niche habit of large regulated firms. The catalogue page for ISO 30401, the international standard for knowledge management systems, says it sets requirements and guidelines for establishing, maintaining, reviewing and improving such a system, and that its requirements apply to any organization whatever its type or size (our paraphrase of a search excerpt).
SourceX's own data library puts the material in plain terms: "Business documentation — wikis, reports, manuals, proposals and knowledge bases — captures institutional knowledge in long-form text." Its screening page lists SOPs, internal knowledge bases, project histories, QA records and support workflows the company created itself as the original documentation it looks for.
One distinction keeps the trigger honest. The new pages a project produces are young, while SourceX screens for years of records a company created itself. The history the project draws on, its tickets, jobs, projects and procedures, matters more than the pages. The project points you to the CEO; it is not the asset.
Six reasons a company starts writing things down, and what each does to timing
The purpose behind the project decides whether this is a good week to ask, a good quarter or no time at all.
| Why the project started | What it tells you | Put the question to the CEO? | Hold until |
|---|---|---|---|
| Long-serving people are retiring or leaving | The CEO sees years of know-how at risk | Yes, once the capture plan is agreed | The plan exists; never while a departure is raw or disputed |
| Onboarding and training are being rebuilt | Growth, and a CEO thinking about how work is learned | Yes, after the scope is signed off | Scope sign-off |
| Old material is moving to a new wiki or knowledge base | Shared drives or a legacy wiki may be archived on a date | Yes, naming the date as the company's own fact | The CEO has confirmed the date |
| A customer audit or certification asked for written procedures | An outside party set the scope and the deadline | After the audit, not during it | The audit is over |
| The company is preparing for a sale or investment | The CEO is weighing value; a deal may change who decides | Only if the CEO raises it | The CEO says the process allows it; after closing, the acquirer's CEO decides |
| An incident, regulator finding or dispute forced it | Crisis-driven writing, often with counsel involved | No | Counsel and the CEO have closed the matter |
In the sale row, the target's CEO decides until closing, and a new topic raised mid-process can be unwelcome even when it is allowed.
The documentation owner interview guide
Eight questions for the person running the project, asked only once the CEO has named them or knows you are talking. Every answer concerns the project; none needs a document, a screen share or a login, and no record's contents are ever described.
| # | Question | What the answer tells you | Sounds like "ask the CEO now" | Sounds like "wait" |
|---|---|---|---|---|
| 1 | Who commissioned the project, and does the CEO sponsor it? | Whether the CEO is already thinking about know-how | The CEO kicked it off and reviews progress | Nobody senior is involved yet |
| 2 | What event started it? | Which row of the timing table applies | Two senior technicians retire next year | A regulator's letter last month |
| 3 | What stage is it at: scoping, writing, review or launch? | Whether the team has room for a new topic | Scope signed off, writing under way | Final week before an audit |
| 4 | Which teams and which years of work does it draw on? | Whether long operating history sits behind the pages | Service procedures built from job notes kept since 2011 | Only this year's policies |
| 5 | Who is writing: staff, an outside firm, AI drafting tools? | Authorship, which SourceX's rights review will ask about | Our own supervisors, edited by the project lead | Mostly an agency's templates |
| 6 | What happens to the old material when the project ends? | A dated event, if there is one | The old drive goes read-only in March | Undecided |
| 7 | Has anyone outside approached the company about licensing what it knows? | Earlier contact with SourceX would make it a duplicate | Not that I know of; the CEO would know | We spoke to SourceX last year |
| 8 | Would the CEO want to hear about a licensing conversation, and from whom? | The route, and whether there is one | Raise it with the CEO directly | Leave it alone |
Question 5 matters more than it looks. SourceX's documentation page lists confirming authorship rights in its preparation checklist, and its process page lists, among what a supplier confirms, that the data was not created or altered with AI for the sale and has not been licensed for AI training before. So never suggest that a company write, rewrite or tidy material because a license might follow. The project has its own purpose; the question to the CEO is about what the company already holds.
A stop at question 2, 3 or 8 ends the interview for now, not the relationship: note the answer and the date, and return only when the condition changes. If the CEO says the timing is wrong, take that answer at face value.
Two projects, two timings (Illustrative)
Illustrative. Generic companies, invented facts, no outcomes implied.
A. Ask now. A 180-person heating and cooling service company is documenting its repair procedures because two founding technicians retire next year. The CEO sponsors the project; the operations manager runs it; supervisors write the pages from job notes the company has kept since 2011; the old shared drive becomes read-only in March. The company's IT partner, who knows the CEO well, runs through questions 1 to 8 with the operations manager, then writes to the CEO with one question and a disclosure. The CEO says yes in writing and names the operations manager to describe the systems.
B. Wait. A 240-person freight forwarder is writing down its processes because a prospective acquirer's diligence list asked for them. The project owner answers question 2 openly, and the partner stops there. Until closing, the forwarder's own CEO decides; after closing, the acquirer's CEO does, and the acquirer's group shares one reward cap. The partner notes "revisit after the transaction settles" with the date and sends nothing.
Who owns the project, and who owns the decision
| Person | What they can do here | What they cannot do |
|---|---|---|
| The project owner | Describe the project's purpose, stage, scope and end date; later, if the CEO agrees, help describe systems | Decide whether the company talks to SourceX, or hand over documents |
| An outside writing or implementation firm | Mention SourceX to the CEO, outside the paid scope and with its interest disclosed | Describe anything it read while doing the work |
| The CEO | Decide whether the company has a licensing conversation, and sign for it | Settle the rights questions alone; SourceX's review and the company's contracts decide those |
| SourceX | Review fit, rights and relevance to current programs | Decide for the company, which signs its own agreement |
Before anyone is introduced, check the facts that sit outside the project. Full-time headcount must have peaked at 50 or more, contractors excluded. 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. Name the legal entity that holds the records and confirm whether a parent or acquirer stands above it. And ask the CEO directly whether the company has ever applied to, written to or held an account with SourceX.
For neighboring situations: when the project centers on procedure versions and approvals, the SOP revision history interview is the closer guide; when a records manager has just been hired, use the records-role sponsor handoff; and handover records ahead of a practice acquisition are covered in knowledge handover gaps.
The one question, and the record you keep afterward
Put it to the CEO in your own words, briefly:
I gather you are writing down how the company works, partly because [the reason the project owner gave]. A company called SourceX licenses business records directly from companies for AI training and evaluation. Would you like a conversation with them about the company's own operating history? I should say that SourceX could pay me a referral reward if a license goes ahead. What the company would be paid does not change either way.
That last line rests on section 4 of the terms: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation."
Then write down four things: the date you asked, the CEO's answer in their own words, the next step the CEO authorized and who owns it. If the answer is yes, sign the SourceX Channel Partner Agreement before you submit anything, make the introduction, and let the company apply itself. Credit, if any, follows the dated records: SourceX credits the first valid introduction of a company new to it, once the company files a verified application within the 90-day attribution window; a link click alone decides nothing. If the answer is "after launch", record the launch date as the CEO's condition. If it is no, close the row.
Method note. The timing table, interview and cases apply SourceX's documentation, process and screening pages, the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04) and ISO's catalogue description of ISO 30401, all read on 2026-10-27. They are this page's design. No figures have been published on how often a documentation project leads to an introduction; to build your own, count projects heard of, interviews run, where each stopped and CEOs who asked to be introduced. The guides collection holds the other business-change moments.
When a documentation project points the wrong way
- Pages are not history. A brand-new wiki may hold a year of writing and nothing older. Ask what the project draws on, not how many pages it has.
- Borrowed text. Vendor manuals, franchisor material and agency templates belong to someone else, and records written for clients may belong to those clients. SourceX's rights review settles what is the company's own.
- AI-drafted content. Pages produced with AI tools raise questions the company must answer in review; a partner should never wave them through.
- Fit and demand are decided later. Relevance to SourceX's current data needs, and whether any program wants these records, are assessed only in review.
- The relationship outweighs the referral. Interrupting a project at the wrong moment can cost you the work, and the CEO's answer, including no, ends it.
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 project owner's answers put the timing right and the CEO has asked for the conversation, open a partner account, hold the company up against the screening criteria one last time and keep the program terms beside you as you write the introduction.