Search guides, questions and resources

No. For SourceX's size baseline, a franchisor counts its own full-time employees: support-center staff, field teams and staff at company-owned units on its payroll. Employees of independent franchisees work for those franchisees, so they do not count, even when the brand advertises system-wide jobs. Joint-employer disputes are a separate legal question that does not change this count.

A no-shop clause usually stops the seller from soliciting or negotiating competing acquisition proposals during exclusivity, not every other contract. Whether it blocks a data license depends on how the LOI defines the restricted transaction and on any conduct-of-business limits on new material contracts or IP licenses. Read both, and get the buyer's written consent before signing.

Usually not by itself. A customer non-solicit typically bars you from soliciting a former employer's customers for competing business, and an employee non-solicit bars recruiting its staff; introducing a company to SourceX to license its own records is a different activity. The exact wording, state law and your confidentiality terms still control, so read the agreement or ask counsel.

A one-time data license usually raises a portfolio company's ASC 820 mark only by the net cash it adds, not through a higher multiple. Valuation teams commonly normalize a single license payment out of run-rate EBITDA, so enterprise value barely moves, while lower net debt can lift equity value.

Usually, yes. When a business converts, renames or is bought into a new entity, what matters for data licensing is how far back its records go and whether the rights to them reached the current owner, not the date the entity was formed. Conversion filings, the purchase agreement and any IP assignment are the documents that show it.

Not by itself. ABA Model Rule 5.4(a) bars a lawyer from sharing legal fees with a nonlawyer. A SourceX referral reward is paid out of SourceX's own platform fee, and no legal fee changes hands, so the analysis usually shifts to conflicts of interest, independent judgment, client disclosure and your state's version of the rules.

No. A buyer does not get standing access to your systems. The company or its IT provider exports an agreed, de-identified scope after an executed agreement and the company's authorization. Large deliveries can stay in the company's own storage or ship on encrypted drives, so the buyer receives a dataset, not credentials.

An exclusive AI training license does not stop a company from being sold. The company keeps ownership of its records, and the license gives one buyer AI-training rights to a defined dataset for an agreed term. What carries over to an acquirer depends on the assignment and change-of-control clauses, so settle them with deal counsel before signing.

An NDA generally survives an acquisition or shutdown for as long as its own survival clause says, but whether it binds a buyer depends on the deal structure and its assignment terms. M&A advisors should list each NDA and its survival period before scoping any post-deal data license.

An SBA EIDL lien can cover intellectual property, company data and license proceeds when the loan's security agreement lists general intangibles, all assets or proceeds as collateral. That does not rule out a data license, but the CFO should read the collateral and transfer covenants and ask counsel whether SBA consent is needed before the company signs.

CAN-SPAM can apply to business-to-business email, because it regulates commercial messages and is generally understood not to exempt business recipients. A permissioned one-to-one introduction is lower risk than a bulk send, but the message should still be honest, identify the sender, include an address and offer an opt-out.

Contributing to a benchmarking survey, credit bureau or claims database usually does not stop a company licensing its own records, because it is not an AI training license. The contributor terms should still be checked for exclusivity, use limits or ownership language before those fields are listed.

GDPR applies to a US company in two ways under Article 3: when it processes personal data in the context of an EU establishment, such as a subsidiary or branch, or when it offers goods or services to people in the EU or monitors their behavior there. A US-only business with no EU presence or targeting is generally outside it.

Git history matters because commits, pull requests and review comments record how code changed and why, which a snapshot cannot show. For a data license, full history is the more useful asset. A fractional CTO should preserve it before any migration, then introduce qualifying companies to SourceX.

GLBA's Privacy Rule generally protects consumers, meaning individuals who obtain financial products for personal, family or household purposes, not businesses borrowing for commercial use. Guarantors, sole proprietors, the Safeguards Rule, state law and contracts still limit what a commercial lender can license. Counsel must confirm the position for each dataset.

GST on a referral commission from a foreign company usually turns on whether you are treated as an intermediary. If you are, the supply can be treated as taking place in India and GST may apply despite the foreign payer. If not, the commission may be a zero-rated export of services, typically under an LUT. Income tax is separate.

