You'll find answers to common questions about 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) to SourceX on this page. Our goal is to help advisors like you confidently refer businesses in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia, ensuring a smooth and rewarding process. This resource is designed for referral partners who introduce enterprise companies with 50+ full-time employees at their peak to SourceX, their direct licensing partner for approved business data for AI training and evaluation. SourceX licenses data directly from companies and manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. Learn how SourceX licenses high-quality business data directly from companies, and understand the steps to refer companies successfully. Referral rewards are the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout—the eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements—with no cap, subject to any signed Schedule A or addendum. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. SourceX funds rewards separately; they do not reduce the company's payout.
Answers to common questions about referring companies
Specific answers to common questions about 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) to SourceX for data licensing. For the short version, see the FAQ.
- 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 type of companies should I refer for data licensing?
You should refer enterprise companies with 50+ full-time employees at their peak. SourceX is their direct licensing partner, licensing approved business data directly from them for AI training and evaluation, subject to acceptance at Closing and agreed terms.
What are the rewards for referring companies in the U.S., Canada, the EU, the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia?
Rewards for referring 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) are the greater of $50,000 plus 5% and 15% of the Actual Supplier Payout—the eligible licensing compensation SourceX actually pays the referred company, excluding separately itemized taxes and expense reimbursements—with no cap, subject to any signed Schedule A or addendum. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details. SourceX funds rewards separately; they do not reduce the company's payout.
Who benefits from SourceX's data licensing?
AI labs and data buyers benefit from the approved business data SourceX licenses directly from companies for AI training and evaluation. SourceX manages the agreement, rights review, data preparation, delivery and payout, subject to acceptance at Closing and agreed terms. Advisors contribute by introducing suitable enterprise companies.
What is the process for referring companies to SourceX?
The process involves simple steps for partners to refer companies successfully. Partners submit company introductions, ensuring a smooth and rewarding process for connecting businesses with SourceX.
Related pages
- An AI company offered to buy a client's data mid-sale: what should the advisor do?
- Does helping a client license data affect CPA independence?
- Does a one-time data license raise a portfolio company's ASC 820 mark?
- Can a PE portfolio company license its data to SourceX?
- Can an M&A advisor share client information when introducing a client?
- Can a company use customer data to train AI under its customer contracts?
- Who can say yes to licensing defect closeout verification records? A decision tree for construction QA consultants
Introduce the contractor's CEO, with the contracts manager or general counsel, and bring in the quality manager as sponsor. The quality manager knows which projects have clean, linked defect histories and which were closed in a rush, so they are the right first contact. Being able to log in to the inspection platform, or even to close punch items as final approver, is access, not authority. Owner contracts and photos taken inside occupied units go to counsel, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing deliverable acceptance revisions records? A decision tree for contract advisors
The program operations director is the right first contact: they run delivery reviews and know where drafts, acceptance criteria, revision requests and sign-off dates are kept. They sponsor the conversation; they rarely decide it. The yes comes from the CEO, after counsel has read the client contracts, because an accepted deliverable often belongs to the client and a government acceptance carries its own rules. What can be licensed stays open until SourceX's rights review.
Read → - Who can say yes to licensing detention charge disputes records? A decision tree for partners
The first person to talk to is usually the operations director, who runs detention disputes and knows what was kept. The person who can say yes to a licensing discussion is the CEO, advised by counsel on carrier and shipper contracts. The AP manager and TMS administrator own or hold the records but cannot authorize their use. What can actually be licensed stays unknown until SourceX's rights review with the company.
Read → - Who can say yes to licensing emergency work order prioritization records? A decision tree for dispatch consultants
Introduce the CEO, with general counsel, and use the service operations director as the convener. The service operations director owns the priority scheme and knows which years were logged well, so they are the right first contact, but they rarely approve a licensing discussion alone. The dispatch system administrator can describe what an export holds; that is access, not authority. Client site records and safety incidents need counsel's view of each maintenance contract, and the final answer waits for SourceX's rights review.
Read → - Who can say yes to licensing exception routing calibration records? A decision tree for workflow advisors
Introduce the CEO, who can authorize the discussion and sign, with general counsel reading the customer terms, and ask the quality operations head to convene. That person ran the review meetings and knows what survived, but seldom has the standing to approve a licensing talk alone. Whoever administers the routing product can pull files; that is access, not authority. An outside vendor or integrator may keep copies from a project, yet the material belongs to the company that ran the queues.
Read → - Who can say yes to licensing expense policy exception records? An approval tree for partners
Start with the head of finance operations, who runs the exception queue and knows where the history sits. The person who can say yes to a licensing discussion is the CEO, often with the CFO preparing the case and HR and counsel consulted because expense records describe employees. The expense administrator and the controller hold or control the records but cannot authorize their use. What can actually be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing failed-port records? A decision tree for telecom systems consultants
Introduce the provisioning director first, as the person who convenes the conversation and can explain how failed ports are worked, then the CEO, who can authorize a licensing discussion. The tree splits on who created each record: the provider's own orders, tickets and notes sit with its CEO; CSR copies and rejection notices came from the other carrier; customer account details carry CPNI duties; reseller work may belong to a wholesale contract. A platform administrator has access to all of it and authority over none.
Read → - Who can say yes to licensing false-positive closure records? A decision tree for security partners
Start with the SOC director, who knows what closure records exist, where and for how long. At a managed security provider, the person who can say yes to a licensing discussion is the CEO, advised by general counsel, because client agreements govern much of what the SOC holds. In an in-house SOC it is also the CEO, with the CISO as sponsor and legal and the CFO advising. Detection engineers and SIEM administrators hold the records but cannot authorize their use, and the final scope stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing feature flag rollback records? A decision tree for DevOps consultants
Introduce the CEO (in an owner-run company, usually the owner) as the signer, with the CTO or VP of engineering supporting, and use the engineering director as your sponsor and first contact. The director knows which systems hold rollback history and can run the counts, but rarely has authority to license company records alone. Flag platform and incident platform admins have access, not authority. Customer names in incident messages and vendor terms go to legal, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing first-visit failure records? A decision tree for field service software partners
Introduce the CEO (the owner in a founder-led business) as the signer, with the COO supporting and general counsel on rights, and start with the service director as your sponsor. The service director runs callbacks, knows which years were coded well and can name the systems, but rarely has authority to license company records. Dispatchers and the field service platform admin can export every job and cannot agree to license any of it. Customer service contracts, manufacturer program terms and technician personal data go to counsel, and the answer stays open until SourceX's rights review.
Read → - Who can say yes to licensing group booking change records? A decision tree by hotel operating structure
Start with the director of events, who knows where event order versions, captain's counts and banquet corrections are kept, then find the person who can approve a licensing discussion. In a hotel that depends on the operating structure: the owning company's CEO, often the owner personally, at an owner-operated property, the management company's CEO with the owner's consent at a managed hotel, and the same people plus a check of the brand agreement at a franchised one. Counsel reads client contracts for confidentiality terms.
Read → - Who can say yes to licensing incident containment records? A decision tree from SOC lead to signer
Start with the incident response director or SOC lead, who knows how handoffs work and where approvals, owner changes and verification notes are kept, then bring in the CEO, who can approve a licensing discussion. For records in the company's own tools, the CISO recommends and general counsel advises. Records an outside provider created may fall under the services agreement, and a security provider's client incidents fall under client contracts.
Read → - Who can say yes to licensing interchange dispute records? A decision tree for transport data consultants
Start with the operations director, who runs dispatch, knows the tracker vendor and knows where dispute files live, then introduce the CEO, who can authorize a licensing discussion. Ownership splits three ways: the carrier's own dispatch emails, dispute files and credit memos; tracker data that the device vendor's contract may govern; and receipts and images the equipment provider created. A system administrator who can export all of it has access, not authority. The vendor and provider branches stay open until SourceX's rights review.
Read → - Who can say yes to licensing intercompany reconciliation records? A decision tree for multi-entity groups
Start with the group controller, who knows where intercompany records sit and what they mean, then introduce the officer who can authorize a licensing discussion for every entity whose records are involved: the group CEO, with a subsidiary's own CEO where that subsidiary signs for itself. Running the close is not authority to license. Counsel decides which entity holds rights to each record, and that answer stays open until SourceX's rights review.
Read → - Who can say yes to licensing knowledge handover records? A decision tree for acquisitions
Start with the operations director, who usually runs the handover program and knows where checklists, process pages and tracker tickets live, but expect the yes to come from someone else. Before closing, that is the firm's CEO, normally the selling owner or managing partner, within what the purchase agreement allows. After closing, it is the acquirer's CEO, with its integration lead as sponsor. Administrators and the departing practice lead have access or knowledge, not authority. Client terms and deal restrictions stay open until counsel and SourceX's rights review settle them.
Read → - Who can say yes to licensing lab result correction records? A decision tree for LIMS consultants
Introduce the CEO (in an owner-run lab, usually the owner), with the laboratory director as sponsor and general counsel or the contracts lead at the table. The laboratory director owns the review and amendment procedure and knows which years are complete, so they are the right first conversation, but they rarely decide whether company records may be licensed. The quality manager and LIMS administrator have knowledge and access, not authority. Whether client results, or patient data in a clinical lab, can be part of any discussion stays open until counsel and SourceX's rights review settle it.
Read → - Who can say yes to licensing lease abstraction correction records? A decision tree for lease technology advisors
Introduce the CEO, who can authorize the discussion and sign, with the CFO or controller and general counsel, and bring in the head of lease operations or lease administration as the convener. Lease operations knows how abstracts are kept and how often they were corrected, so it is the right first contact, but it does not decide whether landlord terms can leave the building. Counsel reviews lease confidentiality clauses; a lease administration firm working on clients' leases usually needs those clients. Abstraction tool access is not authority, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing license reclamation records? A decision tree for software asset consultants
Start with the head of IT asset management, because they run the reclamation process and know what exists. Then follow the records to the executive who owns them, usually the CIO or COO, and on to the CEO, who can authorize their use, with HR, privacy and legal input because assignment and usage records describe employees. Administrator rights in the asset manager or identity system are technical access, not authority to license. Introduce the CEO, with the records owner as sponsor and the asset management head copied as the subject-matter contact.
Read → - Who can say yes to licensing merchant settlement records? A decision tree from payments ops to signer
For merchant settlement reconciliation records, start with the payments operations director or the controller, who know which processors, batches and adjustment approvals exist, then find the officer who can approve a licensing discussion: the CEO, with the CFO preparing the case and general counsel advising. The company's own ledger and workpapers are its records. Processor-generated reports may sit under the processor agreement, and cardholder data never enters the discussion at all.
Read → - Who can say yes to licensing mis-pick recovery records? A decision tree for 3PL account advisors
Introduce the retailer's CEO, with general counsel close behind, and ask the customer operations head to open the door. That head runs the complaint desk, knows how replacements are approved and can describe which years of tickets exist, but rarely holds authority to approve a licensing discussion. Ticket admins and 3PL account staff can see the data without owning it. Which records can be licensed stays unknown until counsel reads the 3PL contract and SourceX completes its rights review.
Read → - Who can say yes to licensing network change acceptance records? A decision tree for network automation integrators
Introduce the operator's CEO, usually with general counsel, and ask the head of network operations to make the connection. That head runs the change process and knows which tools hold test results, maintenance notes and approvals and how far back they go, but rarely has authority to license them. Change board members, test engineers and contractors have access, not authority. What can be licensed stays unknown until counsel and SourceX's rights review have looked at contractor terms and customer information.
Read → - Who can say yes to licensing nonconformance disposition records? A decision tree for QMS consultants
Start with the quality director, who owns the nonconformance procedure and knows where the records and their gaps are, then bring in the CEO, who can open a licensing discussion. General counsel joins when records cite customer drawings or quality agreements, and suppliers' own reports may need separate treatment. Administrator access to the QMS is not authority. Whatever the tree suggests, the final answer on what can be licensed stays open until SourceX's rights review.
Read → - Who can say yes to licensing nonstandard contract approval records? A deal desk decision tree
Start with the head of revenue operations: they run the deal desk and the quoting tool, so they know whether discount requests, redlines and approval chains survived the last migration. They open the door but rarely own the records. Ownership usually sits with the CFO; the authority to explore licensing and sign sits with the CEO, who takes it to the board where the delegation of authority reserves IP licenses. General counsel reads customer contracts before anything is scoped, and SourceX's rights review settles the rest.
Read → - Who can say yes to licensing placement guarantee dispute records? A decision tree for staffing software consultants
Start with the operations director, who usually signs off placement guarantee decisions and knows where the memos, claims and credit notes sit. That person sponsors; the approval to open a licensing discussion comes from the CEO (in an owner-run firm, the owner), often with the CFO preparing the case. Admin rights in the ATS are access, not authority. Counsel reads the client agreements for confidentiality terms, and the placed candidates' details raise privacy questions that stay open until SourceX's rights review.
Read → - Who can say yes to licensing production schedule recovery records? A decision tree for partners
Introduce the CEO, who can authorize a licensing discussion, with the plant operations director as working contact. Start the conversation with the operations director, who knows how recoveries are decided and where each record is kept, and let them bring in the CEO. System administrators, planners and maintenance managers own records day to day but cannot approve their use. Customer agreements, a parent group and employee data can each add a required sign-off, and SourceX's rights review settles what remains open.
Read → - Who can say yes to licensing referral and scheduling records? A decision tree for healthcare advisors
Start with the administration director, who runs intake and scheduling and knows where the unmatched referrals went, then find who controls the records. In healthcare administration that is a legal question: if the company holds referrals as a business associate for practices, its contracts limit what it may do, and the practices may need to agree. The CEO of the controlling party authorizes a discussion; the privacy officer and counsel advise.
Read → - Who can say yes to licensing refund abuse review records? A decision tree for ecommerce advisors
Introduce the customer operations director first, as the sponsor who runs the review queue and can explain how held refunds are decided, then the CEO, who can authorize a licensing discussion, with counsel alongside. The tree splits on what each record contains and who created it: the retailer's own rules and reviewer decisions sit with its CEO; customer names and order histories bring privacy terms; vendor-held logs depend on the returns app contract. Admins have access to all of it and authority over none.
Read → - Who can say yes to licensing revenue allocation corrections records? A decision tree for accounting systems advisors
Introduce the head of revenue accounting first, as the person who convenes the conversation and knows which contracts were modified, where each calculation version is stored and who approved it. The person who can authorize a licensing discussion is the CEO, with the CFO preparing the case and counsel advising, because customer contracts carry confidentiality terms. The controller confirms which records the company owns. A systems administrator or outside advisor with access to billing and the revenue tool can describe the records but cannot commit them.
Read → - Who can say yes to licensing RFI-to-change-order records? A decision tree for partners
Introduce the CEO, who can authorize a licensing discussion, and bring the project controls director in as the working contact. Document controllers and platform administrators can describe the archive but cannot approve its use. Counsel weighs owner contracts, design copyright and federal handling terms. Whether any record can actually be licensed stays unknown until SourceX's rights review. The decision tree below walks a partner through each branch.
Read → - Who can say yes to licensing roadside repair authorization records? A decision tree for fleet consultants
Start with the fleet manager, who approves roadside spend and knows where every quote, approval and work order lives, but introduce the CEO, who can authorize a licensing discussion; the CFO can help prepare the case for financial records. The fleet manager sponsors; the CEO signs. Records describing outside vendors, notes kept by a third-party breakdown service and telematics data under an equipment contract each send part of the answer to counsel. Technical access to the fleet system is not authority.
Read → - Who can say yes to licensing root-cause feedback records? A decision tree for field service integrators
Start with the aftermarket or service director, who owns the claim and service process, then introduce the CEO, who can authorize a licensing discussion. The records are split three ways: service owns claims and field reports, quality owns returns lab findings, and engineering owns change orders. Each department head can describe their part, but none can commit the company. Legal reviews dealer and installer agreements.
Read → - Who can say yes to licensing scope creep adjudication records? A sign-off tree for PSA consultants
Start with the delivery director, who approves or rejects change requests and knows where the trail of SOWs, client requests and approvals is kept. That person sponsors the conversation but rarely decides it. The yes comes from the CEO (in a partnership, the managing partner), with the contracts lead or general counsel reading client agreements first, because SOWs quote client names, prices and systems. A PSA administrator's access is not authority, and what can be licensed stays open until SourceX's rights review.
Read → - Who can say yes to licensing service credit adjudication records? An approval tree for SaaS finance advisors
Start with the commercial operations head, who knows how service credits were decided and where the evidence went, then bring in the CEO, who can approve a licensing discussion, with the CFO, who owns the billing records, preparing the case. General counsel joins early, because SLA terms, incident details and credit amounts are often confidential under customer agreements. The billing admin and the site reliability lead can confirm what exists, but technical access is not authority, and the final scope stays open until SourceX's rights review.
Read → - Who can say yes to licensing service recovery approvals records? A hotel authority tree for CX consultants
The guest operations director, or the director of rooms, is the right first contact: they run service recovery, know which promises turned into disputes and know where threads, service requests and folio credits sit. They do not approve a licensing discussion; the CEO does. Structure decides whose consent is also needed: the owner's when a management agreement governs the records, and the brand's terms for a franchised property. Privacy counsel joins early, because guest messages are personal data, and the final answer waits for SourceX's rights review.
Read → - Who can say yes to licensing stock variance records? A decision tree for warehouses and 3PLs
Begin with the warehouse director, who knows how stock variances get looked into and where the reasoning ends up. Then identify the person who can approve a licensing discussion: usually an operations executive acting with finance and legal and, where the business stores goods for clients, within the terms of each client contract. Being able to log in is not the same as being allowed to decide. An outside consultant or the IT team may hold administrator rights everywhere and still have no say over licensing.
Read → - Who can say yes to licensing subcontractor evidence reconciliation records? A decision tree for compliance consultants
Start with the supplier compliance director, who knows where evidence packages, reviewer notes and decisions live and how complete they are. The person who can authorize a licensing discussion is the CEO. General counsel must weigh in on anything the subcontractor authored or anything touching government customer information. Portal administrator rights are access, not authority, and what can actually be licensed stays open until SourceX's rights review.
Read → - Who can say yes to licensing submittal revision review records? A decision tree for construction document consultants
Start with the head of design coordination, or the project engineering manager, who knows which projects have clean revision chains and where the gaps are. The decision to discuss licensing belongs to the CEO, with general counsel or the contracts manager reviewing what owner and design agreements allow. Platform admin rights are access, not authority. What can actually be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing subscription pause recovery records? A decision tree for subscription platform consultants
Introduce the head of retention operations first, as the convener, and let them lead you to the CEO, who can authorize a licensing discussion, with finance and customer care confirming their record classes and counsel reviewing customer data. The retention lead knows how pauses and fixes work and can size the history, but that knowledge is not authority. Nobody with only system access, including the consultant, can say yes.
Read → - Who can say yes to licensing supplier corrective action records? A decision tree for quality systems advisors
Introduce the supplier quality head first, as the sponsor who knows what exists, then let them lead you to the CEO, who can authorize a licensing discussion, with purchasing confirming supplier contract terms and counsel reviewing supplier-provided content. Portal admin rights, QMS access or a consulting engagement are not authority. The hardest question is not who owns the company's own defect and verification records but who controls the supplier's responses inside them.
Read → - Who can say yes to licensing supplier onboarding exception records? A decision tree for advisors
Introduce the CEO (in an owner-run company, usually the owner), with the head of supplier operations or vendor master data as the convener. The supplier operations head knows how exceptions are worked and where the notes live, so they are the right first conversation. But one onboarding file mixes procurement's request, compliance's screening, tax's form check and finance's bank verification, each owned by a different team, and only the CEO can approve a licensing discussion across all of them.
Read → - Who can say yes to licensing supplier substitution approval records? A decision tree for procurement systems consultants
Start with the procurement director, who knows which substitutions happened and where the requests, quotes and purchase orders sit. The approval to open a licensing discussion has to come from someone with authority over procurement, quality and engineering records together, which means the CEO, with general counsel involved. A QMS administrator who can export records has access, not authority. Supplier quotes and customer drawings add outside owners whose terms stay open until SourceX's rights review.
Read → - Who can say yes to licensing temperature excursion records? A handler-or-shipper decision tree for cold-chain systems advisors
Start with the quality director, who owns the excursion procedure and the deviation records and can sponsor the conversation. The approval to open a licensing discussion comes from the CEO, with general counsel reading the shipper quality agreements. A systems administrator with platform access has no authority to say yes. Disposition decisions often belong to the shipper's quality unit, so what the handler can license stays open until SourceX's rights review.
Read → - Who can say yes to licensing time write-off review records? A decision tree for accountants
Introduce the CEO, or in a partnership the managing partner, as the person who can authorize a licensing discussion, and name the practice operations head as the person who knows the records. The operations head runs or sees the write-off reviews and knows where reasons are recorded, but rarely decides. Billing staff and system administrators can confirm what exists; they cannot say yes. Because time entries describe client work, the general counsel or risk partner usually checks client terms before anything is proposed.
Read → - Who can say yes to licensing underwriting referral records? A decision tree from operations head to signer
For underwriting referral triage records, start with the underwriting operations head, who knows where referral flags, decision notes and approval conditions live, then reach the CEO, who can authorize a licensing discussion, with the chief underwriting officer speaking to content and general counsel reading carrier, broker and privacy terms. A managing general agent adds one check first: what its delegated authority agreements say about underwriting files.
Read → - Who can say yes to licensing vulnerability exception records? A decision tree for GRC consultants
Introduce the CEO, who can authorize a discussion about company records, and name the risk owner or CISO as the person who knows where the exceptions live. The risk owner approved or delegated each renewal, which makes them the right first conversation, but accepting a security risk is a different power from agreeing to discuss licensing records about it. Counsel reviews what the records reveal.
Read → - Who can say yes to licensing warranty dispute records? A decision tree for asset consultants
Start with the head of aftermarket operations, who decides contested claims and knows which years were recorded properly, then introduce the CEO, who can authorize a licensing discussion, with general counsel reviewing dealer, supplier and customer terms. A warranty administrator who can export the system has technical access, not authority. Contract questions are noted by the partner and settled in SourceX's rights review.
Read → - Who can say yes to licensing workforce schedule exception records? A decision tree for WFM advisors
Introduce the CEO, with HR and counsel involved, and bring in the workforce director as the convener. The workforce director knows which exception days were documented and where overrides were logged, so they are the right first contact, but schedules, adherence and time cards describe individual employees, and the person who runs the WFM tool is rarely the one who can say yes. Technical access to the platform is not authority. What can be licensed stays unknown until SourceX's rights review.
Read → - Who can sign a data license for a company in receivership?
In a US receivership, the receiver usually signs contracts for the company, but only within the powers the appointment order grants. A data license outside the ordinary course, or one the order reserves to the court, generally needs court approval first. In a limited receivership, officers may still sign for assets outside the receiver's control, often with lender consent.
Read →
Free resources
- Earnout scenario calculator — Probability-weighted earnout value and its present value.
- Profit margin calculator — Profit and margin across three scenarios.
- Client opportunity brief generator — An editable intro email, summary and checklist.
- 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