Search guides, questions and resources

Founder retirement can prompt a review of operating archives and decision-making authority. A founder’s personal access does not itself establish permission to license company records. The introduction needs a current authorized sponsor.

A helpdesk migration can prompt a review of support archives and knowledge bases. These records may include personal, confidential or third-party information. Share broad context only and leave assessment and permissions with the company and SourceX.

A restructuring may reveal company-controlled archives, but approval authority and rights must be clarified first. Do not present a possible data license as assured funding or a substitute for professional restructuring advice.

Software consolidation can reveal operating records spread across current and legacy tools. A useful introduction describes systems and history without exporting records. Consolidation is not a reason to combine sensitive data or expand access.

Acquisition integration can surface inherited operating archives and changing access responsibilities. First establish who controls the records and who can approve an introduction. Acquisition alone does not establish licensing rights or buyer demand.

An email migration can reveal operating history, but mailboxes may contain personal, privileged or third-party information. Introduce an authorized company contact without sharing messages. Migration access does not establish a right to license email content.

An ERP replacement can surface finance, procurement and operations histories that may merit assessment. Their presence does not prove buyer demand or licensing eligibility. Start with an authorized contact and a system-level description.

Most companies need both, for different jobs. The company's own lawyer advises on rights and privacy, negotiates and approves the license agreement. A data licensing platform such as SourceX qualifies the company, runs the data inventory, brings AI buyers, coordinates delivery and collects payment, with its fee included in one all-in price.

SourceX referral payouts are a share of the fees SourceX collects from successful data licensing deals. You can use our editable template to see how the reward rate and cap apply to hypothetical scenarios.

Data licensing grants defined rights to use data for a fee, with scope, term and ownership written down. Data sharing usually gives a partner access for a joint purpose, often unpaid and loosely scoped. For AI training, licensing is the paid, controlled model that buyers and SourceX use.

Data lineage traces how data moves and changes between systems, from source through each transformation to its final output. Data provenance records where data originally came from, who created it, when, and on what rights basis. In AI data licensing, provenance decides whether data can be licensed at all; lineage shows what was done to it before delivery.

Data mapping for privacy compliance means recording every system that holds personal information, the categories inside it, its owner, its purpose and how long data is kept. Add two columns, years of history and export route, and the same map covers most of the data inventory a company completes before licensing records through SourceX.

A data marketplace listing suits a finished, repeatable dataset; managed data licensing suits operational archives where scope, redaction and rights must be negotiated. With SourceX's managed route, the company keeps ownership, agrees one all-in price, and signs only when terms work. Most operating companies fall in the second group.

A data monetization consultant sells advice for a retainer or project fee whether or not a deal follows; a success-fee licensing platform like SourceX earns its fee, included in one all-in price, only when a license closes and is paid. Consultants suit strategy; platforms suit companies that already hold licensable records.

Data monetization consulting usually focuses on internal analytics, pricing and data products sold to customers. Licensing operational records to AI developers is a separate route with its own rights review, buyers and contracts. Consultants can keep advising on the first two and refer suitable US clients to SourceX, which manages licensing from rights review to delivery and payment.

PE portfolio companies can monetize data three ways: build a recurring data product, sell analytics or benchmarking services, or license historical operational records for AI training. Licensing needs no product build or new sales team and pays once for an exclusive term, so it suits companies with deep records and no appetite to become a data business.

Data monetization in 2026 follows three trend lines: using data inside products and operations, sharing it under privacy-preserving controls, and licensing records directly to AI developers for training and evaluation. The third suits mid-size US operating companies with deep, rights-clear records; SourceX manages that licensing, and referral partners make the introduction.

A data opportunity handoff checklist for acquisition integration should include verifying the target company's profile against SourceX's baseline, confirming licensing rights and data types, and identifying an authorized sponsor. This ensures potential data assets are ready for AI licensing without handling company data directly.

An effective data opportunity handoff checklist for annual client reviews includes verifying the company profile against SourceX baselines, confirming data licensing rights, identifying an authorized sponsor, and documenting archive types. It also emphasizes that partners never handle sensitive company data directly.

A data opportunity handoff checklist ensures the referred company meets SourceX's baseline criteria for data licensing, covering company profile, licensing rights, and authorized sponsorship. This streamlined process helps M&A advisors identify viable opportunities for their clients.

A data opportunity handoff checklist for portfolio reviews should confirm the company meets SourceX's baseline, possesses licensing rights, has an authorized sponsor, and clarifies the data archive types available. It's crucial that partners never handle or transfer company data directly.

For restructuring advisors, a data opportunity handoff checklist should cover the company's baseline eligibility, confirmation of data licensing rights, and identification of an authorized sponsor and relevant data archives. This ensures the company meets SourceX's criteria for data licensing.

When identifying data licensing opportunities during software consolidations, a handoff checklist should cover company eligibility against SourceX's baseline, data licensing rights, types of archives, and the presence of an authorized sponsor. This ensures a smooth referral without handling sensitive company data.

This checklist helps identify and prepare valuable data assets from a winding-down company for potential licensing. It ensures all SourceX partner referral criteria are met before introduction.

A data opportunity handoff checklist for a helpdesk migration should cover the referred company's profile against SourceX's baseline, confirm licensing rights, identify an authorized sponsor, and detail archive types. Partners never handle company data directly.

A data owner is accountable for a data set and its use, a custodian runs the systems that store it, and a steward maintains its quality and definitions. Only the company's authorized sponsor, such as the owner, CEO, CFO or an authorized representative, can approve a license. IT custodians and admins cannot.

