This hub offers practical guides and best practices for advisors looking to successfully introduce companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) to SourceX, a direct licensing partner for approved business data for AI training and evaluation. Here, you'll discover step-by-step instructions and strategic insights for introducing companies to SourceX, which licenses data directly from companies and manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. These resources are designed to help you navigate the process efficiently, focusing on companies with 50+ full-time employees at peak. Unlock the potential of valuable data partnerships by leveraging these comprehensive guides.
Practical guides to successful company data introductions
Short, task-focused guides on identifying suitable companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English), recognizing valuable proprietary data, and making an introduction the decision maker will welcome.
- Step 1Share your linkSend your personal link to a company you know.
- Step 2Company appliesThe company applies itself at /apply.
- Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
- Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.
Common questions
What kind of companies should I introduce to SourceX?
You should focus on introducing companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia (outside the U.S., Canada and the EU, at least 70% of the data must be in English) that have 50 or more full-time employees at peak. These are the companies that can unlock the potential for valuable data partnerships with AI labs and data buyers.
What is the purpose of these guides?
These guides offer practical instructions and strategic insights for advisors to successfully introduce companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia to SourceX. They help navigate the process efficiently and identify valuable proprietary data for AI labs and data buyers.
Who benefits from SourceX data introductions?
AI labs and data buyers benefit from approved business data that SourceX licenses directly from companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia for AI training and evaluation. Advisors can also benefit by introducing companies to SourceX as their direct licensing partner.
What kind of information do these guides provide?
These guides provide step-by-step instructions and best practices for identifying suitable companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia. They help in recognizing valuable proprietary data and making introductions that decision makers will welcome, facilitating data transactions for AI.
Related pages
- How to model a one-time receipt, like a data license, in a 13-week cash flow forecast
- 2021-vintage private equity funds: what to do with companies bought at peak multiples
- 3PL and logistics M&A in 2026: what buyers want and what sellers should preserve
- 3PL valuation multiples in 2026: what buyers pay for in a logistics business
- A/E industry M&A trends in 2026, and what selling firms should prepare
- Acquiring a business from a retiring owner: assessing decades of records before they go
- How to control internal access while preparing records for licensing
Limit who can touch exports during a licensing project: name a small team, stage files in one locked area, log every access, and delete working copies once handover is confirmed. Internal handling is where leaks tend to start, so set these controls before the first export runs, not after.
Read → - How to coordinate a referral across regional fund offices: a claim, hold and choose workflow that names one speaker for each company before any office makes contact, and leaves credit to SourceX's dated records
When two or more of a fund's regional offices know the same company, agree on one speaker before anyone contacts it: normally the person with a direct, current relationship with the CEO of the company that holds the records. Write the choice down with a date in one shared log, let the other offices send their context through the speaker, and keep location facts on separate lines. Offices coordinate who speaks to the company, not who gets credit. Only one introduction can be credited, and SourceX settles overlapping cases in duplicate review from dated records.
Read → - How to coordinate local chapters without duplicate outreach: a chapter communication ownership map that gives each member company one notice, one person to answer it and one record, and leaves overlapping credit to SourceX
Give each member company one notice, one person to reply to and one record, however many chapters it belongs to. The national office sends the notice, chapters reuse it word for word, and a single request desk answers every member CEO and keeps the declines that all chapters honor. Those are rules your association adopts for itself. SourceX's terms say nothing about chapters: they credit no more than one introduction per company and leave overlapping claims to SourceX's duplicate review.
Read → - How to coordinate office hours across time zones: a timezone-fair rotation that shares the early and late slots, adds a written lane for founders who cannot attend and asks for a question, never company data
Publish a rotation, not a fixed hour. Pick three windows in UTC so that each one falls inside the working day of most of your founders, cycle the sessions through them so no region always gets the early or the late slot, and give anyone who still cannot attend a written lane that gets the same answers. Recheck every published time in the weeks when clocks change. Ask for a time window and a question only, never company facts, and wait for a CEO's written request before anything moves toward SourceX.
Read → - How to correct a mistyped company name in a referral record: a nine-line correction request that keeps the original entry and proves which company you meant
Leave the original entry as it is and send SourceX a dated correction beside it. State the mistyped name exactly as recorded, the company's correct legal name, and the details that were right from the start: the web domain, the CEO you introduced and your dated introduction email. Attribution is decided from dated records about a company, so a spelling slip is usually repairable when those details agree. A correction cannot move your introduction date, create a written record that never existed or turn a different company into the one you meant.
Read → - How to correct a referral email sent with too much detail: an incident triage and correction checklist for the first hour, the first day and the record, with the CEO's call, a written deletion request to every recipient and a replacement message that carries five lines
Stop the email from traveling further, tell the company's CEO what went out and to whom, and ask every recipient in writing to delete it along with any forwards. Then send a replacement that carries only what an introduction needs, and record the incident in your own files without copying the detail again. Recall buttons rarely help once a message has left your own organization. Whether the slip triggers any legal duty is a question for your counsel and the company's, not for the correction email.
Read → - How to correct a shared referral graphic with wrong economics: an asset replacement and notice workflow that finds every copy of the image, replaces or stamps each one, tells the people who acted on it and retires the old file for good
Treat a wrong graphic as many copies, not one post. Save the original, list every place the image now lives (your web page and its link preview, posts, decks, PDFs, email attachments, colleagues' reposts), replace the file wherever you control it, and where you cannot, publish a corrected image that carries a visible correction on its face. Tell the people you know acted on it what changed, then delete the old file from every template and asset folder so nobody reuses it next month.
Read → - How to correct an overenthusiastic message before it spreads: one correction text, channel-by-channel placement rules and a first-day checklist
Correct it where it was said, as visibly as it was said, and the same day. Find every copy, then send or post one short correction that names each wrong claim, gives the accurate term and links to it, and adds the reward disclosure if it was missing. Do not delete quietly where people have already read it, and do not count on an email recall: Outlook's recall works only within one organization. Then ask anyone who forwarded the original to forward the correction, and write down what you did.
Read → - How to cross-sell accounting firm services with a records-and-systems question
Cross-selling accounting firm services works best when it starts from a problem the client has. A records-and-systems question, such as where years of history live and what happens to them at the next migration or sale, opens firm advisory work first; for clients with deep records and an interested owner, it can lead to a cleared, permissioned data-licensing introduction.
Read → - How to cut software costs without losing the history in cancelled tools
Software rationalization reduces cost by inventorying every application a company pays for, measuring real usage, and cutting or consolidating tools at renewal. Before cancelling any tool that holds years of work, export its full history to company-controlled storage; tickets, deals and project records with outcomes can sometimes be licensed to SourceX for a one-time payment.
Read → - How to decline an introduction request without hurting the relationship
To decline an introduction request, reply within two business days, say no to the introduction rather than the person, give one honest reason and offer a small alternative. Use a quick test on fit, timing and conflicts first. It keeps your network trusted and keeps SourceX introductions high quality.
Read → - How to delegate referral screening without delegating judgment: ten training rows, named escalation triggers and a calibration check before the screener works alone
Delegate the checks that have published answers and keep the calls that need a relationship or a judgment. An associate can screen a company's metadata against the published fit facts and decline the clear misses with a logged reason. The platform lead keeps every decision to ask, every edge case and anything touching consent, confidential sources, records or money. Train the screener on worked rows, escalate on named triggers, and let the screener decline alone only after a calibration round with no missed escalations.
Read → - How to deleverage a portfolio company without selling assets
To deleverage a portfolio company without selling assets, combine fast cash levers (working capital, pricing, cost) with one-time, non-dilutive sources such as licensing operational records, then route the cash through the credit agreement's prepayment and sweep rules. A license keeps ownership with the company, and payment typically arrives within 60 calendar days after SourceX receives a valid invoice following Closing.
Read → - How to describe a client's data assets in a CIM without exposing confidential records
Describe data assets in a CIM at metadata level: name the systems, the years of history each holds, the workflows and outcomes they record, and who owns the rights, without quoting any record. If the company has signed or is negotiating a license, disclose scope, exclusivity, term and payment structure, and withhold licensee names unless the agreement allows them.
Read → - How to describe an archive's time coverage accurately: a date notation guide for start, end, gaps, migrations and the dates nobody is sure of
Describe an archive's time coverage as a dated range, not a count of years: the month the company's own records start, the month they end or the date you checked a system that is still running, every known gap, and which date the range counts (when the work happened, when it was entered or when it was migrated). Mark approximate and uncertain dates instead of rounding them, and say who supplied each date. The company approves the line, and no records travel with it.
Read → - How to describe operating history without exposing records: the altitude test, one company drafted three ways and a six-line summary the CEO approves
Describe operating history at the altitude of categories, spans and ranges, never at the altitude of a record. A useful referral summary says which kinds of work the company recorded, since roughly when, in what volume, in which kind of system and who created it, then names what nobody knows yet. It quotes no record, names no customer or employee, attaches nothing, and goes out only after the CEO approves the wording. Whether any of it fits a current program is for SourceX's review to decide.
Read → - How to describe referral economics without treating them as forecast revenue: an uncertain reward scenario worksheet with no odds column and no total row, eight scenarios each tied to a dated record, and the words that keep a possible reward out of the practice plan
Describe a SourceX reward as a one-off, conditional amount that exists only after a company you introduced is credited to you and completes a qualifying, paid licensing deal under the published terms. Until then you can state the formula, on the company's first qualifying transaction the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, and the conditions, but not an amount. Keep it out of revenue forecasts, budgets and pipeline totals, and record a reward when it is paid.
Read → - How to describe security work without claiming certification: a status evidence review sheet for every security line, badge and icon on a partner's pages, posts and agency copy, matched to the sentence its owner published and the date it was checked
Describe security work as work: in its owner's own words, with a status and a date. For SourceX, quote its trust center, which on 28 October 2026 listed a SOC 2 Type II report and ISO/IEC 27001 and 27701 certifications as in progress, none issued, beside the controls it says are in place today. On your own pages, posts, graphics and FAQs, remove any badge, seal, icon or adjective that implies a certificate, and keep your firm's own security claims visibly apart from SourceX's.
Read → - How to design a key employee retention plan that keeps IT admins through a wind-down
A key employee retention plan in a wind-down should cover the people who hold admin rights to email, file storage, CRM and backups, because records can only be assessed or licensed if someone can export them. Tie stay bonuses to export milestones, have counsel check section 503(c) limits on insider pay, and fund the plan before systems go dark.
Read → - How to disclose a referral incentive to a portfolio founder: model language that names who at the fund would be paid, tells the founder a no costs nothing with the fund, and keeps board knowledge out of the ask
Put the disclosure in writing, in its own message, before the founder weighs the idea. Name who would be paid if the company licenses data through SourceX: a fund entity, a named person or nobody. Say that the company receives the same amount either way, that the founder's answer has no bearing on the fund's support, follow-on decisions or board conduct, and that nothing the fund learned in the boardroom will travel to SourceX. Then step back and let the CEO decide.
Read → - How to disclose a referral relationship on a resource page: a nine-spot placement guide, built on the FTC's own disclosure wording, that puts the line wherever a reader actually meets SourceX, from a card in a grid to a downloaded PDF and a search preview
Put the disclosure where the reader meets SourceX, not where the page ends. On a resource page that is several places at once: the SourceX entry, its link or button, any other entry that mentions SourceX, the phone view that collapses text, a downloaded copy and the preview a search engine or social post shows. In each spot, one plain line saying you may be paid, beside the link and in the same view. Before any line names SourceX, get its written authorization.
Read → - How to disclose a reward naturally in an introductory email: five plain-language variants, the one place the sentence belongs, and a message rewritten before and after
Write one plain sentence in the body of the email, just before you ask for the call: SourceX pays you, the amount depends on what SourceX actually pays the company, it never comes out of the company's money, and nothing is owed for the introduction itself. Use the voice of the rest of the email. A disclosure reads naturally when it is specific and sits where the owner decides; it reads as evasive in a footer, a P.S. or a reply sent only after someone asks.
Read → - How to disclose an existing data license in M&A due diligence
Disclose an existing data license the way you would any material IP license: list it on the material contracts and intellectual property schedules, put the executed agreement and amendments in the data room, and prepare a one-page summary of scope, exclusivity, term, payments and data handling. Deal counsel decides what the representations require.
Read → - How to disclose an incentive without implying the advice is independent: an independence language review sheet that finds the words readers take as a promise of neutrality, swaps them for a plain role statement and puts the disclosure ahead of the suggestion
Disclose the incentive in the same breath as the suggestion, and remove every word that tells the reader your view is free of it: independent, objective, unbiased, neutral, no stake, purely in your interest. A disclosure placed beside one of those words contradicts itself. Use a short role statement instead, saying what you are (someone SourceX may pay if a deal completes) and what you are not (SourceX's agent, or the company's reviewer of the deal unless engaged), and let the CEO weigh your suggestion knowing both.
Read → - How to discuss an active referral in a partner meeting: a need-to-know meeting notes template that moves the item to the end of the agenda, clears guests and automatic note-takers first, and writes one line per referral instead of the company's story
Give an active referral a short slot at the end of the partner meeting, after guests have left and any automatic note-taking has stopped. Say five things aloud: the reference code, who holds the CEO relationship, the stage in generic words, the next action and whether the room has to decide anything. Minute one line per referral. The company's records, figures, any estimate, the buyer, SourceX's reasons and anything a board seat revealed stay out of the room and out of the notes. The company's CEO, not the meeting, decides what the company does next.
Read → - How to discuss archive access without making security promises: an eleven-sentence verification checklist that sends each claim to the system's custodian, the client's CEO or SourceX's own trust center
Say only what you have checked yourself, and route every other claim to the party that owns it. As the IT partner you can state facts about the archive you run: which system, which years, when access ends. The client's CEO decides scope and whether to talk at all. Only SourceX's published trust center speaks for SourceX's controls, so quote it and link it instead of promising encryption, anonymity, certifications or where files will sit.
Read → - How to discuss audit status without overstating certifications: an eight-check claim test and twelve sample sentences, each matched to the issued document, the date and the party that owns it
Say only what the issuing document says, or what SourceX's own trust center says, and give the date. On 27 October 2026 that page listed a SOC 2 Type II report and ISO/IEC 27001 and 27701 certifications as in progress, with none issued. So "certified", "compliant" and "audited" are all overstatements about SourceX today. Use each instrument's own noun: a service auditor issues a report, and an outside certification body issues a certificate. When a founder asks, link the page, state the date and let SourceX answer anything beyond it.
Read → - How to discuss referral conflicts at an operating committee: a committee decision memo template with a declaration round, a step-out rule and minute wording that approves only the fund's route to one CEO, never the company, the reward or SourceX
Bring one proposed introduction at a time, in a short memo circulated before the meeting. The memo names who would ask the company's CEO, which party could be paid and every committee member's tie to the company or to SourceX. Members with a tie declare it and step out of the decision. The committee then chooses only the fund's route for that ask: paid through the firm, paid personally with approval, unpaid, or no part. Its minutes say plainly that it judged neither the company's fit nor any reward. The company's CEO still decides.
Read → - How to distinguish an illustrative company from a real customer: a four-class example labeling standard that keeps the Illustrative label attached through screenshots and excerpts, treats a disguised client as real and leaves customer stories to SourceX's own pages
An illustrative company is one you invented to explain how the program works. A real customer is a company that actually did business with SourceX, and only SourceX's own pages present those. Partner content keeps the two apart by sorting every example into four classes: invented, composite, disguised real and SourceX-published. The first two carry the word Illustrative wherever an excerpt will keep it; a disguised real company counts as real and stays out; SourceX's own material is quoted exactly as published, label included.
Read → - How to distinguish program learning from financial return: a results memo in which every finding needs a denominator and every dollar needs a payment record
Learning is a finding that changed what the fund will do next. Financial return is reward cash that SourceX has actually paid. Report them in separate sections of one memo and never add them together. A learning line needs a count, a denominator and the decision it changed. A return line needs a payment date, a reference code and an amount that matches the bank. Estimates go in neither section, and a reward that arrives in month nine is not an annual yield.
Read → - How to document a client's system history without inspecting content: a systems timeline questionnaire in which every answer names its source, and none comes from opening a record
Build the timeline from three places that never require opening a record: your own service records (contracts, project tickets, invoices and the software inventory you already keep), what the client's system owners tell you, and decisions only the CEO makes. Write the source beside every answer. If a question can be answered only by searching, counting, sampling or exporting the data itself, it is not yours to answer; leave it blank for the company to fill in when it applies to SourceX.
Read → - How to document a potential confidentiality constraint: a four-level escalation register that records the kind of duty and who can read it, never the secret itself
Document a possible constraint as a type, a holder and a next step, never as a description of the confidential thing. One register line says where the duty may come from (a customer contract, an NDA, an employee-privacy promise, a regulator or your fund's own information rights), who at the company can read the governing text, whether the company has approved sharing the line, and one of four escalation levels. Attach no contracts or records: the company and its counsel decide what SourceX hears.
Read → - How to document a professional's decision not to participate: a ten-field decision record that states scope, basis and review date with no client detail in it, and four client replies that steer a company neither toward SourceX nor away from it
Write it down twice. A decision record in your own or your firm's files says who decided, for what scope (the whole firm, a practice, an office, one client), which activity is declined, on what kind of basis (a rules review with your counsel or ethics adviser, an employer policy, a conflict, a capacity call) and when it will be revisited, and it holds no client detail. A short written reply to any client who asks says you are not taking part, that the decision concerns your role rather than their company, and how the company can approach SourceX on its own.
Read → - How to document data rights and provenance before licensing data for AI training
To document data rights for AI licensing, build a rights file showing, system by system, who created the records, which contracts and policies were reviewed, what notices employees and customers received, and which data is excluded. At a PE-backed company the CFO usually owns it with counsel, and the same file answers data questions in exit diligence.
Read → - How to document SOPs before selling a business
To document SOPs before selling a business, list recurring processes, rank them by risk, record how the work is really done, write each in a fixed template, link it to its evidence, test it with a second person and freeze a dated version. Pair procedures with execution records so buyers can verify them.
Read → - How to document why an archive referral cannot proceed: a no-go reason and evidence register that names one blocking fact per file, grades the evidence behind it, reports it in the words of whoever said it, and dates the event that would reopen it
Record one blocking fact per archive file, the evidence behind it, the words of whoever stated it and the event that would reopen it. The register below has nine archive-specific reasons, from no named controller to an earlier AI-training license, and three evidence grades: a written statement from the decision-maker or their counsel, your same-day note of what they told you, or secondhand word. Only the first two close a file. Nothing from inside the archive, and no legal conclusion of your own, goes in.
Read → - How to document why an old referral is newly relevant: a one-page changed-facts rescreening memo that dates the old decision, the transition that changed it and who controls the records now
Write one page before anyone re-contacts the company. Record the original decision with its date and reason, the transition that changed it with a dated source, and three facts kept apart: where the records sit now, who controls the company now, and every earlier contact with SourceX you know of. The memo supports a new introduction only when a dated change answers the original reason and the current CEO wants the conversation. Otherwise it records why you stopped, which is just as useful.
Read → - How to end a referral thread without burning the relationship: a four-line close and a suppression record that stops your firm asking twice
End the thread with one short message: thank them, say plainly that you will not raise it again, confirm that nothing is pending and none of their information was passed on, and leave the only way back in their hands. Then log a suppression record so no colleague asks twice: who asked, the scope, the date and who must honor it, without their private reasons. If they objected, do not schedule a check-in to see whether they changed their mind.
Read → - How to escalate a referral without sending repeated messages: a threshold and contact map in which every message reaches a new recipient or carries new evidence, and an unanswered one is closed, not resent
Escalate only when a dated threshold is crossed, and make each message do something the last one did not: reach a different person, or carry new evidence. Never send the same question to the same inbox again. Inside your firm, an overdue step goes up to the operations lead. At the company nobody sits above the CEO, so the CEO gets one question and the answer, or the silence, stands. With SourceX, ask about your own referral first, and send a disagreement once, with evidence, under section 7 of the terms.
Read → - How to estimate partner work before promising easy earnings: a task-by-task planner that counts the hours a firm spends before any reward can exist
List every task an introduction requires, from screening your client book to supplying tax details, give each an owner and an hour range, multiply by the clients you will actually approach, and compare the total with the capacity you really have. Most of those hours fall before anyone can know whether a reward will exist, because a lead, meeting or signed agreement alone earns nothing payable. Present the hours first and the reward formula second, and never promise an amount.
Read → - How to evaluate a partner offer your clients did not ask for: a ten-question need interview that names the offer only at the end, and a count that settles pilot, keep small or decline
Judge an unsolicited partner offer by what your clients have recently done, not by the reward or the vendor's pitch. Before signing anything, interview six to ten clients about events the offer claims to address, without naming it: systems retired, outside requests for their records, data kept only out of caution, decisions postponed. Code each answer as evidence, politeness or nothing. Two or more clients with evidence and a CEO who would want the conversation justify a small pilot. Fewer means keep a one-line answer ready, or decline.
Read → - How to evaluate a strategic network's referral quality: a twelve-point scorecard that grades each introduction on what was true the day it was sent, reads SourceX's status stages only later, and never mistakes volume for quality
Grade each introduction on what was true the day it left the network: the company's CEO asked for it in writing, nothing commercial was open between the corporate and the company, the published fit facts were known, the company had no earlier contact with SourceX, nothing was collected or forwarded, and the written record was complete. Add the grades up by network segment. Read what SourceX reports later, in generic status stages, as a lagging check, and never treat the number of introductions or rewards as quality.
Read → - How to evaluate an unsolicited offer to buy your company's data
To evaluate an unsolicited offer to buy company data, pause before replying, build a metadata-only inventory, check your rights, define scope on paper and get terms in writing. Never send raw records first. Treat requests for ownership, unclear purpose or pressure deadlines as red flags, and compare the offer with a managed licensing process.
Read → - How to exchange referral criteria without exchanging client lists: a one-page criteria-only collaboration brief that travels between funds while every company name stays with the fund that knows it
Send the test, not the list. One fund writes a one-page brief built only from public material: SourceX's published fit criteria, a handful of metadata questions, what never to share and how a match moves forward. Each receiving fund screens its own network privately, and where a CEO it knows says yes, that fund introduces the company itself as a registered partner. No names, portfolio lists or board knowledge cross between funds, so nobody's confidentiality is spent and every founder hears from one investor.
Read → - How to explain a data referral to a founder in two minutes: a timed conversation outline that leaves room for their questions, and three endings that are all acceptable
Spend the two minutes on four things: why this company came to mind, what SourceX does, exactly what you are asking for and what you would earn, and an easy no. The ask is narrow: permission to introduce the company's CEO to SourceX or, if the founder is not the CEO, whether they will raise it with the CEO themselves. Being an investor gives you no authority to open that conversation, and a founder's interest alone does not authorize the company.
Read → - How to explain a mandate rejection without closing the relationship: four message templates, a revisit note and the phrases that end conversations
Give the specific reason, say what the no does not judge, name the condition that would reopen it and who will raise it, then stop. A mandate rejection is a statement about SourceX's current program criteria, not about the company or its founder, and the message should read that way. "Not the right fit right now" sounds like a brush-off and leaves the founder guessing. One precise reason with a dated revisit trigger keeps both the relationship and a later introduction possible.
Read → - How to explain an archive opportunity to a creditors' committee: a counsel-reviewed brief outline that says what exists, who decides and what nobody can promise yet, written so every line could reach the creditors the committee represents
Bring the committee a short written brief that estate counsel and committee counsel have read before it circulates. It describes the records at metadata level, names whoever controls the estate and the date that was checked, states any hold or order that limits the archive, and lists what nobody can say yet: whether SourceX wants the records, what they might bring and when. It carries no figure. The committee can question it; the decision belongs to whoever controls the estate, and nothing is opened or copied to prepare it.
Read → - How to explain attribution without promising manual exceptions: a nine-request language guide that names the term, the review or the signed writing that decides each
Explain attribution as a rule applied to dated records, and say plainly who can change it: nobody on your team, and nobody by email or phone. SourceX credits the first valid introduction of a new company when that company submits a verified application within 90 days of the recorded introduction, one partner per company. Any change to those terms needs a writing signed by both parties. So every exception request gets one of three answers: the term decides, SourceX's review decides, or only a signed writing could change it.
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