Search guides, questions and resources

Generally the developer, not the data owner, answers for how a model is trained, deployed and used, because it controls those choices, and a well-drafted license says so. The owner remains responsible for its own promises: that it had the rights and permissions to license the records and that it described them accurately.

It depends on the state. Sales tax applies only where a state's law reaches the transaction, and states differ on whether licensing a dataset is a sale of a digital product, a taxable information or data processing service, or a transfer of intangible rights outside the tax. Delivery method, buyer location and contract wording all matter.

Whether a finder's fee is legal depends mainly on what you introduce. Fees tied to securities transactions, such as capital raises or the sale of a company's stock, can require broker-dealer registration under Exchange Act section 15(a). An introduction for a commercial data license is a different question, shaped by the contract and your own professional rules.

Whether a one-time data license fee is ordinary income or a capital gain depends on the signed terms and the tax rules, so a CPA must decide it. A license that keeps ownership with the company is generally different from a transfer of all substantial rights. Resolve the questions below before the agreement is signed.

Yes. A referral reward is a conflict of interest a fractional CFO should disclose, because you advise on a decision that could pay you. It can usually be managed: disclose in writing before the introduction, keep your retainer fixed, leave decisions to the owner, and decline the reward if you sign for the company or your contracts forbid it.

A referral fee is calculated on whatever base the agreement defines: gross revenue (everything billed), net revenue (after listed deductions) or fees actually collected. SourceX uses a narrow, checkable base: partners earn {{rate}} of the eligible platform fees SourceX collects from a referred company's licensing deals, capped at {{cap}} per company, never from the company's proceeds.

A referral program is not a pyramid scheme when rewards come from completed, paid deals with real customers rather than from recruiting other participants. SourceX pays a partner a share of the fee it actually collects after a buyer pays. The published program facts include no payment for joining or for recruiting other partners.

Not automatically. For a non-resident, pay for personal services is generally US-source only to the extent the services are performed in the United States, so a referral reward for introductions made entirely from abroad is usually foreign-source. How the payment is characterized and where you actually did the work can change that, so confirm with a US tax adviser.

A SourceX referral reward is generally not a 1.510 contingent fee, because 1.510 covers result-dependent fees a CPA charges a client, while the reward is paid by SourceX from its own fee. The reward is tested under 1.520 instead. State boards can be stricter, so confirm before accepting anything.

Yes, AI data licensing is a legitimate market, but each offer must earn trust on its own. A sound offer charges no upfront fees, moves no data before a signed agreement, reviews rights first, puts price and payment terms in writing, and pays referral partners only after the buyer pays. SourceX's published process maps to each of those tests.

Yes, but it is one-time revenue, not a recurring line. Public filings and press reports show AI developers paying for licensed content, including multi-year contracts Reddit disclosed in its IPO filing. For a mid-market company, a license is a single payment for a defined dataset, and nothing is owed until a buyer selects the data and pays.

Nobody can say for sure. AI valuations and spending may correct, but the need for real business records to train and test agents is a separate technical question, because such records are scarce on the public web. A bubble could reduce buyer numbers and prices, so no deal or reward is guaranteed.

There is no blanket answer: in the US, whether AI training is fair use is decided case by case, weighing four factors against the facts of each lawsuit, and the litigation is still moving. Licensed business records largely avoid the question, because the buyer trains under express permission in a signed license rather than relying on a fair-use defense.

It depends on how passive the arrangement is. A tax-exempt association can owe tax on income from an unrelated trade or business it regularly carries on, but royalties are generally excluded under IRC 512(b)(2). Payments for active promotion or services, such as per-introduction referral rewards, tend to fall outside that exclusion, so structure the arrangement with tax counsel.

An undisclosed referral fee can be commercial bribery when someone who owes a duty to another party takes a payment without that party's knowledge and consent. State statutes and the agency rule against secret profits focus on secrecy, so SourceX partners disclose the reward before introducing.

Usually, yes. Article 9 makes general intangibles the catch-all for personal property that fits no other category, and the definition names software, so databases and business records typically land there. A blanket lien covering general intangibles therefore usually reaches them, which is why a CFO should read the loan documents before a company signs a data license.