US data privacy law is sectoral, so the rule that matters depends on the industry: HIPAA for health data, the Gramm-Leach-Bliley Act for financial customer information, state laws such as the CCPA for consumer data, and wiretap rules for call recordings. Partners should flag regimes early and leave rights review to the company and SourceX.

A data processing agreement (DPA) limits what a company may do with customer data it handles, so owners should review purpose, confidentiality, sub-processing, deletion and audit clauses with counsel before any records containing customer data are put in scope for a SourceX data license. Company-created records usually face fewer limits.

A data processing agreement governs how a vendor handles data on a company's behalf; a data license agreement grants another party rights to use the company's data for stated purposes and a term, usually for payment. They are separate contracts with different reviewers, and a DPA does not create or replace licensing rights.

Data quality due diligence tests whether a target's records are complete, deep in history, linked across systems and exportable. Use the CHLE test on each core system: Completeness, History, Linkage, Exportability. Failing two or more tests means a remediation plan, an integration cost or a price conversation.

Yes, this worksheet provides a structured approach for professional consulting firms to screen potential data licensing referrals against SourceX's core criteria. It helps identify suitable US companies with 50+ employees, robust records, and licensing authority.

Yes, this worksheet provides a structured approach for staffing and recruiting firms to screen potential data referral candidates against SourceX's core eligibility criteria. It helps identify US companies with the right characteristics to license their valuable data.

Before selling a business, do not delete old systems, shared drives or tool histories until counsel has cleared legal holds and retention rules and someone has assessed what the records are worth. Years of email, tickets, CRM activity and project files can support a buyer's diligence and, for qualifying companies, a separate data license.

A data retention policy template sets how long each class of company records is kept, who owns it, how legal holds pause deletion and how records are destroyed. This version adds a pre-disposal value review, so a mid-sized company checks holds, privacy promises, archive cost and possible licensing value before deleting old systems or mailboxes.

Data rights due diligence tests whether a company owns its records and may use them as an acquirer or licensee intends. Cover six areas: who created the material, customer contract terms, third-party content, what employees and callers were told, regulated data, and existing licenses. The same review prepares a company to license.

A data room for selling a business should hold corporate, financial, tax, commercial, employee, IP, IT, privacy, property and litigation documents, indexed by folder and released by bid stage. Alongside it, build a separate records map: a metadata-only list of operating systems and years of history that shows whether the company holds licensable data, without exposing it.

A data room index organizes the documents a buyer of the company reviews in diligence. A data licensing inventory describes, as metadata only, which systems hold records, over what years, with what rights and export options, for AI labs and data buyers considering a license. Use each for its own counterparty and keep them separate unless counsel approves.

Data synergies in M&A are gains from combining two companies' records. Operational synergies improve the business itself, while licensing value comes from granting AI developers rights to pre-acquisition records. Licensing needs separate tests for records, rights, consents and authority, and belongs outside the base-case synergy model.

A Day 1 readiness plan should block irreversible actions on the acquired company's legacy systems and defer every licensing decision. Integration leads can add a one-line hold with a review date, run a short records inventory in the first 60 to 90 days, then decide system by system.

De minimis asset sale procedures are case-specific chapter 11 orders that let a debtor sell lower-value assets on short written notice instead of filing a separate motion each time, usually with value tiers and liens attaching to proceeds. A records license fits only if the order reaches licenses, the price sits within a tier and no exclusion applies.

De-identify free text under HIPAA by classifying sources, excluding patient-facing queues, running entity detection, replacing identifiers consistently, reviewing samples by hand, and choosing Safe Harbor or Expert Determination. Free text fails quietly because identifiers hide in sentences. SourceX agrees redaction requirements with the company before any work begins.

The most common deal killers in due diligence are earnings that do not hold up, customer concentration or churn, undisclosed liabilities, owner dependence, and records problems: unclear code or IP ownership, missing contracts, deleted archives and privacy consent gaps. The records problems matter twice, because they also decide whether a company can ever license its data.

In a holding company, the legal entity that holds the records and rights signs through an authorized officer, and parent or investor approvals sit above it. In decentralized holdcos the subsidiary president may need parent sign-off for an exclusive contract, so confirm the documents before introducing anyone.

Section 280 is Delaware's court-supervised dissolution route: the company gives notice to claimants, bars late claims and asks the Court of Chancery to set reserves. Section 281(b) is the default: the board adopts its own plan of distribution providing for known, pending and likely future claims. If records may still be licensed, raise it before either is fixed.

A delegation of authority matrix lists each type of decision, who may initiate, review and approve it, up to what limit, and when the board or owners must consent. Use this template to add a row for licensing company records, so everyone knows which sponsor can authorize a SourceX review and which terms need board sign-off.

A data delivery manifest is a one-page-per-delivery record the licensing company keeps, listing what was handed over: systems, date ranges, file counts, checksums, exclusions applied, delivery method, recipient and date. It lets the company prove later exactly what was delivered and what was withheld.

Under DGCL section 278, a dissolved Delaware corporation continues as a body corporate for three years after dissolution, or longer if the Court of Chancery directs, to settle its affairs: suing and being sued, disposing of property, paying liabilities and distributing assets. It cannot continue its business. A properly authorized one-time records license may fit that window.

Section 279 of the Delaware General Corporation Law lets the Court of Chancery appoint trustees or receivers to wind up a dissolved corporation, including when assets remain. If a long-closed Delaware company still holds archives, that appointment can supply the authority needed before anyone introduces it to SourceX.