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
- The archive review before a storage contract ends: a storage-deadline escalation checklist that names whose contract it is, carries the first date to whoever controls the company now and records a stop when nobody can answer before that date
A storage contract's end date forces a decision, and the custodian holding the archive almost never makes it. Before the contract's first date, the archive review settles five things: whose name is on the contract, whose records are stored, who controls that company today, what counsel says must be kept, and whether the controller renews, extends or lets it end. A licensing question can ride along as one line, never as the reason. In a wind-down or formal process the CEO may not be enough; whoever controls the estate decides.
Read → - The ask-me-anything format for referral questions: a moderated question-routing guide in which votes set the order but never the answer, each question goes to the one source that can settle it, and the thread stays correctable after it closes
An AMA suits referral questions when a moderator routes each question before anyone answers it. Answer in the thread only what SourceX's published pages or the host's own policies settle, and link the source. Move anything about one identifiable company to a private reply. Say plainly when nobody can answer, such as what a company would be paid or whether it will be accepted. Pin who could be paid at the top, let votes set the order but never the route, and keep the transcript dated and correctable after the thread closes.
Read → - The association board's questions before joining SourceX: a nine-part decision memo that reads the partner agreement before the vote, names who signs and writes the exit down first
A board asked to join SourceX's referral program is approving a contract, not a vendor. Before the vote, its memo should answer five things on paper: which legal person signs the SourceX Channel Partner Agreement and what that agreement binds it to, what members will hear, how any reward is disclosed and recorded, what the association may never do for a member company, and how the association leaves. Approve a small opt-in pilot first, never a mailing to the whole membership.
Read → - The attribution questions to resolve before a joint campaign: a twelve-question rules sheet for two organizations promoting one referral program
Before two organizations promote SourceX together, agree in writing which one is the partner of record, which single link the campaign uses, how the hosts share anything between themselves and which companies are already spoken for. The program credits one partner per company: the first valid introduction of a company new to SourceX, judged from dated records, once that company submits a verified application within the 90-day window. A click alone decides nothing, and a co-host is never credited as a second partner.
Read → - The boundary between public signals and private board knowledge: an evidence source classification sheet for the in-between cases, from a press story that echoes the board deck to a fact a colleague repeated at the partners' meeting
Classify each signal by how the fund came to know it, not by whether some version of it is public. A fact first learned through a board seat, information rights or a partners' meeting stays board knowledge even when a press story, job posting or announcement later says something similar; only public words, found and dated on their own, are usable. Board knowledge may prompt one question to that company's own CEO and goes nowhere else: never to SourceX, never toward a different company. Fund counsel decides the fund's actual duties.
Read → - The business history missing from startup leaderboards: a coverage-gap protocol that shows which fit-passing companies a ranking can never list
A startup leaderboard is a filtered list, and its filters are not SourceX's fit facts. Deloitte's 2026 North American Technology Fast 500, for example, takes only technology companies founded by the end of 2021, with 50% or more revenue growth and no parent company, and only those that enter. A 31-year-old inspection firm that shrank from 420 to 190 full-time employees can never appear there, and it may still pass every fit test. Read a list's entry rules before you read its ranks.
Read → - The CFO's questions when a partner suggests data licensing: a fourteen-question first-call pack that marks who answers each one, quotes what SourceX already publishes and leaves the rest open until review
Ask four sets of questions on the first call: about the partner (how they know the company, whether and how they are paid), about the money (whether the reward touches the company's payout, how and when the company is paid), about the records (what would be licensed and what leaves the building, when), and about the decision (who signs, and how to stop). SourceX's published pages already answer several. Whether the records fit and what SourceX would pay wait for its review, and tax treatment goes to the company's own advisers.
Read → - The chamber workshop that starts with company questions: an agenda members write before the day, a named answerer for every block, prices kept out of the room and a follow-up only when a CEO asks
Build the session from the questions members send in before it, not from a presentation. Collect them anonymously, order the agenda by how often each was asked, and give every block one named answerer: SourceX's published pages, the member's own adviser, the member's CEO, or SourceX's review when nothing can be said yet. Keep prices and deal terms out of a room of competitors, say what the chamber could earn, let anyone leave after any block, and introduce a member only when its CEO asks in writing.
Read → - The client conflict check before a data introduction: a conflict screening issue list that runs every party the introduction touches through your conflicts system, records the one SourceX never names to you and leaves the route to ethics counsel and the CEO
Run a conflict check before you introduce a client to SourceX, the way you would before opening a matter. List every party the introduction touches, check each one against the firm's clients, and add your own interest in any reward. One party cannot be checked: SourceX licenses onward in its own name and need not name the AI developer that takes the data. Ethics counsel then picks one of three routes with the client's CEO: a referral, an unpaid introduction, or no part in it at all.
Read → - The client disclosure a finance advisor should review before referring: a twelve-item draft that says who may pay you, on what basis and what you will never do, read by your board, professional body, firm or counsel before the client sees a word
Draft the disclosure before you mention SourceX, and have it read by whoever can say what your own rules require: your state board's published rules, a professional body such as the AICPA or CFP Board, your firm's ethics or compliance lead, or counsel. Rules differ by role and by place, and some do not permit pay for a referral alone, which no wording can fix. A reviewable draft says who may pay you, on what basis, that the client is paid the same either way, what you will never do and how the client can go ahead without you.
Read → - The client retention question behind a new partner offer: a client trust feedback study that tests raising it inside the engagement against raising it through a separate channel
A partner offer earns its place only if clients who hear it renew, buy and trust the firm at least as much as clients who do not. Neither the reward nor a client's first reaction can show that. Before scaling, run a small client trust feedback study: raise the offer in one of two ways, ask the same few questions at four points, and judge the result by renewals and complaints rather than by introductions made. SourceX has published no results of this kind; the method follows.
Read → - The company has changed systems three times: a system-history timeline canvas that asks what crossed each cutover, what stayed behind and who can still open it
Three system changes mean four eras of records and three cutovers, and each cutover decided what history survived. For every cutover, ask what crossed (full history, open items and balances, a snapshot from a chosen year or nothing), whether record IDs survived so the eras can be joined, what stayed behind and in what form, who can open it today and when that access ends. Draw it on one timeline the CEO approves, label estimates and unknowns, and attach no records.
Read → - The company introduction hidden in an LP's operating network: a five-part discussion guide for asking an LP about the companies they run, chair or advise, with the fund left out of the conversation and each company's CEO left to decide
Many limited partners are also operators. They chair a family company, sit on outside boards, run a division or meet monthly with a group of fellow CEOs. Any company in that operating network can be introduced to SourceX if it passes the published screen and its CEO wants the conversation. Raise the subject with the LP only in a conversation whose non-investment purpose you state first, held apart from fund business, and let the LP decide whether to mention it to the CEO. Unless the LP is that company's CEO, the LP never decides for it.
Read → - The company is famous: is it actually a good referral? A reputation-versus-eligibility test for eight kinds of fame, and what each one leaves you to confirm
Usually not because of the fame. A famous name tells you an audience noticed the company. A referral needs facts no audience sees: 50+ full-time employees at peak, years of the company's own operating records, rights to license them, a CEO who wants the conversation, and no earlier contact with SourceX. Fame helps with none of these directly, and it often works against two of them: the CEO is harder to reach, and the name is one other people think of first. Run the test below and introduce only what survives it.
Read → - The company name appears in a draft article: who must approve? A publication consent workflow that sorts every line by whose information it carries, sends each to the one person who can clear it, and never reads an introduction yes as a publication yes
Up to three people may need to approve, and a yes to an introduction from any of them covers none of this. The company's CEO approves its name and every fact about it. SourceX must authorize in writing any line that publicly identifies it as your partner or discloses non-public deal details, under section 4.5 of the sample Channel Partner Agreement. Your own counsel clears anything you learned in confidence. Lines about the company's process status, amounts or board material stay out by default.
Read → - The compliance consultant who spots a potential data owner: an owner introduction discovery sheet the CEO fills in, which leaves the engagement evidence where it is, separates the company's own records from what it holds for customers and names who decides
A compliance consultant often notices, before anyone else, that a client has kept years of its own records in well-run systems. That noticing can justify one question to the CEO; it cannot be the introduction. What you learned from asset registers, data flow diagrams and findings stays inside the engagement. The introduction rests on a short discovery sheet the CEO answers from their own knowledge: which records the company creates for itself, which it holds for customers, whether it has dealt with SourceX before, and who decides. That person is the CEO.
Read → - The confidentiality test before publishing a network success story: an inference and permission gate that asks what a reader could work out from each line, starting with the company's payout hidden inside your reward, before asking who could allow it
Test a network success story twice before it goes anywhere. First for inference: what could a reader work out from each line, even with no company named? A reward figure lets anyone compute the company's payout, a "we were paid" post dates the company's payment, and a sector-size-region description can pick one company out of a public portfolio. Then for permission: the company's CEO clears facts about the company, SourceX clears in writing anything identifying it as your partner or describing the deal, and nobody in your chain can clear an Acquisition Partner's identity. SourceX's own default for deals is silence.
Read → - The corporate venture office hour that produces useful follow-up: a qualified follow-up meeting that waits for the CEO's written request, keeps procurement and pilot teams out, and has the corporate step out once the introduction is made
Judge the office hour by its follow-up, and allow only one kind toward SourceX: a short meeting that the company's CEO asked for in writing, held after the corporate has submitted a written introduction, with nobody from procurement, the pilot team or an open financing at the table. The corporate's relationship owner opens it, states the corporate's role and any reward it could receive, then leaves the CEO with SourceX. Every other office-hour conversation ends in links, a direct application, a dated "not now" or a recorded no.
Read → - The cost of an unqualified introduction: a time-diary protocol that measures who pays, in minutes, before anyone guesses a dollar figure
An unqualified introduction costs time, and any hourly figure you see for it is a guess, because the cost has never been measured. It is spread across three people: the partner who screens and asks, the owner who reads, discusses and applies, and the SourceX reviewer who checks and declines. This protocol measures it with short time diaries kept by all three, for qualified and unqualified introductions alike, and reports minutes and elapsed days before anyone attaches a dollar value.
Read → - The customer advisory board discussion about data partnerships: a 45-minute research plan that keeps the referral out of the room until a member asks
A customer advisory board is the right place to learn whether your customers want to hear about licensing their own operating records, and the wrong place to recruit them. Run the session as research: ask what members' companies keep, what would worry them and who would decide. Never quote their usage data. Offer an introduction to SourceX only afterwards, in a separate step, to members who ask for one and whose CEO wants the conversation.
Read → - The customer education email that avoids a vendor endorsement claim: nine annotated lines a SaaS vendor can send about SourceX
Send customers an optional resource, not a recommendation. A SaaS customer referral email about SourceX should state in one factual sentence what SourceX does, say that your company endorses no outcome, shares none of the customer's data and takes no part in any decision, disclose that you may receive a referral reward paid by SourceX, confirm the customer's product and support stay exactly the same, and leave the next step to the customer's CEO. The template below does each of those in a single line.
Read → - The data conversation after a quality management upgrade: a quality-history discovery brief, filled in from what the CEO and the quality lead say once the new system is live, that turns the old archive's fate into one fair question
A quality management upgrade, whether the move to a new quality system or the transition to the 2026 edition of ISO 9001, makes a company's leaders decide what happens to years of nonconformance, corrective-action and audit history. Once the new system is live and that decision is on the table, a partner who knows the CEO can fairly ask one question: would the company like to hear whether records it wrote itself could be licensed for AI training and evaluation? Build the brief from what people tell you, never from the records.
Read → - The data introduction before a wind-down team disconnects systems: a five-phase shutdown decision timeline that puts one question to whoever controls the company before the first system goes dark, leaves the run-sheet exactly as it was, and records a stop when the answer cannot come in time
Ask one question, early, of whoever controls the company on that date, and change nothing about the shutdown. A wind-down's system run-sheet decides when each family of records stops being reachable; the introduction never moves those dates, never keeps a system running and never copies anything for SourceX. In a formal process the CEO may not be enough, and whoever controls the estate decides. If that person cannot answer before the records are gone, the right outcome is a dated stop, not a rescue.
Read → - The data introduction friction index: six measures a stage clock misses, and the rules that keep the score honest
A data introduction friction index should measure what makes an introduction harder without showing up on a stage clock: how many people must agree before the CEO hears the request, how many fit facts are unknown at handoff, how many rights questions open, how often the authorized contact changes, how much rework the introduction needs and how often the company goes quiet. Elapsed time is already handled by stage-duration benchmarks. No index values exist yet, so publish the specification, weights and a sensitivity test first, and keep declined introductions in.
Read → - The data opportunity conversation for a vertical SaaS network: a five-test relevance guide that tells you which customer segments to invite and which to leave out
A vertical SaaS company can open a data opportunity conversation with the customers in its industry, but only about records those customers own, and only as an introducer. Before anyone says a word, score each customer segment on five stated tests: 50+ full-time employees at peak, records about the firm's own operations rather than its clients' or consumers', years of history, a reachable CEO and an eligible location. Invite the segments that pass, by opt-in, keep product data out of it, and let each customer and SourceX decide.
Read → - The data opportunity inside a successful process repair
A repaired process leaves five kinds of record: the failure itself (tickets, nonconformance or incident reports), the investigation (root cause analysis or postmortem), the intervention (corrective action and change requests), the revised policy (a new procedure version with its change history), and the validation (an effectiveness check comparing results before and after). The chain is most useful when each record links to the next and the outcome was measured.
Read → - The data opportunity question during a service catalog redesign: eight service-history prompts timed to the redesign's own review meetings, so the CEO hears one clear question and nobody opens a record
A service catalog redesign is one of the few moments when a company's leaders study their own service history on purpose: what was requested, what was delivered, and what should now be merged or dropped. That makes it a fair time to put one question to the CEO, through whoever holds the relationship: would the company like to know whether the history behind its old services could be licensed for AI training and evaluation? Ask at a scheduled review point, keep every question at the level of metadata, and let the CEO decide.
Read → - The data opportunity questions investors hear from founders: a question-frequency taxonomy of eight families, a capture card filled in within one business day and a founder-level count that keeps silent founders in the denominator, with no frequencies published yet
No one has counted these questions yet, SourceX has published no tally of them, and this page reports none. A credible report would count founders, not questions: every founder an investor told about SourceX in a fixed window, including those who asked nothing, each question logged on a short capture card within one business day, paraphrased without company detail and coded into eight families by two coders working apart. It would publish the share of founders asking in each family, by stage, and only after the window closes.
Read → - The data partnership conversation after a founder hires a CFO: a before-and-after timing guide in which the finance tray moves to the new CFO, the decision stays with the CEO, and the question waits for the first full reporting cycle
A founder's first CFO hire changes who in the company can tell you whether there is room for a licensing conversation; it does not change who decides or whether the company fits. The CEO still decides, every published check stays where it was, and the new CFO is worth hearing from on timing and workload only once the CEO brings them in, never as the authorizer and never as someone who reviews records for a partner. Let the CFO get through a first full reporting cycle, then ask the CEO, once.
Read → - The data partnership workshop for experienced founders: a decision-based workbook that marks which choices can be undone and which become permanent, names who makes each one and leaves the room with the founder
Experienced founders do not need licensing explained from the beginning; they need the decisions laid out. Run a 90-minute working session around a private six-page workbook, one page per decision about licensing a company's records for AI training, from whether to look at all to what becomes permanent once a deal is paid. Each page names who decides, which is always the company's CEO and never the host, what the founder can answer alone and what only signed documents or counsel can answer. No company data enters the room, the workbook leaves with the founder, and attending implies nothing about fit.
Read → - The data question during an owner's succession plan: a seven-stage permission guide that shows whose yes counts from the first private mention to the month after a sale closes, and when one question is fair
In a succession, the person whose yes counts can change before anyone outside the company notices. Until a successor actually takes office, the current CEO decides whether the company talks to SourceX about licensing its records; from the day the successor becomes CEO, the successor decides. If the succession is a sale, the target's CEO decides up to closing and the acquirer's CEO after it. Raise the question once, only at a stage the owner has opened to you, and leave tax, estate and legal questions to the owner's own advisers.
Read → - The data referral conversation with a client's controller: a four-move controller-to-CEO escalation script that leaves the books and the controller's knowledge where they are, settles your own pay question first and hands the decision to the CEO
A client's controller can be a valuable sponsor inside the company, but the CEO decides whether the company talks to SourceX. So the conversation with the controller has one job: agree how the question reaches the CEO, with nothing from the books attached. Before you mention SourceX, settle your own pay question with the people who can answer it, ask whether the company has already been in touch with SourceX, and keep every figure, export and file out of the exchange.
Read → - The data referral handoff between old and new owners: a two-part owner transition packet, one half kept by the company and one by the partner, so the new CEO decides from dated facts and nothing confidential crosses
When a portfolio company changes owners, a data referral survives as dated facts, never as permission. Split the handoff in two. A company copy, kept by the CEO and passed to the new owners in the ordinary course of the sale, records what was discussed with SourceX, which records were described, which duties apply and the decision now waiting. A partner file, kept by whoever submitted the introduction, holds the dated introduction and the signed agreement. After closing, the acquirer's CEO decides whether anything continues.
Read → - The data referral question for a liquidation advisor: an authorized-owner inquiry checklist that puts one written question to whoever controls the estate, times it around preservation, and treats a recorded stop as a finished answer
Mostly, that the question is not yours to answer. A liquidation advisor works for whoever controls the company now, and SourceX's screening page says of a wound-down company that the CEO may not be enough and the estate's controller decides. The advisor's job is to put one written question to that controller, after confirming through them who holds the records, what preservation duties apply and whether the published fit facts are met, and to record a stop when any of those fails. Nobody opens, copies or moves a record, and nothing about value is promised.
Read → - The data referral questions behind a rapid product launch cycle: a product-history interview that dates the release record before anyone counts launches
A rapid launch cycle shows that a company produces release records quickly: plans, issue histories, test sign-offs, release notes. It does not show that those records fit. Ask the company to date its product history first: when release tracking began, which systems hold it, how many releases it spans, who created the records and whether any belong to customers. A steady twelve-year release history can outrank two frantic years. Fit stays SourceX's decision: 50+ full-time employees at peak, the company's own records, rights and an authorized CEO.
Read → - The data supply conversation for funds focused on enterprise software: a one-page activation brief that starts with how portfolio companies run themselves, not the data their products host
An enterprise software portfolio holds two kinds of records, and usually only one belongs to the portfolio. The data each product hosts is the customers'; a vendor processing it on their behalf cannot offer it. What a software company may own is the record of running itself: support case handling, implementation projects, incident reviews, QA and release histories. Start the data supply conversation there, with companies that reached 50 or more full-time employees at peak, then add two lanes: customers whose CEOs opt in through the vendor, and the enterprise operators the fund already convenes.
Read → - The decision trail is the dataset: approvals, reversals and final outcomes across company systems
A business decision is explained by a chain of records, not one document: the request that started it, the analysis and its revisions, the approval with the approver's authority at the time, any reversal and its reason, the revised decision, and the review that measured what happened. Those records usually sit in four or five systems. A trail is complete when one identifier or reliable cross-reference links all of them, and when version and approval history were kept rather than overwritten.
Read → - The difference between a category bet and a company endorsement: an attribution guide that gives every thesis sentence a level and an owner before it reaches founders or LPs
A category bet is the fund's own claim about where demand is heading. A company endorsement is a claim that a particular company, or SourceX itself, is a fit, a good choice or safe. The two need different evidence and different owners. Before any thesis sentence reaches founders or LPs, tag its level (category, company, program or outcome) and its owner (the fund, a cited source, the CEO, SourceX's published terms, or nobody yet). A sentence that claims more than its owner can support is an endorsement in disguise: rewrite it or cut it.
Read → - The difference between a client benefit and a referral incentive: a two-column disclosure guide that keeps what the company could receive and what you could be paid on separate sides of the page, each traced to its own document
A client benefit is what the company itself could receive: compensation fixed in its own signed Dataset Deal Confirmation if its data reaches Closing, with SourceX running the rights check, preparation and delivery. A referral incentive is what SourceX could pay you under its program terms, separately and never deducted from the company's compensation. The two come from different documents, start at different moments and are decided by different people. Describe each in its own column, and never present your reward as something the client gains.
Read → - The difference between a contact record and a dataset sample: twelve boundary examples that sort what a fund may hold about the person it introduces from anything drawn out of the company's own records, which never passes through the fund
A contact record is what a partner holds about an introduction: the CEO's name, role and business contact details, the company and its domain, and dated facts about who agreed to what. A dataset sample is any piece of the company's own records, however small, redacted or "anonymized": a ticket, a row, a screenshot, a page from a procedure manual. The partner keeps the first, under its own privacy duties. The second never passes through the partner, because the company decides what it shares, and shares it with SourceX directly.
Read → - The difference between a corporate pilot and a referral program: a scope table showing who buys, who signs, whose records move and who can stop each one, so a venture team never runs a SourceX introduction as a pilot
In a corporate pilot the corporate is the customer: a business unit tests a vendor's product in its own operations, under its own procurement and data rules, and decides whether to buy. A SourceX introduction has no customer on the corporate side. The corporate buys nothing, hosts nothing and hands over no records; at most it introduces a company whose CEO then decides, alone, whether that company licenses its own records to SourceX. Run an introduction through pilot machinery and everyone misreads who decides and who pays.
Read → - The difference between a founder yes and corporate authorization: eight Illustrative yeses on a two-axis grid, and the one cell that lets you submit
Permission and authority answer different questions. Permission is a person's consent to what you do with their name and the facts they told you. Authority is the power to commit the company to a licensing discussion, and in this program it sits with the CEO. A founder's yes can carry either, both or neither. Submit an introduction only when the CEO wants the conversation and has approved exactly what you will pass on. Your fund's shares and board seat supply neither.
Read → - The difference between a referral channel and a lead-buying business: a nine-line boundary comparison that shows where a bought contact stops earning credit
A referral channel introduces companies whose leaders already trust you, with their permission, and is paid after the referred company has been paid. A lead-buying business pays for contacts up front and earns by converting or reselling them in volume. SourceX's program works only as the first. No introduction alone creates a fee, credit needs the company's own verified application, and a company that already had any lead, account or email exchange with SourceX is not credited. A firm that buys lists takes on the cost without the credit.
Read → - The difference between a referral fit check and buyer acceptance: an eight-rung evidence ladder from your first screen to the Acquisition Partner's written selection
A fit check is your own screen of a company against SourceX's published criteria, and it promises nothing. Buyer acceptance is the Acquisition Partner's final written acceptance of a complete, validated dataset, which the program terms define as unconditional selection under the data license. Six stages sit between the two, each owned by someone other than you. Report a portfolio company's status by the highest rung it has reached, and never describe a fit check as acceptance.
Read → - The difference between a stalled referral and a closed one: eight first-match rules in which only a dated event from the CEO, SourceX, a recorded payout or the calendar closes a record, and silence never does
A referral is closed only when someone entitled to end it produces a dated event: the CEO declines or withdraws the company, SourceX reports an outcome such as no credit after duplicate review, a canceled reward or a deal that did not close, the dashboard records the reward as Paid, or 90 days pass after the recorded introduction with no verified application. Every other quiet referral is stalled: still open, with a step somebody holds. Silence, a long review and your own impatience close nothing.
Read → - The difference between a useful signal and an assumed dataset: a signal-versus-verified fact table that turns nine common clues into questions a known contact can answer
A signal is something you observed about a company, with a source and a date. An assumed dataset is the story built on top of it: "340 staff, 25 years of records, a huge CRM." Only the company can turn a signal into a fact. Write down what you saw, turn each assumption into a question, ask someone you already know there, and introduce the company only when confirmed facts, a plausible fit and the CEO's interest line up.
Read → - The difference between a warm contact and an authorized contact: a five-turn conversation guide that turns a friendly client contact into a route to the CEO's own yes
A warm contact is anyone who trusts you enough to take your call. An authorized contact is the person who can open a data licensing discussion for the company, and under SourceX's program that is the CEO. Warmth earns you a conversation; authority decides whether there is anything to introduce. Use the warm contact to learn who decides and whether that person wants to hear more, then introduce only the CEO, after the CEO has said yes in their own words.
Read → - The difference between an interesting angle and an unsupported claim: tag every sentence of a referral message by its evidence, then keep, cite, ask or cut
An angle tells a company why a conversation might matter to it, built from a fact you can trace to that company and phrased so the reader can say no. A claim states something as true, and it needs evidence in hand before the message goes out. Edit a referral message one sentence at a time: tag what each sentence asserts, write down the evidence behind it, then keep it, cite it, turn it into a question, attach a condition or cut it.
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