The trap is assuming the first person you meet holds all three keys. A dispatcher who has worked somewhere for twenty years can describe every system change since 2006 and still have no say in what happens to a single file.
The person who knows the archive may not control it
Knowing, holding and deciding are separate powers. American civil procedure keeps them apart: Rule 34 of the Federal Rules of Civil Procedure reaches documents and electronically stored information in a party's "possession, custody, or control". The rule names all three because having a copy, keeping it and having the right to direct it are not the same thing. This page borrows that distinction as a working vocabulary, not as legal analysis.
For a licensing introduction the deciding power is settled. The CEO is the one who authorizes a licensing discussion and signs for the company; in an owner-run business the owner is usually the CEO. SourceX's screening guidance names two situations that are usually not a fit: an introduction the decision maker was unaware of, and data the company does not control. So the knower and the custodian matter for describing the archive, while only the CEO can say yes to discussing it.
Operating history makes the split wider than it is for a single system. A company with fifteen years of records has lived through several eras: a server in a back office, an on-premises ERP, a move to cloud software, perhaps an acquisition. Each era had its own administrator and its own vendor, and the people who built the early systems may have moved on. The governance roles themselves (owner, custodian, steward) are defined in data owner vs data custodian. What follows adds the time dimension: who knows and holds each era today. Archives left behind by a sale, a shutdown or a system change are traced in the quiet business archives outside the AI spotlight.
Map operators, system administrators, owners and counsel
Most archives have six kinds of people around them. Each can help, and only one can open the discussion.
| Person | What they usually know | What they usually hold | What they can decide | Useful question, asked through the relationship owner |
|---|---|---|---|---|
| Long-tenured operator (dispatch lead, support lead, warehouse manager) | Why records look the way they do, which years are thin, what changed in each migration | Nothing beyond their own login | Nothing about licensing | Which eras of records exist, and roughly when each began and ended? |
| Former employee or retired founder | The earliest era, often better than anyone still employed | Nothing the company has not given them | Nothing; the company decides | Would the company want this person's memory of the early years when it describes its archive? |
| Internal system administrator | Which systems hold which years, and what is still readable | Credentials and backups | Technical steps, once the company asks | Which era is held inside the company and which by an outside provider? |
| Outside custodian (managed IT provider, software vendor, records-storage company, outsourced bookkeeper) | Where the bytes or boxes are | The records themselves, under a contract with the company | Nothing about licensing; it acts on the company's instructions | Is the storage or service contract in the company's own name? |
| Record owners and sponsors (CFO, COO, department heads) | What the records are worth to the business, and the risks | Accountability for a domain, not the archive | They can prepare the case and sponsor it internally; the CEO decides | Would you raise this with the CEO, and what would the CEO want to know first? |
| General counsel or outside counsel | Customer contracts, privacy notices, sale agreements | Copies of the agreements | Advice on rights; the CEO decides whether to proceed | Not a partner question: counsel's reading comes after the CEO says yes |
Board members and investors belong on the map as relationship owners when they know the CEO well. Owning shares or holding a board seat does not make them the decision-maker for a licensing discussion. The live guide to finding the right decision maker covers titles in general; the map below is about one archive.
The owner-authority relationship map
Build one row per era of the archive, not one row per system, and fill the decision column last. The map below is Illustrative: a generic 180-person regional distributor with invented facts.
| Era | Records (as described, never viewed) | Who knows it | Who holds it | Who decides | Open question for review |
|---|---|---|---|---|---|
| 2008 to 2015 | Orders, returns and credit notes in a retired on-premises system; older paper files | The retired controller, now an occasional consultant, and the warehouse lead | A server image kept by the outside IT provider; boxes at a records-storage company | The CEO | Is the server image readable, and is the storage account in the company's name? |
| 2016 to 2021 | Orders, returns and customer service notes in an on-premises ERP | The operations manager | The internal administrator, with backups at the IT provider | The CEO | Did the 2022 move carry these years across, or only balances? |
| 2022 to now | Cloud ERP and a helpdesk | The operations manager and the support lead | Two software vendors, under the company's subscriptions | The CEO | Do the subscription terms limit what the company can export? A rights and contract question, not one for the partner |
| An add-on bought in 2019 | Its own order history from before the purchase | The add-on's former owner | Possibly still the seller's systems | The CEO of the group, if the purchase transferred the records | What the purchase agreement transferred |
Read the columns from left to right and one pattern stands out. The knowers change, the custodians change, and the decider does not. Every era routes to the same CEO, except where control of the records is itself in doubt, as in the last row. That is the question this map exists to surface before anyone talks to SourceX.
Method note. The map uses three published facts: the CEO authorizes; data the company does not control is usually not a fit; and partners do not need to export, upload or describe confidential records. It records what the company says about its eras, dated and attributed. It does not test whether any era is readable, licensable or in demand; SourceX assesses rights, documentation and relevance in its own review.
How a trusted relationship reaches the current authority
The map tells you who decides. The next question is who can ask them and be heard. Four paths are common, and each has a rule.
| Path | When it works | What goes wrong | The rule |
|---|---|---|---|
| Through a board member, investor or adviser who knows the CEO | The relationship is regular and trusted | The CEO feels pressured by someone with influence over the company | Present it as optional and easy to decline |
| Through the outside custodian, such as a managed IT provider | The provider's account lead talks to the CEO already | The provider is tempted to look at the archive to "see what is there" | Describe the opportunity; never open, sample or describe the records |
| Through the knower | The long-tenured operator has the CEO's ear | An employee is put in the awkward position of selling an idea upward | Ask whether they would like to raise it; accept a no |
| Through a record owner, such as the CFO | The CFO already discusses new revenue with the CEO | The CFO is mistaken for the decision-maker | The CFO can sponsor; the CEO says yes |
Whichever path you use, the relationship owner asks the CEO first, and the CEO decides whether anyone else in the company hears about it. If you are torn between going straight to the CEO and going through a sponsor, introducing through a sponsor or directly to the CEO sets out the trade-offs, and identifying an internal sponsor covers the person who carries the case inside.
The minimum context for a useful handoff
A useful handoff carries enough for SourceX to know why the company might fit and what is still unknown, and nothing a company would mind losing.
Send:
- The legal entity that holds the records, who controls it and the date you confirmed it.
- The CEO's name, and confirmation that the CEO knows about the introduction and wants the conversation.
- The archive's eras in years and system types, labeled with whose recollection they are.
- For each era, whether the records sit inside the company or with an outside custodian.
- Peak full-time headcount, contractors excluded (the program needs 50 or more at peak), or "unknown".
- Where the company operates. 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.
- The open questions from the map, phrased as questions.
Leave out files, samples, screenshots, exports, logins, customer names and anything learned from board materials. You make the introduction; you never handle the archive.
What to do when authority is unresolved
Sometimes the map's decision column will not fill. Five situations are worth planning for.
- The company was acquired. The acquirer's CEO decides for it now, not the former board or founder.
- An era sits with a seller or a former parent. Whether those records came across depends on how the business was bought; asset and stock purchases differ here. Leave the question for SourceX's rights review and the company's counsel.
- Ownership is deadlocked or under outside control. With two 50/50 owners, or under a trustee, receiver or court, the CEO alone may not be enough, because someone else may control the assets.
- The records are about to disappear. A storage contract ending or a server being retired is a real, dated reason to talk now; archive deadlines explains how to raise one without pressure.
- A related company may already know SourceX. If the parent, a sister business or another partner has been in touch with SourceX about an affiliate, do not guess how that affects credit. SourceX works it out when it reviews duplicates, and the terms already make the company itself a duplicate if it has any earlier application, lead, account or email correspondence with SourceX.
In each case, park the row with a dated note naming what must be resolved and by whom. Do not submit an introduction until the decision column holds a name.
A no-custody owner introduction checklist
Tick every line before anything goes to SourceX.
- I can name the company's current CEO, and I confirmed it on a date I wrote down.
- I know who owns the CEO relationship, and that person agreed to ask.
- The CEO knows about the idea and wants the conversation.
- Each era of the archive is described in years and system types, labeled with the source of that description.
- For each era I know whether the records sit inside the company or with an outside custodian.
- Nobody has sent or offered me files, samples, exports, screenshots or logins, and I have asked for none.
- I have not asked an administrator or custodian to look anything up in a system.
- Peak full-time headcount is confirmed at 50 or more, or marked unknown.
- Every unresolved question is written as a question for SourceX or the company, not answered by me.
- I signed the SourceX Channel Partner Agreement before submitting the introduction.
The operating partner's version of this exercise, which adds gatekeepers who can stop a conversation, is in the map of data owners and gatekeepers. More guides are listed on the guides hub.
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 map shows a CEO who wants the conversation and names a custodian for every era, the last preparation is yours: a tracked link from partner sign-up, a check of the company against the qualification criteria and a reading of the program's terms, all before the relationship owner makes the introduction.