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 introduce a company for an AI data partnership
Pick a company in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE or Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) you know well, confirm it has documented operations, contact the decision maker personally, explain SourceX in one sentence, disclose your referral reward, and send your referral link for a short assessment. No data changes hands at this stage.
Read → - How to identify valuable proprietary data before making a referral
Ask metadata-level questions about what the company documents, how much, over what period, in which systems and who owns it. Original, consistent, well-maintained, company-owned material is the strongest signal. You never need to see the content.
Read → - 'We need to talk to our lawyer first': how partners should respond
When a client says they need to talk to their lawyer first, encourage it, say you are not a lawyer, share the process facts (nothing is binding until signed, rights are the company's call) and step back. Legal review is a good sign, not a stall, and partners never give legal advice.
Read → - 2021-vintage private equity funds: what to do with companies bought at peak multiples
2021-vintage private equity funds hold many companies bought at high entry multiples with cheap debt, so returns now depend on EBITDA growth and cash rather than multiple expansion. Levers range from pricing and working capital to add-ons, NAV loans and continuation vehicles; for qualifying companies, a one-time data license with SourceX adds capital-light cash.
Read → - 3PL and logistics M&A in 2026: what buyers want and what sellers should preserve
3PL M&A in 2026 rewards specialization: buyers look harder at logistics providers with a defensible niche, sticky client contracts and well-run warehouse and transportation systems than at generalist space-and-labor providers. Sellers should prepare clean WMS and TMS histories and a clear map of which records belong to the 3PL and which belong to its clients.
Read → - 3PL bankruptcy: separating shipper data from the 3PL's own WMS history
In a 3PL bankruptcy, shipper inventory and order data belong to shippers, while the 3PL's own WMS configuration, labor standards and exception-handling history may be estate assets. Restructuring professionals should preserve exports, classify records and obtain estate approval before any introduction to SourceX.
Read → - 3PL roll-ups and WMS consolidation: a data screen for PE operating teams
When a PE-backed 3PL consolidates warehouses onto one WMS, run a records screen before cutover: size, years of WMS and TMS history, linked systems, export owner and customer-contract rights. Qualifying companies with 50+ full-time employees at peak can be introduced to SourceX, which handles inventory, SourceX review and delivery.
Read → - 3PL valuation multiples in 2026: what buyers pay for in a logistics business
3PL valuation multiples are driven by the operating model and its risks: buyers start from normalized EBITDA and move the multiple for asset-light or asset-heavy operations, customer concentration, contract and lease terms, specialization and systems. Separately, a 3PL's WMS and TMS operating history can be licensed to SourceX where client contracts allow.
Read → - A backlog for founder questions your platform team cannot answer: log each one, route it to whoever can, and pause when the queue outruns the program
Most founder questions about data licensing are not the platform team's to answer. Fit with current demand, price, rights, contracts, credit and tax belong to SourceX, the company's counsel or its advisers. Keep a backlog: record each question, answer only from published program facts with the version you read, route everything else to a named owner with a date, and tell the founder who will answer. Log the minutes with income at zero, and pause when questions arrive faster than they close.
Read → - A business broker's guide to conditional referral outcomes: six ways an introduction can end, the condition that decides each, and why no closing, the sale's or the license's, pays the reward by itself
A broker's introduction to SourceX can end in six ways: not credited, lapsed, declined in review, no deal, paid, or paid and later reduced. Each turns on a written condition, and none turns on the business sale. Credit needs the first valid introduction of a company new to SourceX and a verified application inside the 90-day window. Payment needs the Acquisition Partner's final written acceptance, completed handoff, cleared funds, the company's own payout and finance approval. Explain that sequence to the owner before you introduce, not after.
Read → - A business expands into a new product line: is the timing useful? A five-question relevance test that checks whether the launch sent the CEO back to records the company already holds, and says wait when it did not
Sometimes, and usually later than it feels. A new product line arrives with plans, forecasts and new hires, not years of operating records, so it is never the thing a company would license. The expansion helps only when it has sent the CEO back to what the existing lines already hold, such as procedures being rewritten to train the new team, and the launch rush is over. Run the five questions below first; if any of the first three fails, treat the expansion as news and wait.
Read → - A business introducer's guide to operational data licensing
As a business introducer, you connect 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) with SourceX for operational data licensing to SourceX. Your reward on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap—Actual Supplier Payout being the eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements. Each further qualifying transaction first agreed within 12 months of the first qualifying Closing pays 15%, and a transaction qualifies with an Actual Supplier Payout of at least USD 100,000 unless SourceX agrees in writing, subject to program conditions and any signed Schedule A or addendum. 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. SourceX funds rewards separately; they do not reduce the company's payout.
Read → - A business reopens after dormancy: what has changed? A ten-question resumption facts and authority checklist that tests whether the company that reopened is the one that closed, who decides for it now and which of its old records came through the quiet years
Five things may have changed while the business was closed: who owns and runs it, whether the company that reopened is the same legal entity, where its pre-closure records spent the quiet years and whether they survived, whether it had contact with SourceX before it closed, and whether anyone licensed or sold its archive in the meantime. Confirm each with the CEO, let the restart settle, and only then ask one question. SourceX's published screen reads size at its peak and looks for years of the company's own records; how a closed stretch counts is for SourceX's review.
Read → - A business with years of support records may be worth a conversation: eleven call prompts that take a public clue to a permission ask, or to a polite close
A public sign of long support history, such as a help center with articles dated a decade back, is a reason to ask someone you already know a few questions. It proves nothing about whether tickets were kept, who owns them or whether anyone wants them. Use the clue to open a metadata-only conversation with a known contact, confirm the facts with whoever administers the support system, ask whether the CEO wants a conversation, and close politely when the answers show no fit.
Read → - A buyer's acquisition thesis does not establish data rights: a five-test screen that sorts each data line in the deal memo into documented, assumed or contradicted before anyone mentions licensing
A buyer's acquisition thesis is a forecast written by a party that, until closing, neither owns the target's records nor runs the target. It can argue the records are valuable; it cannot show who holds the rights to them. Rights turn on who created the records, what the signed deal documents convey, what the target promised its customers and whether the data was ever licensed for AI training. Until closing, only the target's CEO can agree to a licensing conversation; afterward, the acquirer's CEO decides.
Read → - A Canadian MSP's route to introducing an eligible operating company
A Canadian MSP introduces an eligible operating company by confirming four things from what it already knows (full-time headcount, years of records, which systems hold them, who owns the business), getting the owner's opt-in, and passing an authorized contact to SourceX. The MSP never exports, samples or reads client records, even with admin rights. Canadian companies qualify under the published rules; SourceX then runs inventory, rights review and any agreement with the company directly.
Read → - A candidate submitted by two business units: a worked candidate ownership conflict, step by step
The records that explain a candidate ownership conflict are the ones that fix three facts in time: who first had the candidate's agreement to be represented, who first submitted through the client's channel, and who decided between the claims and under which rule. In practice that means ATS activities and submittals, a filed representation email, the client portal's submission and duplicate notices, the client agreement clause, and an adjudication note. Without all three facts, a conflict reads as an argument rather than a decision.
Read → - A client wants cash quickly: set the right referral expectations with a timing uncertainty sheet that shows where no money can move, which steps carry no date you can plan on, and why a dated cash need is the wrong reason to introduce
Tell the client early and plainly that data licensing cannot be relied on for a cash need with a date. No money moves before Closing, the amount exists only once the company signs a Dataset Deal Confirmation, data that never closes earns nothing, and after Closing the company invoices, with payment due within 60 calendar days of a valid invoice under SourceX's published standard unless signed terms differ. Introduce the company only if its CEO wants to explore licensing for its own sake, with the cash plan built without it.
Read → - A client-first business case for an unpaid referral path: score what the client and your firm gain with the reward fixed at zero, then pilot, keep, widen or drop it
An unpaid referral path is worth offering when the client gets a real, low-cost option and your firm's effort and trust exposure stay small, with compensation scored at zero. Be clear about what declining does not do: SourceX pays any partner reward separately and never deducts it from the company's compensation, so taking nothing adds nothing to your client's payout. The case has to rest on usefulness, independence and simplicity, and it should be written down before anyone mentions money.
Read → - A co-investor introduces the wrong entity: how to correct it with a ten-field handoff template that keeps the original record visible, names the right company and its CEO, and leaves the credit question to SourceX
Correct it through the person who submitted it, in writing, without erasing anything. The co-investor who made the introduction tells SourceX which entity was named, which entity was meant and who confirmed the difference, and the CEO of the right company confirms it in their own words. Do not file a second introduction yourself: two records for one company read as a contest, and the founder hears two asks. Whether the corrected entity keeps the original date is for SourceX to decide in its review.
Read → - A cohort report for referrals made under different criteria: tag each introduction with the rules in force that day, and compare cohorts only at the same age
Never pool introductions made under different rules into one rate. Tag every introduction with the criteria in force on the day it was made: your fund's own referral mandate, the program-terms version and, where SourceX tells you, the program the company was reviewed against. Count unique companies per cohort, report every stage including cases still open, and compare cohorts only at the same age since introduction. With cohorts this small, publish counts with denominators, such as 3 of 9, never bare percentages.
Read → - A community calendar built around questions, not repeated launches: a question-led plan that gives a month's slot only to a question several members asked, announces the program once and keeps every founder's company facts out of the planning sheet
Build the calendar from the questions your members ask, not from the referral program. Log every question about AI data licensing and introductions with the asker's company details removed, group the questions into clusters, and give a session only to a cluster that three or more members raised and that a named person can answer from a published page. Announce the program once. Every seat stays optional, and a question that needs one company's facts goes to that company's own conversation with SourceX.
Read → - A company wants a valuation before an intro: find out which of five questions the founder means, answer it without a figure of your own, and know when to stop
Don't give one, and don't guess. Nobody can price a company's records before SourceX has seen its inventory, and a figure from an operating partner arrives carrying your reward and the fund's authority. First find out which question the founder is asking: what the records would earn, whether licensing moves the company's own valuation, whether it is worth the team's time, what floor to hold, or what to tell the board. Answer that one from published facts, and send the price question to SourceX's application, which returns an indicative estimate without any files.
Read → - A corporate director's data opportunity question set: ten board-context question cards for the normal course of strategy, risk and contract oversight, asked without naming any vendor, with confidentiality first and the CEO left to decide whether SourceX ever comes up
A corporate director can raise the company's own records as a topic in the normal course of board work: as a strategy question about what the company knows that others cannot easily rebuild, a risk question about who may use its data, and a contract question about what customer agreements allow. Ask those questions without naming a vendor, and keep the answers inside the boardroom. SourceX enters the conversation only if the CEO wants it there, and only after the director has disclosed any personal interest. The CEO decides.
Read → - A corporate network referral without sharing customer contracts: a nine-line qualification summary built from what the company says, while every agreement stays with the party that signed it
No contract needs to move for a corporate network introduction. Customer agreements belong to the operating company, and its own counsel reads them during SourceX's rights review. The corporate's supply papers and investment documents belong to the corporate and stay out of the conversation. What a platform manager carries is a short qualification summary built from the CEO's answers and public records: full-time headcount at its peak, the kinds of records and their years, whose records they are, and whether counsel has looked at reuse limits yet.
Read → - A corporate venture referral needs two approval paths: a seven-sign-off map that keeps the corporate's permission to ask apart from the company CEO's permission to proceed, and says what happens when only one path clears
Two sets of approvals have to clear, and neither can stand in for the other. Inside the corporate, the relationship owner, compliance and an authorized signer decide whether the corporate, or one of its people, may raise the idea at all. Inside the operating company, only the CEO decides whether to discuss licensing its records with SourceX. Keep each path on its own record, submit an introduction only when both are complete, and remember that if the corporate path closes, the CEO can still apply directly.
Read → - A CRM deduplication rule for legal entities and brand names: an entity-brand matching specification that hangs every trade name and domain on the one entity whose CEO decides, links sister companies instead of merging them and leaves credit to SourceX
Deduplicate on the legal entity, not on the name a website shows. Give each company record one entity key and hang every brand name, former name and web domain off it as an alias. Link sister companies through a group field instead of merging them, and send uncertain matches to a person, not an automatic merge. That stops two colleagues approaching one CEO under two names. It does not predict credit: that depends on SourceX's own records and its duplicate review, which no partner CRM can see.
Read → - A cybersecurity advisor's role in a data introduction: a security-role handoff that shows who holds the line at each stage, and why the advisor who could earn a reward should not also grade the deal's risk
Your privileged access exists because the client hired you to protect its systems, so it gives you no standing to export, sample, size or vouch for its records in a licensing deal. What security work does give you is timing: retention reviews, system retirements and data mapping put old records in view before anyone else notices them. Your part is narrow. Spot the moment, tell the person who would sponsor it that SourceX exists and that you could be paid, let the CEO decide, and stay out of grading the risk of a deal you have a stake in.
Read → - A data introduction from an industry consortium: a member permission and role map that keeps the shared pool off the table, gives every member its own door and leaves each decision with that member's CEO
A consortium can tell its members that SourceX exists. It cannot introduce members as a group, offer the data members contributed to it, or decide for anyone. Each member company is a separate introduction that starts only when its own CEO asks, and the company then applies, is reviewed and signs on its own. The corporate that convenes or funds the consortium gets no preferred view of any member's records, and nobody gathers member data for SourceX.
Read → - A data partnership panel hosted by a professional association: a member-safe moderation guide with a speaker disclosure roster, eight live-question cards that keep client detail and rules verdicts off the stage, and a close that collects nothing for SourceX
Run the panel as a room full of people who hold other people's confidences. Before the day, every speaker puts their tie to SourceX in writing, and a speaker who is a SourceX partner gets SourceX's written permission before naming it on stage. During the panel, the moderator turns client detail into generic terms, sends every "am I allowed?" to the member's own ethics counsel and keeps prices off the table. Afterward, the association passes no attendee list to anyone, and members act for themselves.
Read → - A data partnership thesis should name its bottleneck: a seven-row map of the constraints a network can relieve, and the partner action for each
A data partnership thesis helps a platform team only when it names the single step it believes is scarce. "Real business records are valuable to AI" names none, so it produces a mailing list. Name the bottleneck, whether that is a CEO who wants the conversation, rights to license, or records that show how work actually ended, and the thesis tells you which companies to ask, what to ask them and which result would prove you wrong. A network can relieve some bottlenecks. Others belong to the market or to SourceX's review.
Read → - A data referral during an IT due diligence engagement: an engagement boundary review that sorts what you learned for the buyer, whose CEO decides at each stage of the deal, and when an introduction can start without a word from the data room
Everything you see in IT due diligence was handed to you for one client and one purpose: evaluating a transaction. It can tell you a company keeps years of its own records, but it cannot be the basis of an introduction. Before closing, the target's CEO decides on licensing; after closing, the acquirer's CEO does. Wait until the engagement ends or the idea sits clearly outside it, check your engagement letter and any confidentiality agreement, tell your client before approaching anyone, and build an introduction only from what the deciding CEO tells you directly.
Read → - A data referral program should fit your existing client promise: a clause-by-clause worksheet that tests what you already promise clients before the reward enters the room
A referral program fits an advisory firm when every promise the firm already makes to clients still holds after it joins: independent advice, confidentiality, the scope it was hired for, how it is paid and how hard it pushes. Write those promises down in the firm's own words, test each one against what the program asks and pays, and choose the participation model that breaks none of them. The reward is the last line on the worksheet, not the first.
Read → - A demo day follow-up that does not assume dataset fit: one post-event relevance email with four reply words, sent once to guests who asked for follow-up, that lets every reader rule themselves in or out
Send one email that lets readers judge relevance, never one that presumes their company holds a licensable dataset. Companies pitching at a demo day have usually just finished an accelerator batch, so SourceX's size and history tests rule most of them out for now; guests who run or work at established companies, and investors who know such CEOs, are more often the readers it concerns. Put the published tests first, disclose the fund's possible reward, offer four reply words including no, and send nothing further unless someone replies.
Read → - A developer tool vendor's path to company introductions: an engineering-owner sponsor map that climbs to the CEO without touching customer repositories
A developer tool vendor can introduce customers whose own engineering records, such as issue histories, code reviews and incident write-ups, may qualify for direct licensing to SourceX, but its role ends at the introduction. Those records belong to the customer, the vendor never exports or describes them, and product analytics play no part in choosing whom to ask. The working path runs from your account relationship to the customer's engineering owner, who sponsors the idea, and on to the CEO, who authorizes.
Read → - A disclosure checklist for investor-hosted data webinars: a spoken-and-written placement guide that reaches the late joiner, the dial-in listener and the replay viewer, and keeps the fund's referral interest apart from any stake in SourceX
Settle who at the fund would take part before the invitation goes out: the fund entity, one named person or nobody. Then make that fact, and any stake the fund has in SourceX as an investor, reachable from every door a viewer can use: the invitation, the registration page, a spoken line at the start and at each change of segment, a strip that stays on screen, the pinned chat, the replay page and the follow-up email. Questions about investing in SourceX stay off the call.
Read → - A false-positive closure worked step by step: the backup job that looked like ransomware staging
The records that explain how a false positive was handled are the alert with its rule version, the analyst's evidence and reasoning, the closure verdict with its reason, any tuning proposal and the review of it, the rule change that shipped, and a later check that the change held. The worked case below walks one hard closure through those records in order. A disposition label alone shows only that someone called the alert harmless; the sequence shows why.
Read → - A family office's business network may be broader than its portfolio: a seven-branch map of who inside the office holds each tie, whose CEO decides and which asks stay off the table
A family office's portfolio is the part of its network a fund sees. The rest runs through the family's own operating business, the companies its family members run or govern, its charitable boards, its co-investors and peers, and the advisers it hires. Any company in that wider network can be introduced to SourceX if it passes the published screen and its CEO wants the conversation. Find out which person inside the office holds each tie, raise the subject with that person under a stated non-investment purpose, and leave every decision to the company's CEO.
Read → - A Field Guide for Reliability Consultants: Finding Companies with Incident and On-Call Records
Reliability consultants can identify companies with valuable incident and on-call records by focusing on organizations with 50+ full-time employees at peak and a history of operations. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. Your existing network and understanding of system reliability challenges are key to pinpointing potential candidates for data licensing.
Read → - A field guide to failed data introductions: an identification key that names each failure by the dated evidence it left, sorts preventable failures from correct stops, and a case collection protocol that sets every failure beside an introduction that nearly failed
A failed data introduction teaches something only when its mechanism can be shown from dated records and told apart from a correct stop, such as a company the published criteria ruled out. This field guide gives an identification key with eight types, the evidence each type leaves and the type it is most often mistaken for, plus a protocol for collecting consented, anonymized cases that sets every failure beside a comparable introduction that nearly failed but went ahead. No cases have been collected or published yet.
Read → - A finance advisor's referral log should exclude financial attachments: a fourteen-field minimal client referral log that proves who agreed, when and on what terms, and holds no ledger, return, statement or screenshot from any client
Log your own actions and the client's decisions, never the client's finances. A referral log needs the company's public identity, the CEO's yes in the CEO's own words with its date, your rules check and who answered it, the paid or unpaid route you chose, what you submitted and when, and the stage words SourceX's dashboard shows. Ledgers, trial balances, tax returns, bank statements, payroll files and screenshots of client systems stay out. Nothing SourceX decides needs them, and every one is client information you would then have to protect.
Read → - A First Month Referral Plan for Industry Associations
Industry associations can kickstart their SourceX referral efforts by dedicating the first month to identifying suitable member companies, confirming their licensing readiness, and making initial introductions. This structured approach helps maximize referral impact.
Read → - A first month referral plan for staffing firms
Staffing firm owners can leverage their client relationships by identifying companies that meet SourceX's criteria for data licensing. The first month focuses on client screening, sponsor confirmation, making introductions, and tracking the referral process.
Read → - A First-Month Referral Plan for CRM Consultants
CRM consultants can begin referring suitable clients to SourceX by identifying companies with valuable data, making warm introductions, and tracking the referral process. This plan helps integrate data licensing referrals into existing client strategies.
Read → - A first-month referral plan for wealth advisors
Wealth advisors can start data licensing referrals in four weeks: get a compliance answer first, screen owner clients for size, history, rights and an authorized sponsor, prepare a disclosed conversation, then make one introduction. 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.
Read → - A follow-up timing test that respects founder preferences: a consent-bounded design in which each founder names the window and the weeks to avoid, the single check-in moves only inside that window, and every company is read on the same day-120 clock
Test timing only inside the window each founder gives you. When a founder agrees to hear about SourceX, ask once when a single check-in would be welcome and which weeks to avoid. Founders who name a date get that date. Only founders who leave the timing to you are assigned, from a list drawn before anyone enrolls, to an early or a late check-in inside their own window. Read every company on one clock, day 120 after the yes, so the late group is never judged before its time is up. No results exist yet.
Read → - A founder benefit metric beyond referral compensation: one confirmed-benefit rate, the eight-question survey that produces it and a denominator that keeps silent founders in
Measure what founders say they gained, not what the fund might earn. One number does this well: the confirmed-benefit rate, the share of founders offered a data licensing conversation who later report a specific decision or action they took because of it, with no harm reported. Every eligible founder who was offered the conversation stays in the denominator, including those who declined or never answered. Collect it with an eight-question survey at 30 days and again at 120, sent by someone with no stake in any reward.
Read → - A founder interview study before you scale the channel: a sampling protocol that interviews the founders a wider rollout would reach next, not the pilot's warm core again, and sets a scale, amend or hold rule for each group before the first interview
Interview the founders a wider rollout would reach, not the pilot's founders again. Split that next population into groups that differ from the pilot in ways that could change how a mention lands, such as board-seat companies, companies the fund never backed and companies whose headcount never reached the program's size bar. Interview a handful from each until new themes stop appearing, then decide per group, by rules written beforehand, whether to scale, amend the approach or hold. Nobody interviewed is asked for an introduction.
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