This hub offers practical guides and best practices for advisors looking to successfully introduce companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) to SourceX, a direct licensing partner for approved business data for AI training and evaluation. Here, you'll discover step-by-step instructions and strategic insights for introducing companies to SourceX, which licenses data directly from companies and manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. These resources are designed to help you navigate the process efficiently, focusing on companies with 50+ full-time employees at peak. Unlock the potential of valuable data partnerships by leveraging these comprehensive guides.
Practical guides to successful company data introductions
Short, task-focused guides on identifying suitable companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English), recognizing valuable proprietary data, and making an introduction the decision maker will welcome.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
- Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.
Common questions
What kind of companies should I introduce to SourceX?
You should focus on introducing companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) that have 50 or more full-time employees at peak. These are the companies that can unlock the potential for valuable data partnerships with AI labs and data buyers.
What is the purpose of these guides?
These guides offer practical instructions and strategic insights for advisors to successfully introduce companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia to SourceX. They help navigate the process efficiently and identify valuable proprietary data for AI labs and data buyers.
Who benefits from SourceX data introductions?
AI labs and data buyers benefit from approved business data that SourceX licenses directly from companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia for AI training and evaluation. Advisors can also benefit by introducing companies to SourceX as their direct licensing partner.
What kind of information do these guides provide?
These guides provide step-by-step instructions and best practices for identifying suitable companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia. They help in recognizing valuable proprietary data and making introductions that decision makers will welcome, facilitating data transactions for AI.
Related pages
- How to model a one-time receipt, like a data license, in a 13-week cash flow forecast
- 2021-vintage private equity funds: what to do with companies bought at peak multiples
- 3PL and logistics M&A in 2026: what buyers want and what sellers should preserve
- 3PL valuation multiples in 2026: what buyers pay for in a logistics business
- A/E industry M&A trends in 2026, and what selling firms should prepare
- Acquiring a business from a retiring owner: assessing decades of records before they go
- The questions that turn AI hype into referral diligence: a claim-to-question worksheet that reduces five popular AI data claims to facts one CEO can confirm
Treat every AI headline as a hypothesis with a source, not as a reason to call someone. Find what the original research, filing or enforcement record actually says, restate it as one question about a specific company's records, ownership or CEO, and decide in advance which answer stops the introduction. A claim that cannot be reduced to such a question is noise for referral purposes, however loudly it is repeated. The worksheet below translates five common claims.
Read → - The quiet business archives sitting outside the AI spotlight: an archive-owner discovery map that separates where old records sit, who holds them and who can say yes
Many established companies hold years of operating records that nobody in AI talks about: files left behind by a sale, a founder's retirement, a merger, an office move or a closure. For a network owner, the job is not to value that archive. It is to find who controls it today and whether that person wants a conversation. Keep three answers apart (where the records sit, who has custody and who can authorize a license) and reach the authorizer through the adviser who already serves them.
Read → - The referral attribution FAQ for a multi-partner firm: 14 questions sorted by who answers them, your firm or SourceX
SourceX credits one partner per company: the first valid introduction of a company new to SourceX, once that company submits a verified application within 90 days. A firm's policy cannot create, split or move that credit. It can decide who in the firm submits, under which signed agreement, and how colleagues avoid colliding. Write the policy around that line, settle internal claims before anyone writes to a CEO, and send what only SourceX's records can answer to its duplicate review.
Read → - The referral boundary in a syndicate relationship: a responsibility matrix that keeps the lead's carry, the backers' deal pages and a SourceX introduction in separate lanes
A syndicate invests together, but a referral is one person's act, taken with the founder's permission. Normally the lead, who holds the founder relationship, is the only one who asks the CEO; backers who spot a fit tell the lead and do not approach the company on the strength of a deal page. Whoever introduces signs the partner agreement in their own name, and SourceX credits one partner per company. Carry from the investment and a referral reward from SourceX never mix.
Read → - The referral conversation after a business reorganization: a reorganization entity review that maps the old entities onto the new ones, finds which entity holds the records and whose CEO decides today, and stops for the estate's controller when a court process is involved
A reorganization changes the map, not the rules. Before reopening a referral conversation, redraw the company's entities as they stand after the change: which entity employed the people who created the records, which entity holds those records now, who that entity's CEO is, and which group it belongs to for the reward cap. Then ask the current CEO of the records-holding entity, not the person who said yes before. If any part of the reorganization runs through a court or a formal insolvency process, the CEO may not be enough, and whoever controls the estate decides.
Read → - The referral conversation after a company combines two support teams: a consolidation introduction guide that times one question to the CEO after cutover, names who decides in four kinds of merger and leaves every ticket unread
When a company combines two support teams, its CEO is already looking at what the merged function holds and what the old setup will leave behind. That makes it a fair moment for a partner who knows the CEO to ask one question: would the company like to hear whether material it created itself, such as its support procedures and internal knowledge base, could be licensed to SourceX? Confirm who decides, wait until the cutover has settled, ask once, and never open, export or summarize a single ticket.
Read → - The referral conversation after customer support consolidation: an operational-change introduction brief that logs which facts the consolidation moved and which it left alone, then holds the question until the new desk runs steady
A customer support consolidation changes who answers for the support function, how stretched that team is and which vendor contracts or old help desks end on a date. It does not change who decides about licensing, or whether the company fits. Write those changes down as facts the company itself gave you, keep the unchanged checks beside them, wait until the consolidated desk runs steady, then ask the CEO one question that names what moved.
Read → - The referral conversation around a major process audit: an audit-to-referral boundary guide that keeps the licensing question out of planning, fieldwork and findings, waits until the company closes its own response, and gives the CEO one question that needs nothing from the audit
A major process audit can make one licensing question timely, because for weeks the CEO has watched the company explain how its work is done and where its records live. It never makes the audit a source. Keep the question out of planning, fieldwork and findings; wait until management has responded and the company itself says the audit is closed; then ask the CEO one question that needs nothing the audit produced. Findings, workpapers, samples and records stay with the company and its auditors.
Read → - The referral conversation with a globally distributed leadership team: an authority alignment meeting plan that settles once that the CEO decides, then sets who hears the idea first, when the CEO hears it and which leaders join only at the CEO's request
Distance changes the order of conversations, never who decides: the CEO authorizes a licensing discussion wherever the other leaders sit. Speak first to the one leader you actually know, and ask only whether the idea deserves the CEO's time. Reach the CEO second, through that leader or with that leader's knowledge. Bring in leaders from other countries only when the CEO asks for them. Write every meeting time in each participant's own zone, and keep records and approvals out of every call.
Read → - The referral conversation with a privacy officer: a first-meeting agenda that settles which seat the privacy officer sits in, keeps every company's personal data out of the room, sends conflict and pay questions to their own counsel and ends in an introduction, an unpaid mention or no part
Treat a privacy officer as someone whose duty runs to the organization they protect, not as a source of introductions. In a first meeting, settle which seat they occupy (inside one company, an outside officer for several clients, or a privacy lawyer), keep every company's personal data and compliance files out of the conversation, send the conflict and pay questions to their own counsel or employer, and agree one permitted next step: an introduction the CEO wants, an unpaid mention, or nothing.
Read → - The referral conversation with an executive search partner: a one-page collaboration brief that asks only about CEOs they know in their own right, keeps every search and candidate file shut, and leaves each decision with the CEO
An executive search partner can help a fund's network in one narrow way: by asking a CEO they know in their own right whether that CEO would like to hear about SourceX. Nothing from a search can travel, whether it is a client's mandate, a candidate's interest or what a board said in a briefing, and a search is never the occasion for the question. Give the search partner a one-page brief that says so, disclose who could be paid, and leave the decision to the company's CEO.
Read → - The referral CRM should track companies, permissions and next steps: a three-object schema of fourteen fields, a save rule that refuses any step no permission covers, and nine fields the system never accepts
Build the referral CRM from three small objects: the company (who it is, which group it belongs to and who decides for it), the permissions its CEO has given, and the next steps your team owes. Then add one save rule: no next step can be saved unless a dated permission, still in force, covers it. Leave out amounts, probabilities, files, samples and logins entirely. The record proves who agreed to what and what happens next; it never describes what the company holds.
Read → - The referral email that explains the reward formula without making a payout promise
Say the formula once, in the same sentence as its base and its trigger: SourceX may pay you the greater of $50,000 plus 5% and 15% of what it actually pays the company on its first qualifying transaction, and only after the deal completes and the company is paid. Then say who pays it (SourceX, separately) and what it does not mean (no estimate, no promise). Put that disclosure in the body of the email, before the request for a call.
Read → - The referral experiment behind a category-creation story: split the story into claims, test only the ones introductions can reach, and rewrite it from what comes back
A category-creation story is a bundle of claims, and introductions can test only some of them. A narrow referral experiment can show whether companies matching the story sit in your network, describe the records the story assumes, appear to control them and have CEOs who want the conversation. It cannot show buyer demand, prices or that the category will win. Split the story into sentences, mark each one testable by referral, testable elsewhere or cut, pilot the first group with eight companies, and rewrite the story from the results.
Read → - The referral experiment retrospective that captures unexpected harm: an outcome-and-side-effect review that hears from everyone the test touched, sorts each harm by who bore it and whether the plan foresaw it, and names one change per harm
A referral experiment retrospective catches unexpected harm only if it looks past the measures in the plan. Review outcomes and side effects together: ask every group the test touched, including clients who were never asked and your own colleagues, what went wrong; log each report whether or not it fits a measure; then record who bore it, whether the plan foresaw it, how serious and reversible it was, and whether one version, both versions or the test itself caused it. Every harm gets one named change.
Read → - The referral experiment that tracks negative feedback: a positive-and-negative outcome ledger that gathers reactions from every place a founder might voice them, flags a yes given out of obligation as a warning, and reads harm as events because a small network cannot measure it as a rate
In a venture network the most telling negative feedback rarely arrives as a complaint. It reaches a deal partner at a board meeting, hides inside a founder's polite yes to an investor, or shows up as an agreed introduction that never becomes an application. Track it with a two-sided ledger for every company contacted: positive entries on one side, negative entries on the other, and a warning flag on any yes that looks given for the fund's sake. Gather reactions from every channel a founder uses, read each negative as an event, and keep flagged yeses out of any win. No results are published here.
Read → - The referral invoice question: nine points a partner's finance team should settle with SourceX before billing a reward, starting with whether to bill at all
Start with whether SourceX wants an invoice at all. The published terms make the partner's payment and tax details a payment condition and say nothing about a partner invoice. If one is wanted, send it only after the reward shows Approved, from the exact legal entity that signed the Channel Partner Agreement, for the approved amount and its reference code, with no due date or late fee of your own. An invoice cannot move the payment deadline, change the amount or earn the once-per-company floor a second time; the signed agreement and the program terms decide all three.
Read → - The referral landing page test for different decision-makers: a two-stage study in which every non-CEO version points the reader to the CEO, comprehension is checked role by role before launch, and qualified applications decide the result
A partner growth manager can test role-specific versions of their own referral landing page, but only one role decides: the CEO. Versions written for finance leads, operations leads, counsel or board members must route those readers to the CEO and never invite them to decide or apply. Run the test in two stages: paraphrase interviews with each role before launch, then a live comparison judged on qualified applications from companies whose CEO asked for the introduction, not on visits or clicks. No results for this design are published.
Read → - The referral message for a skeptical operator: an evidence-and-questions format where every line is a sourced fact, a question, a disclosure or a choice
A skeptical operator discards any sentence they cannot check, so build the message from four kinds of line only: a fact with its source, a question only the company can answer, a plain disclosure that SourceX may pay you a reward, and one choice they can decline. Name why this company, using what the operator has told you, say what stays conditional, and leave out estimates, deadlines and talk of buyers. If a line fits none of the four types, cut it.
Read → - The referral metrics that survive a denominator check: a seven-test worksheet that keeps three common metrics, repairs four and retires two
A referral metric survives a denominator check when its numerator and denominator count the same unit (unique companies, not contacts), every company in the numerator also sits in the denominator, both come from one introduction cohort with one cutoff date, every company in the denominator has had time to reach the numerator's stage, and exclusions are declared rather than dropped. Ratios built from mixed periods or contact counts fail. The worksheet below tests nine common metrics: three survive as written, four can be repaired and two should be retired.
Read → - The referral moment after a long documentation cleanup: a readiness-change trigger worksheet that separates what the cleanup changed about timing from the checks it never touches, and asks the CEO only once the company calls the work closed
A long documentation cleanup is a timing signal and nothing more. Once the company says the work is finished, the CEO may have attention to spare, and someone inside now knows where the records sit and what was removed. The cleanup never makes a company fit, and it never gives a partner a reason to see, review or export a single record. Wait for the company to call it closed, then put one question to the CEO, naming that change.
Read → - The referral note format that preserves context: a facts, questions and permission entry that records who introduced whom, when, what was asked and what waits on whom, and carries none of the company's records
A referral CRM note should let a colleague who has never met the company rebuild the route of an introduction in under a minute: who introduced whom and how they know each other, when and through which channel, what was asked, what is waiting and on whom, and what the company's CEO has allowed, in the CEO's own words. Write every entry in three blocks, facts, questions and permission. Tag each line with where it came from, add new entries instead of editing old ones, and keep the company's records, figures and attachments out of the note entirely.
Read → - The referral operations handbook for a new team member: a four-week reading path through the existing operations guides, sorted by role, with the moment to open each one and no rule of its own
A new team member does not need another rulebook. They need the operations guides that already exist, in the order the work will reach them. Read the program basics and your firm's signed Channel Partner Agreement before anything else, then take one group of guides per week: what a referral record holds, how a CEO's yes becomes an introduction, how open referrals keep moving, and how they end and get counted. Every guide below comes with one line on when to open it, and the rules stay in the guides and the terms.
Read → - The referral partnership review before hiring a dedicated manager: a 13-week workload log, an outcome gate and the arithmetic that shows why rewards cannot carry a salary
Hire only after a 13-week review shows sustained work that a named partner cannot carry, and only if the role is paid for by something other than referral rewards. Log hours by task, count outcomes as stages the program records, such as CEO-approved introductions and verified applications, and set the cost of a hire beside what a reward can do: it is contingent, arrives months after acceptance and depends on deal sizes your firm cannot plan. Most advisory firms should keep the work with one owner or step back.
Read → - The referral policy for a paid business membership: a member-contract and incentive review that reads what dues already promise, lists everyone who could be paid, and keeps every company's decision with its CEO
Before a dues-funded membership mentions SourceX, read what members already bought: the membership terms, the privacy notice, the community or directory rules and any sponsorship policy. Then list everyone who could be paid for an introduction, from the organization itself to a staff member, a director or a member referring a peer, and decide in writing which of them the policy allows, how each is disclosed and who approves. Each member company's CEO decides for that company; the policy never lets dues, perks or a reward stand in for that decision.
Read → - The referral program that does not require product integration: what a SaaS partner team signs, builds and never touches in an introduction-only pilot
It asks for no build at all. In SourceX's program a software company signs the Channel Partner Agreement, registers and introduces a customer's CEO when that customer wants the conversation. There is no API, data connector, single sign-on, marketplace listing or technical review, and no customer data passes through your product or your team. That makes the motion cheap to pilot, but it moves the hard work from engineering to judgment: choosing accounts without product analytics, getting consent and keeping the customer's records out of your hands.
Read → - The referral promise a partner must never make on SourceX's behalf: ten no-unverified-commitment training scenarios that show where a partner's authority ends, who actually decides and the sentence to use when a client wants a yes only SourceX can give
A referral partner can introduce a company, but it cannot commit SourceX to anything. SourceX's sample Channel Partner Agreement says the partner "is not an agent of SourceX and may not commit SourceX to prices, licenses, payouts or other obligations." So a promise of acceptance, a price, a date, an exception to the criteria, special handling of data or a share of the reward is a promise about someone else's decision. Train staff and agencies to name who decides, quote what SourceX has published and stop there.
Read → - The referral quality review before entering a new sector: a twelve-check pilot that tests company size, record rights, duplicate risk and review hours before you recruit a single partner there
Treat a new sector as a hypothesis and test it with a small pilot before recruiting partners into it. Write the checks first: how many firms in the sector reach 50 full-time employees at peak, whether their records belong to them or to their clients, how often introductions collide with companies SourceX already knows, and whether your team can review the volume. Expand only when the pilot clears thresholds you set before it started. A sector that sounds relevant to AI is not evidence.
Read → - The referral quality review before pressing send: a 14-line final submission scorecard with four stop lines, scored on the outgoing message instead of the company
A data referral quality checklist should score the outgoing message, not the company. Before anything leaves, four stop lines must be clean: the right recipients, the CEO's dated consent, zero attachments and no sentence that tells anyone the company qualifies. Ten more lines check that every fact is the company's own, labeled and owned, and that the handoff names a contact and an agenda. A zero on any stop line holds the message, whatever its total.
Read → - The referral question a law firm should resolve before promoting SourceX: whether the firm will also advise the companies it introduces, taken to ethics counsel through a seven-item review agenda that ends in a paid route, an unpaid mention or no part at all
Settle one question at firm level before any client alert, seminar or lawyer mentions SourceX: will the firm also act for the companies it introduces, on their rights review or on their agreement with SourceX? A referral reward depends on the client being paid, and advice on whether the client should sign sits right beside it. Take that question, with the facts on this page, to the firm's ethics counsel or general counsel. This page takes no position on whether any lawyer may accept a reward; that answer belongs to them.
Read → - The referral questions after a long-term vendor contract ends: a vendor-transition metadata review that sorts what came back, what the vendor kept or deleted and what the company can show is its own, before the CEO is asked anything
After a long vendor contract ends, a company knows something it did not know before: which records came back, which ones the vendor kept or deleted, and which ones it can show are its own. That settled picture, not the scramble of the exit, is the right moment to ask the CEO whether the company wants to explore licensing. Wait until the return is complete, keep every question at the level of metadata, and let the company confirm its own rights. SourceX reviews rights during qualification.
Read → - The referral questions after a product recall review: an eight-check appropriateness test that keeps the licensing question apart from the recall, waits until the company has closed its own review and lets the CEO speak about it first
Treat a product recall review as a reason to wait, not an opening. The licensing question becomes fair only after the recall is closed, the company has finished looking back at it, nothing about the product is still being fought over, and the CEO has talked about the review with you or in public. Even then, ask the CEO once, in a conversation that does not lean on the recall, and take a no as final. A recall never makes a company's records more likely to fit.
Read → - The referral questions around a founder buyback: a control-change worksheet showing what the fund gives up, what the founder takes on and when a data conversation is fair to raise
In a founder buyback the person who can authorize a licensing discussion usually stays put: the founder is still the CEO. What changes is everything around that yes. The fund gives up its board seat, its information rights and most of its standing; the founder takes on full control and often a lender. While the price is being negotiated, a licensing conversation is information both sides should have. Raise it before the price is set and in front of both sides, or wait until after closing.
Read → - The referral questions around a ticketing platform replacement: a service history worksheet that separates what the company wrote from what its customers wrote, and gives each part an owner before cutover
A ticketing replacement raises five referral questions, and you answer only one of them yourself: whether to tell the client's CEO. Whose service history it is, what the outgoing vendor deletes and when, which parts the company wrote and which its customers wrote, and whether any of it could be licensed belong to the company and to SourceX's review. The worksheet below splits service history into its parts and names, for each, what you may note, who decides and what SourceX reviews.
Read → - The referral questions behind a company anniversary: four dates a 'since 1979' line can stand for, and ten history-based discovery questions that find the one that counts
A company anniversary tells you how long a name has been in business. It does not tell you how far back the records go, which legal entity holds them, or whether the company was ever big enough to fit. Treat the milestone as a reason to ask someone you already know a short set of questions that walk the company's history from founding to today, and introduce it only after the CEO confirms the answers and wants the conversation.
Read → - The referral questions in an asset sale versus a share sale: an eight-row matrix for which entity applies, whose CEO says yes, which cap applies and which records stay behind with the seller
In a share sale, the company that created the records survives the deal, so most referral questions stay put: the same entity applies, and only the person who decides changes at closing, from the company's own CEO to the acquirer's CEO. In an asset sale, the referral splits along with the records. Purchased records sit with the buyer's entity and its CEO; excluded records stay with the seller, whose CEO decides only while the seller can still act. Settle the entity, the CEO and the record set before anyone is introduced.
Read → - The referral questions to ask after an acquisition: eight questions and a sponsor map for each phase from signing to full merger
Authority to say yes moves at closing after an acquisition, and a referral has to follow it. Before closing, the target's own CEO still decides and the buyer should not be steering the business. From closing onward, the acquirer's CEO decides for the acquired company, whether it runs standalone, is being integrated or has been merged in; the acquired company's own CEO, while the role lasts, sponsors the ask and can carry it internally but does not authorize it. Name the phase, the CEO who decides today and the internal sponsor, check whether the group already knows SourceX, and only then ask.
Read → - The referral readiness interview for a returning founder: twelve context questions for a founder back in the CEO's chair that separate what they remember from what the company holds now, before anyone mentions data licensing
A founder who comes back as CEO decides for the company again, but their picture of its systems, contracts and people dates from the day they left. Before mentioning data licensing, a portfolio engagement lead should run a short context interview: confirm the appointment, learn what changed during the absence, check whether anyone already spoke with SourceX, and find out when the founder will have room for an outside idea. The interview gathers context only. It never decides fit and never asks for a file.
Read → - The referral readiness review for an owner-led group: a group authority and scope canvas that records which hat the owner wears at each company, and which records belong on the first call
An owner-led group looks like one decision and usually is not. One person may own every company but be CEO of only some, the records often sit in a sister company's systems, and SourceX's published rule treats a parent and its subsidiaries as one referred company for the once-per-company reward floor, not companies held side by side. Before summarizing the group, fill one canvas row per company, have the owner and each operating CEO approve their rows, and put only the companies with a clear CEO yes on the first call.
Read → - The referral review before an enterprise tool contract ends: twelve checks in three locked blocks that prove the export and name the decision-maker before anyone mentions licensing
When a portfolio company is about to end an enterprise tool contract, the referral question comes last. First prove that a complete export sits in storage the company controls, inside the return window its signed contract gives. Then confirm who decides for the company today: the CEO, or the acquirer's CEO after a sale. Then let counsel clear any hold. Only after those checks does anyone ask the CEO whether a licensing conversation is wanted, and a failed check means wait or stop.
Read → - The referral reward calculation: four payment scenarios worked on the 2026 default formula
Under the 2026 default terms a company's first qualifying transaction pays the greater of USD 50,000 plus 5% of Actual Supplier Payout and 15% of it, with no cap; each further qualifying transaction first agreed within 12 months of the first Closing pays 15%. Only compensation SourceX actually pays the company counts: separately itemized taxes and expense reimbursements do not, and offers and signed agreements do not count until money is paid. Four scenarios show single payments, a repeat license and staged payments.
Read → - The referral shortlist hidden in your existing client relationships: a three-column canvas that keeps public clues, engagement knowledge and client-confirmed facts apart
Your strongest referral shortlist is already in your client book, but only part of what you know about each client may be used. Sort it into three columns: public clues anyone can see, knowledge your team gained doing the work, and facts the client has confirmed for this purpose. Only the third column travels with an introduction. Engagement knowledge can tell you whom to ask, never what to share. A client joins the shortlist when someone at your firm owns the CEO relationship and a plausible fit question exists.
Read → - The referral trigger hidden in a documentation project: why a CEO who orders a write-down of how the company works is ready for one question, and an eight-question interview with the project owner that decides when to ask it
A documentation project is a referral trigger because the CEO has already decided that what the company knows is worth writing down, and the project gives one person the job of finding out what exists and who looks after it. That makes it a fair moment to ask the CEO one question: would the company like a conversation with SourceX about licensing its own operating records? Learn the project's purpose and stage from its owner first, time the question to them, and never read, collect or summarize the documents yourself.
Read → - The referral trust survey for venture platform teams: a matched-pair instrument that asks the platform lead and the founder the same questions about one data licensing suggestion, measures the gap between them and has not yet been fielded
A venture referral trust survey has to measure something a general trust poll cannot: whether a founder felt free to refuse a suggestion that came from an investor, and whether the platform team knows how the founder felt. This design asks the platform lead and the founder the same questions about one data licensing suggestion, collects both through an independent researcher so the fund never sees founder answers, and measures the gap between the two. No wave has been fielded, and no results exist.
Read → - The referral window before a portfolio company retires a system: a three-track timeline that keeps custody, control and the introduction apart, and closes when the archive scope is signed
The referral window opens when a portfolio company puts a date on a system's retirement and closes when it signs off what the archive will keep. After sign-off, only what made it into the archive can ever be discussed. Inside the window, keep three tracks apart: custody, meaning who holds the records at each step; control, meaning the CEO decides within any hold, retention minimum or disposal duty; and the introduction, which never moves the retirement date or asks for an export.
Read → - The referral-program evidence page: which facts to publish, who owns them, and how to date them
A referral-program proof page should publish each primary fact once, in plain words, beside the document that makes it true: the reward base and rate, the once-per-company floor and the Repeat Window, the payment trigger and deadline, company eligibility, and attribution. Each fact needs a named owner, a terms version, the date it was last checked, and a visible correction history. Anything the program has not measured, such as conversion rates, should be marked not yet published rather than estimated.
Read → - The relationship brief for a new senior network steward: a purpose-and-permission handover in which each LP, executive and advisor tie arrives with why it exists and what was agreed, every decline binds from day one, and no permission passes until the contact gives it again
A senior network changes hands as purposes and permissions, never as a contact list. For each LP, executive or advisor, the outgoing steward writes down why the relationship exists, what the person agreed to be asked and by whom, what they declined and until when, and what they have been told about who could be paid. The new steward inherits the record but not the yes: every permission waits until the contact renews it, and every company those contacts know stays with its own CEO.
Read → - The renewal conversation is not always the right referral moment: a six-signal pressure test for SaaS teams, and calmer windows to use instead
Raise a SourceX introduction at renewal only when nothing commercial is open in the room. If price or terms are still being negotiated, the person you would ask also signs your renewal, an escalation is unresolved or your own deadline is close, the customer cannot cleanly separate the data question from the deal, and a yes given under that pressure is worth little. Score six signals before mentioning it. At two or more, wait for a window the customer controls.
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