The mistake is easy to make because so many titles contain the words people use for authority. "Data owner", "head of data", "chief data officer": each sounds like the answer to "who can license this?" None of them is.
A title answers one question, and partners lean on it for three
Three questions sit behind every introduction, and different people hold the answers.
| Question | Who holds the answer | What a title can contribute |
|---|---|---|
| What records exist, in which systems, over how many years? | Whoever works with them: operations leads, system administrators, analysts | A lot: the title points you to the right person to ask |
| Can the company license them? | The company, through its own contracts, tested in SourceX's rights review | Nothing: no contract turns on an employee's title |
| Who agrees to a licensing discussion and signs? | The CEO; once a company is acquired, the acquirer's CEO | Only whether the person holds that role today |
Governance vocabulary makes the slide from the first row to the second feel natural. NIST's security glossary defines an information owner as an official with authority over specified information and responsibility for the controls on how it is generated, collected, processed, shared and disposed of. It lists the information system owner, the person who runs the system itself, as a separate role. Both are internal control assignments. Neither says that the person, or even the company, may grant a license to an outside party.
Privacy law draws the same line from the other side. The European Data Protection Board's guidelines on controllers and processors say, in substance, that a party's role follows what it actually does in a given situation rather than the label it has been given. An org chart label is where a question starts, never where it ends.
Note where each title came from and who connects you
Before a title goes into any note, write three things beside it.
- Source. A profile, a conference bio, the company's leadership page, an email signature or a conversation. Profiles and bios are self-descriptions written for a different audience, often months ago.
- Date seen. Titles change with promotions, reorganizations and acquisitions. A title without a date cannot tell you whether the role still exists.
- Relationship path. Your own client contact, a colleague's contact, someone you met once, or nobody. Only the first two can ask anyone anything on your behalf.
A title pulled from a purchased contact list fails all three: unknown source, unknown date, no path. It is not a sourcing signal for this program. SourceX's screening guidance treats an introduction the decision maker does not know about as usually not a fit, and a stranger has no way to carry the idea to the CEO.
Eight titles decoded: role versus authority (Illustrative)
Illustrative. Generic companies and roles. Each row separates what the title reliably points to from what it cannot settle.
| Title you see | Likely knows | Cannot settle | Ask the contact | Who says yes |
|---|---|---|---|---|
| Chief Data Officer, 400-person insurer | Data catalog, systems, retention settings | Whether reinsurer or client contracts limit reuse | Which record families are the company's own, and since when? | The CEO |
| Claims director named "data owner" in a governance chart | Claims system history, quality rules, access approvals | Licensing rights; the label covers internal controls | How many years of claim notes, in one system or several? | The CEO |
| IT director, 220-person distributor | Where archives sit, volumes, backup and deletion settings | Rights, or any decision to export | Metadata only; never a sample or a login | The CEO |
| General counsel, 600-person logistics group | Which contracts restrict customer and employee data | The decision itself; counsel advises on rights | Would you join a rights review if the CEO opts in? | The CEO |
| CFO, owner-run 150-person manufacturer | ERP history, the cost of keeping old systems | Whether the owner wants the conversation | Would you raise it with the owner? | The owner, as CEO |
| Founder and executive chair who handed over the CEO role | Company history, where early records went | Authority now held by the CEO | Would you introduce me to the CEO? | The current CEO |
| "CEO" on the profile of a brand acquired two years ago | The brand's records and systems | Authority for a company that now sits inside a group | Who runs the group, and do you still speak with them? | The acquirer's CEO |
| Head of client data, 900-person outsourcer | Volumes processed for clients, client systems | Rights to records that belong to clients | Which records does the company create about its own operations? | The CEO, for the company's own records |
Read down the last column: every row ends with a chief executive, and the one row whose title says CEO points to someone else. The second and seventh rows are the easiest to misread, because the words "owner" and "CEO" look like answers. One is a control assignment; the other is a title that outlived the company's independence. SourceX's screening page says it directly: after an acquisition, the acquirer's CEO decides for the company, not its former leadership.
The last row runs the other way: the most knowledge and the weakest rights. Where an outsourcer acts as its clients' processor, the European Data Protection Board describes it as handling personal data on their behalf, and SourceX treats material that belongs to a company's clients as usually not a fit. The outsourcer's own QA scorecards, staffing plans and training material are a different matter, and they are what the question in that row is for. For how ownership is documented link by link, see chain of title for training data.
Strike the inference before the note leaves your desk
Illustrative. A fractional CFO is drafting a note about a 300-person freight broker she has advised for two years. Each line gets a type and a basis before anything is shared.
| Line in the draft note | Type | Basis | Keep it? |
|---|---|---|---|
| The company's VP of data and analytics knows the shipment history | Observed | Leadership page, seen 2026-10-20, and two years of meetings | Keep, with the date |
| The transport management system holds loads back to 2013 | Confirmed by the company | The VP said so on a call on 2026-10-22 | Keep, as the VP's statement |
| Full-time headcount peaked at about 310 in 2023 | Confirmed by the company | The controller's figure, contractors excluded | Keep |
| The VP owns the shipment data | Inferred from the title | Nothing beyond the title | Strike; ownership is a rights review question |
| She can approve a licensing discussion | Inferred from seniority | Nothing | Strike; the CEO decides |
| Shipper contracts allow reuse | Unknown | Never discussed | Mark unknown; do not guess |
Two strikes and one unknown leave a note that is shorter and harder to misread. It names the person who knows the records, repeats only what the company confirmed and leaves rights and authority with the people who hold them. For grading the proof that a sponsor really speaks for the CEO, use the sponsor evidence test.
Public clue, confirmed facts or no path: three contacts side by side
Illustrative. Three generic contacts, invented facts, no outcomes implied.
A public clue and no relationship. A conference bio lists a chief data officer at a 500-person health billing company. You have never spoken. The bio is a self-description, its date is unclear and nobody you know can ask the CEO. Stop here, or look for someone in your own network who genuinely knows the company. A cold message that leans on her title is exactly the move this page argues against.
Confirmed company facts through a client. The COO of a 260-person facilities firm you advise confirms the full-time headcount at its peak and work-order records in the company's own system since 2011, and offers to raise the idea with the CEO. The CEO wants to talk. That is the shape of a sound introduction: the COO knew the records, the CEO said yes, and your partner link lets the company apply itself.
A senior title with the wrong records. The head of client data at a 900-person outsourcer is warm and keen. Nearly everything she manages belongs to the outsourcer's clients. The company's own operating records might still justify a conversation, but only the CEO can choose to open it, and rights review decides what is in scope. If the CEO is not interested, the row closes as no fit for now.
Permission first, then route the yes to the CEO
Once the note is clean, the routing is short.
- Ask your contact whether they will take the idea to the CEO, or would prefer you raise it through a relationship you both share. A no ends it.
- Wait until the CEO wants the conversation. Never describe your contact's title as approval in anything you send.
- Share your partner link so the company applies itself. Discovery stays at metadata: record types, rough counts, years, systems and who administers them. Files, samples and logins stay inside the company.
- Sign the SourceX Channel Partner Agreement before you submit anything.
Credit follows the dated record, not the seniority of your contact. Section 2 of the terms reads: "The first valid introduction of a new company within the 90-day attribution window receives credit when that company submits a verified application." A promising call with a chief data officer that never reaches the CEO produces no application, so on its own it earns nothing. The warm versus authorized contact guide covers the conversation that gets you from a friendly contact to the CEO.
Where titles mislead even careful partners
- Owner-run companies. One person may hold every title on the leadership page. The owner is usually the CEO, and that is the yes you need.
- Split control. In a 50/50 ownership, or under a receiver, assignee or bankruptcy trustee, the CEO alone may not be enough, because someone else may control the assets. The authorized signatory explainer covers how signing authority is documented.
- Stale profiles after roll-ups. Expect the seventh row wherever a group has been buying smaller firms. Check who runs the group now before you write a single line.
- Titles inside the records. Inside a dataset, a job title raises a different issue: combined with a town and a date it can point to one person. SourceX's guide to reviewing job title, town and date together covers that preparation step, which belongs to the company and SourceX, not the partner.
- What this page cannot measure. SourceX has not published how often title-led introductions stall before reaching a CEO. If you want a number, count your own: notes drafted, notes that reached the CEO and CEOs who wanted the conversation.
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 your note names the person who knows the records and a CEO who wants the conversation, register as a partner, test the company against who qualifies or the company fit checker, and read the program terms before you share your link. Other checks on a contact's role before you ask are collected in the guides hub.