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 authorize licensing engineering change records? A who-can-say-yes tree for PLM integrators
Introduce the person who can authorize a licensing discussion, the CEO (in an owner-run manufacturer, usually the owner), with the head of engineering operations as sponsor and working contact. The engineering operations head runs the change process and knows where every record lives. The systems lead and change analysts can describe the records but cannot approve their use. Counsel must weigh customer designs, supplier drawings and export controls. What can be licensed stays unknown until SourceX's rights review.
Read → - Who can authorize licensing entitlement exception records? A who-can-say-yes tree for customer platform consultants
Introduce the CEO, who can authorize a licensing discussion and sign for the company, with the customer support director as sponsor and working contact. The support director knows where the plan, permission and ticket records live. Billing, identity and helpdesk administrators can describe their systems but cannot approve the use of what they hold. Counsel weighs customer contracts and personal data in identity logs. What can be licensed stays unknown until SourceX's rights review.
Read → - Who can authorize licensing outage restoration records? A decision tree for utility asset consultants
Start with the operations director, who runs outage response and can say which records survive, then bring in the CEO, who can approve a licensing discussion, with counsel setting limits, and at a cooperative or municipal utility often the board or council as well. Dispatchers, system operators and platform administrators create and store the records, but none of them can authorize licensing them. Customer-linked fields, network details and contractor logs take side branches that counsel and SourceX's rights review settle.
Read → - Who can authorize licensing promotion exception records? A who-can-say-yes tree for retail systems consultants
Introduce the CEO (in an owner-run chain, usually the owner), who can authorize a licensing discussion, with the retail operations director as sponsor and working contact. The operations director knows where promotion rules, POS receipts and corrections live. Pricing, POS and loyalty administrators can describe their systems but cannot approve the use of what they hold. Franchisees, suppliers that fund promotions and loyalty members may each have a stake. What can be licensed stays unknown until SourceX's rights review.
Read → - Who can authorize licensing utility billing dispute records? A decision tree for owners and managers
For utility billing dispute records, start with the finance director or controller, because property accounting runs utility recovery and knows where reads, allocation rules, tickets and credits live. Then reach the CEO, who can authorize a licensing discussion; at an owner-operator that is usually the owner. If the company manages buildings for third-party owners, each owner's consent may be needed for that owner's books, and if an outside vendor bills tenants, its contract may govern the records it holds.
Read → - Who can license advertising delivery reconciliation records? A decision tree from record owner to authorized signer
Start with the advertising operations director, who runs reconciliation and knows where each count, adjustment and makegood lives. That person is usually the sponsor, not the approver. The executive who can authorize a licensing discussion and sign is the CEO; the chief revenue officer, CFO or general counsel may advise, because advertiser contracts and data policy sit with them. Some questions, such as advertiser consent and de-identification, stay open until SourceX's rights review, whoever signs.
Read → - Who can license coverage query escalation records? A who-can-say-yes decision tree for insurers and MGAs
Start with the operations director, who runs the service desk and knows where escalated coverage queries go, but do not stop there. The decision to open a licensing discussion sits with the CEO, advised by general counsel, while the head of underwriting and compliance own the policy versions, referral notes, letters and complaint register. For a managing general agent, the carrier's rights under its agreements can be decisive. The decision tree below shows the order to ask in.
Read → - Who can license customer access review remediation records? A who-can-say-yes decision tree
Start with the security operations head, who knows which systems hold the access review chain, how far back it runs and where it breaks. Then make sure the introduction reaches whoever can approve a licensing discussion, the CEO, with general counsel or the privacy lead clearing customer contract limits. Technical access, including your own admin rights as an identity consultant, is not authority. After an acquisition, the CEO who can authorize may be the parent company's. The decision tree below sets out the order.
Read → - Who can license demurrage invoice appeals records? A who-can-say-yes decision tree
Introduce the CEO, who can approve a licensing discussion about company data, with the finance director as sponsor. The finance director runs the dispute process and knows the coverage; the logistics accountant confirms the records exist; general counsel reviews client, carrier and clearance agreements. A portal login or ERP admin role is access, not authority. Whether any record can be licensed stays unknown until SourceX's rights review.
Read → - Who can license loan document exception closure records? A who-can-say-yes decision tree for lenders
Start with the lending operations head, who knows the closing checklist, the exception log and the systems, and introduce them alongside the executive who can authorize a licensing discussion: the CEO of the lending business. Four others shape the answer without deciding it: the post-closing manager, the chief credit officer, general counsel or the compliance lead, and the IT owner of the e-sign and imaging systems. Administrator rights are technical access, not authority to license, and what is licensable stays unknown until SourceX's rights review.
Read → - Who can license maintenance escalation closure records? A who-can-say-yes decision tree for property managers
Start with the operations director, because they run maintenance and know where escalations are written down. The person who can authorize a licensing discussion is the CEO of the management company (often its owner), with counsel reviewing management agreements. Platform administrator rights are not authority. If the company manages for third-party owners, control of some records may sit with those owners, and what is licensable stays unknown until SourceX's rights review.
Read → - Who can license performance alert investigation records? A who-can-say-yes decision tree for operators
Start with the asset operations director: that person knows which sites kept disciplined investigation notes and which periods a subcontractor ran, which makes them the natural sponsor. The approver is the operator's CEO, after counsel has read the operations agreements, because telemetry often belongs to the asset owner while the investigation notes are the operator's own work product. A login to the monitoring platform is access, not authority, and some answers stay open until SourceX's rights review.
Read → - Who can license prior authorization follow-up records? A decision tree for revenue cycle advisors
Introduce the CEO, who can approve a licensing discussion about company data, with the revenue cycle director as sponsor and the privacy officer or general counsel at the table from the start. The director runs the authorization team and knows coverage; a work queue admin knows what the system stores. Neither role carries authority. For a billing company, provider agreements also shape the answer, and SourceX's rights review settles what can be licensed.
Read → - Who can license progress claim reconciliation records? A contractor's who-can-say-yes tree
Introduce the CEO, who can commit the company to a discussion about licensing its records, with the commercial director as sponsor. The construction accountant and project controls manager confirm what exists; full ERP admin rights are access, not authority. Then check three branches: government contracts, joint ventures and subcontractor records. Each can add a sign-off. Whether any record can be licensed stays unknown until SourceX's rights review.
Read → - Who can license proof-of-delivery dispute records? A courier's who-can-say-yes tree
Introduce the CEO, who can approve a discussion about licensing company records, with the operations director as sponsor. The operations director knows which systems hold scans, photos and claims and which change is coming, but rarely has authority alone. Then check two branches: whose shipments the records describe, and how recipient names, addresses and doorstep photos are handled. Each can add a sign-off, and SourceX's rights review settles the rest.
Read → - Who can license protocol deviation resolution records? A who-can-say-yes decision tree for CROs
Introduce the CEO, who can approve a licensing discussion about company data, with the quality director as sponsor. The quality director knows how deviations were classified and where the gaps are; the head of clinical operations confirms studies, sites and years; general counsel reads sponsor agreements, which often decide who controls trial records. Administrator access to the trial platform is not authority, and whether any record can be licensed stays unknown until SourceX's rights review.
Read → - Who can license purchase order mismatch resolution records? A who-can-say-yes decision tree
Introduce the CEO, who can commit the company to a licensing discussion about its own data (in an owner-run company, usually the owner), with the procure-to-pay head as sponsor. The procurement systems lead, the warehouse lead and the AP manager each hold part of the record, and counsel checks supplier agreements. An implementation partner's admin login to the ERP or procurement suite is access, not authority. Whether any of these records can be licensed stays unknown until SourceX's rights review.
Read → - Who can license quality scoring disagreements records? A who-can-say-yes decision tree for QA history
Introduce the CEO, who can approve a licensing discussion, with the quality director as sponsor. The quality director runs calibration, knows where adjudication notes are written and can say how many years they cover. Ownership splits by record type: forms and rulings are usually company work product, recordings involve customers and agents, an outsourcer's client calls are usually the client's, and vendor auto-scores may fall under vendor terms. Platform access is not authority, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can license rate parity exception review records? A decision tree for hotel groups
Introduce the CEO, who can commit the hotel company to a conversation about its data, with the revenue operations head as sponsor. The revenue operations head knows which snapshots, mappings and correction logs exist; counsel reads the channel agreements; at managed or franchised hotels the owner or asset manager may also need to consent. Extranet or channel manager access is not authority. What can be licensed stays unknown until SourceX's rights review.
Read → - Who can license rebate claim reconciliation records? A yes-path tree for distributors
Introduce the CEO, with the commercial finance head as sponsor. Commercial finance usually owns the rebate accrual, approves claims and knows where the claim files live, so it can describe the history accurately. Approval to discuss licensing sits higher. Counsel reads buying-group and manufacturer agreements, which can restrict disclosure of program terms. A rebate administrator who can export every claim still cannot authorize the discussion. What can be licensed stays unknown until SourceX's rights review.
Read → - Who can license royalty reconciliation dispute records? A who-can-say-yes decision tree for franchisors
Introduce the CEO, who can approve a licensing discussion about company data, with the franchise finance head as sponsor and first contact. The finance head owns the royalty receivable and knows where dispute notes live; the royalty analyst confirms which records exist; general counsel reads the franchise agreements; the POS administrator flags card data. Export access is not authority. Whether anything can be licensed stays unknown until SourceX's rights review.
Read → - Who can license special pricing agreement exception records? A who-can-say-yes decision tree for distributors
Introduce the pricing director first, then expect the CEO, with counsel, to decide. The pricing director runs the request and approval process and knows where approvals, claims and rejections are kept, which makes them the best guide and usual sponsor. Licensing authority sits higher, because special pricing records are shaped by supplier program agreements and name end customers. Some questions stay open until SourceX's rights review.
Read → - Who can license store transfer discrepancy records? A decision tree from inventory lead to authorized signer
Start with the head of inventory operations, then ask them to name the owner of each system and to bring in the CEO, who can approve a licensing discussion. The inventory lead knows where variances are worked, how reason codes are used and roughly how many cases a year there are, so they are the best first contact and usual sponsor. They seldom hold authority over employee data, customer data or licensing; that rests with the CEO, with counsel.
Read → - Who can license vessel maintenance deferral records? A decision tree for owner and manager sign-off
Start with the technical director, then follow the records to whoever can authorize a licensing discussion. The technical director can confirm systems, record classes and years of coverage, but technical access is not authority. For ships the company owns, the managing director or CEO usually decides. For ships it manages for others, the management agreement decides, and the owner's representative may need to join. Where the agreement is silent, name both and leave the answer to SourceX's rights review.
Read → - Who can say yes to licensing alert and incident records? A decision tree for partners
Introduce the CEO, who can authorize a data discussion, and name the operations center director as the person who knows the records; the CTO or VP of engineering often sponsors it internally. The director can say what exists and how good the notes are, but administrator access to a monitoring platform is not authority to license what it holds. Customer contracts and employee names in notes can add counsel and privacy sign-off.
Read → - Who can say yes to licensing assessment appeal records? A decision tree for assessment systems advisors
Introduce the chief executive or managing director, with the head of academic operations as the convener and working contact, and legal counsel or the data protection lead brought in early. The head of academic operations runs marking and appeals and can describe the records accurately, but rarely has authority to discuss licensing candidate records alone. Platform administrators have access, not authority. Candidate terms, platform contracts and student-privacy law decide what is possible, and that stays open until SourceX's rights review.
Read → - Who can say yes to licensing backorder substitution records? A decision tree for distribution ERP consultants
Introduce the CEO (in an owner-led distributor, usually the owner), often with the COO or CFO, and bring in the sales operations director as the convener. The sales operations director knows how substitutes are offered and approved and which systems hold the approvals, which makes them the right first contact, but they rarely have authority to discuss licensing company records alone. ERP and CRM administrators can run exports; that is access, not authority. Customer contacts and supplier price data raise questions for counsel, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing backup restore validation records? A decision tree for partners
Introduce the CEO of the managed IT provider or company, who can authorize a data discussion, and name the infrastructure director as the person who knows the records. The director can say which restore logs, integrity checks and client sign-offs exist, but console access to a backup platform is not authority to license what it holds. When records describe client systems, client contracts and counsel join the path.
Read → - Who can say yes to licensing brand standard exception records? A franchisor decision tree
Introduce the franchisor's chief executive, who can authorize a data discussion and sign, and name the head of franchise operations as the sponsor who can explain the files. Granting a variance is an operating decision; agreeing to license the history of those decisions is a company decision. When a file holds material a franchisee, landlord or local authority supplied, the tree adds general counsel before anyone says yes.
Read → - Who can say yes to licensing bundle inventory records? A decision tree for commerce ERP integrators
The inventory director is the right first contact for bundle inventory records, because that person approves stock corrections and knows where counts, kit definitions and adjustment history live. The person who can authorize a licensing discussion is the CEO; the CFO or COO often prepares the case. Finance typically owns the adjustment register, merchandising owns why bundles changed, and 3PL, supplier or app contracts can limit what may be shared. An integrator's admin access is never authority.
Read → - Who can say yes to licensing call transfer recovery records? A decision tree for CCaaS consultants
Introduce the CEO, usually with general counsel, and bring in the head of customer operations as the convener. The head of customer operations knows which transfers lose context, where recovery is recorded and which queues are involved, so they are the right first contact, but they rarely have authority to discuss licensing company records alone. Telephony and CRM administrators can run exports; that is access, not authority. Recordings and outsourced client calls need counsel, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing candidate ownership conflict records after a merger? A decision tree
Introduce the CEO of the merged firm, with counsel advising and the CFO preparing the terms, and bring in the commercial operations head as the convener. The commercial operations head usually adjudicates ownership conflicts and knows which client terms apply, which makes them the right first contact, but not the person who can approve a licensing discussion alone. ATS administrators know fields and visibility settings; that is access, not authority. Client terms, candidate personal data and an unfinished legal integration all need counsel, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing cash application exception records? A decision tree for treasury advisors
Introduce the CEO, often with the CFO or controller, and bring in the AR director as the convener. The AR director runs cash application and knows where remittances, matching decisions and deduction cases are kept, which makes them the right first contact, but they rarely have authority to discuss licensing company records alone. Treasury and ERP administrators can run reports and exports; that is access, not authority. Customer contract terms and outsourced case notes need counsel, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing catalog correction records? A decision tree for partners
Start with the catalog operations head, who knows which systems hold the correction history and how fixes are approved, but expect the yes to come from the CEO, usually with counsel. PIM and marketplace administrators have access, not authority. Supplier-provided content, agency work and marketplace seller terms add questions that counsel reviews, and some stay open until SourceX's rights review.
Read → - Who can say yes to licensing change collision recovery records? A decision tree for ITSM partners
Introduce the CEO, usually with general counsel, and ask the service delivery director to convene. The director knows which change conflicts happened, where the conflict results and post-incident reviews were written, and who would weigh a new revenue line against customer concerns. The ServiceNow platform owner, the monitoring admin and you, the implementation partner, have access, not authority. Reviews that name hosted customers need counsel, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing chargeback evidence assembly records? A decision tree for payments consultants
Introduce the CEO, usually with general counsel, and ask the disputes director or head of payments operations to convene. The director knows which systems built the response files and where outcomes are stored, but rarely has authority to discuss licensing company records. The support desk admin who can export every chat has access, not authority. Customer messages need privacy review, carrier and processor data may carry third-party terms, and what is in scope stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing claim denial routing records? A decision tree for billing operations consultants
Introduce the CEO, with the head of revenue cycle as sponsor and the compliance officer or general counsel at the table. The revenue cycle head owns the denial process and can describe routing rules and case history, so they are the right first contact, but rarely the person who can commit company records. Denial analysts and billing system administrators have access, not authority. Whether a billing company may license claim-level records depends on its provider agreements and HIPAA, and stays open until SourceX's rights review.
Read → - Who can say yes to licensing claims completeness review records? A decision tree for claims workflow consultants
Introduce the CEO, with the head of claims operations as convener and general counsel or the privacy officer involved from the first call. The head of claims operations owns the checklist process and knows where requests and receipts are kept, which makes them the right starting contact. Completeness reviewers, the claims system administrator and the repository owner have access but no authority. If the company handles claims for carriers, the carrier contracts may decide what can be licensed, and the full answer stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing classification corrections records? A decision tree for trade systems integrators
Introduce the CEO, usually together with general counsel, and bring in the compliance director as the convener. The compliance director knows which corrections exist, where the reasoning was written down and which broker relationships apply, so they are the right first contact. They rarely approve a licensing discussion alone. A trade systems integrator or IT team can see every table; that is access, not authority. Broker-authored material and consultant memos need contract review, and the final answer waits for SourceX's rights review.
Read → - Who can say yes to licensing client SOP change adoption records? A BPO decision tree
Introduce the CEO, together with general counsel, and bring in the delivery director as the convener. The delivery director knows which accounts, teams and systems produced the records and when each client transition happens, so they are the right first contact, but they rarely approve a licensing discussion alone. Knowledge, training and quality leads can describe and export records; that is access, not authority. Client-derived procedures and interaction data need counsel and often the client's consent, and the final answer waits for SourceX's rights review.
Read → - Who can say yes to licensing commission reconciliation records? A deal-stage decision tree for insurance accountants
Start with the finance director, who runs the monthly commission close and knows where insurer remittances, reversals and clawbacks are kept, then find the person who can approve a licensing discussion. In an agency or brokerage that answer depends on where the firm sits in a sale: its CEO (in an owner-run brokerage, usually the owner) before signing, the same person with buyer consent between signing and closing, and the acquirer's CEO after closing. Counsel advises on carrier and producer terms.
Read → - Who can say yes to licensing commissioning punch list closure records? A decision tree for energy project advisors
Introduce the contractor's CEO, with general counsel, and bring in the commissioning director as sponsor. The commissioning director knows which projects kept every test attempt and which were closed in a hurry, so they are the right first contact. They rarely hold authority to license company records alone. Platform administrators can open and export projects; that is access, not authority. Owner turnover terms and grid security details need counsel, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing content rights clearance records? A decision tree for media workflow consultants
Introduce the CEO, usually with the head of business affairs or general counsel, and bring in the head of rights operations as sponsor. The rights operations head knows where schedules, clearance memos and version logs are kept, so they are the right first contact, but they rarely decide alone whether the company's clearance history may be licensed. A rights coordinator or system administrator can run an export; that is access, not authority. Licensed content, licensor confidentiality and catalog sales need counsel, and what is in scope stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing contract renewal scope reconciliation records? A decision tree for sourcing advisors
Introduce the CEO (in a founder-led company, usually the owner), and ask the commercial operations director to sponsor the conversation. The director runs vendor renewals, knows where renewal drafts, asset histories, approvals and invoice checks are kept, and can explain the work. The CLM administrator, the IT asset manager and any advisor with repository access can describe records but cannot agree to license them. Vendor confidentiality terms go to counsel, and what can actually be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing course version approval records? A content-origin decision tree for LMS consultants
Start with the head of learning operations, who runs the review cycle for each course release and knows whether version history, reviewer sign-offs and retired assessments still exist. Then sort the content by who wrote it. Approval history and staff-written material usually take the short path to the COO and CEO; modules by outside authors, licensed publisher content and anything touching learners go through counsel first. Whether any of it can be licensed stays open until SourceX's rights review.
Read → - Who can say yes to licensing covenant reporting corrections records? A decision tree for loan systems consultants
Introduce the CEO of the lending business, usually with the chief credit officer's support, and ask the credit operations or portfolio monitoring head to start the conversation. That head knows where certificates, calculation versions and clarification threads live and how complete they are, but rarely has authority to approve a licensing discussion. General counsel reads the credit agreement confidentiality terms. Platform administrators and analysts have access, not authority, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing customer escalation recovery records? A decision tree for customer success consultants
Introduce the CEO, together with general counsel, and bring in the customer success director as sponsor. The director knows which escalations happened, where executive updates were written and how renewals were decided, so they are the right first contact, but they rarely hold authority to license company records alone. Helpdesk and success platform admins have access, not authority. Customer contract terms and personal data in tickets need counsel, and what can be licensed stays unknown until SourceX's rights review.
Read → - Who can say yes to licensing cutover reconciliation records? A decision tree for systems integrators
Start with the implementation director, because they know where mapping versions, run logs, reconciliations and tickets sit, then introduce the CEO, who can authorize the discussion and sign, with legal reviewing contract limits. Admin rights on the ETL tool or project tracker, the integrator's included, are access, not authority. Mapping documents the integrator wrote may belong to the client or the integrator under the statement of work, and customer contracts can limit order data. Those questions stay open until SourceX's rights review.
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