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
- The respectful close when a founder declines: read whose authority the no carried, acknowledge it in three sentences and switch off every channel your fund controls
Take a founder's no as complete, then check whose authority it carried. A founder who is the CEO has answered for the company. A founder who no longer runs it has given a personal answer, and nobody goes around them to the CEO. A sponsor who steps back has withdrawn only their own help. Every close is the same: three sentences, no request, and the topic switched off on every channel your fund controls. The no never travels into board or deal work.
Read → - The responsible handoff from wind-down advisor to SourceX: an authority-and-preservation handoff packet that passes the conversation to whoever controls the estate, carries counsel's constraints in counsel's own words, and ends the advisor's part on a named date
A responsible handoff moves a conversation, never records. Once whoever controls the estate has agreed in writing, the advisor sends an eight-item packet: the entity and its status, the controller, the controller's written agreement, counsel's preservation position in counsel's own words, dated system and storage events, the controller's fit statements, the advisor's role and reward disclosure, and what the advisor will not do. From then on the controller deals with SourceX directly, and the advisor's part ends on a date both have agreed.
Read → - The retained archive after a business divestiture: a retained-assets authority map that shows when the seller's copy can open a licensing conversation, and whose CEO decides when it cannot
Holding an archive is not the same as being free to license it. After a divestiture, the seller's copy of the sold unit's records is usually kept for listed purposes, such as tax support or defending claims, and SourceX's own guide on retained copies says a copy kept for those reasons usually cannot be licensed, even after de-identification. So a broker first learns which grant the seller holds. Records of the business the seller kept are its CEO's to discuss; the sold unit's records are the buyer's CEO's.
Read → - The retired administrator who knows the archive location: a knowledge-to-current-owner handoff that moves what they remember to the client, keeps passwords out of it and leaves the MSP's admin access unused
Treat the retired administrator's call as a knowledge transfer that belongs to the client, not as a lead you work. Write down what they remember about place, years, format and the tools needed to read it, and hand that note to the client's CEO and the person who owns IT decisions there today. Keep passwords and keys out of it, and do not use your own admin access to go and look. Touch the archive only on a written client instruction, and introduce the CEO to SourceX only if the CEO wants that.
Read → - The reward discussion with a partner who expects payment at signing: a five-turn correction script and four outcomes to rehearse first
No SourceX referral reward is paid at signing. On a company's first qualifying transaction the reward is the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap, and it becomes payable only after the Acquisition Partner's final written acceptance, completed handoff, cleared funds, payment of the company, finance approval and your tax and payment details. A partner finance manager's task is to move a colleague from "paid when they sign" to "projected at signing, earned once the company is paid", with a clause behind every sentence.
Read → - The rights questions that belong in a referral summary: an eight-line handoff appendix that records who can answer each one, never the partner's guess
A referral summary should carry rights questions, never rights conclusions. Eight belong in it: who created the records, which entity holds them, what customer contracts and privacy promises say, whether those terms have changed, how much personal information the records hold, whether third-party material is mixed in, whether anything is already licensed, and whether a lender, investor or parent must consent. For each, the appendix records who at the company can answer and whether they have. Counsel and SourceX's rights review supply the answers.
Read → - The risk of using old mandate criteria in founder outreach: a versioned distribution process that stamps, links and recalls every criteria sentence you send
Old criteria in a founder email do three kinds of damage: they invite companies that no longer fit, turn away companies that now do, and describe an agreement or payment trigger that has since changed. SourceX's referral terms record versions taking effect on 12, 19, 21 and 22 October 2026, and its qualification page says criteria differ by program. Treat every criteria sentence you send as a versioned document: stamp it, link the live source, log who received it and recall it when the source changes.
Read → - The SaaS partner pilot with an opt-in customer cohort: a ten-week launch plan that never touches product data
Run the pilot as a small, time-boxed cohort of customers who each said yes in writing, and keep three things apart: what your product knows about a customer, what the customer has agreed to hear about, and your own role, which is to introduce and nothing more. The customer's CEO decides whether to talk to SourceX and what, if anything, to license. Your company never moves, describes or vouches for the customer's records, and a reward follows only if SourceX actually pays that customer.
Read → - The SaaSpocalypse explained: what PE-backed software companies can do next
The SaaSpocalypse is the 2026 nickname for the sell-off in software valuations driven by fears that AI agents will shrink seat-based revenue. PE-backed software companies can respond through product, pricing, cost and M&A, and can add a fifth option: licensing engineering records such as repositories, code reviews and tickets to SourceX and data users, without selling the IP.
Read → - The seller has left: finding the authorized person after closing with a five-step reconnection guide that dates every authority fact from public sources, never from the closing file
Reconnect with whoever decides today, not with the person you used to know. After closing, the acquirer's CEO decides for an acquired company. If some records stayed in the selling entity as excluded assets, that entity's CEO decides for them, and that may still be your former client. Confirm each authority fact from a dated public source rather than your deal file, use the departed seller as a relay only if they still have a live line, and otherwise send one plain note saying who you are and why you are writing.
Read → - The seller's permission comes before a data introduction: a ten-line instruction that sell-side advisors get signed by the client and the target's CEO, and the milestones that make it lapse
Get permission in writing, from the right people, before the company's name leaves your firm. In a sale two permissions are in play: your client's instruction under your engagement, and the decision of the target's own CEO, who decides for the company until closing. In an owner-run business one person gives both, in two capacities. A short written instruction records the facts you may pass on, who may hear them, how any reward is disclosed, and the milestone at which it lapses and has to be given again.
Read → - The shared inbox problem in company referral tracking: a six-step identity check that turns info@ into one legal company, one group and one CEO
A shared inbox breaks referral tracking because an email address identifies a mailbox, not a company or a person. An introduction sent to info@ reaches whoever reads it that day, a reply from it does not show who agreed, and the company may already have written to SourceX from that same address. Before you introduce, resolve the address to one legal entity, its group and a named CEO who has replied personally, then record the company, domain, method and timestamps in your submission.
Read → - The small business retirement wave: what the boomer exit wave means for M&A advisors
The small business retirement wave means more owners will try to exit than buyers can finance. McKinsey estimates about six million US small and medium-size businesses face ownership transitions by 2035, yet only a little more than one million are viable sale candidates. For M&A advisors, that gap brings non-sale options, including licensing operational records, into client conversations.
Read → - The State of Company Data Introductions: a blueprint for an annual report that counts every attempt, including the ones that failed
A credible report on company data introductions publishes its method before its findings and counts every attempt, including introductions that were declined, withdrawn, duplicated or never answered. SourceX has not published such a report, so no results exist. What a partner research lead needs is the blueprint: a census of every introduction submitted in a calendar year, the consent each group gives, a fixed list of variables, analysis rules written in advance, and twelve questions that stay open until data answers them.
Read → - The supplier-day workshop for data licensing introductions: a 45-minute opt-in agenda that keeps procurement out of the room, speaks to each supplier as an independent company and collects nothing for SourceX
A supplier day is the corporate's own event, organized around buying, so any data licensing session inside it begins with a pressure problem. Run it only as an opt-in breakout that procurement neither organizes nor attends, keep any attendance record away from both procurement and SourceX, say at the start whether anyone in the corporate could be paid, and speak to each supplier as an independent company whose CEO decides about its own records. Collect nothing in the room; suppliers who want more apply directly or ask later.
Read → - The system integrator's data opportunity qualification sheet: a system-history and authority intake that dates every platform a client has run, records who created what each one holds and ends with the CEO's answer
Qualify the company first, then describe its systems; never the other way round. A system integrator usually knows what no CEO has written down: which platforms the company has run, for how many years, and what happened to the old ones at each cutover. Put that on one sheet as metadata, add who created and who administers the records in each system, check the company facts SourceX screens first, and take the sheet to the CEO. The company lists its own systems when it applies; you never export, count or sample anything.
Read → - The ten-introduction experiment for an AI data network thesis: a pre-registered plan that still teaches you something if no deal closes
Ten introductions cannot estimate a conversion rate, but they can reject a confident thesis if the plan is written down first. Before the first ask, fix which ten companies enter and why, the outcome at each stage, the decision rules, a comparison and the stop criteria, then date the plan. Declined and unanswered rows stay in the denominator. With ten rows, one or no CEO conversations rejects the claim that most mapped companies convert; four or more rejects the claim that almost none do.
Read → - The time cost of a data introduction: a platform team time-diary study that logs each episode of work on the day it happens, keeps the hours spent on companies that never qualify in the total and publishes no figures until the cohort closes
That nobody has measured it, and that estimates made from memory will not answer it. Recall turns a scattered week of short calls and abandoned checks into a tidy guess. This study design has every platform team member, and every outside relationship owner who agrees, log each episode of introduction work on the day it happens, coded by activity and by company, including work on companies that never qualify. Hours per verified application are reported only after the cohort closes. No diaries have been kept and no results exist.
Read → - The trade network's data opportunity office hour: a 60-minute drop-in format that sorts every member question into one of four lanes, writes down questions instead of company facts and leaves each decision with the member's CEO
Run it as a question clinic, not an intake desk. Members drop in with questions; the host answers only from SourceX's published pages, sends every question about fit, price or rights to the member's own application or to SourceX directly, and leaves every decision with the member's CEO. The host writes down questions, never company facts: no records, systems lists or headcounts are collected, and nothing about any member goes to SourceX.
Read → - The UK debate on AI training and copyright: what referral partners should know
The UK debate on AI training and copyright asks whether developers may copy protected works unless owners opt out, or only with permission. It concerns public creative content. SourceX introductions involve US companies licensing their own records under signed agreements, so the debate is background for partners, not a rule that governs their introductions.
Read → - The unpaid introduction path for a finance professional: a four-part template that records your rules check, puts the reward question to SourceX in writing, and only then gives the CEO a message saying exactly who is paid
An unpaid introduction from a finance professional takes three steps, in this order. First, clear your own rules with your board, society, employer or counsel. Second, ask SourceX in writing how it will handle an introduction from someone who wants no reward: its published terms do not cover declining one, so SourceX decides. Third, give the CEO a message that repeats exactly what SourceX told you. The company is paid the same either way. The template below holds all three steps, plus a file note.
Read → - The US Copyright Office report on generative AI training, explained
The US Copyright Office's Part 3 report on generative AI training, released in May 2025 as a pre-publication version, discusses where AI training may implicate copyright, how fair use may apply and how practical licensing is. It is regulator analysis, not law, and it does not decide any one company's rights.
Read → - The value of a documented refusal: when an agent should ask first
The records that show an agent should ask first are the ones where a person paused instead of acting: the original instruction, the specific conflict they noticed (scope that did not match, authority that was missing, evidence that was incomplete), the question they asked and to whom, the answer, and what happened next. A documented hold or refusal with a reason code is the strongest form, because it shows a rule being applied before anything went wrong.
Read → - The voice note script for a trusted business contact: five beats in sixty seconds that name the company's reason, say what you earn and leave an easy no
A data referral voice note works when it sounds like you talking about one company, not a program reading itself aloud. Keep it near sixty seconds and five beats: why this company, the records you know it keeps, what SourceX does, the referral reward you would receive if a deal completes, and an easy way to say no. Record it only for someone who already knows your voice, say the reward in the audio itself, and send the written terms afterward.
Read → - The warm handoff from a specialist fund to a generalist: a one-page context brief that carries sector knowledge to the partner the CEO trusts, leaves diligence material behind and names one person to ask
A specialist fund often sees why a company's records might matter before anyone else does, but the CEO usually listens to the generalist who sits on the board. Let the specialist write the context and the generalist make the ask. The handoff is a one-page brief built only from sector knowledge, public facts and what the CEO has already said in the open; anything the specialist learned under a confidentiality agreement or in board materials stays behind. One person then contacts the CEO, and SourceX credits at most one introduction.
Read → - The weekly partner pipeline meeting that stays useful: an exception-only agenda of eight triggers, a 25-minute running order and a decision log that keeps on-track referrals off the table
Run it weekly for 25 minutes and spend the time only on exceptions: referrals whose facts changed since last week, or that need a decision nobody can make alone. Eight triggers put a record on the agenda, from a CEO withdrawing to a dashboard status moving backward; everything on track is read beforehand and never discussed. Every decision leaves with an owner and a date. The meeting never recites client facts, never forecasts rewards and never decides credit, which SourceX settles from dated records.
Read → - The workflow continuity test: can a ticket be traced to its final resolution?
An operational workflow has a complete evidence trail when every step can be reached from the one before it by a shared identifier, from the first request to a confirmed resolution. An introducer can check this without seeing any record: ask the company to trace a few closed cases hop by hop and report how many links carry an ID, how many rely on dates or memory, and where the chain breaks. That count says more than any promise about dataset value.
Read → - Thomson Reuters v. Ross: the first AI fair use ruling explained
Thomson Reuters v. Ross is a 2025 federal district court decision in which, as widely reported, fair use was rejected for copying a publisher's proprietary Westlaw content to build a competing AI tool. It is one fact-specific ruling, was headed to appeal, and does not settle AI training law.
Read → - Time write-off review across time tracker, ERP and billing: a system map of records and linking keys
Five linking keys join a time write-off review across systems: the time entry ID that ties hours to their narrative, the original project and task code, the adjustment ID that pairs a reversal with its replacement lines, the reason code with the reviewer's name, and the invoice or credit note number that shows what the client was finally charged. The entry ID is the hinge. If a system rewrites the entry in place, the move between projects disappears.
Read → - Time write-off review history: what to inventory before a timekeeping platform change
Before a timekeeping platform change, inventory the history behind each time write-off decision: the original time entry and its narrative, the project and budget it was charged to, the pre-bill edit or write-off request, the reviewer's reason, and the adjustment that followed. Record which system holds each, whether reversed lines survive the move, and when the old system goes dark. An accountant introducing the firm collects only metadata and connects the practice operations head with whoever can authorize a licensing discussion.
Read → - Time write-off review, a worked hard case: one task, two projects, one charge code
The records that explain a time write-off exception are the original time entry with its narrative, the project and budget it hit, the pre-bill write-off proposal, the reviewer's reason, the reversal and replacement lines, and the invoice the client accepted. The write-off amount alone shows a loss; the sequence shows a judgment about who the work was for. The Illustrative case below walks through one disputed entry step by step, then shows how to spot similar cases at a client.
Read → - Timesheet correction approval history: what to inventory before a payroll platform transition
Before a payroll platform transition, inventory the records that show how timesheet corrections were approved and settled: the worker's original submission, the client's approval in the VMS, the payroll run that paid it, the revised timesheet or credit and debit memo, and the adjusted invoice. Note years covered, which system holds each, who owns it, and when access to the old payroll platform ends. Then introduce the payroll operations head.
Read → - Timesheet correction approvals across VMS, front office, payroll and accounting: a system map with linking keys
Four identifiers join a timesheet correction across systems: the client's work order or assignment number, the firm's placement ID, the VMS timesheet ID, and the credit or debit memo number that references the original invoice. Payroll adds a fifth, the employee ID with pay period, and every system has to agree on where a pay week starts. The mapping between work order and placement ID, and the reason for each correction, are the two links most often kept outside any system.
Read → - Timesheet correction approvals hard case: a night shift that crosses the payroll and billing cutoffs
The records that explain how a staffing firm handled a timesheet exception are the ones that follow one correction through every system it touches: the worker's original time entry, the correction request, the client approver's sign-off, the payroll adjustment, the revised invoice or credit memo, and the reconciliation showing paid hours and billed hours agree again. The hard case is a shift that crosses a weekly cutoff, because the error changes overtime, pay and billing at once.
Read → - Tool-call provenance in a business workflow: tracing a support status change to the rule that made it
Tool-call provenance is the record of which tool, rule or person changed a business record, with which inputs, under which version, and what happened next. In a help desk it looks like an audit line saying a ticket moved to Solved because a named trigger read a confirmed billing credit. The record is useful when the actor, the inputs, the rule version and the outcome are logged together for each change.
Read → - Toysmart and RadioShack: what customer data sales in bankruptcy teach restructuring pros
Toysmart and RadioShack are the cases most often cited for a simple rule: customer data can be sold in bankruptcy only within the privacy promises the debtor made. The Bankruptcy Code now routes certain sales through a consumer privacy ombudsman and court review, which is one reason operational business records are the cleaner asset.
Read → - Track company satisfaction before asking for another introduction: a six-question post-handoff interview and a gate that one bad answer can close
Referred company satisfaction is the CEO's account of how the introduction and the handoff to SourceX were handled: whether what they were told matched what happened, whether a no was easy to say, what it cost in time and whether confidentiality held. It is not whether the company licensed anything. Collect it in a short interview at fixed points after handoff and use it as a gate: no second ask of that CEO, or of whoever brokered the first introduction, until the latest interview comes back clean.
Read → - Trade association AI guidance for members: what to cover on their own data
A trade association AI policy should include a neutral section on members' own data: licensing is each company's decision, rights and privacy come first, exclusivity should be understood, and the association educates and introduces without collecting, pooling or pricing member records or endorsing any buyer.
Read → - Trade secrets in AI training data licenses: what attorneys should flag
Licensing company records as AI training data can put trade-secret status at risk if secret material leaves the company without tight scope, redaction and confidentiality terms; whether it does depends on what is delivered and how it is protected. Counsel typically carves out source code, formulas, pricing logic and similar core secrets first, then limits use, access and onward disclosure.
Read → - Trajectory-level evaluation: when a refund is the right amount but issued without authority
Trajectory-level evaluation grades the path to a result, not only the result: which steps were taken, in what order, and by whom. In an ordinary business workflow, a store refund of exactly the right amount still fails the check if the person who approved it was not authorized to. The records that support it show every step of a routine task with the person, the time and the rule that applied.
Read → - Transfer the domain and seller-held accounts after buying a business
To transfer a domain after buying a business, list every account, confirm who is registrant and admin, require transfer in the purchase agreement, add a company-owned admin before removing the seller, and export archives first. Until accounts move, the buyer does not control the company's email and file history that a SourceX review would need.
Read → - TSA expiry for M&A integration advisors: who preserves the record inventory before tenant access ends
At transition service agreement (TSA) expiry, the person who can preserve an approved record inventory is the executive who owns the carved-out business's records under the purchase agreement, usually the buyer's CEO or CFO, acting through the IT lead who controls tenant cutover. An M&A integration advisor's job is to ask that owner, before access ends, who will list what exists and keep it. If the company looks eligible and wants to explore licensing, the advisor introduces the decision-maker to SourceX.
Read → - Turnaround consulting outlook for 2026: distress signals and one intake addition
The 2026 turnaround consulting outlook turns on four pressures: refinancing deadlines, borrowing costs, tariffs and stress in private-credit portfolios. Read each signal by its period and method before comparing them. Then add one intake step: a records-and-rights screen, so a long-lived client's operating records are assessed as a possible recovery before systems are shut off.
Read → - Two suppliers, one letter apart: a supplier onboarding exception worked step by step
The supplier onboarding records that explain an exception are the ones that show the question, the evidence and the person who answered it: the supplier request, the duplicate-check result that paused it, the missing-document request and what came back, each screening hit with its disposition, the tax identity check, the bank verification note and the acceptance note. Payment history afterwards shows whether the decision held.
Read → - Underperforming portfolio company options, and where its records fit
An underperforming portfolio company usually has seven paths: turn it around, recapitalize, sell it, merge it into another holding, run a distressed sale, assign its assets, or wind it down. Before any path that retires systems, a sponsor can also screen whether years of operating records could be licensed for AI training as additional recovery.
Read → - Underwriting referral triage across workbench, email, policy admin and loss control: a system map of linking keys
Five joins rebuild an underwriting referral across systems: submission to referral flag, flag to referral question, question to approval, approval to the bound policy's conditions, and conditions to the evidence that cleared them. The submission or quote number is the hinge, carried forward as the job number and then the policy number. The broker email thread is the join most often missing, because it lives in a mailbox keyed to nothing but a subject line.
Read → - Underwriting referral triage hard case: a warehouse above authority, traced step by step
The records that explain how an insurer handled an underwriting exception are the trigger that raised the referral, the line underwriter's question, the evidence gathered, the senior decision with its conditions, the bound policy showing those conditions, and proof each condition was later met. Together they show why the case needed a senior view, what was traded for accepting it, and whether the trade held. The case below follows one referral from flag to cleared condition.
Read → - Underwriting referral triage history: what to inventory before a workbench rollout
Before an underwriting workbench rollout, inventory the trail behind every referral: the rule or limit that triggered it, the line underwriter's referral question, the senior decision note, the approval conditions, and the evidence that each condition was later cleared. Record which system holds each piece, which years and authority grids it covers, and when the legacy system goes read-only. A transformation advisor collects only this metadata and introduces the underwriting operations head with the executive who can authorize a licensing discussion.
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