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 contact wants details you cannot verify: an eleven-question response bank that sorts every ask into answer now, link the published page or hand to SourceX
Say what you know, name what you do not, and route the rest to the party that can answer it in writing. As a partner you can verify the published program terms and what you have seen yourself about the company. You cannot verify what its records would earn, who the buyer is, whether it will be accepted or what a license would contain. Answer the first group from the terms, decline to guess on the second, and offer one route to SourceX's review.
Read → - When a corporate portfolio company is an acquired subsidiary: a six-state mandate screen that shows whose CEO decides, which group counts as one referred company and when the venture team should step back
Ask who owns the company today before asking anything else. While the corporate holds only a stake, the company's own CEO decides. Once a purchase closes, whether the buyer is your parent, an outside group or another portfolio company, the acquirer's CEO decides, and the company joins that buyer's group, which the program counts as one referred company: the USD 50,000 floor applies once and the 12-month Repeat Window runs across the group. If your own parent is the buyer, the venture team stops being an outside introducer: the decision sits with your own CEO, and the idea usually travels inside the group.
Read → - When a CPA firm acquires your fractional CFO firm: re-checking your referrals
When a CPA firm acquires a fractional CFO practice, the CFO team comes under the buyer's ethics rules, attest client list and referral policy. Before and after closing, list every referral arrangement, ask risk management which clients are now restricted, update disclosures, and confirm how SourceX attribution treats introductions made before and after the deal.
Read → - When a CTO intro needs an owner or general counsel: an escalation map that keeps systems questions with the CTO, sends rights questions to counsel and every yes to the CEO
A CTO can tell you which systems hold the company's history, how far back it goes and how hard an export would be. A CTO cannot authorize a licensing discussion: in this program the CEO does, and in an owner-run company that is usually the owner. Escalate to the CEO before the company is named to anyone. Bring in general counsel as soon as a question turns on rights: customer contracts, vendor terms, privacy promises or who owns the material. Everything else can stay with the CTO.
Read → - When a customer asks the vendor to handle the data transfer: a three-level escalation script that keeps you out of the data path
Decline the transfer and keep the route. As the referral partner, your company introduces the customer and stops there: the customer's CEO decides whether to license, the customer agrees scope and terms directly with SourceX, and the customer delivers its own records under its own agreement. If the customer needs help getting its data out of your product, treat that as an ordinary export request under its existing contract, delivered to the customer, handled by support and kept apart from the referral.
Read → - When a customer introduction can become a data licensing introduction: a seven-question permission checklist for platform teams
A customer introduction becomes a data licensing introduction only when three things change hands: the purpose, the person and the evidence. Executives in a fund's customer network agreed to meet vendors, so licensing their own company's records is a new purpose that needs a fresh yes. The contact is often a functional leader, while the CEO authorizes. And the company itself must pass the fit tests: its full-time workforce numbered 50 or more at its peak, it has a documented operating history, it holds rights to license, and it has an authorized contact.
Read → - When a customer success manager spots a potential referral: a three-gate permission and handoff checklist, from the remark you heard to the CEO who decides
Pause, then clear three gates before saying anything. First, the signal must come from what the customer told you, never from looking through its data in your product. Second, only the customer's CEO can decide on a licensing conversation, so ask your contact whether the CEO would want information, and get permission before passing on any name. Third, hand the lead to your partnerships owner with a metadata-only note, step out, and keep the topic away from renewals.
Read → - When a deal falls through but the data conversation remains: a twelve-row reset checklist that sorts what the dead sale ended, what it left running and what only the CEO can renew
Treat the failed sale as a hard reset. Permissions and facts that existed because of the process, such as the owner's go-ahead to mention licensing, a bidder's questions about the archive and everything you learned in diligence, either ended with it or stay inside it. Nothing closed, so the target's CEO still decides. Start a separate conversation: ask that CEO again, let the company describe its own records, and never offer licensing as a way to make up the price the buyer did not pay.
Read → - When a divestiture splits the data and the decision-makers: a sponsor map that gives every separated record set one rights holder, one deciding CEO and one insider who can explain it
Map each record set separately, because a divestiture usually moves the decision before it moves the records. From closing, the buyer's CEO decides for the unit it bought, while the unit's history can stay on the seller's systems for months and the people who understand it may stay with the seller too. For every record set, write down who owns it after closing, whose CEO can say yes, who holds it today and which insider can explain it. Introduce only the sets where all four line up.
Read → - When a finance advisor considers declining compensation: a five-question compensation review decision tree that finds who holds the partner seat, flags pay from both sides of one deal and leaves every verdict with the rule-maker, the CEO or SourceX
Only the bodies that license or admit you, your firm and your own counsel can say when you must turn compensation down, and this page will not guess. What it does is sort the question into five checks: who holds the partner seat, whether you would be paid by both sides of one deal, whether your rule-maker has answered, when that answer is due, and what the client's CEO wants. Declining also changes less than many advisers expect: the company is paid the same amount either way.
Read → - When a finance advisor is also an investor in the client: a dual-role conflict worksheet that lists every hat you wear at the company, what each one gains from a yes and who must hear about both before the CEO is asked
If you advise a company and also own part of it, a data licensing introduction gives you two reasons to want a yes: your shares gain if the company is paid, and SourceX could pay you a reward. Neither role lets you decide, because the CEO authorizes any licensing discussion. Before raising it, list every role you hold, take your independence and pay questions to your own adviser, write both interests into what the CEO reads, and agree a paid or unpaid route the CEO approves.
Read → - When a former employee knows where the archive is: a knowledge-without-access guide that turns a tip into a dated note for the CEO, with no logins, copies or files changing hands
Treat the former employee as someone who can point, not someone who can open. What they remember, such as which system, which years, who ran it and when it might be switched off, belongs with the company's current CEO, and quickly, because archives tied to departed staff often sit on a deletion clock. What they must not do is log in, copy, export or describe confidential contents to you. The company searches, the CEO decides, and an introduction follows only if the CEO wants one.
Read → - When a founder asks who will ultimately use the data: an unknown-versus-confirmed sheet showing what SourceX publishes, what the company's own agreement fixes and what no partner is told
Say what SourceX publishes, and admit what you cannot know. SourceX licenses records from the company, then licenses a de-identified dataset onward to AI developers in its own name, for AI training and evaluation; its investor page lists anonymity for the Acquisition Partners who source data through it. Partners never receive confidential buyer information, so you cannot name a lab. The exact dataset, payout and rights are fixed in the company's own Dataset Deal Confirmation, signed before SourceX presents the opportunity externally. Send everything else to SourceX in writing.
Read → - When a founder community wants a SourceX guest session: five answers to get in writing before anyone is booked, a speaker claims checklist with a published source for every line, and an invitation that brings established companies into the room without a sign-up sheet
Treat it as a question for SourceX, not a booking: none of SourceX's published pages describes a speaker, office-hour or event program. Ask in writing whether it will take part, or have a registered partner speak instead. Brief whoever speaks with a claims sheet where every line has a published source, disclose who could be paid, invite established companies through the people who know their CEOs, and collect nothing but names. A seat never means a company fits; only its CEO decides what comes next.
Read → - When a founder is interested in data licensing but has no spare team: a workload-first expectation worksheet that sets what the founder assumes beside what SourceX's live pages say, names the one person who would carry the company's share and waits for the milestone that frees them
Settle the workload before the introduction, not after it. Set what the founder assumes beside what SourceX's live pages say the company does and what SourceX does, name the one person who would carry the company's share and what they would put down, and find the milestone after which they are free. Then the CEO decides: apply now, apply after a named date, or not at all. Do not fill the gap with fund staff, and do not promise that SourceX will do work its pages do not describe.
Read → - When a founder says the timing is wrong: a seven-question interview guide that finds whose calendar is speaking, offers a clean exit and records only the company's own condition
Treat "the timing is wrong" as a full answer until the founder chooses to say more. Then ask a short run of neutral questions to learn whose calendar is speaking: the company's, the founder's own, or a polite no that is easier to give an investor than a refusal. Offer to drop the idea outright. If a real company event is the reason, write the condition down in the founder's words, leave the revisit with the CEO and send SourceX nothing in the meantime.
Read → - When a founder wants a summary they can share internally: an approved internal briefing template that the CEO edits and owns, labeled for the company only, with SourceX's published facts, your reward stated plainly and nothing the fund knows in confidence
Draft it for the CEO to own, not for you to circulate. Keep it to one page: what SourceX does in its own published words, what the company would decide and who decides it, the published fit criteria, what stays unknown until SourceX reviews, what you may be paid and that it never reduces the company's payment, and where to take questions. Leave out anything you know from board materials, any estimate and any talk of buyers. Label it for the company only, send it to the CEO alone, and let the CEO decide who reads it.
Read → - When a founder wants an anonymous first conversation: an anonymized inquiry feasibility checklist that sorts what a founder can learn without naming the company from what only a named application can answer, and flags the early contact that can turn a later introduction into a duplicate
A founder can learn most of what a first conversation covers without naming the company: SourceX's published terms, its fit criteria, how deals and data handling work, and a preliminary fit check that asks for no contact details. What cannot happen anonymously is anything about this company: an application, a rights review, an offer or credit for an introduction. Run the feasibility checklist, strip identifying combinations from any question that travels, and agree when the founder will be named. Early direct contact can change who is credited.
Read → - When a founder wants to bring counsel to the first call: a 45-minute agenda that names whom each lawyer represents and sorts counsel's questions by when they can be answered
Welcome it, then settle two things before the call: which lawyer is coming and what the call can decide. Company counsel represents the company, which acts through its CEO; a founder's personal lawyer represents the founder; the fund's lawyer represents the fund and does not belong on the call. The first call is a fit conversation in which no records change hands and nothing is signed. Give counsel an agenda that sorts their questions into those answerable today, after review or only in the agreements, and leave once the introductions are done.
Read → - When a fund prefers unpaid introductions: a decision record that tests each reason against SourceX's published terms, lists everyone the preference must reach from partners to scouts, and keeps the founder message true
A fund can introduce companies without anyone being paid, but the preference holds only if it reaches everyone who might otherwise register, from investment staff to venture partners, scouts and advisors, and only if it is written down before any founder hears about SourceX. The cleanest unpaid route has no partner at all: the founder applies on the company's own. Because SourceX pays any reward separately, the company receives the same amount either way, so going unpaid settles the fund's position, not the company's economics.
Read → - When a lawyer's client asks about the referral reward: a written client explanation drafted from SourceX's published terms, read by ethics counsel before it is sent, that answers what the terms can and leaves blank what only your rules can settle
Answer in writing, and only once your ethics counsel has read the answer. A client who asks about the reward is asking three things at once: who pays you and how much, whether the company loses anything, and whether your advice can still be trusted. SourceX's published terms answer the first two. The third, and whether you may take a reward at all, belong to your state's rules and your ethics counsel. The explanation sheet below keeps those parts apart, and every route it offers ends in a referral, an unpaid introduction or no part at all.
Read → - When a network has plenty of contacts but no suitable companies: a six-gap no-fit diagnosis and the stop rules that end the search
Treat an empty shortlist as a diagnosis, not a verdict on your network. When many contacts yield no suitable company, one of six gaps usually explains it: the companies are too small or too young, your contacts sit far from the CEO, the valuable records belong to someone else, the companies are outside the eligible geography, SourceX already knows them, or the relationship owner will not ask. Name the dominant gap, apply a stop rule, then change where you look or stop.
Read → - When a network's reach is large but its fit is low: an eight-stage funnel from audience to askable CEO, and the point at which a firm should stop broadcasting
Expect it, and plan around the tail rather than the total. Most businesses are tiny: the SBA's Office of Advocacy counts 36.2 million small businesses, and only 17.7% of them have any paid employees. A network built on small-business relationships will hold few companies with 50+ full-time employees at peak. Run the reach-to-eligible-company funnel on your own records, work the narrow tail personally, and do not broadcast a reward offer to an audience that mostly cannot take it up.
Read → - When a partner claims its network is the fastest growing: a comparison universe substantiation plan that asks fastest among whom, measured how, over which dates and checkable by whom, and replaces the superlative with a dated fact
Treat "fastest growing" as a comparative, measurable claim: it needs a named comparison universe, one metric, a fixed period and evidence any reader can check. SourceX publishes no growth figures, and its program documents rank no partners, so a claim of rank inside the program, or any superlative about SourceX itself, has nothing to rest on and should be struck. A claim about your own network in general needs public, checkable evidence and your counsel's review, and should sit apart from anything about SourceX. Most partners are better served by a plain, dated fact about themselves.
Read → - When a partner leaves the fund with an active introduction: a departure attribution handoff protocol that reads each open introduction's capacity from the record, hands the CEO contact, board seat and login to named people, and sends every money question to the fund's own papers
When a partner walks out with an introduction still open, nothing about the introduction moves on its own. Credit stays wherever SourceX's dated records put it, with the party named on the signed agreement, whether that is the fund entity or the partner personally. What the fund has to move is everything around the introduction: the CEO's contact, the board seat, the login and notice inbox, and the partner's working notes. Sort each open introduction by the agreement it sits under, hand each piece to a named person in writing, and ask SourceX about whatever the published terms leave open.
Read → - When a partner network grows faster than review capacity: an arrival-rate model that shows the month your backlog starts, and the recruiting pause that prevents it
When proposals arrive faster than your team can review them, the backlog grows every month and each new partner makes it worse. Estimate arrivals as enabled partners times the proposals each sends a month, estimate capacity as review hours divided by hours per review, and divide the first by the second. Keep that ratio under about 0.8, our planning margin, by pausing recruitment, improving proposals or adding hours, and place your review before the introduction so a queue never spends a company's 90-day window.
Read → - When a partner program needs qualitative research first: a research-before-test decision guide that sorts each conversion problem by whether you know its cause and can count its outcome, worked on registered partners who never make an introduction
Do qualitative research first when you cannot yet say why a problem happens, cannot name two truthful versions that each answer a known cause, or cannot define the outcome so two people would score the same case the same way. Run a test first only when the cause is known, both versions are truthful and the outcome can be counted inside the 90-day attribution window. A test run too early compares two guesses and spends the sample. No interviews have run under the plan below; no findings are published.
Read → - When a partner uses outdated broker language: a direct-licensing terminology review that finds the listing, buyer, commission and non-circumvention words in a partner's materials, tests each one against the signed agreement and replaces it before the next company reads it
Replace it before the next company reads it. Broker vocabulary (our buyers, list your data, my commission from your sale, non-circ protection, an exclusive mandate) describes a role the Channel Partner Agreement does not give a partner. SourceX licenses directly from the company, pays the company itself and pays any reward separately; the partner makes introductions, is not SourceX's agent and binds no company. Test each phrase against the sample agreement and the terms, swap in direct-licensing wording, and tell anyone who received the old version.
Read → - When a partner's landing page implies guaranteed acceptance: an acceptance claim correction guide that names the gate each promise skips, rewrites it in words SourceX's own documents support and logs the fix
A partner's landing page implies guaranteed acceptance, a yes no partner can give, whenever its words, numbers or design tell a company that applying through the partner ends in approval: "pre-approved", "fast-track", "your company qualifies", an acceptance rate, a fit score shown as a verdict or a payout shown as an outcome. SourceX's sample partner agreement says "Qualification does not guarantee a transaction." Find each implied promise, name the gate that really decides it, rewrite it in words SourceX's published pages support and keep a dated record of the fix.
Read → - When a passing test misses a customer dependency: a worked network change acceptance exception
The records that explain an exception are the ones that show the gap between "the test passed" and "the customer was fine", and how the operator closed it: the change request with its impact analysis, the test results the approver relied on, the engineer's maintenance notes, the incident ticket, the configuration backups compared afterwards, the emergency change and the review that updated the test template. An approval alone proves only that someone signed.
Read → - When a pilot needs a holdout group: a six-question feasibility tree that decides whether anyone should be held back, separates what a holdout may withhold from what it never can, and names the design to use when the answer is no
A pilot needs a holdout only when four things hold at once: it asks whether an activity changed what people did, the outcome could plausibly happen without that activity, the activity can be withheld without withholding anything a CEO or partner is owed, and the held-back group can stay apart until the reading date. If any one fails, a holdout adds cost and no truth. Run a feasibility pilot, a delayed-start group or a dated before-and-after log instead, and say plainly which limits remain.
Read → - When a portfolio company asks whether the fund benefits: a five-pocket answer that follows every route by which money or information could reach the fund, from a referral reward to what the fund would see about the deal, in words the founder can check
Answer in writing, one pocket at a time. The company's payout is the same whether or not anyone is credited as its partner, because SourceX pays any referral reward separately. A reward goes only to whoever signed SourceX's partner agreement and is credited: a fund entity, one named person or nobody, with any onward flow set by the fund's own documents. The referral adds nothing to the fund's shares. Any stake in SourceX is a separate fact to state. A fund that is the partner would see its reward, which moves with the payout.
Read → - When a professional cannot accept a success-based reward: an unpaid alternative pathway keyed to the point at which the answer arrives, before you register, after you introduce or while the company is in review, with the company paid the same on every route
Whether you may accept a referral reward is for your own counsel, employer or professional body; this page starts once their answer is no. A SourceX reward is success-based: it exists only if the company licenses data and is paid, often long after the introduction. So find where you stand on that timeline first, then take the route still open at that point: an unpaid introduction with SourceX's written answer, a public pointer the CEO acts on alone, or no part at all. In every route the company is paid the same.
Read → - When a professional's employer must approve referral activity: eight trigger facts that bring your employer's policy into play, an approval request that offers four defined answers, and a dated reply before you register
SourceX's terms do not decide this; your employer's policy does, and for some licensed roles a regulator's rule sits beside it. Make the employer's written answer your first step whenever the company is your employer's client, you know its CEO through work, you would use firm time, email or title, your contract has outside-activity or third-party pay clauses, or you are registered with FINRA. Ask in a request that offers four answers: the firm takes the partner seat, you do with conditions, you introduce unpaid, or you take no part. Register after the reply.
Read → - When a promised feature reroutes the approval: a worked nonstandard contract approval case
The records that explain a contract exception are the ones that show its shape: the original approval route, the term that broke it, the recall and resubmission, each new approver's decision and condition, the executed order, and a note on what happened after signing. A discount approval on its own records a number. A nonstandard approval records a judgment, and the sequence below shows where that judgment lives and which system keeps each piece.
Read → - When a referral candidate already works with another licensing provider: nine screening questions that show which records are still free, asked of the CEO and never guessed from a press release
Do not drop the company, and do not pitch over the other provider. What matters is which records the existing deal covers and what it promised about the rest. SourceX asks suppliers to confirm their data has not been licensed for AI training before, and its own licenses are exclusive for AI training, so anything already licensed for that purpose elsewhere is out. Records the other deal never touched may still be offered if its contract allows it. Ask the CEO, let counsel read the contract, and introduce only on the CEO's yes.
Read → - When a referral has no named next-step owner: a four-question triage that finds whose side the stalled step sits on, and an owner-and-date register that counts an owner only once they have said the step is theirs
When nobody owns the next step on a referral, nothing pauses: the 90-day attribution window keeps running from the recorded introduction, and the CEO's interest cools. Find the last dated event, decide whose side the next step is on, and act only on your own side. A step at your firm gets a named colleague who acknowledged it in writing, and a date. A step at the company belongs to whoever the CEO names, so you ask the CEO once. A step at SourceX is SourceX's; you read your dashboard and never fill the gap yourself.
Read → - When a referral includes third-party confidentiality terms: a counsel escalation trigger sheet that shows which clauses stop you before you speak, which questions belong to the company's counsel, and which facts may travel at all
Sort the terms by whom they bind before anyone speaks. Terms that bind you or your fund, such as a deal-process NDA, an investor-rights confidentiality clause or a co-investor's memo, go to your own counsel before the company is mentioned to anyone, SourceX included. Terms that bind the company's records, such as customer, vendor or employee obligations, belong to the company's counsel and SourceX's rights review; you never read or forward them. Only the CEO's own words and SourceX's published facts travel, and SourceX's partner agreement gives you no authority to share a company's records.
Read → - When a referral link is used across multiple campaigns: a company-level measurement design that shows which campaign produced introductions, without touching credit
A referral link used across several campaigns tells SourceX that a company arrived through you. It cannot tell you which campaign worked, and no campaign decides credit. Credit goes to the first valid introduction of a new company when it submits a verified application within 90 days of the recorded introduction. To learn which campaigns to keep, measure at the company level: log every send by company and date, turn interested companies into dated written introductions to the CEO, and read outcomes from your dashboard.
Read → - When a referral moves between partner managers: a manager transfer checklist keyed to the stage the referral has reached, a six-point read-back before the switch, and five parts of the record that no reassignment can touch
A reassignment inside your firm changes who does the work, never the record. The partner of record, the introduction evidence, the 90-day window, the scope of the CEO's permission and the reward basis all stay exactly where they were. Move the referral on one dated transfer entry, have the receiving manager read the file back before the switch, check what your CRM carried across and what it left behind, and tell the CEO only if the CEO was expecting to hear from the outgoing manager. Nobody re-asks, re-introduces or resubmits.
Read → - When a referral moves from an angel network to a platform team: a ten-line transfer checklist that first asks whether the angel already introduced the company, then carries the CEO's own words across and leaves the network's screening notes behind
Credit does not travel in a handoff. SourceX credits the first valid introduction of a new company by a partner who has signed the Channel Partner Agreement, once the company files a verified application, and the terms describe no way to pass that credit from one partner to another. So before the platform team does anything, find out whether the angel already introduced the company. If so, the team supports and never re-submits. If not, the CEO picks one messenger, and the transfer carries only what she has said.
Read → - When a referral partner should end the conversation: a stop checklist of seven no-fit facts and five no-consent signals, any one of which ends the ask on the spot
End the conversation the moment you learn a fact that rules the company out, or hear that its CEO does not want it. The facts are few: full-time headcount that never reached 50, records that belong to clients or were already licensed for AI training, an earlier relationship with SourceX, the wrong geography or language, a one-off file, no operating history. The consent signals are plainer still: a no, a refusal to involve the CEO, a suggestion to go around them. Persuasion fixes neither, so stop asking.
Read → - When a referral program distracts from core portfolio support: a stop-or-rescope worksheet built on five displacement signals
A referral program distracts when it takes the hours, asks or goodwill that founders' own requests need. Check five signals in records you already keep: core requests waiting longer, the program's share of platform hours outrunning the share of founders it can serve, conversations the platform starts rather than founders, relationship owners declining to ask, and any founder who felt pressed. One signal means rescope. Two or more for a month, or one harmed relationship, means stop. Referral income counts as zero.
Read → - When a referral program should remain a small optional service: a four-step guide that names the evidence for each step up and the trigger that sends the service back down
Keep a data referral program small and optional when your clients have not asked for it, one person can carry it in a few hours a quarter, and nothing an expansion would add changes what SourceX pays or decides. Small means a one-page policy, one named owner, the subject raised only at defined client moments, and no marketing. Expand only after a pilot shows CEOs who wanted the conversation, more than once, at a cost the firm could carry if no reward ever arrived.
Read → - When a referral relationship must be disclosed in writing: a disclosure-format review checklist that asks your reviewer for the form, the moment, the signature and the record in each channel you use, before any message names SourceX
SourceX's program terms and its sample partner agreement set no format for telling a client about your referral relationship. Whether it must be in writing, signed by the client, given before the introduction, repeated later or shown inside a public post is decided by the rules that govern you and by the channel you use. So ask your reviewer something narrower than "must I disclose?": in what form, at what moment, with whose signature and kept where, channel by channel, before any message names SourceX.
Read → - When a regional partner shares outdated country criteria: a five-step correction loop that answers with the live page and the date you read it, asks the sender to retire their own copy, and never fills a gap with a rule of your own
Correct it with the live page, not with a better summary of your own. SourceX's current country criteria are the sentences on refer.sourcex.si/who-qualifies as they read today; a forwarded slide, last quarter's one-pager or a chat message is a copy that may have aged. Send the regional partner the live sentence and link with the date you read it, ask them to date and replace their own copy, help them reach whoever received the old line, and leave each company's fit to SourceX, which applies the criteria of the specific program.
Read → - When a reseller and a SaaS vendor both know the customer: a seven-step coordination protocol that names one introducer before anyone contacts the CEO
Decide between yourselves, in writing and before anyone contacts the customer, which firm will make the introduction, then send one message to the customer's CEO that names both firms' roles and any referral interest. SourceX credits a single partner per referred company from dated records, so two parallel introductions earn nothing extra and can stall in duplicate review. Neither firm uses product data, admin access or usage analytics to choose the customer. The customer's CEO decides, and the customer applies itself.
Read → - When a reseller wants to refer its customer network: an opt-in pilot plan that announces the fit tests once, lets each customer's CEO raise a hand, and introduces willing companies one at a time, never as a list
Run an opt-in pilot, not a list upload. A reseller's customer list, the license data in its vendor portals and the admin access it holds can suggest which customers might fit, but none of them lets the reseller license a customer's records or speak for the customer. Tell customers once what SourceX looks for, let each CEO who is interested come forward, and introduce each willing company separately, in that CEO's words. Every customer is its own company, with its own CEO, its own fit test and its own attribution window.
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