Possibly, in part. Section 541 of the Bankruptcy Code addresses what becomes property of the estate, so business records and data rights the company holds may be estate assets controlled by a debtor in possession or trustee. Ownership, contracts and privacy promises decide each case; confirm with bankruptcy counsel.

It depends on the structure, and the company's CPA should decide. License income is taxable unless a law exempts it, but whether a data license payment is ordinary income or capital gain turns on what the agreement transfers, who receives the money and how the company is organized. Flag the license to the tax adviser before signing.

Yes. In a small, long-tenured team, role, project detail, timing and writing style can identify a person even after names are removed. Risk drops with stronger role and project redaction, excluding small units, broader aggregation, a shorter date window, and a contractual ban on re-identification, tested by colleagues before delivery.

Usually not. HIPAA's definition of protected health information excludes employment records a covered entity holds in its role as employer, and most employers are not covered entities at all. Employee health details in HR files are still protected by disability, leave and state privacy laws, so companies keep them out of any data license.

Employee keystroke and screen monitoring is often legal in the US when the employer owns the systems and gives any notice a state requires, but licensing the captures is a separate decision. Screens expose personal and customer data, so SourceX scopes them strictly, and many companies license structured logs instead.

Fleet telematics data can be valuable for AI training, but rarely as raw location pings. The value sits in what the pings connect to: dispatch decisions, exceptions such as breakdowns and detention, how the team resolved them, and the outcomes. A fleet operator licensing years of those linked records is a different business from consumer vehicle-data resale.

Accepting a referral fee is ethical when four things hold: the introduction serves the other person's interest, the fee is disclosed before they decide, your professional rules and employer allow it, and the payment does not change your advice. A hidden fee, or one that steers someone to a worse option or breaks your code, is a kickback.

It can be ethical to take a referral fee from a client deal when four conditions hold: you disclose it before the client acts, it costs the client nothing, your advice stays independent and your rules allow it. A SourceX reward comes out of SourceX's collected fee, never the company's proceeds, and is paid only after the buyer pays.

It can be defensible. Licensing during layoffs supports recovery when the sponsor authorizes it, personal and HR content is excluded, departing staff's content is limited, and employees are told before delivery. It feels exploitative when timed against termination notices or kept quiet. Take employment counsel's advice on timing.

Generally yes, when the company owns the records and five gates clear: ownership, contracts, privacy law, sector rules, and notices or consent. No general US law forbids licensing records you own, but each gate can narrow the scope. Counsel confirms the position, and nothing is binding until the company signs.

Licensing business data to AI developers can be lawful in the US, but it depends on three things: whether the company owns the records, whether its contracts and privacy promises allow the use, and whether privacy or sector laws such as the CCPA, HIPAA or GLBA apply. Rights review and de-identification come before any delivery.

Licensing a closed company's email archive is often lawful, but it depends on three things: who now controls the company's assets, what employee policies and privacy notices promised, and what the messages contain. Federal and state communications and privacy laws, any bankruptcy court approval, and de-identification agreed before work begins all shape the answer.

Licensing company data carries real but manageable risk. With SourceX, only the agreed scope is delivered, only after the company signs, and de-identification and redaction rules are set before work begins. Residual risks, such as re-identification and contract conflicts, stay with the company to weigh before it agrees.

Licensing company data to AI developers can be ethical when the company holds the rights, identifiers are removed, employees and customers are treated fairly and buyers get an accurate description. It is the consent-based alternative to unpermissioned collection. Consumer personal data, unauthorized health records and data owned by clients are red flags.

Licensing company data is worth it for a mid-sized company that holds years of its own operational records across many systems, clear rights to license them and a sponsor willing to grant an exclusive AI-training license for a one-time payment. It is rarely worth it when rights are unclear, records are mostly consumer or health data, or exports are impossible.

Licensing data can be a sale under the CCPA when personal information of California residents goes to a third party for money or other valuable consideration. Properly de-identified records are analyzed differently. The definition is in Civil Code section 1798.140, and the company's counsel decides how it applies to a given scope.

