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 founder says they own the data. What happens next: decode the claim, write a dated handoff note and let SourceX's rights review test it
When a founder says the company owns its data, treat the sentence as a claim to pass on, not a fact to repeat. Write it down word for word with the date, place it on the right entity, controller and CEO, and translate it into a short note that SourceX's rights review can test: who created the records, in which system, and whether clients or contracts have a say. Then stop. The partner never certifies ownership, asks for contracts or handles records.
Read → - A founder succession can reset the introduction path: a succession sponsor handoff checklist that sorts what your tie to the departing founder still carries, names who you speak to once a new CEO holds the role, and asks that CEO afresh
A founder succession resets the introduction path because the decision moves to a new person while your relationship stays with the old one. From the day a successor holds the CEO title, the successor decides whether the company talks to SourceX; an earlier yes from the founder, and your standing with the founder, do not pass to them. If the succession runs through a sale, the target's CEO decides until closing and the acquirer's CEO after it. Rebuild a path to whoever now holds the role before you ask anything.
Read → - A founder survey before a data partnership webinar: six questions that ask only what founders want covered and whether they will attend, a results-to-agenda rule set before the send, and answers that never leave the host
Before a data partnership webinar, ask founders three things only: which topics they want covered, which questions they want answered and whether they plan to attend. Ask nothing about their companies, so no names, headcounts, systems, record types or customers. Say at the top who is asking, that the fund could be paid as a SourceX referral partner, and that answers stay with the host and come back only as totals. Then let the replies reshape the agenda by a rule you wrote down before sending.
Read → - A fractional CFO's playbook for MSPs: separating the MSP's records from client data
A fractional CFO for an MSP or IT services firm runs agreement profitability, technician utilization, cash and board reporting from the PSA, project and finance systems, which shows how deep the firm's records go. The MSP's own operational records may suit a data licensing introduction; data from inside client environments belongs to clients and needs their consent.
Read → - A fractional CFO's playbook for spotting licensable records at B2B SaaS clients
A fractional CFO serving SaaS companies sees the vendor list and the board deck, which makes them well placed to spot clients whose internal work records could be licensed for AI training. The best fits have 50+ full-time employees at peak (contractors excluded), years of Jira, Git and support history, clean IP assignments and a CEO open to a license.
Read → - A fund network can collaborate without a shared database: a minimal shared-state model in which each fund keeps its own notes and only four fields about any company ever pass between funds
Coordinate the ask, not the data. A network of funds needs to know one thing per company: which single person is asking its CEO, and where that ask stands. Everything else, from fit notes to board knowledge to SourceX's updates, can stay in each fund's own system. A pooled spreadsheet of companies adds confidentiality exposure, invites claims SourceX's terms never honor and goes stale as the people who wrote it move on. Four shared fields, sent only between funds that already know the company, do the coordination job.
Read → - A fund partnership memo that separates help from compensation: a two-track collaboration memorandum where contributions are logged without a price and payment questions are answered without crediting anyone's help
Write it in two tracks that never refer to each other. Track A logs the help each fund gives around one company decision, such as context, a path to the CEO or stepping aside, and attaches no value to any of it. Track B answers the money questions once: SourceX credits one partner per company and pays that partner directly, anything between the funds needs its own signed agreement or does not exist, and each firm's own documents govern what its people may accept. Sign it before anyone contacts the CEO.
Read → - A fund's network inventory should include former operators: a permissioned outreach map that tests what they remember against who runs the company today
Former operators, the ex-COOs, ex-CEOs and functional leaders who now advise, scout or sit on a fund's bench, often know mature, owner-led companies that never appear on a cap table. They belong in your network inventory, with one discipline: what they remember is dated. Before anyone asks, confirm who runs and owns the company today, whether the operator still has a relationship with that CEO, and that the CEO wants the conversation. Order the calls by those checks, never by what a license might pay.
Read → - A fund's senior advisors need a common referral brief: an advisor enablement one-pager that gives every advisor the same fit facts, the same CEO-decides line, the same list of things never promised and one way to record an introduction, with the terms linked rather than retold
Write one dated page that every senior advisor uses when SourceX comes up, and retire the versions they have been improvising. It should say who might fit and link the rest, name the company's CEO as the person who decides, list what an advisor never promises and set one way to record and credit an introduction: one introducer per company, agreed before anyone asks. Link the program terms instead of retelling them, and leave each advisor's own agreement with the fund in charge of whether they may be paid.
Read → - A global network pilot with country-specific stop rules: a local-review stop criteria matrix in which each pilot market goes, amends or stops on triggers the platform team writes before the first ask, while SourceX's published geography sentence stays the only country rule
Run it as several small pilots, one per market, under stop rules your platform team writes before anyone asks a CEO. Each market carries its own triggers, such as an introducer whose local professional or employer rules are not yet cleared, an invitation translated without review, or a contact offering company records. When one fires, that market amends or stops while the others continue. These are your operating rules, not SourceX's: the only country rule SourceX publishes is the geography sentence on its who-qualifies page, and SourceX's review decides fit.
Read → - A global partner directory should show coverage, not blanket approval: a coverage-versus-eligibility metadata standard in which every country field describes where a partner works, SourceX's sentence appears once and word for word, and no field speaks for SourceX
Give each listing coverage fields only: the countries where the partner works, as ISO country codes, the languages they work in, the sectors they know, and the date they last confirmed it. Keep eligibility out of listings entirely. Quote SourceX's geography sentence once, word for word, at the top of the directory, link the English-language guide, and never expand the sentence into a country list, a tick or a shaded map. A listing says where a partner can make introductions; SourceX alone decides which companies fit.
Read → - A global portfolio is not a single data referral market: a market-specific screening design that records partner location, company location, record language, the entity holding the records and the deciding CEO as five separate facts, and routes every local question to the person who owns it
Do not run one program for a portfolio that spans continents. SourceX screens companies, not funds, so a global platform team needs a design that records five facts separately for every company: where the introducing partner is, where the company is based, what language its records are in, which entity holds them and whose CEO decides. The published location rule settles only some of those cases. Questions about local tax, law or payments go to the right adviser, never to the platform team's best guess.
Read → - A growth signal dashboard with no invented revenue numbers: ten public fields and one private one, each tied to a source, a date and a fit check
A growth signal is a change between two dated public observations of the same field, such as the employee count in two annual reports. It tells a research lead where to look; it does not show that a company fits a data licensing program or that its records are worth anything. Build the dashboard from fields that each feed one published fit check (size at peak, operating history, rights, an authorized CEO, location and language), date every cell, and leave revenue estimates off it.
Read → - A high-paying referral program for people who know company owners: what to check first
Before joining any referral program, someone who knows company owners should check five things in writing: what the percentage is calculated on, whether there is a cap or a minimum transaction size, which events must happen before payment, what a later reduction does to the reward, and whether the reward comes out of the owner's money. Then check your own position: disclosure to the owner, any advisory conflict and whether your contacts actually qualify.
Read → - A hiring surge is a clue, not proof of a valuable dataset: grade every public signal from A to D before it shapes an introduction
A hiring surge tells you a company expects more work. It says nothing reliable about the records it already holds, who owns them or whether anyone would license them. Use job postings as clues and grade each one: A for a dated record from the company about the fact itself, B for a company publication that implies it, C for a third-party aggregate, D for your own inference. Never let a C or D settle size or rights, and ask the company for the rest.
Read → - A leadership offsite can surface data ownership questions: an optional module the company runs and keeps for itself, a partner who stays out of the room, and a CEO who decides whether anything follows
An offsite is the company's private working time, so a partner's part in it is small: offer an optional discussion module the leadership team can run for itself, stay out of the room, and wait. Whatever surfaces, from who owns each record set to what customer contracts promise, belongs to the company. A partner does not attend for SourceX, ask for the notes or treat the agenda as a lead. If the CEO later wants a conversation about licensing records, the CEO raises it, and SourceX decides whether the company fits.
Read → - A lightweight service level for founder introductions: a one-page response-and-escalation template that commits the platform team only to clocks it controls
Commit founders only to clocks the platform team controls: how fast it acknowledges a request, how soon it gives a yes, no or later on fit, and when it escalates a stall. For SourceX's side, repeat only what SourceX publishes, such as its supplier-process targets and the referral payment deadline, and say plainly that review timing belongs to SourceX. Run the commitments as internal objectives, not a contract, and keep them only if a zero-revenue pilot shows founders actually use them.
Read → - A link click is a browser, credit is a company: the event-to-entity map from first visit to attributed company
A click proves that a browser opened your link. Attribution is a decision about a company. SourceX credits the first valid introduction of a company that is new to SourceX, once that company submits a verified application within 90 days of the recorded introduction, and its terms say an earlier click alone does not decide credit. Between the click and the credit sit five entity questions: which person, which organization, which legal company, which group, and whether SourceX already knew it.
Read → - A LinkedIn conversation that leads to an authorized introduction: six private turns from a CEO's public post to a written yes, with an exit at every turn
Keep the conversation private and keep the CEO in charge of it. React to what the CEO posted in public without mentioning data or SourceX, then send one private message asking whether they want to hear about it. Explain the program and your reward only after they say yes, confirm that yes by email, and only then submit the introduction. Nothing about the company or your partner role goes in a public post or comment, and a reply from a colleague is not the CEO's authorization.
Read → - A longitudinal study of repeat company introductions: a partner behavior cohort protocol that asks whether news about a partner's first company changes when they introduce the next, follows each partner for 24 months and counts only months under a signed agreement
Nothing is known yet: SourceX has published no figures on whether a partner's next introduction depends on what happened to their first. A study that could answer it follows every partner from their first submitted introduction for 24 months, records what each one could see about earlier companies on the day of every later introduction, counts only months under a signed Channel Partner Agreement as time at risk, and keeps partners who never return in the count. No results are published.
Read → - A member webinar should include who is unlikely to qualify: an eight-card audience module for the first fifteen minutes, each card with its published basis, what could change it and where that member goes instead
A member webinar on licensing company records to SourceX treats attendees fairly only when each of them can tell early whether it applies to their company. Give the members it does not suit the first fifteen minutes, not a footnote: firms whose full-time headcount never reached 50, firms whose files belong to clients, consumer-data businesses, records already licensed for AI training and four more cases. Show each with its published basis and what could change it, then hand everyone a private self-check and an easy way out.
Read → - A meter correction dispute worked step by step: an exchanged device billed at the old scaling factor
The records that explain a meter correction dispute are the reading history on both sides of a device exchange, the dated scaling factor in billing, the dispute ticket, the field investigation note with nameplate evidence and the approved rebill that corrects both the bills and the configuration. Together they show what went wrong, who decided each step and how the fix was checked. The Illustrative case below walks through one dispute in order.
Read → - A monthly financial review meeting agenda for CFOs and business owners
A monthly financial review meeting should run about 60 minutes in a fixed order: close status, flash results, cash, budget-versus-actual variances, KPIs, the rolling forecast, a five-minute standing item on underused assets, and a decision log. The standing item gives a CFO a routine slot to ask whether years of operational records could be licensed.
Read → - A monthly investor partner report that protects confidentiality: one coded row per company, a reason in every empty cell, and no names beyond the fund team
A useful investor partner referral report follows each unique company, not each introduction, through dated stages from the CEO's consent to a paid reward, and gives every empty cell a reason: zero, unresolved, closed, not applicable, not available or withheld. Company names live in a register that only the people covered by each CEO's consent can open; the monthly edition uses reference codes. SourceX's statuses are confidential under the Channel Partner Agreement, so the edition stays inside the fund unless SourceX authorizes more in writing.
Read → - A network expansion plan with clear quality gates: five stages from a founding cohort to open enrollment, each opened by evidence and guarded by a rollback trigger
Expand a referral network one stage at a time and let evidence, not sign-ups, open each gate. A workable plan has five stages, from a founding cohort to open enrollment. Each stage opens only when the previous cohort's introductions were clean, active companies fit within the hours available and the duplicate register holds no unresolved claims; each also carries a rollback trigger that sends the network back a stage. Logo counts open none of the gates.
Read → - A network inventory that excludes people who declined: a suppression pass that runs before any fit screen, and a consent and decline template whose states only the right person can change
Referral network suppression means taking out every person and company that has said no, or that a relationship owner has said no for, before the inventory is screened for fit. Merge the declines your firm keeps in different places into one record per contact with a state, a scope, a source and a date. A fresh public clue never reopens a recorded no. What survives the pass is a list of people you are allowed to ask, which is not the same thing as a list of companies that qualify.
Read → - A new CEO's first 100 days: include a data asset review
A new CEO's first 100 days plan can include a short data asset review: list the systems that hold years of operational records, who can export them and who owns the rights. It takes little time and shows early whether licensing records to SourceX is a realistic option for the company.
Read → - A new CFO's first 90 days, with a data asset inventory built in
A new CFO's first 90 days run in three phases: learn cash, the close, controls and people by day 30; fix reporting and forecast gaps by day 60; set the budget, board package and priorities by day 90. Add one metadata-only step: list every system and its years of history, because that map can reveal a licensable data asset.
Read → - A new operations leader reviews the company's archives: why the review's readout to the CEO is a fair moment for one licensing question, and a one-page introduction brief in which the new leader helps find what exists and the CEO alone answers
When a new operations leader reviews what the company has kept, the CEO is about to hear, in one place, which archives, old systems and storage contracts hold the company's history and what each one costs. That readout is a fair moment to ask the CEO one question about licensing the company's own records. The new leader can help find who decides and what exists. The CEO decides, and nobody outside the company reviews, exports or summarizes a single record.
Read → - A new records manager can clarify the introduction path: a records-role sponsor handoff that uses their first inventory to name the entity, the systems and the CEO who decides, without asking them to decide or to send anything
When a company hires a records manager, someone is about to write down what records exist, where they sit and who answers for each. That makes the hire a good moment to clarify the introduction path, and a poor moment to ask the new person for a decision. With the CEO's agreement, a records manager can help confirm which entity holds the records, which systems they live in and who runs each one. The CEO alone decides whether the company discusses licensing, and nothing is sent anywhere.
Read → - A part that passes one specification and fails another: a worked nonconformance disposition case
The records that explain a disposition are the ones that capture the problem, the authorized action and the checked result in sequence: the inspection report with its sample data, the hold report, the engineering notes on cause, the review board minutes listing options, the customer's answer to any request to ship as is, the rework instruction and the re-inspection. A status field that says "rework, closed" keeps only the ending.
Read → - A partner changes employers: who owns the active referral? A five-record review that starts at the signature page, not the business card
An open referral belongs to whoever is the Partner in the signed SourceX Channel Partner Agreement and recorded the introduction, and that party can be you as an individual or the firm you worked for. Changing employers does not move it. If you signed in your own name, it goes with you; if your employer signed and you introduced through its account, it stays with the employer. Assignment needs SourceX's written consent, accrued rights survive the end of an agreement, and what you owe an employer is a separate contract.
Read → - A partner directory should not imply guaranteed results: an evidence standard for each field on a listing, from 'SourceX partner' to 'companies introduced'
Treat every field on a directory listing as a claim, and publish only what its evidence supports. Calling someone a SourceX partner needs SourceX's written authorization under the Channel Partner Agreement. Activity counts need dated records of unique companies. Results, such as completed licenses or rewards paid, need permissioned, verified records and a fair picture of what is typical; SourceX publishes no outcome averages. Anything that implies acceptance, earnings or speed nobody controls stays off the listing entirely.
Read → - A partner firm's internal reward allocation needs its own agreement: a twelve-point review checklist to settle before anyone is promised a share
SourceX pays the partner named in the signed Channel Partner Agreement, whether that is a firm or an individual, and nothing in its terms or agreement says how a firm divides a reward among the people who made an introduction possible. That division needs its own written agreement, settled before the first introduction: who counts as a contributor, what each share is calculated on, when it is paid, and what happens after a reduction, a departure or a reward that never arrives.
Read → - A partner marketplace listing for an introduction-only program: a 13-field accuracy checklist before a SaaS company lists a data licensing partner
List it as an introduction, never as an integration. A SaaS company that adds an introduction-only data licensing program to its partner marketplace or partner directory should say plainly that no data passes through its product, that the customer's CEO decides and SourceX contracts with the customer directly, which companies may qualify, and that the vendor may earn a referral reward paid by SourceX. Remove anything that implies a connector, likely payouts or pre-approval.
Read → - A partner's first-response checklist for an interested owner: ten pre-send checks that make the first reply answer the owner's question, name the CEO as the person who decides, disclose your interest and promise nothing
Treat "I'm interested" as a question, not a yes. The first reply should answer what the owner actually asked in its opening lines, confirm that the company's CEO is the one who decides (in an owner-run company that is usually the owner), say plainly that SourceX could pay you a reward, and give the published fit screens so the owner can test the company alone. It promises no outcome and no date, asks for no records, makes a no as easy as a yes, and sends nothing to SourceX until the CEO agrees in writing.
Read → - A partner's public research notes should state their limits: a source-date-inference notation that marks every clue with where it came from, when it was true, what you concluded and what it cannot show, so a note prompts a question for the CEO and never reads as a verdict on fit
A public research note is useful only as a source of questions for someone who knows the CEO. Write every line in six marked parts: the source, the date it was published, the date you viewed it, the inference you drew, the limit of that inference, and the question it suggests. Public information can prompt a question; it never establishes fit, rights or eligibility. The CEO confirms facts, SourceX's review decides fit, and a note with no path to the CEO ends in an archive, not an email.
Read → - A partner's questions before forecasting a large reward: a twelve-line evidence checklist that decides whether a large figure belongs in cash, on watch or in a memo
A large reward is a ceiling, not a receivable, until SourceX has paid the referred company. The default on a company's first qualifying transaction is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, so a USD 70,000 reward needs USD 400,000 actually paid to one company or corporate group; repeat transactions within the 12-month Repeat Window pay 15%. Before a large figure enters a forecast, a finance manager needs evidence on twelve points: credit, the payout document, whether the floor is already used, group structure, installments, timing anchors, open conditions and signed exceptions. Where evidence is missing, the figure stays off the cash line.
Read → - A partnership budget that accounts for training and review: a full-cost pilot budget that prices the hours firms forget before the first introduction
Budget for the hours a referral partnership uses whether or not anything pays: training the people who will introduce clients, reviewing each candidate before a CEO is asked, checking conflicts and professional rules, keeping records and reviewing the pilot at the end. Price those hours at a loaded cost, meaning wages plus benefits, and set every reward line to zero. In the Illustrative budget below, training and review take about two-thirds of the hours, which is why a budget that counts only client conversations comes out far too low.
Read → - A payer requirement changed mid-request: one prior authorization follow-up case worked step by step
The prior authorization records that explain how an exception was handled are the version chain: each submission as it was sent, with its attachments; the pend or missing-document request that stopped it; the internal task that fixed it; and the final status with its authorization number and dates. A single final status hides the exception. The versions in order show the problem, the authorized action and the checked result. The illustrative case below works through one such chain.
Read → - A peer learning session for founders who declined: a noncommercial design that founders chair, built on how each one decided rather than on advice, with no SourceX in the room, no follow-up from the host and nothing that reopens a no
Hold the session only if founders ask for it, let a founder chair it, and keep everything commercial out: no SourceX speaker, no partner link, no reward talk and no follow-up from the fund to anyone who attends. The learning comes from founders who have already decided, comparing how they decided: what they checked, whom they asked and what settled it. A no stays a no. The session is not a second ask, and the host should design it so that it cannot turn into one.
Read → - A permission log for investor-led company introductions: a source-date-scope register with one row per yes, and a send rule that passes on only what every row allows
An investor-led introduction usually rests on several permissions, not one. The person who owns the relationship agrees to an ask, the CEO agrees to an introduction, and the CEO decides what may be shared and whether your fund can be named. Log each as its own row: who agreed and in what role (source), when and with what written evidence (date), and exactly what it covers and leaves out (scope). Send SourceX only what every active row allows, and stop the chain when anyone withdraws.
Read → - A pilot for networks with few eligible companies: a small-network feasibility test that counts the eligible pool before anyone is asked, sends every company through one truthful protocol and judges the pilot on what a zero-transaction result can still show
Count the pool before you design anything. When only a handful of companies in your network pass SourceX's published fit facts, a pilot cannot compare two messages or estimate a rate. What it can show is whether the work is feasible: whether your desk count was right, whether relationship owners will ask, whether founders feel free to say no and whether the protocol holds. Run every eligible company through one truthful protocol, report each case and every zero as published counts, and decide on a date fixed in advance. No results from this design are published.
Read → - A pilot that includes companies likely to decline: a negative-case sampling plan in which each relationship owner seals a prediction before any ask, the draw takes a fixed number from the companies expected to say no, and every CEO is asked the same way
Put companies you expect to decline into the pilot on purpose, or it can only measure your favorites. Before any ask, each relationship owner seals a prediction for every company that passes the fit facts they know: likely yes, unsure or likely no. The draw then takes a fixed number from each group, likely no included, and every CEO gets the same single ask with an easy no. If likely-no companies say yes about as often as likely-yes companies, your silent pre-screening is discarding conversations. No results exist yet.
Read → - A pilot that measures founder understanding before applications: an eight-statement comprehension survey with a scoring key for the misreadings an investor's mention can create, two truthful explainers, and stop rules a platform team writes before any founder applies
Test what founders believe before any of them applies, and score the explainer rather than the founder. Ask each consenting founder eight true-or-false statements about what applying starts, who decides and who is paid; mark the six whose misreading would do harm; and compare your standard note with the same note plus a one-page sheet of SourceX's own facts. Write the cohort, measures, stop rules and decision rule first. No founder has taken the survey yet, and its results table is empty.
Read → - A plain-English fund participation policy for data referrals: a twelve-clause policy blueprint with counsel checkpoints, written in sentences a portfolio founder could read, that says who may ask, through which account, what the company is told and where the fund's own papers take over
A workable policy fits on two pages and answers six things in plain words: whether the fund takes part and through which party, who may raise SourceX with a company, what every CEO hears first, which information never moves, where any reward goes, and who keeps the policy current. The blueprint below gives twelve clauses with draft wording. Five carry counsel checkpoints, because only fund counsel reading the fund's own documents can complete them. SourceX's published terms supply the referral facts; nothing here is legal advice.
Read → - A platform company CEO's playbook for buy-and-build integration and combined records
A platform company CEO in a buy-and-build should sequence integration around people, customers, cash and systems, then make one decision only the platform can make: who owns, keeps and may license the combined records of every add-on. As the authorized sponsor, the CEO decides whether SourceX should assess those archives for an AI-training license.
Read → - A platform team's early-warning system for changing data needs: a weekly, monthly and quarterly review cadence that weighs each signal by its distance from a SourceX decision
Data needs change in layers, and an early-warning system should weigh each layer by its distance from a SourceX decision. SourceX's own program pages, the terms version and the who-qualifies criteria, are authoritative and cheap to check weekly. Your introductions' outcomes are direct but sparse, so review them monthly. AI research and regulation move first but say nothing about any program, so read them quarterly as hypotheses. Change founder outreach only on the first two layers, and never infer who is buying from news.
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