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
- How to keep a co-investor's confidentiality promise intact: a twelve-item disclosure boundary checklist that tags every fact by where you learned it and whose promise it would break on the way to SourceX
Treat whatever a co-investor told you about a company as information still bound by the co-investor's promise to that company, not as yours to pass on. Before a SourceX introduction, tag each fact by where you learned it. Public facts, and what the CEO tells you directly, can travel once the CEO agrees to be introduced. Anything that reached you through the co-investor, its board seat or its diligence stays behind unless the co-investor and the CEO both say otherwise.
Read → - How to keep a data introduction separate from an audit engagement: an engagement separation review map that tests the idea's source, the people, the channel, any pay and the records, before anyone at the firm mentions SourceX to the CEO
Treat the audit engagement and any data introduction as two files that never merge. Nothing learned through engagement access or audit evidence may be used to pick out a company or describe its records; an introduction can rest only on public facts or on something the CEO raised outside the work. Before pay is even considered, the rules that bind you for this client decide whether you may take part at all. Ask your board, society or counsel, because nothing on this page is legal or professional-conduct advice.
Read → - How to keep a referral pipeline current with limited staff: a date-filed upkeep routine in which every fact gets a check-by date when it is written, only the records due today are opened, and anything that arrives is filed the same day
Give every fact in a referral record its own check-by date at the moment you write it, and open a record only when one of those dates arrives or something new comes in about it. The 90-day attribution window, the CEO's latest answer, the next action and SourceX's dashboard status each go stale on a different clock. A ten-minute pass through the facts due that day, plus filing anything that arrives on the day it arrives, keeps a small pipeline current without anyone rereading every row.
Read → - How to keep AI note-taking from expanding a referral's audience: a meeting capture permission checklist that finds every copy a note-taker makes, who receives it by default and which company details never enter the note you share
Settle the capture rules before the call, because a referral's audience is the set of people the CEO agreed to speak with, and an AI note-taker can widen it without anyone deciding to. Depending on settings, a summary can email itself to every invitee, post to a group chat or sit beside a transcript that anyone invited can open. Name every capture tool on the call, keep company detail out of anything shared, and have a person, not the summary, write the one note the next step needs.
Read → - How to keep board pressure out of a voluntary introduction: a conversation guide that keeps six investor levers out of the ask and makes a no cost the founder nothing
Keep the ask away from every lever your fund holds over the company. Raise it outside board meetings and outside any financing, follow-on or consent decision, say in the same breath that a no needs no reason and changes nothing, disclose the reward you could earn, ask once and treat silence as a no. A board seat gives you a voice in the boardroom, not authority over this choice: the CEO decides whether the company talks to SourceX, and an introduction the CEO did not choose is usually not a fit.
Read → - How to keep campaign tags separate from reward attribution: a two-ledger table for partners who put UTM tags on their SourceX link
Treat campaign tags as your own marketing measurement, and the dated introduction as the only record that matters for a reward. UTM parameters show which newsletter, post or webinar carried a visitor to SourceX; credit for a company is decided from dated records, including written introduction evidence, existing applications and preexisting relationships, and an earlier link click alone does not decide it. Keep two ledgers: an analytics ledger you may tag, remodel and reorganize, and a contract ledger of dated introductions you never edit.
Read → - How to keep custom terms from confusing standard partners: a five-segment communication plan that tells each partner only the terms that govern them
Publish one default and keep every custom term inside the signed documents of the partner it belongs to. Segment partners by the document that governs them, not by status or size: not yet signed, standard, earlier-title agreement, signed exception, and departed. Each segment hears only its own terms. Shared decks, group chats and leaderboards carry the published default and the line that a signed Schedule A or addendum can differ, and never another partner's numbers.
Read → - How to keep existing commercial deals separate from referral rewards: a boundary ledger that gives each contract with the company its own row, its own signers and no line into the reward
Keep three deals on three rows and never let a term in one depend on another. The corporate's supply, sales, pilot or investment agreements with a company live in their own papers. The company's license lives in its Master Supplier Licensing Agreement and Dataset Deal Confirmation with SourceX. Any reward is SourceX's separate obligation to the registered partner under Schedule A. No price, renewal, discount or invoice may move because the company licenses, and nothing for the partner comes out of the company's agreed compensation.
Read → - How to keep international payout expectations conditional: a payment-condition guide that gives a cross-border network one sentence per stage, ties each to SourceX's published terms and adds nothing on tax, currency or timing
Say only what SourceX's terms say, in the order they say it. A reward exists only if a company you introduced is credited to you and completes a qualifying, paid licensing deal; by default it is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, on the company's first qualifying transaction, the USD 50,000 floor counting once for the company and its corporate group, and it becomes payable only when every condition in section 5 of the terms is met. Across borders, add nothing: no tax treatment, no currency or exchange rate, no timing beyond the terms. Tax questions go to each person's own adviser.
Read → - How to keep investment memos out of referral workflows: a source-separation operating guide that maps every memo section to the referral steps it must never reach and rebuilds each referral fact from what the CEO says for that purpose
Treat the memo as a closed document. Nothing in it travels into a referral note, an introduction email, a tracker field, a portal submission or a conversation with SourceX. A memo blends diligence received under confidentiality terms, board and information-rights material and the fund's own judgments, and a referral needs none of it. Rebuild the few facts an introduction uses from what the company's CEO says for that purpose and SourceX's published criteria, and let the CEO decide what the company tells SourceX. Fund counsel decides what the fund's agreements allow.
Read → - How to keep IT systems running in an ABC or receivership, and who must approve it
In an assignment for the benefit of creditors (ABC) or a receivership, the assignee or receiver controls the company's IT systems, so only they, acting under state law and any court order, can approve keep-alive spending, system access or a records assessment. Decide early which systems hold years of records, because subscriptions lapse on billing cycles, not court calendars.
Read → - How to keep ownership of your company data when you license it
You keep ownership of company data in a license by granting a limited right to use it instead of assigning or selling it. The agreement should state that title stays with you, limit use to AI training, set a defined term, bar resale and free sublicensing, and keep confidentiality and deletion duties. Nothing binds you until you sign.
Read → - How to keep partner pages aligned with current program terms: a page-to-terms audit worksheet that ties every program sentence on your site to a numbered section and a dated version, so the next terms update finds your stale lines before a company does
Treat every program sentence on your site as a citation. Next to each one, record the section it rests on and the terms version you checked (currently Version 2026-11-04, published 4 November 2026), replace your own summary of the economics with the verbatim offer block, and delete any rule you cannot find in the terms, the who-qualifies page or your signed agreement. Run the check again whenever the version line changes. Editing your page never changes a signed agreement, and an old page never changes the terms.
Read → - How to keep privileged material out of data referral discussions: a privilege-preserving introduction checklist for the six places matter material slips into a referral, from where the idea came from to the introducer's own notes, with the company's counsel deciding what counts
Keep the referral to facts the CEO would state in an ordinary business conversation, and send everything else back to the company's counsel. Privileged and matter material slips into a referral in six places: where the idea came from, the introduction message, the first call, documents someone volunteers, the introducer's own notes and the company's application. The checklist below sets two checks at each, names what can travel instead, and leaves every judgment about what is privileged with the company's counsel, which is how SourceX's own guidance on legal material reads.
Read → - How to keep referral incentives transparent in a member newsletter: disclosure placement examples for nine spots in an issue, from the subject line to a forwarded copy, and the four facts every disclosure carries
Put the disclosure inside the item that mentions SourceX, next to the reply instruction or link, in the same type as the item, and carry it wherever the item travels: web archive, digest, social excerpt or forwarded copy. Say who could be paid, that SourceX pays it, what has to happen first and that none of it comes out of the member company's compensation. A footer, a sponsor page or a link to the association's policy can back the disclosure up, but none of them carries it alone.
Read → - How to keep referral notes out of client support tickets: a separate-workflow documentation guide that says what each system may record, which fields the referral log holds and how to repair a note that already slipped into a ticket
Give the introduction its own record and keep it out of every client system. A ticket belongs to the client's service history: depending on the tool and how it is set up, a note can appear in the client's portal, print on an invoice, or sit in front of every agent who opens the ticket, the client's own staff included. Write only service facts in tickets. Record the referral in a partner log that two named people at your firm can open, and never write the client's record counts, files or value guesses anywhere at all.
Read → - How to keep referral rewards out of investment selection: a separation-of-decisions control map for the six fund decisions a reward could tilt, from screening a new deal to backing a follow-on, with an owner and a dated record for each control
Treat a possible referral reward as an interest that must not reach any investment decision. Write down who at the fund could receive one, then put a control on each decision it could tilt: deal screening, the investment memo, use of diligence material, follow-on and reserve calls, platform support, and any look at SourceX itself as an investment. Give each control an owner and a dated record. Fund counsel decides whether disclosure, separation or taking no rewards at all is enough.
Read → - How to keep the licensing conversation from disrupting the sale: a two-track timeline that sets each SourceX step beside the deal calendar, an eight-week rule for signatures and the crossings that need the CEO or counsel
Give the licensing conversation its own track and let it touch the sale only where the target's CEO approves. Steps that bind nobody, a no-files application and an inventory call, fit before marketing begins. SourceX's two signatures, the Master agreement and a Dataset Deal Confirmation, create a contract and an exclusive license for AI training on the selected data, so place them before the letter of intent with deal counsel informed, or after closing, when the acquirer's CEO decides. Material from the data room never crosses between the tracks.
Read → - How to keep Xero records after a business closes or ceases trading
To keep Xero records after a business ceases, export the full ledger, reports, contacts, invoices, bills and attachments to company-owned storage before the subscription is canceled, since post-cancellation access depends on Xero's current terms and should not be relied on. Then record who controls the archive: the directors, an assignee, a receiver or a bankruptcy trustee.
Read → - How to label estimates in a founder referral brief: an estimate-versus-observed field guide that catches the real number measuring the wrong thing
Label each number by how it was produced, not by how confident it sounds. A figure counts as observed only when a named person at the company read it from a named source on a stated date, and it measures exactly what the fit check asks. Everything else is an estimate: write it as a range with its method, its inputs, the assumption that moves it most, who made it and when. Keep that label through every forward, and attach no records.
Read → - How to limit access to referral notes inside a fund: a role-based access design brief that splits every introduction's notes into five layers, gives each role only the layer its next decision needs and leaves board knowledge out of all of them
Treat referral notes as five layers rather than one file: the introduction record, the internal approval, SourceX's updates, counsel's file and the payment file. Give each role in the fund the one or two layers its next decision needs, and nobody any layer by default. SourceX's sample partner agreement lets confidential information go only to people who need it for the referral and are bound to keep it confidential, and what the fund learned through a board seat belongs in no layer at all.
Read → - How to liquidate a company with no physical assets, and where its records fit
Liquidating a company with no physical assets means realizing intangibles: collect receivables first, then market contracts, code and IP, domains and trademarks, and operational records. Records are the easiest bucket to overlook. If the company had 50+ full-time employees at peak (contractors excluded), it can license those records to SourceX without disturbing collections.
Read → - How to list data and records in the intangibles section of Schedule A/B
On Official Form 206A/B, list operational records and databases in the intangibles and intellectual property part, usually as customer lists or compilations or as other intangibles. Describe systems and date ranges, state value as unknown unless appraised, and keep personal data off the docket, so a trustee or committee can spot a possible license.
Read → - How to locate the authorized successor to a wound-down company: a successor contact verification plan that confirms each claim from a record the claimant did not write, reaches them on a channel you found yourself, and stops when no claim holds
A wound-down company's authorized successor is whoever controls it today, and SourceX's screening page lists the possibilities: the board and CEO, an acquirer, or a trustee, receiver or assignee in a formal process. Finding a name is only half the work. The other half is proving the claim: confirm the role from a record the claimant did not write, reach the person through contact details you found yourself, get a dated written yes, and stop when no claim survives those checks.
Read → - How to make a referral ask easy to decline: a four-cost audit, a no written for the recipient, and one invitation rewritten for four situations
Ask a question the person can answer in one word, write the no for them ("reply 'not for us' and I won't raise it again"), disclose your reward once as information rather than pressure, and set no deadline of your own. A referral ask is easy to decline when a no takes one short reply, needs no reason and changes nothing else between you. For a SourceX introduction it is also the practical choice: an introduction the CEO did not want is usually not a fit.
Read → - How to make a referral during an ERP migration: two doors, one no-ask stretch, and a migration-window introduction brief that keeps custody, control and the ask on separate lines
Make the referral through the portfolio company's CEO, at one of two doors in the project: while the data migration strategy is still a draft, or after hypercare has ended and before the legacy system is switched off. Between those doors the project team is extracting, loading and reconciling data, and a referral has no place on that critical path. Throughout, the integrator and the data team hold copies, the CEO decides, and the introduction never changes what history is converted, archived or deleted.
Read → - How to make an introduction when you can't accept a referral fee
If your employer, license or court order rules out a referral reward, the route that needs nothing from SourceX registers no partner: tell the CEO that SourceX exists and let the company apply on its own. The published terms do not cover a partner declining a reward, so anyone who wants to submit an introduction unpaid asks SourceX in writing first, and SourceX decides. Auditors, bank staff and court-appointed fiduciaries commonly need this path.
Read → - How to make an introduction without vouching for the outcome
To make an introduction without endorsing, state what you know, say what you do not, disclose any reward, and leave every decision to the recipient. Use verbs like introduce and connect, not recommend or guarantee. With SourceX, nothing is binding until the company agrees price and terms and signs, and no reward is guaranteed.
Read → - How to make sure an owner never feels pressured into a data deal
Avoid pressuring clients by making one clear suggestion, putting the facts in writing, letting the owner control the pace, following up only at points you agreed in advance, and saying plainly that no is a fine answer. Introduce and step back; the owner decides, and your relationship matters more than any reward.
Read → - How to make the introduction useful without overselling the dataset: bound every line by who said it, when and in what unit, with six before-and-after examples
Describe the records the way a reviewer will read them, not the way a pitch would sell them: record type, system, span of years, a rough count, and who told you and when. Leave value, uniqueness, buyer interest and quality verdicts out, because only SourceX's review can establish them. A line such as "about 38,000 closed tickets since 2018 in one helpdesk, per the head of support on 9 October" gives SourceX something to check, and it gives the founder nothing to be let down by later.
Read → - How to map shared companies without revealing dealflow: a company-consented overlap process that starts from what both funds can already see, and lets each CEO, not a list comparison, disclose the rest
Do not compare lists. Begin with the overlap both funds can already see, such as companies whose cap tables you share, and coordinate only on those. Every other relationship stays inside the fund that holds it. If you want to know whether another fund also knows a company, ask that company's CEO, who decides whether to say and who should make the introduction. SourceX will not tell either fund who else introduced a company, so a list match buys little and leaks a great deal.
Read → - How to maximize what you walk away with when selling a business
To maximize proceeds from the sale of a business, work on price, deal structure, taxes and fees, and value outside the sale, in that order. Compare offers on net proceeds, not headline price, and treat any records license as a separate agreement that must be disclosed to buyers and agreed with counsel.
Read → - How to measure a partner benefit without counting every member: an opt-in cohort dashboard of eight tiles, each with a named denominator, and a list of what the association never counts
Measure the members who chose to take part, not the membership. Send one notice, treat everyone who replies as the cohort, and report a few counts about that cohort only: who found the material useful, what each member decided, how many CEOs asked for an introduction and what went wrong. Show every result as "x of n", count complaints from anyone who sends one, and collect nothing about members who stayed silent or about anyone's records.
Read → - How to measure event quality beyond registrations: an attendance-to-consented-intro funnel in which the attendee crosses every stage, every rate names its denominator, and introductions are counted but never targeted
Count what attendees chose to do, over the right denominator, and keep every number the host can inflate out of the quality score. Invitations and registrations measure the reach of the invitation. Quality shows up later: how many attendees asked a real question, how many questions got a sourced answer, how many people asked for a next step and received exactly that, and how many left knowing who decides for their company. Count the CEOs who later ask to be introduced, but never set a target for them.
Read → - How to measure repeated introductions from the same network: a cohort retention report that counts returning introducers, not returning companies
Count returning people, not returning companies. A network repeats when the same introducer, the person who owns a CEO relationship, brings a second new company that reaches a verified application in a later quarter. Re-sending a company SourceX already knows, a renewal by a company introduced earlier and an introduction of a sister entity are separate events with separate rules. Group introducers by the quarter of their first verified application, follow each group quarter by quarter, and print the denominator, the open cases and the quarters not yet observed in every row.
Read → - How to measure the effect of sponsor selection: a sponsor-route comparison that flips a coin only where both routes to the CEO are genuinely open, logs every other route as observed, and counts the ideas that die between an executive and the CEO
Sponsor selection is the choice of who inside a company hears about SourceX first: the CEO, or another executive who then decides whether to carry the idea to the CEO. Its effect can be measured only where both routes are genuinely open; everywhere else the route reflects the relationship, not a choice. Flip a coin for those companies, log the rest as observed, and count CEO decisions, ideas that stall with the executive and CEOs who felt bypassed. The CEO decides on both routes. No results exist yet.
Read → - How to measure whether a tool helps partners find better fits: a baseline-then-split screening study that compares partners with and without a criteria tool on qualified outcomes per company considered, and audits every company the tool led them to set aside
Measure the tool by what happens to the companies partners consider, not by how often they open it. Run every partner without the tool for a baseline period, then give it to a randomly chosen half for a second period. Compare how qualified outcomes per ten companies considered change in each half, and audit every company the tool led a partner to set aside. The tool only restates SourceX's published criteria; partners never upload, scan or score records, and SourceX's review decides fit. No results have been published.
Read → - How to measure whether partners misunderstand the payment trigger: a payment-trigger knowledge survey that pairs each published sentence with its likeliest misreading, counts wrong and unsure apart, and keeps every partner who never answered in the denominator
Ask partners to choose between paired statements, one restating SourceX's published wording and one stating a likely misreading, and count a misunderstanding only when someone picks the misreading; "not sure" is counted on its own as not knowing. Key every pair to the published trigger, a qualifying, paid licensing deal, and to the events the terms say do not make a reward payable. Report every item against everyone invited. No survey has been run, so no rate exists, and this page reports none.
Read → - How to migrate GitLab to GitHub without losing merge request history
You can migrate GitLab to GitHub with merge request history only partly: commits, branches and tags move with Git, while review threads, approvals and pipeline logs depend on your migration tool and often need a separate archive. Take a full backup of the old instance before decommissioning it.
Read → - How to model a one-time receipt, like a data license, in a 13-week cash flow forecast
Keep a possible one-time receipt, such as a data license payment, out of the base 13-week cash flow forecast until the agreement is signed and the buyer has selected the data. Until then, show it in a labeled scenario dated to the expected cash receipt, within 60 calendar days after SourceX receives a valid invoice following Closing, never to the signing date.
Read → - How to model referral income when no deal is guaranteed: a probability-free scenario planner that keeps every amount at zero until a payment condition is met
Model it as named scenarios tied to the program terms, not as an expected value. Give each introduced company a ledger state, keep its planned income at zero until SourceX has paid the company and every payment condition has cleared, and run four cases side by side: zero, delayed, reduced and repeat. If a reward becomes payable, a first qualifying transaction pays the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, and a repeat inside the Repeat Window pays 15%; until then it is a possibility, not earned income.
Read → - How to monetize non-core assets in a mid-sized company: sell, lease or license
To monetize non-core assets, list everything the company owns but does not need for its core business, then choose a route for each: sell, sale-leaseback, lease, license or retire. Real estate and equipment are usually sold or leased; intellectual property and operational data can often be licensed, bringing in cash while the company keeps ownership.
Read → - How to negotiate an AI data licensing deal: priorities in order
Negotiate scope and exclusions first, then rights clarity, exclusivity term, acceptance criteria and payment timing. SourceX licenses approved business data directly from companies for AI training and evaluation as their direct licensing partner, managing the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. The company's own counsel negotiates contract language with SourceX. Nothing is binding until the company agrees price and terms and signs.
Read → - How to nurture business owners who are two to five years from selling
Nurture future sell-side clients with a planned calendar of useful touchpoints instead of check-in calls: a yearly valuation view, a readiness review, and one metadata-only conversation about the company's records. That records conversation can lead to a SourceX data license now, which pays the company without a sale and leaves better-documented systems for a later process.
Read → - How to offboard a partner while preserving active company relationships: a six-stage continuity checklist that leaves credit where the record puts it and gives every CEO one named contact
Offboarding ends a partner's role in your network, not the conversations their companies are having. Before the exit date, list every company the partner touched, sort each by stage, give each CEO one named contact, leave credit exactly where the dated record puts it, and remove the partner's access to shared trackers while keeping the records. Start by checking whose name is on the SourceX agreement, because that decides whether the departing person or your firm stays the credited partner.
Read → - How to offer a data introduction during a backup review: a 15-point backup-owner checklist that keeps the retention decision, the CEO's question and SourceX's review in three separate hands
Finish the backup review first and write its decisions down, then raise the introduction as a separate item for the company's CEO to decide, not the IT lead who booked the review. Describe only what the review already showed, at the level of descriptions: which systems are protected, how many years they reach back, which old backup sets are due to retire. Say that you may receive a referral reward. Run no restores, exports or catalog reports for it. If the CEO wants the conversation, the company applies and SourceX does the review.
Read → - How to offer a referral link without forcing event registration: a choice-preserving call-to-action design in which the seat never depends on the link, the link never depends on the seat, and a click decides nothing
Keep the seat and the link apart. The event is open to everyone, registering takes a name and an email, and it never requires your partner link, a SourceX account or any detail about the company. If you offer the link at all, show it after the content as one of four equal choices: apply to SourceX directly, ask you privately, use your link, or do nothing. Put a sentence beside it saying you could be paid, and remember that a click decides nothing; SourceX decides credit from dated records.
Read → - How to offer a referral program without selling your member list: an opt-in communication design in which the list never leaves the association, members start every step and SourceX hears only from CEOs who asked
Keep the list inside the association and let members come forward. Send one notice through your own channels that describes the program, the published screening facts and any reward the association could receive; allow one reminder at most; then act only when a member company's CEO writes asking for an introduction. Pass SourceX that CEO's own words and contact, one company at a time, and nothing else: no list, no survey answers, no record of who opened the email, no description of anyone's records.
Read →
Free resources
- Business succession planning assessment — Ten questions on successor, transition and documentation.
- NPV calculator — Net present value with a discounted cash flow table.
- Time value of money calculator — Future and present value with optional regular payments.
- All free tools · MCP resource center
Know a company with valuable proprietary data?
Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.
Refer a company →I own a business
Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.
Start an assessment