It depends on the client relationship and the role the firm takes. The AICPA Code says a member who assumes a management responsibility for an attest client, such as deciding on, committing to or signing a data license for it, impairs independence. Any referral reward raises separate commission rules, so check attest relationships and your state board first.

Licensing source code does carry security risk, but the serious risks are specific and controllable: credentials buried in git history, infrastructure details and code the company does not own. Scanning the full history and rotating secrets, excluding client and vendored repositories, stripping environment specifics and scoping by repository and date handle most of it before anything leaves.

Licensing company data does not by itself raise or lower valuation; acquirers look at how the license is structured and disclosed. Under a SourceX-managed license the company keeps ownership and normal use, AI-training exclusivity runs for an agreed term, and the payment is one-time. List the agreement for bidders and have deal counsel review it before signing.

Licensing company data can affect cyber or D&O insurance, depending on notice clauses, contractual liability exclusions and what the application said about data sharing. The company's broker should read the policy against the draft license before signing, and a CFO can raise five written questions to start.

Licensing data does not automatically conflict with SOC 2, because the report describes controls rather than banning transfers. Conflicts come from customer agreements, security addenda, privacy notices and internal policies. An MSP should separate its own records from client data and review those documents before any introduction.

Shareholder approval is generally required when a corporation sells, leases or exchanges all or substantially all of its assets, as Delaware's section 271 provides. A scoped, non-transferable data license that leaves ownership with the company is usually analyzed differently, but late in a wind-down, when records may be most of what remains, counsel should confirm before the board signs.

Licensing company data does not automatically raise valuation, because one-time license income is usually treated as non-recurring. It can still strengthen an exit story by showing outside demand, documented rights and organized records. Advisors should present it as evidence in the data room, not as a multiple-boosting asset.

Licensing company data usually needs approval only as far as the company's own governing documents require. A scoped license that leaves the company owning its data is normally an ordinary contract signed by an authorized officer, but bylaws, investor rights or lender covenants can add steps. Company counsel confirms which apply.

Not automatically. Trade secret status depends on reasonable measures to keep information secret, and sharing under confidentiality terms can be consistent with that. The safe approach is to exclude true secrets and license redacted workflow records, decided with counsel before scoping. This is general information, not legal advice.

Not directly: competitors never receive the data, but the risk is not zero. A license limits use to AI training, keeps sensitive categories out of scope, de-identifies records and is typically exclusive for an agreed term. What no license can promise is that widely used AI models never get better at the kind of work the company does.

No. A healthy company licensing a defined set of records is a different transaction from a distressed sale of archives. The company keeps ownership, approves scope and price, receives a one-time payment, and nothing is binding until it signs. Long operating histories are what AI buyers look for, which favors established businesses.

Model distillation does not remove the need for training data; it shifts it. A smaller student model copies a larger teacher, so it inherits the teacher's knowledge and gaps. New capabilities still require novel, high-quality real records the teacher never saw, which keeps demand for licensed business data.

No. Annual recurring revenue covers contracted revenue expected to repeat, and a one-time data license payment does not. Report it on a separate non-recurring line, keep ARR, growth and retention figures unchanged, and check investor and lender definitions before the cash arrives.

It depends on the purchase agreement. Whether one-time revenue such as a data license counts toward an earnout turns on how the agreement defines the metric, which accounting principles it adopts and whether it excludes non-recurring items. Buyer and seller should agree the treatment in writing before signing, with counsel and accountants involved.

It depends on the credit agreement, not on GAAP. Covenant tests use a defined term such as Consolidated EBITDA, and some definitions exclude non-recurring, extraordinary or unusual gains while others are silent. Read the definition, confirm when the license revenue is recognized, and get the lender's treatment in writing before counting one-time license income toward a ratio.

One-time revenue, such as a data license fee, should not drive a software company's headline Rule of 40. The metric is meant to show repeatable growth plus profitability, and a non-recurring license inflates both in the year it lands, then drags next year's growth. Report the clean score on recurring revenue and show the license in a labeled bridge.

