This hub offers practical guides and best practices for advisors looking to successfully introduce companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) to SourceX, a direct licensing partner for approved business data for AI training and evaluation. Here, you'll discover step-by-step instructions and strategic insights for introducing companies to SourceX, which licenses data directly from companies and manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. These resources are designed to help you navigate the process efficiently, focusing on companies with 50+ full-time employees at peak. Unlock the potential of valuable data partnerships by leveraging these comprehensive guides.
Practical guides to successful company data introductions
Short, task-focused guides on identifying suitable companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English), recognizing valuable proprietary data, and making an introduction the decision maker will welcome.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
- 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
What kind of companies should I introduce to SourceX?
You should focus on introducing companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) that have 50 or more full-time employees at peak. These are the companies that can unlock the potential for valuable data partnerships with AI labs and data buyers.
What is the purpose of these guides?
These guides offer practical instructions and strategic insights for advisors to successfully introduce companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia to SourceX. They help navigate the process efficiently and identify valuable proprietary data for AI labs and data buyers.
Who benefits from SourceX data introductions?
AI labs and data buyers benefit from approved business data that SourceX licenses directly from companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia for AI training and evaluation. Advisors can also benefit by introducing companies to SourceX as their direct licensing partner.
What kind of information do these guides provide?
These guides provide step-by-step instructions and best practices for identifying suitable companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia. They help in recognizing valuable proprietary data and making introductions that decision makers will welcome, facilitating data transactions for AI.
Related pages
- How to model a one-time receipt, like a data license, in a 13-week cash flow forecast
- 2021-vintage private equity funds: what to do with companies bought at peak multiples
- 3PL and logistics M&A in 2026: what buyers want and what sellers should preserve
- 3PL valuation multiples in 2026: what buyers pay for in a logistics business
- A/E industry M&A trends in 2026, and what selling firms should prepare
- Acquiring a business from a retiring owner: assessing decades of records before they go
- When a restructuring team needs to pause licensing discussions: a pause-trigger and authority review sheet that names each event, what stops while it runs and the written word from today's controller that lifts it
Pause the moment an event changes who controls the company or its records: a bankruptcy filing, an assignment or receivership, a newly appointed controller or CEO, a sale process that reaches the archive, a dispute over control, or a preservation instruction from counsel. While the pause runs, nobody on the referral side nudges, forwards or submits anything. It lifts only when today's controller, confirmed through counsel, says in writing that they want the conversation. If nobody can say that, close the file.
Read → - When a search fund has just acquired the business: a seven-check mandate screen for the broker who sold it, from the closing date to the searcher-CEO's own yes
Once the purchase closes, the searcher who bought the company normally becomes its CEO, and that CEO alone can open a conversation about licensing the company's records. Your former client can point the way but no longer decides. Before raising anything, settle seven things: that the deal has closed, who runs the company now, where the records sit, the basic fit facts, any earlier contact with SourceX, who else holds the relationship, and whether the new CEO wants the conversation at all.
Read → - When a seller wants to license data before closing: test the motive first, then give transaction counsel ten questions grouped by the document that answers each, before the target's CEO says yes
Yes, but only after transaction counsel reads the signed deal documents against SourceX's own steps. Until closing, the target's CEO decides; once an LOI or purchase agreement is signed, its terms may require the buyer's consent before the company grants a license. SourceX's licenses are exclusive for AI training, and once the fee is paid SourceX's license to the de-identified dataset is permanent, so a buyer inherits the result. The advisor's job is to put the checklist in front of counsel and the CEO, not to answer it.
Read → - When a short video explains the referral better than text: a format comparison protocol that records one fixed script both ways, puts the disclosure on screen and in the voice track, keeps a transcript one click away and retires the recording when a line it speaks goes out of date
A short video explains the referral better than text only when CEOs who receive it understand who decides, what is asked of the company and that the partner may be paid at least as well as CEOs who read the same words, and reach as many informed decisions. Test it with one script used both ways: a captioned video with the disclosure on screen and in the voice track, and the identical script as text. Randomize CEOs, score understanding before decisions, and retire the recording whenever a line it speaks goes out of date. No results are published here.
Read → - When a signed addendum changes default referral terms: a default-versus-exception sheet that shows which signed line overrides which default
A signed addendum changes SourceX's default referral terms only where it expressly identifies the change; every other provision keeps its default. The reward formula, calculation base, Minimum Transaction, Repeat Window and any cap in a signed Channel Partner Agreement's Schedule A prevail over the website terms, and the website terms govern attribution and rewards otherwise. Website updates, dashboard edits, calculator changes and one-time exceptions amend nothing. For a finance team the working rule is short: book the default, then overwrite one line at a time, and only from signed text.
Read → - When a signed agreement does not trigger a referral payment: six signatures, one notice and the conditions that still decide the reward
A signature on its own never triggers a SourceX referral payment. The reward on a company's first qualifying transaction is the greater of USD 50,000 plus 5% and 15% of what SourceX actually pays the company you introduced, and it becomes payable only after the Acquisition Partner's final written acceptance, completed handoff, cleared payment to SourceX, payment of the company and finance approval, plus your tax and payment details. A signed Master, a signed Confirmation, a signed buyer license or a renewal signed too late can each leave the reward pending or at zero.
Read → - When a strategic investor wants preferential data access: an escalation brief that splits the request into its separate asks, routes each to the one person who can answer it and keeps all of them out of the SourceX introduction
Take the request out of the introduction. SourceX's partner agreement gives an introducer no data license, no right to train models, no authority over a company's records and no copies of its data without separate written authorization, and the program terms add that partners never see applicant documents. Whatever a strategic investor wants, whether a copy of operating data, a first look or better terms, is a separate request to the company, decided by its CEO under the company's own agreements. Log it, split it into its separate asks, route each one and pause the introduction until it is settled.
Read → - When a strategic partner is the introducer but not the data owner: an authority diagram for corporate venture teams that gives the corporate the introduction, the operating company's CEO the decision and SourceX the review
A strategic partner can open the door to a company; it cannot walk through on the company's behalf. A minority stake, a supply contract, a co-sell arrangement or even hosting the company's systems gives a corporate reach and information, never the right to license the company's records or to agree to a licensing discussion. That decision belongs to the operating company's CEO, rights depend on the company's own contracts, and SourceX runs the review. The corporate's job is one permissioned introduction, cleared inside its own walls first.
Read → - When a strategic partner wants to refer an entire customer base: a targeted opt-in pilot that swaps the list for a few named account owners, one CEO's written yes per introduction and a weekly pace nobody may exceed
Say no to the base and yes to a pilot. A customer base cannot be referred as a block: every SourceX introduction records one identified company and one opportunity, the program credits companies one at a time, and an introduction its CEO did not know about is usually not a fit. What a strategic partner can run is a targeted opt-in pilot: a few account owners who know a customer's CEO personally ask that CEO, one company at a time, at a capped weekly pace, and only a written yes becomes an introduction.
Read → - When a supplier relationship opens a company introduction: a seven-gate permission pathway that starts with which side of the invoice you sit on
A supplier relationship opens an introduction only when two things hold: the company's CEO can say no at no cost to the commercial relationship, and your reason for asking rests on public clues or on what the company tells you for this purpose. Which side of the invoice you sit on sets the main risk. If you buy from the company, it is leverage. If you sell to it, it is what you learned while serving it. Introduce only after the company confirms the screening facts itself.
Read → - When a thesis calls for workflow context, who can you introduce? A four-position map that finds the company running the workflow for itself
Introduce the company that runs the workflow for itself. Around any workflow a thesis points to, four kinds of company sit close by: the operator doing the work for its own business, an outsourcer doing it for clients, the software vendor hosting it and the advisor who redesigned it. Usually only the operator owns the trail of how each case moved, so only its CEO can put those records on the table. The other three are how you find the operator, and sometimes how you reach its CEO.
Read → - When a trusted contact has moved to a new company: a relationship refresh checklist that sorts what travels with the person, what stays with the former employer and what starts again from zero, before any question reaches the new company's CEO
When a trusted contact moves to a new company, the trust you built moves with them, and very little else does. What they know about their former employer stays behind. The new company's CEO decides for the new company, whatever your contact's title. And an earlier introduction of the old company carries no credit, status or date across: the new company is screened and credited on its own dated record. Refresh the relationship first, with no ask in it, then let a checklist decide whether a question ever reaches the new CEO.
Read → - When acquisition-led growth changes the referral entity: a lineage map that follows each acquired business to the entity holding its records today
Acquisition-led growth changes the referral entity whenever a deal moves records or decision rights. A merger folds the target into the surviving company, an asset purchase moves only the records the agreement lists, a stock purchase keeps records in the acquired company under a new owner, and a divestiture can take records out of the group. Trace each acquired business to the entity that holds its records today, and to the CEO who decides for it, before anyone is introduced. However many entities license, a parent and its subsidiaries count as one company, so the USD 50,000 first-transaction floor applies once across the group.
Read → - When an account has several contacts with different permissions: a contact-level permission matrix in which only the CEO decides for the company, every helper's scope is written down with its source and limits, and the partner decides nothing
Give every contact at the company a row of their own, and let only one row decide: the CEO's. Finance, IT, legal, an executive assistant and an outside adviser may help when the CEO asks, each within a scope you write down with its date and source. None of them can say yes for the company, and a no from any of them is a reason to ask the CEO, not an answer. You, the partner, decide nothing for anyone.
Read → - When an affiliate link appears in a comparison article: a disclosure and evidence checklist that puts your interest beside the table, fixes the criteria before any verdict and dates every program fact on that program's own page
Once a comparison article carries a SourceX partner link that could pay you, readers are entitled to know before they read your verdict. Put the disclosure directly above the comparison table and beside each paid link, write the criteria before scoring anything and apply them to every option, date each program fact against that program's own page, write "not published" wherever a figure is missing, and remove any ranking your reward could have shaped. Describing SourceX as your partner in public waits for its written authorization.
Read → - When an agency writes partner content on your behalf: an agency briefing and fact-check pack that hands the writer SourceX's own sentences, keeps every client out of the brief and traces each program claim to a source before your firm's name goes on it
Hand the agency SourceX's published sentences, not your own summary of them; give it no client names or company details; list the claims it may never write; and ask for a claim log that ties every program statement to a section of the terms, the screening page or the sample partner agreement. One named person at your firm approves each piece before it goes out under your name. FTC guidance, paraphrased, says an agency can share legal responsibility for ad claims with the advertiser it writes for, which spreads the duty rather than moving it.
Read → - When an angel and a fund both know the founder: a five-question framework that first checks whether the founder still runs the company, then names one introducer and records what the other one hears
Pick one introducer before either of you mentions SourceX, and begin by checking that the founder you both know is still the company's CEO, since the CEO is the person who authorizes a licensing discussion. Then compare the two relationships on facts: whom the CEO consults about running the business, who has signed the partner agreement, whose rules allow a reward and whether either relationship carries a conflict. One of you introduces in writing and the other steps back. SourceX credits a single partner per company and settles any overlap in duplicate review.
Read → - When an archive contains several businesses' records: twelve entity separation questions that split one archive into each business's share, name today's decider for every share and stop where only opening the records could tell the shares apart
An archive that holds several businesses' records is several referral questions, not one. Each business's share has its own decider today: the group CEO when the businesses form one corporate group, the acquirer's CEO for a business it bought, a trustee, receiver or assignee where a formal process controls an estate, and nobody on the holder's side for work done for clients. Tell the shares apart from deal papers, contracts and labels, never by opening, sorting or copying the archive. Where only opening it would tell them apart, that share stops.
Read → - When an archive has valuable context but unclear provenance: a provenance uncertainty handoff memo that marks ten origin questions known, unknown or disputed, goes only to whoever decides for the records, and stops when a confirmation the company must give comes back no
An archive can be full of useful context and still have no settled origin. Before it reaches SourceX, write a provenance uncertainty handoff memo: ten questions about who created the records, how they arrived, whose material is mixed in and what the licensing company would have to confirm, each marked known, unknown or disputed, with who said so and when. Give it to whoever decides for the records. A no on a required confirmation ends the file; an unknown goes to that decision-maker, never to your own guesswork.
Read → - When an earn-out creates sensitive referral questions: a counsel escalation sheet for six situations in which the seller, the advisor and the acquirer's CEO want different things
An earn-out makes a data referral sensitive whenever the person who wants to make the introduction, or the person who would benefit, has money riding on the earn-out metric. After closing, the acquirer's CEO decides whether the company discusses licensing its records; the seller does not, even while still running the business day to day. Route each conflict to whoever reads the document behind it, say nothing that came from the deal room, and introduce only after the acquirer's CEO has agreed.
Read → - When an industry council wants to publish aggregate findings: a member-consented research plan that keeps the findings the council's own, reports what members think and never who might qualify, and lets every respondent withdraw before the numbers are locked
It can publish, as long as the findings stay the council's own account of what members think and have experienced. Members opt in knowing every use of their answers; the report shows only totals that no reader could trace to a company; it never estimates how many members might qualify for SourceX or anything else; no respondent becomes a referral lead; and wherever SourceX is named, the council's own relationship is disclosed beside it. Pilot the questionnaire with a few volunteers who may decline any part of it.
Read → - When an internal AI project raises external licensing questions: an eight-question map that separates what the build settled for the company's own use from what a license would ask again, with the CEO deciding and no partner touching a record
An internal AI project raises external licensing questions when building it forces the company to ask who owns its records, what its contracts permit and what an outside AI service may do with what it receives. Every answer the build reached was for internal use; a license would put each question again, for a different use. The referral moment comes when the CEO links the project to the records, not when you first hear about the build. Then ask the CEO once, and never see, review or export a record.
Read → - When an introduction-only model is the right choice: a scope-and-capacity guide for deciding how much of a client's data-licensing path your firm should carry
An introduction-only model is the right choice when your client's CEO can carry the licensing conversation without you, your firm has no spare capacity or relevant skill to add, and you want your role, disclosure and conflicts kept simple. In SourceX's program it is also the default shape of the job: you introduce an authorized CEO, and SourceX runs review, agreement, preparation, delivery and payout without needing you on every call. Go beyond it only when the client asks for help your firm already provides.
Read → - When an IT vendor hosts data for many clients: a tenant-owner boundary map that splits what the custodian runs, what each client owns and decides, and what SourceX reviews, so every tenant is introduced as its own company or not at all
Hosting many clients' data can show an IT vendor which clients might hold valuable records; it never gives the vendor the right to license, export or describe them. Each tenant's records belong to that client, so each client is a separate company with its own CEO, its own fit test and its own introduction. The vendor may introduce a willing client's CEO, using facts the client hands it, or introduce itself for records about running its own business.
Read → - When an LP wants to participate without compensation: three routes that keep the favor unpaid, the one question the published terms leave to SourceX, and a seven-line confirmation agreed before the CEO hears a word
An LP who wants to help without being paid has three ways to do it: mention the idea to the company's CEO and let the company apply on its own, let your fund submit the introduction with the LP's consent, or register and submit personally. Only the third raises a question nobody can answer for you. SourceX's published terms say nothing about a partner who turns down its reward, so SourceX decides how that is handled, and the LP should ask SourceX in writing before submitting anything. In all three routes the company's payout is unchanged.
Read → - When an LP-owned company is a referral candidate: an LP relationship conflict review brief that separates the LP as investor from the LP as owner, names who would be paid on each route and leaves the decision with the company's CEO
An LP-owned company is a referral candidate when it passes SourceX's published fit tests on its own and its CEO wants the conversation. The LP's commitment to your fund plays no part in fit. What changes is the fund's side: before anyone mentions SourceX, write down who would take part, who could be paid, how the LP's two roles, investor and owner, bear on each other, and which fund duties apply. Then file the route fund counsel approves: the firm, a named person, an unpaid mention, or no role at all.
Read → - When an owner asks 'Is this selling my customers' data?': an ownership-boundary script that answers in three lines and promises nothing it cannot keep
Answer in three parts. First, what is licensed: the company's own records of how its team works, under a license rather than a sale, with the company keeping ownership of the originals. Second, what stays out: records that belong to customers or that the company holds for them, and personal details, which are removed before anything is delivered. Third, what you cannot promise: whether a contract, privacy notice or law limits any record is decided in SourceX's rights review and by the company's counsel. Then admit what does leave, and offer a step the owner can decline.
Read → - When better screening lowers applications but improves outcomes: a quantity-versus-quality cohort analysis that keeps CEOs who agreed to hear as the fixed denominator, so a shorter pile of applications counts as progress only when qualified outcomes hold or rise
Only when qualified outcomes per CEO reached hold or rise. Ask CEOs to check their company against SourceX's published who-qualifies page before applying, and applications will probably fall while the share that gets through review climbs, almost automatically, because the denominator shrank. That climb proves nothing. Fix the denominator at CEOs who agreed to hear about SourceX, count verified applications still standing at a cutoff, and watch for fitting companies that talked themselves out. No results from this design are published yet.
Read → - When buyer criteria change, re-run only the rows they touch: a criteria change impact register for venture network maps
Treat each criteria change as an event with a date, a source and a scope, then re-screen only the map rows it touches. SourceX applies the criteria of each program rather than one universal minimum, and a company outside one program's criteria may still suit a different program later, so a "no" on your network map is dated, not final. Log changes in an impact register, filter the rows each one reaches, and ask the relationship owner before anyone goes back to a CEO.
Read → - When corporate partner staff change during an active referral: a continuity protocol sorted by where the person went, from a new desk in procurement to a job at the company they introduced
Ask where the person went before you change anything. A staff move never rewrites the introduction record: its date, the partner named on it and the CEO's decision stay where they were. What moves is a seat: who answers the company's CEO, who receives SourceX's notices, who holds the partner login. A colleague who takes a commercial job with the company steps back from the referral; one who joins the company changes sides; one who joins another firm cannot submit the company again.
Read → - When does a chapter 11 debtor need court approval to license its data?
A chapter 11 debtor in possession generally needs court approval, after notice and a hearing under section 363(b)(1), to license data outside the ordinary course of business. If the records include personal information covered by a no-transfer privacy policy, a consumer privacy ombudsman may be needed. With SourceX, nothing binds the debtor until it signs.
Read → - When evaluation data changes which companies you call: ten training-versus-evaluation questions that re-rank a fund's call list, and the evidence that would undo the re-ranking
Evaluation data changes your call list when a company's strongest asset is a set of cases with known, recorded outcomes rather than sheer volume. Training rewards breadth and years of records; evaluation rewards cases where the right answer was checked, failures were kept and nothing was ever published. Re-rank the companies you already know with ten questions that separate the two, call first those whose records carry verified outcomes, and keep the fit tests unchanged: 50+ full-time employees at peak, own records, rights and a CEO who wants to talk.
Read → - When faster company growth creates poorer referral fit: a counterexample-first worksheet that tests the growth thesis on your own network before you rank anyone
Faster growth creates poorer referral fit when the growth is built from what the fit tests leave out: contractors instead of full-time employees, records that are mostly months old, or work that lives in customers' systems. Growth itself earns nothing in screening, because size is counted at peak and history in years. So before ranking a network by growth, hunt for counterexamples in it: fast growers that fail the published fit facts, and steady or shrinking companies that pass them.
Read → - When growth creates too much work for a referral conversation: a timing-capacity matrix that weighs the CEO's next 90 days against the date records disappear
Growth creates too much work when the two people a data conversation needs first, the CEO who authorizes it and the person who knows the systems, are committed for the next 90 days to an integration, a system cutover, a raise or a hiring push. Then introduce only if a dated event threatens the records, and even that starts as a short note to the CEO. Otherwise defer to a named trigger and date: SourceX credits an introduction only when the company applies within 90 days.
Read → - When local professional rules affect referral compensation: a jurisdiction review issue register that gives every person who could be paid one row, names the kinds of rules they should raise with their own adviser, and records a route before any CEO is asked
Local professional rules can affect referral compensation whenever the person who would be paid holds a regulated role, belongs to a professional body, works under an employer's or fund's policy, or advises the company being introduced. Those rules attach to that person and the places they practice, not to SourceX's program, and only their own adviser or regulator can apply them. A global platform team's job is narrower: list every possible recipient, name the kinds of rules each should ask about, log the answer with a date and pick a route. This page gives no legal, tax or regulatory advice.
Read → - When members ask why the association chose this program: a selection criteria disclosure sheet that shows what was compared, what was never checked and whether the association gets paid
Answer with criteria, not enthusiasm, and write them down before anyone asks. A selection criteria disclosure sheet lists each test the association applied to the program, what it found and on what date, the alternative it read, what it never evaluated, and whether the association can be paid. Members asking "why this program?" usually mean three things: did you compare, are you paid, and do you vouch for it. The sheet answers all three, including the lines that do not flatter the choice.
Read → - When network concentration becomes a strategic weakness: a six-shock dependency test that groups partners by the source they share and shows which loss the network cannot absorb
Concentration becomes a strategic weakness when a single event could remove more of your fit companies than the rest of the network could replace. Count it by shared driver, not by partner name: three partners at one accounting firm, or two operating partners working one fund's portfolio, are one exposure. Then run six shocks on dated records: a top partner goes quiet, a shared source goes quiet, a criteria change hits one sector, duplicates inflate one pool, a campaign cohort never activates, and one partner's batch swamps your checking capacity.
Read → - When network research finds no suitable company: a four-test stop-and-rethink review that separates a true zero from a search that looked in the wrong place
Treat the zero as a finding and test it before reporting it. Four checks expose a false zero: were rows screened on the published fit facts rather than proxies, did the search reach every relationship you hold, does each failing fact carry a source and a date, and is any "no fit" really "no path to the CEO"? If the zero survives, record it with your method and its reopening triggers. Never widen into strangers or bought lists, or soften the criteria to make a row pass.
Read → - When new finance leadership reviews dormant business assets: a discovery checklist that sorts each item on the review into a records question, a date worth flagging to the CEO or nothing at all, and never books the company's records as an idle asset
A new finance leader's review of dormant assets is about cost and obligations: systems kept running only for read access, storage contracts, idle subscriptions, entities that no longer trade. It can put two facts in front of the CEO that matter to a referral partner: which items hold the company's own operating records, and which of those end on a date. It never turns records into an asset to cash in, never makes a company fit and never moves the decision away from the CEO. Ask once, after the review's decisions are made.
Read → - When one fund's policy allows rewards and another's does not: a five-branch decision tree that keeps one introducer, never routes a reward around a policy and puts the open question to SourceX in writing
Settle the policy question between the funds before the company hears a word. The company still gets one introduction, from the person its CEO would want to hear it from, and SourceX still credits one partner. What the two policies change is who may sign as that partner. Sort each fund's written policy into one of five answers, follow the tree to a single introducer, and rule out the one move that breaks a policy: the permitted fund introducing so that value can flow back to the restricted one.
Read → - When one large introduction distorts the entire dashboard: put the top company on its own line, print its share, and read every other company as a count
When one introduced company produces most of a fund's paid or estimated referral value, every total, average and per-partner figure on the dashboard describes that company rather than the channel. Put the largest company on its own line, print the share of the total it carries, and read the rest of the cohort as counts of unique companies by stage, with open cases listed. The program has no cap on rewards, so nothing limits how large one row can grow, and one row is often most of the total.
Read → - When operating history matters more than funding stage: one screen for a Series C company and a never-funded distributor
For a data introduction, operating history outranks funding stage every time, because stage describes how a company was financed and history describes what it could license. The program asks for four things: a peak of 50 or more full-time employees, a documented operating history, rights to license and a CEO who wants the conversation. A never-funded 25-year-old distributor can pass all four while a well-known Series C company stalls on rights. Screen the entity that holds the records before anyone promotes the program to it.
Read → - When partners need better criteria instead of more content: a three-test diagnosis that reads your declined introductions before anyone writes another guide
Partners need better criteria, not more content, when their misses repeat on the same check. If many partners propose companies that fail the same test, or two partners reading the same rule reach different answers about the same company, the wording is the problem and another guide will not fix it. Content helps only when partners already apply the rules correctly and still cannot start the CEO conversation. Before commissioning anything, sort your last 20 missed introductions by the first check each failed, and test the rule that fails most.
Read → - When preserving records should come before a licensing conversation: a five-question escalation tree in which the first yes hands the next move to counsel, the records owner or the company's next controller
Preserve first whenever a record set is under a legal hold or a dispute or investigation can reasonably be anticipated, a purge or vendor deletion is dated, or control of the company is about to change. In each case the partner's only move is a short note prompting the CEO to let counsel and the records owner act. The licensing conversation waits until preservation is settled, because an archive can be introduced months later, but one that was deleted, altered or moved without authority cannot be repaired by any introduction.
Read → - When record volume is unknown: five honest ways to write the volume line in a referral brief, and the weak lines to rewrite
An unknown record count does not stop an introduction. SourceX's published screening profile asks about full-time headcount at peak, years in operation, the company's own documentation, rights and an authorized sponsor; it sets no record-count minimum, and SourceX's own volume estimator accepts "No idea" as an answer. What the brief must never do is fill the gap with a guess. Write the volume line as a dated count, a counter reading, an estimate with its basis, a band or a named unknown.
Read → - When restructuring changes the person who can say yes: a six-check authority record to rerun after every reorganization event, with the trigger that voids it
After any restructuring event, treat the yes you had as expired until four things are checked again: which legal entity now holds the records, who that entity's CEO is today, whether a bankruptcy court, a restructuring officer, lenders or a deadlocked board now sit above the CEO, and whether any duty to keep or destroy the records applies. Introduce only when every answer is dated after the event and the current CEO wants the conversation. Otherwise set a date to check again, or stop.
Read → - When security questions arrive before the introduction: a three-tier handoff packet that separates what SourceX publishes, what it shares after review and what waits for the application, with a decline line the founder can send
Answer what is public, route everything else and keep a way out open. Before an introduction no company records have gone anywhere, and none need to: SourceX's first step is a few questions with no files. Sort the founder's questions into three tiers: what SourceX publishes today, what it shares only after review or writes into the agreement, and what no one can answer until the company applies. Hand that sort over as a one-page packet with the escalation contact and a sentence the founder can use to decline.
Read → - When the company wants to limit which records are discussed: a scope boundary statement the CEO approves, with open, parked and closed record families and nothing attached
Let it, and write the limit down before anyone is introduced. SourceX's own process leaves scope to the company, so a CEO who wants some records kept out of the conversation is using a right the program already gives. Turn that wish into a short scope boundary statement the CEO approves: record families open for discussion, families parked until a named condition, and families closed, each named by category and system only. Send the statement, never the records.
Read →
Free resources
- Business succession planning assessment — Ten questions on successor, transition and documentation.
- NPV calculator — Net present value with a discounted cash flow table.
- Time value of money calculator — Future and present value with optional regular payments.
- All free tools · MCP resource center
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