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
- A Portfolio Review: Unlocking Data Licensing Referral Opportunities
Portfolio reviews offer a structured opportunity for partners to identify potential data licensing referrals. They help determine if a company meets SourceX's criteria: 50+ peak full-time employees, years of relevant records, existing licensing rights, and an authorized sponsor, all while keeping the company in control of its data.
Read → - A portfolio screening form that avoids sensitive uploads: twelve fields, no attachments, and the five answers that stop a company early
A referral fit screen can be finished from twelve answers a founder already knows, with no attachments at all. Every published fit test, from peak full-time headcount and operating history to location, language, rights and whether the CEO wants the conversation, can be answered in bands and plain words. Files, samples, exports and logins add risk and no screening value at this stage. Any review of actual records happens later, between SourceX and the company itself.
Read → - A Portfolio Team Guide to Data Licensing Introductions
Portfolio teams should focus on identifying portfolio companies based 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 50+ FTE and robust operating records, ensuring they have data licensing rights and an authorized sponsor for an introduction. Careful coordination is key to maximize referrals and understand the reward structure.
Read → - A portfolio transition calendar for data partnership reviews: ten dated triggers, the day each review falls, and the stretches when nobody should ask
Set data partnership reviews by event, not by month. A portfolio transition calendar lists the dated events that move who holds a company's records or who decides about them, such as an approved sale process, a closing, a system retirement, a layoff notice or a new CEO, and fixes the day each review falls relative to that event. Every review answers three questions only: who holds the records now, who decides, and whether an introduction is open, on hold or closed. Financing rounds and valuation marks never trigger one.
Read → - A post-close integration review can reveal the right sponsor: a twelve-question responsibility interview that shows who now runs each record family and who can carry a licensing note to the acquirer's CEO
After closing, the acquirer's CEO decides whether the business you sold talks about licensing its records, but that CEO seldom hears the idea cold. Someone inside carries it: the sponsor. A post-close integration review is where a broker can learn who that should be, because it shows who now runs each record family, administers its system, sets its retention and reports to the CEO. Ask about responsibility rather than records, repeat only facts the company approves, and keep price, earn-out and escrow out of it.
Read → - A practical map of founder-owned companies around a VC fund: six boxes that show who decides, who can ask and what the founder still holds personally
Founder-owned companies are often the most introducible businesses around a venture fund. The founder usually still runs the company as CEO, so the person who can authorize a licensing discussion is one conversation away, and many of these companies have operated long enough to keep years of their own records. Map each one on six boxes: the founder's role, the ownership split, who in your network can ask, the company's records, anything the founder holds personally, and the fit facts. Then ask through whoever owns the relationship.
Read → - A preservation specialist's role in a company introduction: a specialist-to-owner handoff guide that keeps every preserved copy inside its engagement, carries one sentence to whoever hired you and leaves the licensing decision with the company's controller
A preservation specialist is a messenger in a company introduction, never the source of its facts. You were engaged to protect an archive against alteration or destruction for a client, usually counsel, the company or an estate's controller, and what you hold or learned belongs to that engagement. If licensing might interest the records' owner, say so once to whoever engaged you, without describing anything you preserved, and let the company's controller decide. You make the introduction only if the controller wants that and your engagement and counsel allow it.
Read → - A private referral handoff between fund departments: a scoped handoff protocol that moves one introduction from the person who knows the CEO to the team holding the partner account, carrying the CEO's own request and nothing the fund learned in confidence
Treat every move between departments as a disclosure in its own right. Only three things should cross a department line: the CEO's own request, quoted and dated; the name of the person who holds the relationship; and the few fields a partner record needs. Whatever the sending team holds in confidence, from diligence files to board packs, stays where it is, and the receiving team does not ask for it. Put those items on one short handoff slip, address it to named people, and route any request to add more through the general counsel first.
Read → - A product shutdown can change the referral conversation: a one-page trigger brief that splits customer data from company records before the end-of-life date
A product shutdown changes the referral conversation in three ways. Customer data in the product is returned or deleted when the service ends, under customer contracts and rules such as GDPR Article 28, so it leaves the discussion. The company's own records of building, selling and supporting the product stay and may justify a licensing review. The people who understand those records may be leaving. An operations lead's job is to spot the dated triggers, ask the CEO before the team disperses and stop if only customer data remains.
Read → - A product sunset plan that keeps the retired product's records
A product sunset plan sets the end-of-sale and end-of-life dates, customer notices, migration path, contract obligations, support wind-down and infrastructure shutdown. Add a records step: before tools are cancelled, export and assess the product's support tickets, code history and decision records, because company-owned archives like these can qualify for an AI data license.
Read → - A quarterly brief on network signals worth following: a one-page memo template that keeps dated record events and drops funding noise
The signals worth following in an investor network are dated events that change a company's records or who controls them: a system's end-of-support date, a WARN notice, a sale or merger, a CEO handover, a change to how long archives are kept. Funding rounds and leaderboard ranks say a company is growing, not that it holds licensable history. Once a quarter, log each event with its source and date, test the company against the fit facts, and name one relationship owner for every row worth a conversation.
Read → - A quarterly cleanup that improves referral data quality: a five-dimension record audit in which every fix is a new dated entry, nothing is edited or back-dated, and no SourceX decision moves
Referral CRM data quality is how far a colleague who has never worked a record can trust it without asking anyone: every company, decider, permission and step present, in the allowed form, consistent with itself, current and traceable to where it came from. Once a quarter, test every open record and a sample of closed ones on those five dimensions, and repair each defect by adding a dated correction entry. Never edit, back-date or resubmit. The cleanup changes what your record says about itself and nothing SourceX has decided.
Read → - A readiness review for an acquisition-history business: test every line of the referral summary against the entity and era it came from, before the group CEO approves it
A business built through acquisitions is ready for a referral summary when every line names the entity and the period it describes. Founding year, headcount, years of records and customer terms each come from different acquired businesses, so a group-level sentence such as "operating since 1987" or "thirty years of records" usually overstates what the group can reach today. Review the draft entity by entity and era by era, restate or hold each line, and let the group CEO approve what remains.
Read → - A records playbook for fractional CFOs serving professional services firms
A fractional CFO serving consulting, engineering or advisory firms with 50+ full-time employees at peak (contractors excluded) can spot a data-licensing fit in years of proposals, SOWs, time narratives and methodologies. Before raising a SourceX introduction, sort firm-owned know-how from client deliverables and confidential client files, because licensing starts with what the firm owns.
Read → - A referral content review that checks numbers and definitions: a number-definition-source QA sheet that gives every figure in partner copy the thing it counts, the definition that keeps it true and the sentence it rests on
A factual review of referral content checks more than whether a figure appears somewhere in SourceX's documents. For each number it asks what the figure counts, which definition keeps it true, which sentence it rests on, what scope and date that sentence covers, and whether you may repeat it. Most errors in partner copy are right numbers with their definitions stripped off: 50 employees without "full-time, at peak", 60 days without its trigger, 90 days without the event that starts the count. Restore the definition, cite the sentence, or delete the number.
Read → - A referral content test focused on executive understanding: a twenty-minute comprehension interview, scored blind, that checks whether an executive who read your material can say back who decides, what is asked of the company and who could be paid
Judge your referral material by what the executives who read it can explain afterward, not by clicks or replies. Write two truthful versions, assign each executive to one from a list drawn before anything is sent, and hold a twenty-minute interview: free recall, a teach-back of six points and four misreading probes. A coder who does not know which version the executive saw scores the notes. The primary measure is the share of executives with no critical misreading. No results from this design have been published.
Read → - A referral conversation for a founder with an existing AI policy: a clause-to-review map that shows which parts of the policy SourceX's process will meet, and who at the company answers each
Treat the founder's AI policy as their company's document, not a hurdle to help them clear. Many AI policies govern how staff use AI tools; licensing the company's own records to an AI developer is a different act, and the policy usually routes it to an approval rather than answering it. Show the founder which clauses SourceX's process will meet, leave the reading to the company and its counsel, and introduce only when the CEO, not just the founder you know, wants the conversation.
Read → - A referral dashboard for a small advisory practice: one sheet that counts the firm's own introductions by route and by the portal's status words, shows money only once a reward reads Paid and holds nothing of the client's
A small advisory practice needs one sheet with one row per company it introduced, a route column saying how each introduction was recorded, and a status column that copies SourceX's own words from the partner dashboard: Estimated, Eligible, Approved, Processing or Paid. The board counts rows. It never adds up estimates or forecasts reward income, and it holds no client records. The only money it shows is a reward that reads Paid and has actually arrived.
Read → - A referral email for someone who has never heard of training data: a ten-term plain-language explainer and one email rewritten from industry jargon into the owner's own words
Write the email in the owner's vocabulary, not the AI industry's. Most owners have never needed "training data", "evaluation" or "licensing" in this sense, so translate each into something they already understand: examples a model learns from, tests it is checked against, and paid permission to use copies of records under a contract. Lead with the records you know they keep, say plainly what you would earn, and offer a reply that takes five words.
Read → - A referral experiment with clear failure criteria: a partner-reminder test that names four ways it can fail, fixes the count and the consequence for each before the first reminder goes out, and treats a stop as a finished result
Failure criteria are the results, written down before a test starts, that would make you stop it or reject the change. A referral test needs four kinds: trust failures (a CEO pressed, or introduced without knowing), quality failures (more submissions but no more introductions reaching a verified application), waste failures (the extra submissions are duplicates or miss the published fit facts) and design failures (the test cannot be read). Each gets a count, a check date and a consequence, fixed before the first send. This page reports no result.
Read → - A referral follow-up after a board-approved strategy change: a strategy-to-scope update brief that turns each approved move into one question for the CEO, leaves board material out and lets the company tell SourceX what moved
A board vote on strategy changes the company's plan; it does not change who decides about licensing. The CEO still decides whether the company talks to SourceX, even when the board approved every part of the new strategy. Follow up with the CEO alone, using only facts the CEO has shared outside the boardroom: which records the strategy touches, which entity will hold them, who runs that work now and whether the company has room. If the company is already talking to SourceX, it updates SourceX itself.
Read → - A referral follow-up after a company has asked for more time: write down the terms of the wait, then follow up once, on those terms
A company that asks for more time has given you a preference, not an objection to overcome. Write it down in the company's own words: until when, what it is waiting for, who should be contacted and how, and what, if anything, it wants in the meantime. Then send one follow-up at that point, quote its condition back and offer two easy answers. Your own deadlines, including the 90-day attribution window, stay out of the message.
Read → - A referral launch that does not promise passive income: a conditional-outcomes kit that pairs every result a member or the association might hope for with the conditions behind it and the person who decides each one
Launch it as a conditional offer, never as an income stream. Nothing in SourceX's program pays by itself. A reward exists only if a member whose CEO asked to be introduced is credited, licenses its records and is paid by SourceX, and even then several payment conditions follow. For the member company, SourceX's own published answer to whether licensing income is passive is "Not fully." A good launch kit says both things in plain words, invites a small opt-in group and counts every member who says no.
Read → - A referral network needs an escalation owner: a routing map for nine common issues that names who decides each one, and why the owner decides almost none of them
Name one escalation owner for the whole network: the person who receives every issue that partners, companies or SourceX raise, routes it to whoever actually decides, keeps the clock and writes the closing note. The owner decides very little. SourceX decides attribution, eligibility and rewards; the company's CEO decides whether the company takes part; counsel advises on rights and contracts. What the owner prevents is an issue with two half-owners, or none.
Read → - A referral partner's public FAQ needs a named review owner: an owner map that gives every answer a person, the SourceX sentence it restates, the change that forces a re-read and a fixed date, and takes down any answer nobody owns
Every answer in a public FAQ about SourceX is a claim made in your name, and it goes stale the moment SourceX changes the page you paraphrased. Give each answer one named owner, the SourceX sentence it restates with that page's version or updated date, the events that force a re-read and a fixed review date. Questions only SourceX can answer get a pointer to SourceX, not an answer. Any answer that loses its owner comes down until someone takes it on.
Read → - A referral pilot for a fund exploring vertical AI: a one-page charter that names one sector, up to twelve operating companies, the conflict rule and the result that would end the thesis
A fund exploring vertical AI can test its thesis with a narrow referral pilot instead of a portfolio-wide push. Pick one sector, write the prediction that its established operators keep years of their own decision records, name the result that would disprove it, and ask relationship owners about no more than twelve companies over eight weeks. Aim at the incumbents in the sector, not the fund's AI startups, which rarely pass the size and history tests. Settle the conflict with your own portfolio before the first call.
Read → - A referral pilot that tracks complaints alongside applications: a stage-aligned dashboard that pins every complaint to the step that set up the expectation, keeps counting after SourceX decides, and reads the pilot twice before any variant wins
Put complaints on the same stage-by-stage dashboard as applications, and give every complaint two stages: where it surfaced and where the expectation behind it was set. Keep the complaint window open past the application read, because a misleading line often draws its complaint only after the company hears SourceX's decision. Read the pilot at day 90 and again on a later date fixed in advance. A variant wins only if it leads on applications and does not trail on complaints at both readings.
Read → - A referral pilot with no revenue assumptions: a budget for hours, asks and founder time, seven gates before expanding, and a quarter-end memo that can say stop
Budget the pilot as three capped inputs, platform hours, relationship-owner asks and founder time, each approved as a low-to-high range, and lock the reward income line at $0 for the whole pilot. Expand only if the result holds in the pilot's weaker half, enough qualifying companies with a willing relationship owner remain to fill the next cohort, and someone other than the pilot lead has run the process inside the range. Close every quarter with a one-page memo whose first word is expand, pause or stop.
Read → - A referral program for a network with mixed company sizes: a three-door routing guide that lets every member pick education, a self-check or an opt-in introduction by its own peak full-time headcount, so the association never guesses anyone's size
Write one program with three doors and let each member pick its own. A member whose full-time workforce never reached 50 gets education and a plain statement that the association does not introduce it. A member unsure of its count gets a self-check against SourceX's published criteria. A member that reached 50 or more full-time employees at its peak, contractors left out, can ask for an introduction its CEO approves. The association never sorts members by guessing their size, and never tells one that it qualifies.
Read → - A referral program with strong fit but uncertain conversion: a feasibility memo that separates what your firm can know from what only others decide
Strong fit means your clients look like the companies a program describes. It says almost nothing about how many will convert, because the decisive steps happen outside your firm: the CEO's interest, SourceX's duplicate and rights review, the program's current needs and the Acquisition Partner's final written acceptance. SourceX publishes no conversion rates. So size your firm's part by the cost it can absorb if nothing converts, learn the rate cheaply through a small dated pilot, and write down in advance which result means expand, maintain or decline.
Read → - A referral summary for a business with outsourced operations: a vendor-and-owner question map that routes every question through the company, never to its vendors
Outsourcing changes three facts a referral summary has to state: whose employees did the work, whose system holds the record and what the vendor contract says about both. Vendor staff are not the company's full-time employees, so they never count toward the 50 at peak. Records a vendor creates may still belong to the company, or may sit in the vendor's platform under contract terms. Sort each question by who can answer it, let the company ask its own vendors, and attach no records.
Read → - A referral summary for an offline business archive: a metadata brief written from box labels, tape indexes and storage invoices, with a how-we-know mark on every line and nothing opened, restored or moved
An offline archive, meaning paper files in storage cartons, backup tapes, retired servers, optical discs or drives in a cabinet, can be summarized for a referral without anyone opening it. Build the summary from what already describes the archive from outside: box labels, a box index, tape labels, storage invoices and the holder's own account. Mark how each line is known, name who instructs the holder and who decides for the company, and leave every box and tape exactly where it sits.
Read → - A referral summary that makes the first call shorter: twelve call-ready lines that settle what the company already knows, and an agenda built only from what is still open
A first call runs long when it is spent collecting facts the company already knows. A portfolio operations analyst can take those questions off the call by sending, with the CEO's approval, a summary of twelve short lines: who decides, peak full-time headcount, which systems hold the records, how far back they go and who created them. Every line says whether it is confirmed, an estimate or open, no records travel with it, and the call is left for what only SourceX's review can settle.
Read → - A regional founder newsletter about data partnerships: a location-bounded brief that quotes SourceX's geography sentence word for word, sorts the region's countries against it and keeps every item free of endorsement, qualification claims and reader data collection
A regional founder newsletter can explain that SourceX licenses records directly from established companies, but the region it covers is not a criterion and must never read like one. Brief the item before drafting it: quote SourceX's geography sentence as published, sort the region's countries against it, say that the CEO decides whether to talk and SourceX decides fit, state that the fund could be paid, keep any partnership claim off the page unless SourceX has authorized it in writing, and give readers a route that asks nothing of them. The newsletter collects nothing about readers' companies for SourceX.
Read → - A regional venture partner's role in global referrals: an eight-step handoff map in which the region holds the CEO relationship, the platform team keeps the record and checks for overlap, and SourceX decides fit and credit
A regional venture partner brings the one thing a global platform team usually lacks: a CEO relationship, in the CEO's language and time zone. The platform team brings what the region usually lacks: one current fit sheet, one record of who is asking whom, and a check that no one else in the fund already knows the company. SourceX decides everything else, including fit, duplicates and credit. Agree in writing who asks and who submits before anyone contacts the CEO, and keep partner location, company location and record language as separate facts.
Read → - A research map of the people who unlock company conversations: a role-to-conversation network study that logs every ask as a link between roles, keeps dead-end chains in the count and draws no map until consented chains exist
No one has published which roles in a professional network actually turn a known company into a CEO conversation about licensing its records, SourceX included. This page sets out a study to map it: every ask is logged as a link from one role to the next, from a partner to a company's CEO or to a dead end, and each role is scored on how often the chains passing through it end with a CEO who agrees to talk. Dead ends stay in the count. No chains have been logged, so no map exists yet.
Read → - A retention review for closed referral records: a retention owner checklist that dates the events still ahead of a closed file, from the protection period to a possible reward recalculation, and clears each record only when its last reason to stay has passed
Closing a referral file and clearing it are different moments. A closed file still has dated events ahead of it: the end of the partner agreement's term, a six-month protection period after that, repeat licenses agreed in either, a possible reward recalculation, an open dispute, and your own legal obligations. A retention review gives every record one owner and the event that ends its reason to stay, and clears it only when that event has passed. SourceX's confidential material is returned or deleted on its written request or at termination, and company files should never have been in the file.
Read → - A revenue allocation correction, worked step by step: the bundled-service modification case
The records that explain a revenue allocation correction are the ones that show the allocation before the change, the event that triggered it, the judgment applied, who approved it and the corrected result: the contract schedule, calculation version 1 with its stand-alone selling price inputs, the signed amendment, the adjustment memo, calculation version 2 with the controller's approval, and the reconciled journal entries. A corrected journal entry alone shows that money moved, not why. The worked case below is Illustrative.
Read → - A role changed after the start date: one placement guarantee dispute worked step by step
The records that explain a placement guarantee exception are the ones that show the promise, the change, the claim and the decision side by side: the job order with its fee and guarantee terms, the placement and any correction to its start date, whatever recorded the change in the role, the client's claim, and the memo and credit note that settled it. The illustrative case below follows one dispute through seven steps and names the record each step left.
Read → - A SaaS customer webinar about their own operating history: a 40-minute format that teaches customers what they own before anyone mentions a referral
Make it an education session about records your customers created in running their own businesses, not about what sits in your product. Teach what those records are, who usually owns them, how direct licensing works and which cases rarely fit. Disclose any referral reward on the invitation and on one closing slide, keep tenant data out of every example, treat the invitation as commercial email and follow up only with attendees who ask. Done that way, the session is worth an hour even to customers who never license anything.
Read → - A SaaS partner newsletter needs evidence, not a payout headline: the one-page brief that makes every claim earn its place before the issue ships
Write for the customer's decision, not your reward. In a newsletter about SourceX, the referral reward goes to your company, so a reward-figure headline advertises your incentive and implies a figure no customer has been offered. Lead with what the customer's own company could license, who decides and what your company never touches. Give every claim a source before the issue ships, disclose that you may earn a reward, and judge the issue by opt-in replies from decision-makers, not clicks.
Read → - A small association can run a useful pilot with five members: a one-page charter that tests whether the topic helps members, counts every no and never collects a word about anyone's records
Five members are enough to learn whether the topic helps your members, whether the invitation reads as pressure or as the association vouching for SourceX, and whether your decline and feedback routes actually work. They are not enough to estimate how many members could fit SourceX or what anyone might earn. Write a one-page charter before inviting anyone: who may join, what the association provides and never collects, four questions for every participant, stop rules and a decision date.
Read → - A smaller specialist may need a different referral route: the exception inquiry brief to send SourceX before anyone introduces a company under 50 full-time employees
A specialist below 50 full-time employees at peak sits between two published statements. SourceX's program terms make 50 or more at peak part of the sourcing criteria for introduced companies, while its screening page says smaller specialists can still be considered. Neither says how. So do not introduce such a company as an ordinary referral. Send SourceX a metadata-only exception inquiry first, tell the CEO that nothing is decided, and treat any reward as an open question until SourceX answers in writing.
Read → - A SourceX partner should not invent a buyer relationship: a relationship claim evidence register that sorts every "we work with" line by the relationship it asserts, the record that would prove it and who may say it, and shows why buyer claims fail every row
Make no buyer claim at all. SourceX does not publish the names of the organizations that license its datasets, its sample partner agreement says an Acquisition Partner's identity may stay confidential, and the program terms say partners never receive confidential buyer information. So a partner who writes "we place data with AI labs", shows a lab's logo or hints at who buys has either invented a relationship or repeated something it should not hold. Publish only the relationships you can document.
Read → - A stage model for SourceX referrals that does not imply revenue: a twelve-stage dictionary in which every stage opens only on dated evidence, names who produced it and carries no amount until the reward reads Paid
Name each stage after the evidence that opens it, never after the result you hope for. A SourceX referral passes through stages the partner produces (CEO asked, CEO agreed, introduced), stages the company and SourceX produce (a credited application, review, a signed deal, Closing) and the dashboard's reward statuses, Estimated, Eligible, Approved and Paid. Give none of them an amount, a probability or a forecast date. Only Paid means money has moved, and until then the cash line stays at $0.
Read → - A supplier corrective action worked step by step: the fix that cured short shots and caused warping
The records that best explain how a supplier exception was handled are the ones that show the loop did not stop at the supplier's answer: the defect evidence that opened the SCAR, the supplier's containment and root-cause response, the verification inspection that tested the fix, the reopen entry when the fix failed, the revised action and the closure approval tied to passing lots. A SCAR closed on the supplier's word shows a response; one closed on verification data shows an outcome.
Read → - A surge in transactions is not the same as licensable data: a volume-versus-rights matrix that asks whose record each transaction creates
Screen transaction growth for rights before volume. A surge in payments, orders or claims shows that records are piling up; it does not show whose they are. Split each transaction into layers (the record of the sale, the people in it, client data handled on someone else's behalf, and the company's own handling work) and ask who decides how each layer is used. The part a company can usually license is its own work around the transactions, and that part grows more slowly than the count.
Read → - A trigger-based referral calendar that avoids opportunistic outreach: a relevance-and-consent matrix that sorts every business event into book, hand to the owner, note only or keep off, so one person asks one CEO one question
A referral calendar should book a question only when an event passes two tests: it bears on the company's own records or on who decides for it, and the company shared it in a way that lets it open this conversation. Events that fail either test are noted or kept off the calendar. Give every company one named owner, one question per qualifying event and an expiry date, so a single piece of news never sends several people from the same network to the same CEO.
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