A new operations leader reviews the company's archives: why the review's readout to the CEO is a fair moment for one licensing question, and a one-page introduction brief in which the new leader helps find what exists and the CEO alone answers

Short answer

When a new operations leader reviews what the company has kept, the CEO is about to hear, in one place, which archives, old systems and storage contracts hold the company's history and what each one costs. That readout is a fair moment to ask the CEO one question about licensing the company's own records. The new leader can help find who decides and what exists. The CEO decides, and nobody outside the company reviews, exports or summarizes a single record.

Visual briefFull-size diagram
A lamp labeled operations review casts a beam across three Illustrative archive shelves, offsite boxes from 2004 to 2014, a work-order system read-only since 2019 and a storage contract ending in January, with the labels what exists and who runs it inside the light; outside the beam a door marked the CEO decides, and a note reads one question, after the readout.
Illustrative archive review. The shelves follow the worked case on this page; the beam is what a new operations leader can help find, the door is the decision.

This guide serves partners who sit near that review without running it: outside accountants, IT and managed service partners, consultants and fund operating teams who know the CEO.

Why an archive review by a newcomer ends up with the CEO

The split of roles is the reason this trigger works. The Bureau of Labor Statistics describes chief executives in large organizations as focusing on policy and strategy while general and operations managers direct day-to-day operations, and lists setting policy, running daily operations and planning how materials and staff are used among operations managers' duties (our paraphrase of a search excerpt). Reviewing what the company stores, and what storing it costs, sits squarely inside that remit. Deciding what the company does with its history sits with the CEO.

An archive review by someone new tends to surface things nobody has looked at in years: offsite boxes, servers kept running for one old application, systems left read-only after a migration, shared drives that outlived their teams. Each of those holds part of how the company did its work. SourceX's data library describes the category plainly: "Operations data records how work gets done day to day: work orders, approvals, scheduling, dispatch and process logs."

The review ends with a readout: here is what we keep, where, since when, who runs it, what it costs, and what I recommend. For a few weeks afterward, the CEO is thinking about the company's history as a whole. That is the window.

Which stage of the review suits the question

A new leader is busy proving themselves. A licensing question arriving in week two lands on someone who cannot answer it and on a CEO who has not yet heard the findings.

Stage of the review (Illustrative model)What the new leader is doingPut the question to the CEO?Why
First weeks in the jobMeeting teams, learning how work runsNoNothing has been found yet, and the leader has no standing to discuss it
Inventory under wayListing archives, systems, contracts and costsNoThe picture is incomplete; an early question can look like pressure on the findings
Readout delivered to the CEOPresenting what exists and the recommendationsYes, in the weeks afterThe CEO has the whole picture in front of them
Decisions being carried outRetiring systems, ending contracts on set datesYes, naming any date as the company's own factReal, dated timing; the decision about disposal stays the company's
Review finished and settledBack to running operationsYes, if the CEO is still interestedThe trigger has faded but the facts remain

Hold back entirely, whatever the stage, when any of these is true:

  • The review follows a security incident, a data loss or a regulator's inquiry.
  • Layoffs or a restructuring are running alongside it.
  • Counsel has placed records under a legal hold or a dispute is open.
  • A sale is pending. Until it closes, the target's own CEO decides; after closing, the acquirer's CEO does.
  • You learned about the findings through paid work for the company and the CEO has not raised the topic with you.

What to ask of the new leader, and what never to ask

Useful, and only with the CEO's knowledge. The new leader can tell you which legal entity holds the archives and whether a parent or acquirer sits above it; which systems and stores hold years of the company's own work, and since when; who runs each one today; and which retirements or contract endings carry dates. They can also tell you, at the level of "such contracts exist", whether customer agreements might limit reuse. That is a map of what exists and who looks after it, which is exactly what helps you route a question to the right person.

Never theirs, and never asked. Whether the company talks to SourceX. What scope, if any, it would license. Whether records are the company's own or its customers'; SourceX's rights review and the company's own counsel settle that. Which partner, if any, receives credit. And no request, ever, for files, samples, screenshots, exports, a tour of the storage room or a login. The new leader does not decide for the company, and should not be put in a position where saying no to you feels like a risk to their new job.

The new leader can become the company's internal sponsor if the CEO asks them to: the person who later describes the systems to SourceX and joins the first call. Sponsoring is not authorizing.

The operations review introduction brief

After the readout, and only if you have a relationship with the CEO, send one page. Each block has a source, and none of them is a record.

BlockWhat it saysWhere every word comes fromNever contains
1. Why nowThe review's readout prompted this noteWhat the CEO or the new leader told youYour reading of the findings
2. What the company keepsSystem names, rough years, who runs eachThe CEO's own description, or the new leader's with the CEO's agreementRecord counts you were not given, contents, customer names
3. The questionWould the company like a conversation with SourceX about licensing its own operating records?YouA second question, or a hint that the company qualifies
4. Who decides and who helpsThe CEO decides; the new leader can describe systems later if the CEO wants; SourceX reviews fit and rightsThis page's rolesAnyone else named as the decider
5. What a yes startsThe company applies itself; nothing leaves the company before it approves scope and terms and signsSourceX's process pageA timeline or a payout estimate
6. Your interestYou could be paid a referral reward; the company is paid the same either wayTerms, section 4An amount, or language implying the company pays you
7. What you will not doSee, copy or summarize records; speak to staff about it; weigh in on what to keepYour own commitmentExceptions

