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
- What to do when a client asks the accountant to negotiate: a scope-and-authority handoff guide that keeps you off the deal, names who answers each request, and gives the CEO a one-page note before SourceX's first call
Decline the negotiating role, kindly and in writing, and give the client a clear map of who handles what. You cannot speak for SourceX: its partner agreement says a partner is not its agent and cannot commit it to prices, licenses or payouts. And an introducer who may be paid by SourceX should not bargain for the client over SourceX's terms. The client's CEO negotiates directly with SourceX and signs the company's own Dataset Deal Confirmation, with the company's counsel reading it first.
Read → - What to do when a partner publishes an unsupported superlative: a triage matrix that sorts the claim by whose superlative it is and whether any source could ever back it, and an eight-step correction workflow that reaches every copy within a working week
Treat it as an incident, not a style note. Capture the exact words, then sort the superlative by whose it is: SourceX or its program, the partner itself, a company the partner knows, or the market. For SourceX there is nothing to check against: its program pages publish no rankings, growth rates or partner counts, so the word comes out. A claim about the partner itself survives only with dated evidence already in hand. Then have whoever controls the page fix it, correct every copy, tell anyone who acted on it and log what you did.
Read → - What to do when a partner's tax details are incomplete: a 12-item payment setup check and what an open item does to the 60-day reward clock
Complete them before any reward is close to payable, in the exact legal name of whoever will be paid. Under SourceX's terms, the partner's required payment and tax details are one of the conditions for payment. If one is still open when the 60-day deadline arrives, the reward waits and is paid promptly once you complete it, and no new 60-day period begins. An open item changes when you are paid, not how the reward is calculated, although a missing taxpayer identification number can lead a US payer to withhold part of a payment.
Read → - What to do when a pilot has no completed transactions: a learning review that tags every claim as observed, still open or not yet observable, keeps open companies out of both the win and the loss column, and books the dates they are read again
Treat the zero as what it usually is on a pilot's review date: a count taken before the slowest stages could finish. Write the review from what the record already shows, meaning CEOs asked, CEOs who agreed, verified applications, duplicates, declines and what founders said. List every company still moving as open, neither failed nor nearly won, book fixed dates to read those rows again, and keep revenue and rewards out of the document until a completed handoff exists.
Read → - What to do when someone sends confidential files unasked: a stop-and-escalate procedure that leaves the file where it landed, hands every decision about it to your own policy and counsel, and lets an introduction go ahead only on the CEO's own words
Stop where the file landed. Read no further, forward nothing, copy nothing into a CRM, shared drive or AI tool, and never pass any of it to SourceX or hold it for a referral. Send your own policy owner or counsel a short notice of what arrived and let them decide whether it is returned, deleted or preserved. Tell the sender only that you did not need it. Any introduction then runs on what the company's CEO says for that purpose, because SourceX's published process asks partners for no files.
Read → - What to do with a sub-scale SaaS company that is not growing
A SaaS company that is not growing has five realistic paths: rebuild growth, run it for cash, sell to a consolidator or strategic buyer, merge with a peer, or wind down. Alongside any of them, a company with 50+ full-time employees at peak (contractors excluded) can license years of support and engineering records without selling the business.
Read → - What to do with a windfall in business: allocating one-time license proceeds
Treat a business windfall as one-time capital, not run-rate income: set aside taxes first, restore reserves, weigh debt paydown against reinvestment on after-tax return and risk, and only then decide on owner distributions. For data license proceeds, which arrive as a single payment, write the allocation plan between signing and receipt so the owner commits while decisions are calm.
Read → - What to do with company records when a government contractor loses a recompete
When a contractor loses a recompete, assess its own corporate records before staff leave and accounts close. Government-facing and controlled material is not the company's to license, but finance, HR, proposal and IT history may be. Screen for 50+ full-time employees at peak, rights and a sponsor.
Read → - What to do with old CRM data after a migration: keep, archive, delete or assess
After a CRM migration, decide whether to keep the old system read-only, archive a complete export, delete records under a retention policy, or first assess the multi-year history for licensing. Make that decision before the legacy CRM is switched off, because a complete export with history, files and metadata is far harder to recover afterwards.
Read → - What to do with old PST files before you delete or import them
Inventory old PST files before deleting or importing them. Record each file's location, size, dates and owner without opening any mail, then ask the business owner to decide: import, archive or delete. Surviving multi-year archives may be worth a SourceX data licensing assessment for qualifying companies.
Read → - What to do with questions that require private company context: a public-to-private escalation workflow that answers the general rule in the room, stops before one company's facts are spoken and sends that part to the company's own conversation with SourceX
Split the question. Answer, out loud, the part that holds for every company, from SourceX's published pages, and stop where the answer would depend on one company's records, contracts, customers or numbers. Hand that part back to the founder with a single route: the company's own conversation with SourceX, which its CEO can start by applying, with no files. The host never answers the private part for the room, never writes it down and never carries it to SourceX on the company's behalf.
Read → - What to include in a VC platform's data partnership newsletter: a seven-item editorial-and-disclosure checklist, a four-misreading test for every line and a 400-word budget with no room for a payout headline
A VC platform's data partnership item should carry seven things: one founder question answered from SourceX's published pages, the fit facts with who they leave out, what the fund can and cannot do for a company, the fund's interest, the single route a CEO controls, a date stamp, and a line saying that ignoring the item changes nothing. Then test every sentence against four misreadings: that a company qualifies, that SourceX endorses the fund, that anyone gets priority access to company data, or that the fund decides for a company.
Read → - What to measure in a cross-fund referral pilot: a cohort plan that counts each company once, tracks collisions, founder touches and CEO answers to day 90, and leaves rewards to a read the pilot cannot make
Measure what coordination changes, on a cohort of companies frozen on day 0 and counted once however many funds know them: how often two funds prepared the same ask, how long it took to agree on one introducer, how many investor messages each CEO received, how many CEOs said yes and how many guardrails broke. Read those at day 30 and day 90. Leave rewards out. They depend on acceptance, handoff and payment months after any pilot ends, and estimating them would put a guess at the top of the report.
Read → - What to record when a network contact introduces another introducer: an introducer-chain context ledger with one column per person, covering how each knows the CEO, in what capacity they act, their standing with SourceX and the single role each agreed, so overlaps reach SourceX's duplicate review with one consistent story
When a network contact hands you to someone who introduces companies too, record more than the sequence. For each person in the chain, write down how they know the CEO, in what capacity they act, whether they already hold a SourceX partner account or have raised the company with SourceX before, and the one role each agreed: ask the CEO, submit, or step back. Settle the submitter in writing before the CEO hears anything. Only one introduction can be credited, and SourceX decides overlapping cases from dated records in duplicate review.
Read → - What to say when a business owner tells you they are not ready to sell
When an owner says they are not ready to sell, accept it, ask what would have to change, and offer one useful idea instead of a pitch: established companies can earn a one-time payment by licensing years of operational records to SourceX, without giving up ownership. Ask permission before any introduction, and agree when you will check back.
Read → - What to send before a founder accepts a SourceX introduction: a one-page briefing with your stake in writing, a consent box and a no that costs nothing
Send one page before you ask for an answer: why you thought of the company, what SourceX does and what a first conversation commits the company to, who inside the company decides, what you would earn, exactly what you would pass on if they agree, and three ways to reply, including a no that changes nothing between you. Leave out anything you learned from board materials, any estimate of what the company could earn and any suggestion that it qualifies.
Read → - What to share with a co-investor after a referral is submitted: a status permission matrix that labels every update as your fact, the CEO's fact or SourceX's confidence, stage by stage
Share only what is yours, send the company's news back through its CEO, and keep what SourceX tells you inside your own firm. After you submit an introduction, a co-investor may hear that you made it at the CEO's request, that you are the one contact, and when your part closes. Whether the company applied, what it might license and every figure belong to the company. SourceX's stage codes and estimates reach you under confidentiality and stop with you, and some details SourceX need not give you at all.
Read → - What would disprove your network's data opportunity? A disconfirming-evidence checklist that says whether a finding sinks one company, your network or the whole category
Your network's data opportunity is disproven when the companies you can actually reach keep failing the same necessary condition: too small at peak, no multi-year records of their own, records that belong to clients, CEOs who will not talk, nobody in your network to ask, or companies SourceX already knows. Write each falsifier down before you look, fix how many hits it takes, and record whether a finding sinks one company, your network or the whole category. A single decline disproves nothing.
Read → - What would make this referral channel worth expanding? A remaining-pool scorecard that judges the clients you have not asked yet, not the first ones who said yes
A referral channel is worth expanding when the clients you have not asked yet would be served as well as the ones you started with. Your first introductions came from your strongest relationships and clearest fits, so their results flatter whatever comes next. Score the remaining pool instead: how many unasked clients still pass the fit facts, whether clients found the conversation useful, how many hours each agreed introduction took and whether your professional rules sit comfortably with the reward. Count only rewards actually paid.
Read → - What would prove a highest-paying referral program claim? A dated, repeatable verification standard
Four pieces of evidence, gathered in order and dated: a defined set of comparable programs, each program's written terms saved with the date read, one deal scenario priced under every formula, and data on what each program has actually paid. A headline maximum is none of these. Checked on 2026-10-18, the public record could not support a top-paying claim for any company-data referral program, SourceX included, because no program publishes realized payouts.
Read → - What would prove a venture network is becoming more useful? A falsifiable network-value scorecard with six measures, fixed denominators and the result that would count against each one, written down before the first quarter is counted
Only a result that could have come out the other way. A venture network is becoming more useful when, quarter after quarter, a larger share of its asks give the companies it reaches a quick, clear answer about a real fit, with fewer wasted asks and no rise in complaints, all measured with definitions fixed in advance and with unanswered, declined and failed asks kept in every denominator. This page publishes that test: six measures, a comparison rule and the results that would count against the claim. No network's results are published here.
Read → - When a bespoke large-network arrangement is worth offering: a five-gate commercial review run on dated records, and a written-exception guide for the narrow change that passes
Offer or request a bespoke arrangement only after a network's own dated records pass five gates: enough active introducers, unique companies that pass the fit facts, duplicates caught before submission, screening capacity to spare, and a named problem the default terms leave unsolved. Member counts and logos prove none of these. Most large networks belong on the default Channel Partner Agreement; the few that pass usually need one narrow change, written into an addendum that both parties sign.
Read → - When a board advisor can open the right company door: an eight-point authority and consent checklist that starts with what the seat cannot do, keeps what the role taught you inside it and leaves the yes to the CEO
A board advisor can open the right company door when four things line up. The advisor has a relationship with the company's CEO in their own right. The reason to ask comes from public facts or the CEO's own words, never from anything learned in the advisory role. Every interest the advisor holds, from equity to a possible referral reward, is disclosed in the first message. And the CEO, the only person who decides, agrees in writing. The seat gives no authority over the company, and its confidentiality comes before any introduction.
Read → - When a board network crosses competing companies: a conflict-aware introduction protocol that keeps each company's story in its own boardroom, asks one CEO at a time on public facts and sends the seat questions to counsel first
Treat the two companies as if you knew each through a separate door, because in every way that matters here you do. Each CEO decides alone whether the company talks to SourceX. Neither learns from you what the other is doing, considering or holds, and the reason you give each one comes from public facts or that CEO's own words, never from the other boardroom. Ask one company at a time, disclose every interest, and take any question about your seats or duties to counsel before anything else.
Read → - When a broker's existing engagement limits outside referral fees: a stage-by-stage review of your letter, your license rules and the client's consent before you accept a SourceX reward
Your engagement limits an outside referral fee when its wording, or the rules over your license, reach money paid to you by anyone other than the client. Check four things before you register: a clause making your fee the only pay you take from the engagement, a duty to disclose or credit third-party payments, a transaction definition broad enough to catch a data license, and a license law or association code against undisclosed profit. Then disclose in writing, and leave the licensing decision to the company's CEO.
Read → - When a business changes its customer service model: four directions a service model can move, the question each raises about the history the old model wrote, and why the weeks after the switch suit one question to the CEO
When a company changes how it serves customers, by handing the desk to an outside provider, adding automated channels, moving customers to self-service or giving accounts dedicated teams, its CEO decides who writes the service record from now on and what happens to the record the old model wrote. That makes it a fair moment to ask the CEO one question about material the company's own people created. Ask after the new model is running, through someone the CEO trusts, and never touch a ticket, transcript or call.
Read → - When a business sale falls through: a recovery playbook for owner and advisor
When a business sale falls through, contain the fallout first, then diagnose why the buyer walked before choosing to relist, pause or change path. The systems list, contracts schedule and IP review built for diligence also answer most questions in a records licensing screen, which can produce proceeds while the owner keeps the company.
Read → - When a business standardizes processes across branches: why the program is a fair moment to put one question to the CEO, and a branch-owner discovery worksheet that maps who runs each branch's process without touching its records
Ask the CEO one question, once, after the company has told you about the program and before its busiest rollout weeks. Standardizing processes across branches is a fair moment because the CEO has already sponsored a hard look at how every branch works, and someone now knows which branch runs which process in which system. That makes the licensing question easier for the company to answer, not yours to investigate. Branch managers know their own practice; only the CEO decides whether the company discusses licensing.
Read → - When a client wants the consultant to upload everything: a six-reply redirect script that turns down every upload, login and sample, and hands the CEO to SourceX directly
Say no to the upload, every time, and hand the request back to the person who can decide. Admin rights, backups and a managed services contract let you run a client's systems; none of them lets you send records, samples or logins to SourceX. The company applies itself, with no files, passwords or API tokens, and data moves only after its CEO signs with SourceX. Your part ends at one permissioned introduction of the CEO.
Read → - When a client's archive review raises a data licensing question: an eleven-trigger list that acts only on what the client says or decides, keeps what the files showed you inside the engagement and settles your own pay rules before one question to the CEO
Treat the question as the client's, not yours. An archive review gives a finance advisor a close view of old records, but that view exists for the engagement and is never used to look at, count or describe records for SourceX. Act only on what the client says or decides, settle with your board, professional body, firm or counsel whether you may be paid before SourceX comes up, then answer the CEO's question or ask the CEO one. The CEO decides whether anything follows.
Read → - When a client's contract restricts third-party introductions: split the introduction into four acts, quote the clause that reaches each one in a contract restriction escalation brief, and let your firm's counsel choose a referral, an unpaid mention or no introduction
Stop before you mention SourceX, and escalate. A clause in your engagement letter, master services agreement or a policy it incorporates can restrict an introduction that your professional rules alone might allow: naming the client to an outsider, using what the engagement taught you, accepting value from a third party, or approaching the client about something outside your scope. Quote the clause in the escalation brief below, send it to whoever interprets contracts for your firm, and introduce nobody until it returns with one ending: a referral, an unpaid mention or no introduction.
Read → - When a community moderator should route a question privately: three tests for every post about data referrals, a routing guide for ten kinds of thread, and a private reply that asks for nothing
Move a thread to a private reply when answering it in public would mean discussing one identifiable company: whether it fits, what its records hold, what its contracts allow or what it might be paid. Keep general questions about how the program works in the open, where the answer helps every member and anyone can check it against SourceX's published pages. Remove first and message second when a post exposes something no shared space should hold. A private reply is only a channel: it gives the member routes and asks for nothing.
Read → - When a company asks to withdraw from a referral process: a withdrawal routing and record policy that sends the CEO's stop to the right party at each of five stages, keeps only the dated facts a fund may need and lets only the CEO reopen it
When a company's CEO asks to withdraw, the partner stops at once and routes the request by stage. Before anything is submitted, nothing is sent and the drafts are deleted. After submission, the partner stops all contact and, only if the CEO is content with it, tells SourceX in one line that the CEO asked to stop. Once the company has applied, the CEO tells SourceX directly, because what the company tells SourceX is the CEO's decision. The partner keeps the dates, drops the reasons and never reopens the question.
Read → - When a company brings outsourced work back in-house: an insourcing rights-owner question map that separates the history the company now writes itself from the years still held by its former provider, and leaves the yes to the CEO
When a company takes work back from an outsourcing provider, it starts writing its own records of that work from the day its team goes live, while the earlier years may still sit in the provider's systems. That split is what makes the moment useful for a referral question: the CEO is already deciding what the company should hold and run itself. Ask the CEO, through whoever holds the relationship, which part of the history the company now owns and keeps. The company confirms its rights; SourceX reviews them.
Read → - When a company changes its contact email during review: a verified contact update protocol that confirms the new address through a channel you already trust, lets the company tell SourceX itself and leaves the introduction date where it was
Verify the new address before you use it, and change only your own record. Confirm the change through a channel you already had, such as a call to a number on file or a reply from the old address, never through the new address alone. Ask the CEO to tell SourceX directly, because the company deals with SourceX itself once it applies. Do not resubmit the introduction: its date, the 90-day window and any credit decision stay exactly where they were, and SourceX decides them from dated records.
Read → - When a company changes its domicile during referral review: a nine-line material-change rescreening checklist that logs what moved and what stayed, reads SourceX's published sentence against both homes and hands fit and credit to SourceX with one dated note
A change of domicile moves a company's legal home; it does not rewrite SourceX's rules. When a company you introduced redomiciles during review, write down what moved and what stayed (legal home, the entity holding the records, the CEO, record language, name and domain), read SourceX's published geography sentence against both homes, and send SourceX one dated note. SourceX decides in its own review whether the company still fits and how credit stands. The published terms state no rule for a move, so the partner states none.
Read → - When a company changes its legal name during review: an entity continuity log that proves it is still the company you introduced
A legal name change filed while SourceX is reviewing a company does not make it a new company. The registered entity keeps its rights and obligations under the new name, so the introduction on record, the review under way and its standing as one referred company, with the USD 50,000 floor applied once, stay with it. What a rename breaks is matching: names, domains and email addresses stop lining up. Keep an entity continuity log that ties the old name to the new one through an identifier that did not change.
Read → - When a company controls its software but not its content: six platform-versus-content cases for screening portfolio companies
Then its software is not its dataset. Owning the code, the hosting and the admin console shows who can operate a platform, not who owns the content inside it. SourceX's published screening treats material that belongs to a company's clients as usually not a fit, so a platform company is screened on the records it created about its own work: engineering history, support playbooks, QA and operations records. Set the customer content aside, then let the CEO decide whether to talk.
Read → - When a company has changed its brand but kept its operations: a five-thread continuity sheet to run before you introduce it under the new name
Treat a rebrand as a reason to check, not a reason to assume. If the legal entity, its control, the CEO and the records all carried across, the company behind the new name is the one you knew, and its years under the old name are still its operating history. Confirm each thread from public records and the CEO's own word, and ask whether the company ever dealt with SourceX under its old name: a company SourceX already knew is not credited as new.
Read → - When a company moves from founder-led to professional management: a management-transition authority review that maps what each new manager now owns, keeps the licensing decision with the CEO and waits for the new structure to settle before one question
When a founder-led company builds a professional management layer, more people can tell you about workload, systems and timing, but the person who decides on a licensing conversation stays the same: the CEO. New operating chiefs and department heads are useful contacts once the CEO brings them in; none of them becomes the authorizer, however much of the company they now run. Map what moved, wait for the new structure to settle, then ask the CEO once, naming what changed.
Read → - When a company receives several payments in different periods: a quarter-by-quarter tracker that keeps accrued, received and adjusted amounts apart
Each payment SourceX makes to the introduced company adds its own slice of reward in the period that payment is made: on the company's first qualifying transaction the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, and 15% on each further transaction first agreed within 12 months of the first Closing. The slice becomes payable once the program's conditions are met, and a payment that lands after the 60-day deadline is paid promptly when its conditions are met, with no fresh 60 days. Track four dates for every payment, assign each to a period, and keep accrued, received and adjusted amounts in separate columns.
Read → - When a company registers twice: a five-step duplicate application review that finds the earliest record before anyone argues about credit
A second application does not create a second referral. SourceX's terms count companies, not forms: one partner per company, and a company that already has an application, relationship or earlier valid introduction with SourceX is reviewed as a duplicate and not credited to a later partner. The earliest record therefore governs, and if SourceX knew the company before any partner did, nobody is credited. Your part is to show that both forms belong to one legal entity and to put a date on every record.
Read → - When a company splits customer operations into a new entity: a spinout sponsor and rights map that asks which entity holds each span of case history, whose CEO decides for it, and whether the new entity's work is its own or a service it performs for someone else
Ask about each entity separately, and only once the split has settled. The new customer-operations entity's own CEO decides for it, and the original company's CEO decides for whatever stayed behind. Case history often splits too: years written before the split may stay with the original company, the new entity writes its own from launch, and cases it handles for the original company or outside clients may be those clients' material rather than its own. While both entities sit in one corporate group, they share one reward cap.
Read → - When a company splits its operating and IP entities: a ten-line entity-split introduction review that finds which entity holds the records now, whose CEO decides for them and whether the split is finished, before one question reaches either CEO
When a company moves its intellectual property into a separate entity and keeps trading through an operating company, wait until the split is finished, then ask one question: which entity holds the business records? That entity's CEO decides whether to discuss licensing them. A brand, code or patents moving into an IP entity tells you nothing about where tickets, project files or QA records sit, and nobody outside the company should guess.
Read → - When a company's growth story hides fragmented systems: a risk map of six growth moves, and the two that can delete the history you meant to introduce
Read a growth story as a pointer to where records were split, not as evidence that the company fits. Acquisitions, platform migrations, regional expansion and fast hiring each scatter operating records across tools and legal entities. Scattered systems rarely end a referral on their own, because SourceX manages data preparation. What ends one is history deleted when an old system is switched off, rights left with an acquired entity or a client, or a CEO who does not speak for the entity that holds the records. Map each growth move against those risks before anyone asks the CEO.
Read → - When a consolidator wants to refer several acquired brands: one group, one CEO and one first-transaction floor, plus a brand-entity dataset separation map that decides which brands' records can go forward
Treat the brands as one company with several record sets. The program counts a parent and every subsidiary under it as one referred company, so the USD 50,000 floor applies once, to the group's first qualifying transaction, later qualifying transactions pay 15% with no cap, and the platform's CEO decides for every brand the group owns. What differs by brand is the records: which entity holds them, whether pre-closing history came across in the deal, what contracts limit, and whether any were licensed for AI training before. Map each brand to its entity and datasets first, then make one introduction through the CEO.
Read → - When a consultant is asked to certify ownership: a scope refusal and expert handoff template that declines the signature, keeps the system facts you can state, and names who must make each claim instead
Decline the signature and say who can make the claim instead. A consultant or MSP who runs a client's systems can tell that client what the systems are and how long they have run. It cannot vouch that the company owns the records, may license them, has stripped personal data from them or never licensed them for AI training. Under SourceX's process the company makes those statements itself, in its own signed agreement, after a rights review and with its own counsel wherever something is uncertain.
Read → - When a contact says 'send me something I can forward': a one-page note that still reads right two inboxes later
Send one page that works without you in the thread. It should say who wrote it and that SourceX may pay you a referral reward, why this particular company could fit in two or three facts its CEO will recognize, what SourceX does in one sentence, what is still undecided, and one step the CEO can take or ignore. Put the disclosure inside the note, because the cover email is the first thing a forward drops, and leave out anything your contact told you privately.
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