Licensing company data does not give away the crown jewels when the license is scoped carefully. The company keeps ownership, grants AI developers a defined right to use selected historical records for training, agrees de-identification and redaction rules before any work, and signs only if price and terms work. The real cost to weigh is exclusivity.

Messy company data is often still worth licensing. AI buyers weigh real workflows, years of history and clear rights more than tidy folders, and SourceX handles inventory and preparation after qualification. The genuine blocker is not mess but records that no longer exist, cannot be exported, or belong to someone else.

Your company's data is likely valuable to AI developers if you have 50+ full-time employees at peak (contractors excluded), several years of records across many business systems, records that show how work turned out, the rights to license them and a sponsor willing to consider an exclusive license. Answer the ten questions below to find out.

Verify, don't trust on faith. SourceX manages data licensing from sourcing and rights review to delivery and payment, does not train AI models, is based in Los Angeles with a Delaware legal address, publishes its terms, and gives companies one all-in price with nothing binding until they sign.

No revenue minimum is part of the baseline. SourceX screens on 50+ full-time employees at peak (contractors excluded), several years of documented operations, breadth of records, rights to license and an authorized sponsor. A lower-revenue company with a large team can fit; a high-revenue company with a small team may not.

Possibly. If your consultant, accountant or CFO introduced your company to SourceX as a registered partner, they may earn a share of SourceX's fee if your company licenses data and SourceX is paid. That share comes out of SourceX's fee, never out of your price, and a good advisor tells you about it in writing before you apply.

You can only tell from the vendor's current paperwork: the subscription agreement, privacy policy, data processing addendum and any AI feature terms, plus your admin console's AI settings. Look for clauses letting the vendor use customer content to improve or train models, and check before licensing your own records, since a prior grant can conflict with an exclusive license.

No. Headlines about shut-down startups selling employee Slack messages raised fair questions about who authorized the sale, what was included and who was told. An authorized license through SourceX answers each one: a sponsor with authority signs, scope is written down, de-identification is agreed before work begins, and nothing is delivered before an executed agreement.

An IT due diligence request list already asks for most of what shows whether a company's records could be licensed: the systems inventory, retention settings, retired platforms, privacy notices and data processing terms. Read each answer twice, once for risk and once for value, and never request the records themselves for licensing purposes.

An IT budget template for a mid-sized company should give every system and contract its own line, grouped into applications, finance systems, collaboration, infrastructure, devices, security, managed services, archives and projects. Each line needs an owner, a renewal date, the records it holds and a planned fate, so the budget doubles as a system count before anything is cut.

An IT due diligence checklist reviews a target's infrastructure, applications, security, IT team, vendors and integration costs. Add four data questions: how many systems hold how many years of history, whether contracts and privacy promises allow licensing, whether complete exports are possible, and whether any data is already licensed for AI training.

When you sell your business, hand over every admin credential, tenant, domain, license and archive location against a written checklist signed off by both sides before closing. Record where historical email, ticket and file archives live so the new owner can still find them later.

An MSP that supports trucking companies can introduce a carrier to SourceX when it has 50+ full-time employees at peak, years of TMS, EDI and dispatch records, and clear rights. A TMS upgrade or cloud move is the natural moment, and driver and shipper data stay out of scope.

An IT wind-down checklist keeps a closing company's systems paid, accessible and exportable until the fiduciary in control approves each step, legal holds and retention duties are met, and records have been assessed for value, including a possible SourceX data licensing introduction. Only then are subscriptions cancelled, accounts closed and hardware sent for destruction.

An ITAD data destruction checklist for a routine hardware refresh should confirm three things with the client's owner before any drive is wiped: whether the old device holds history that exists nowhere else, who owns that history, and whether it can still be exported. New hardware goes live on schedule; only destruction waits for sign-off.

ITAR technical data and EAR controlled technology are export-controlled engineering information about defense or dual-use items, and a deemed export can occur even inside the United States. Controlled records therefore need to stay out of any data license. A defense-adjacent manufacturer may still license non-controlled commercial records once its export lead confirms the separation.