Block 5 rests on SourceX's process page: "You approve the scope and terms and sign before any data is delivered." Block 6 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."

A filled brief, Illustrative:

Why now. You mentioned that [new leader]'s review found the old work-order system, kept read-only since the 2019 migration, and offsite boxes going back to 2004. The question. Would you like a conversation with SourceX, which licenses business records directly from companies for AI training and evaluation, about licensing the company's own operating history? Who decides. You do. If you want to go ahead, [new leader] could describe the systems; SourceX reviews fit and rights. If yes. The company applies itself, and nothing is delivered before you approve the scope and terms and sign. My interest. SourceX could pay me a referral reward; what the company would be paid is unchanged. What I won't do. Look at, copy or describe any record, or have any view on what you keep.

For fund platform teams, the portfolio operations review introduction email is a sibling draft written for a founder after a fund-led review.

One review, followed through (Illustrative)

Illustrative: the company below is generic, and every fact about it is made up.

A regional facilities maintenance company with about 300 full-time employees at its peak hires its first chief operating officer in May. Her review finds three things worth a line in the readout: offsite boxes of job files from 2004 to 2014, a work-order system kept read-only since a 2019 migration and holding records from 2009, and a storage contract that ends in January. She presents to the CEO in August, recommending that the boxes be scanned or destroyed and the read-only system retired after the contract ends.

The company's outside accountant, who has known the CEO for years, hears about the readout from the CEO in September, checks the hold list (no incident, no sale, no layoffs) and sends the brief. The CEO replies that she would like the conversation, wants the COO to describe the systems and has never been in touch with SourceX. The accountant signs the SourceX Channel Partner Agreement, submits the introduction and leaves the company to apply. The January contract date stays the company's business; nobody suggests changing it.

A counter-case: had the review followed a ransomware incident, the same accountant would have sent nothing and noted the reason with a date.

Owner, sponsor and credit checks before the introduction

  • Owner. Name the entity that holds the archives. After an acquisition, the acquirer's CEO decides, and the group shares one reward cap; finding the right sponsor after a deal has its own guide, the post-close integration review.
  • Fit. Full-time headcount must have reached 50 at its peak, contractors excluded, with years of records the company created and the rights to license them. 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.
  • Earlier contact. Ask the CEO whether the company has ever applied to, corresponded with or held an account with SourceX. Any of those makes it a duplicate, and no partner is credited.
  • Credit. Only one partner can be credited per company. The first valid introduction of a company new to SourceX counts, decided from dated records, once the company files a verified application within the 90-day attribution window. Keep the CEO's written yes and the date you submitted.

Two neighboring triggers need different handling. A newly hired records manager compiling an inventory is covered by the records-role sponsor handoff, and a retired employee who remembers where an old archive sits by the retired administrator guide. More business-change moments are collected in the guides library.

Method note. The timing model, the hold list, the brief and the worked case apply the BLS description of top executives' and operations managers' roles (a search excerpt), SourceX's operations, process and screening pages and the program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), all read on 2026-10-27. The review stages are this page's model, not measured data. Nobody has published how often a new operations leader's review leads to an introduction; count, for each review you hear about, the stage at which you asked, any hold that applied and the CEO's answer.

Four ways an archive review can mislead a partner

  • Old is not the same as the company's own. Boxes of client files and systems run on a customer's behalf may belong to those customers. SourceX's review decides what is licensable.
  • Retired is not gone, and kept is not usable. A read-only system may hold everything or a fraction; a scanned box may have lost its context. Describe what the CEO says exists and let review judge it.
  • A cost review is not an invitation. If the readout's mood is cutting spend and jobs, a licensing question can sound like one more pitch. Wait.
  • The new leader's view is not the company's. Enthusiasm from a new COO is a good sign and not a decision. Only the CEO's answer moves anything.

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 readout is behind the CEO and they have asked for the conversation, set up your partner account, test the company once more against the screening profile and have the program terms open while you prepare the introduction.

  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

The new operations leader is my contact, not the CEO. Can they make the introduction?

They can carry your question to the CEO and, if the CEO asks them to, act as the internal sponsor. The yes has to come from the CEO in the CEO's own words. Disclose your possible reward to both of them.

The review recommends destroying old archives next month. Should I ask the company to wait?

No. What the company keeps or disposes of is its own decision, made with its advisers. You can name the date in your question to the CEO as the company's fact, but never suggest keeping or deleting anything for the sake of a licensing conversation.

What if the operations leader was hired by a new owner after an acquisition?

Then the acquirer's CEO decides for the company, and the whole group shares one reward cap. Route the question to that CEO, and expect the new leader's review to be part of the integration rather than a separate project.

Sources

  1. bls.gov/ooh/management/top-executives.htm
  2. sourcex.si/data/operations
  3. sourcex.si/how-it-works
  4. refer.sourcex.si/who-qualifies
  5. refer.sourcex.si/terms

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