Whether one-time revenue counts toward a management incentive plan depends on the plan's own definitions. EBITDA-based vesting usually uses a defined, adjusted EBITDA that may exclude non-recurring items, and boards often have discretion to adjust targets. Return-based vesting tied to MOIC or IRR captures cash the sponsor actually receives. Read the plan before assuming anything.

Often, yes. Voluntarily sharing privileged communications with someone outside the attorney-client relationship can waive privilege, and the waiver may not stay limited to the documents shared. Rules differ by court and jurisdiction, so the safe default in data licensing is to leave legal advice, counsel threads and outside-counsel files out of scope entirely.

Software development can qualify for the federal research credit under Internal Revenue Code section 41 when the work aims to improve a product's function or performance, relies on computer science, starts with technical uncertainty and resolves it through experimentation. Internal-use software faces a stricter test. Tickets, pull requests, design documents and commit histories are the usual evidence.

Assume it does. The AICPA Code's commissions and referral fees rule reaches CPAs in public practice, not members in business. A CPA serving several companies as a fractional CFO while holding out as a CPA looks like public practice; a CPA employed full time by one company does not. Your state board's rules are a separate check either way.

Usually not, but it depends on the facts. The federal Anti-Kickback Statute targets payments that induce or reward referrals of items or services paid for by federal health care programs. Introducing a healthcare administration company to license non-PHI operational records is a commercial data license, not that kind of referral, though compliance teams will still check.

The CCPA applies to a for-profit business that does business in California and meets any one of three tests: gross annual revenue of $26,625,000 or more (as adjusted from January 1, 2025), buying, selling or sharing data on one hundred thousand or more California residents or households, or earning half its revenue from selling or sharing personal information.

Generally not directly. The EU AI Act places obligations on providers and deployers of AI systems, not on a US company that licenses its business records to a developer. Buyers may still ask suppliers about data origin and rights to support their own duties. Application dates have changed, so verify them in the consolidated text.

The federal M&A broker exemption does not preempt state law. It addresses SEC registration under the Exchange Act, while state securities regulators apply their own rules, so an M&A advisor must check the home state and each client state. A data licensing introduction is not an ownership transfer and is assessed separately.

A success fee applies to a data licensing deal only if the engagement letter's Transaction definition and fee base reach a license. Letters tied to a sale, merger or change of control usually leave a license outside; broad wording covering licenses, asset transfers or any transaction may not. Read the definition, fee base, tail and exclusivity before introducing a client.

It depends on the signed partner agreement and the published terms, not on a general rule. Check the attribution, assignment and successor language before you rely on any credit. Attribution is tied to a verified company application, and rewards are payable only after the buyer pays and SourceX receives its fee.

A DOT compliance consultant can introduce a fleet with 50+ full-time employees at peak to SourceX, but driver qualification files, MVRs and drug and alcohol testing records are regulated personal data and stay out. Safety-program, maintenance and dispatch records the carrier wrote itself may fit. The consultant shares fit information only.

A double opt-in introduction gets consent from each side before connecting them. For a SourceX referral, send three short emails: a permission ask to the owner, a forwardable blurb the owner can share internally, and a final introduction after they say yes. SourceX learns the company's name only once the owner has agreed.

Funds create distributions without a full exit through dividend recapitalizations, partial or minority stake sales, continuation vehicles, NAV-based financing and sales of non-core assets. Data licensing is a smaller, slower lever: the one-time payment goes to the portfolio company, arrives only after a buyer pays, and reaches LPs only if the company then distributes it.

Driver-based forecasting links a few operating drivers, such as tickets per customer or hours per project, to financial outputs. Tracing each driver to its source system and years of history gives a metadata-only map that also answers SourceX's fit questions about system breadth and record depth, without exporting records.

Add a records-and-rights section to your acquisition diligence: list every system, check archive depth, confirm who created the content, and read customer contracts for data limits. These checks show what you will own after closing and whether the company could license its operating history.

Vet an AI data buyer on five fronts: who the contracting entity is, what it may do with the records, how it secures and deletes them, whether it can pass them on, and how and when you are paid. Put every answer in the signed agreement, not in a sales call.