Search guides, questions and resources

Upfront cash at closing is the most certain payment in a business sale; earnouts and seller notes defer part of the price and tie it to future performance or the buyer's credit. A license of the company's operational records is a separate transaction: paid once, outside the sale price, with ownership retained. Not every company qualifies for one.

Yes, this worksheet provides a practical checklist for e-commerce consultants to screen potential referral companies based on SourceX's eligibility criteria. It helps identify US-based e-commerce businesses that are good candidates for data licensing.

ECPA combines the Wiretap Act, which restricts intercepting communications, and the Stored Communications Act, which covers stored messages. Employers can often access systems they own, but disclosing archives to a licensee is a separate question governed by notices, state law and contracts, so counsel should review before any email or chat records are licensed.

An EHS consultant can introduce a manufacturer to SourceX when it has 50+ full-time employees at peak and years of exportable audits, root-cause analyses and corrective actions. Injured-worker medical details and OSHA privacy-case entries are excluded, and the consultant never handles the records.

An electronic communications policy tells employees that company email, chat, phone and file systems, and the work created in them, belong to the company; that those systems may be monitored; how personal use is limited; and which secondary uses, such as de-identified analytics or licensing, may apply. Counsel should adapt the clauses and apply them going forward.

Email archive migration forces a decision about years of journaled mail before the old archiver's contract ends. An MSP or migration consultant can use that moment to ask the owner whether the history should be assessed for a SourceX data licensing introduction, before anything is deleted or moved.

A data opportunity handoff checklist for an email platform migration should include verifying the company meets SourceX's baseline criteria, possesses clear licensing rights, has an authorized sponsor, and identifies relevant data types like archive email.

A portfolio CFO can raise data licensing with the CEO in two short paragraphs: describe licensing operational records to AI developers for a one-time payment, then ask to run a metadata-only fit screen, with the sponsor copied and no proceeds modeled. The CFO can also act as the company's authorized sponsor if the CEO agrees.

Wind down advisors should use a short, neutral email to introduce the potential for data licensing, emphasizing the client's control over the process and avoiding any promises about income or timelines. The template provided guides this initial communication to ensure clarity and manage expectations.

A search fund investor email to portfolio CEOs should be short, opt-in and factual: explain that some companies license operational records to AI developers for a one-time payment, name the basic fit criteria, link the company fit checker, disclose your referral interest, and ask for a yes or no reply, with no confidential detail or payout promises.

To email a client about AI data licensing news, link one dated public story, state it neutrally, then add the SourceX baseline: a US company with 50+ full-time employees at peak, contractors excluded, that keeps ownership and decides everything. The three templates below cover a monthly contact, an owner weighing an exit and a follow-up.

This template gives a company a fill-in employee announcement and a ten-question FAQ for licensing historical records to AI developers. It states what is and is not included, how identifiers are handled, how to raise concerns and request exclusion, and avoids promises the company cannot keep. Have counsel review it before sending.

A California employee privacy notice tells applicants, employees and contractors, at or before collection, which categories of personal information the company collects, why, whether it is sold or shared, and how long each category is kept. The outline below gives counsel starting text for each clause, including how de-identified business records may be licensed.

A company can sometimes license recordings containing employee voices, but state right-of-publicity and voice laws, employee notices and consent all affect the answer. Many deals deliver transcripts instead of audio, and licenses typically ban voice cloning and speaker identification. Company counsel should check each state where speakers live or work.

For multi-terabyte records, encrypted drives suit one-time, fixed snapshots and slow connections, while seller-hosted access suits datasets the company wants to keep in its own environment under its own logs. SourceX never hosts multi-terabyte datasets, so the handover method is agreed with the company and recorded.

An end-of-life notice template should state four dates (last sale, end of support, shutdown, export deadline), the customer impact, the migration path and the data retention terms. Pair it with an internal records plan so tickets, engineering history and decisions are exported before systems are retired.

An engagement letter disclosure clause tells a client in writing, before any introduction, that the advisor may be paid by a provider the client is referred to, who pays, how the amount is calculated and that the client can decline. Pair a standing clause with a one-off notice for each specific introduction, after checking your professional rules.

Yes, this worksheet provides a structured approach for engineering and design advisors to pre-qualify potential referrals against SourceX's core requirements. It covers company size, operational history, data rights, and sponsorship.

Engineering firm succession planning usually runs through a key-employee buy-in, an ESOP, a sale to a larger firm or a merger, with state licensing and client concentration shaping each. A firm's project histories may be valued records, but client IP and contract terms must be checked before any licensing review.

Enterprise AI data licensing deals are private agreements in which operating companies license internal records, such as support tickets, CRM history and email, to AI developers. Unlike the publisher and platform deals reported in the press, their terms are rarely disclosed, so advisors should treat headline figures as evidence of demand, not as a price guide.

EO suits founders and owners who want a network of fellow entrepreneurs built around small peer forums. YPO suits chief executives whose companies meet its published size tests. Vistage suits CEOs and senior leaders who want a chair-led peer advisory group with one-to-one coaching. Each organization publishes and updates its own criteria, so confirm them directly.

In an EOS annual planning agenda, a data asset question fits as a single Issues List item, handled through IDS like any other issue. Implementers should word it neutrally, run a three-question intro test, disclose any partner arrangement up front, and leave the final decision with the leadership team.

In a data licensing project the EOS Integrator typically sponsors the work: naming a steward, running the records inventory, coordinating rights review and keeping the weekly cadence. The Visionary, owner or another authorized representative still decides on exclusivity, approves price and terms, and signs. Nothing is binding until the company signs.

A well-formed EOS Rock for exploring a data license has one owner, a measurable result and a date inside the quarter, such as a metadata-only systems inventory plus a go or no-go recommendation by week 12. It explores a SourceX fit check; it does not commit the company to any license.

Sponsors can screen equipment finance and non-bank lenders for licensable credit approvals, collections workflows and servicing records. Confirm 50+ full-time employees at peak, several years of linked history, clear rights and guarantor privacy handling, then introduce the company to SourceX, which handles inventory, buyer review, contracting and delivery.

Exporting CRM or ERP data for a license is safe when it happens late, narrowly and under the company's control: only after an executed agreement, by the company's own admins, within an agreed scope and redaction plan, through routes the software vendor's terms allow. The consultant who made the introduction should never run, receive or store the export.

When consolidating ERPs after acquisitions, most teams migrate opening balances, open transactions and a short window of detail, then retire the acquired system. Before retirement, keep a complete, queryable archive of transaction detail and the workflow trail around it: approvals, match exceptions, credit holds, memos and change logs, none of which the trial balance shows.

When a PE portfolio consolidates add-ons onto one ERP, several legacy systems retire at once and their history usually migrates only in part. Operating partners should screen each entity's archive before decommission, confirming years of records, export access, rights and an authorized sponsor, then introduce qualifying companies to SourceX for a data licensing assessment.

An ERP data cleansing checklist should separate master-data cleanup (duplicates, inactive vendors, item codes) from transaction-history deletion. Clean and merge master data, but keep or archive closed invoices, journals and attachments, because that connected history is what auditors, lenders and potential data licensing buyers value.

An ERP discovery questionnaire should cover entities, go-live year, legacy systems, migration scope, archive and export plans, and approvals. This copy-ready template covers all of that and adds two closing questions that show whether the client's records could suit a SourceX data licensing introduction.

An ERP go-live checklist confirms readiness, UAT sign-off, data migration reconciliation, the cutover runbook, go/no-go criteria and hypercare support. Add one step most plans skip: before cutover, inventory the test logs, issue logs, decision logs and legacy system history, and agree how long the old system stays readable, because those records may later have licensing value.

Implementation MSAs and SOWs usually treat client business information as confidential, so an ERP consultant making a SourceX introduction should share only basic fit information, and only with the client's permission. Never share records, configurations or project documents. This is general information; confirm with counsel.

An ERP vendor referral fee pays on a software sale under that vendor's terms. A SourceX data licensing referral reward pays {{rate}} of the platform fees SourceX collects when a client licenses its historical records, subject to a {{cap}} cap per company and payable once the buyer has paid. They reward different events, so one ERP consultant can hold both.

For an ERP replacement, a data opportunity handoff checklist should cover the company's profile against SourceX's baseline, confirm licensing rights, identify an authorized sponsor, and note the types of data archives. Partners never handle company data directly.

For a retiring owner, an ESOP favors continuity and staged payment, while a third-party sale favors liquidity and a clean break. Either way, a data licensing decision is simpler before the ESOP trustee or a buyer is involved, because one authorized owner can still decide and the systems still run.

If a referral payment arrives with no tax withheld, you may owe estimated tax for the period you receive it. Set aside your top federal rate, plus self-employment tax if it is business income, plus state tax. Then pay for that period or raise wage withholding, and use the annualized income method so earlier periods are not penalized.

In client conversations about potential SourceX referral earnings, focus on understanding their data licensing needs and clarifying SourceX's role. Frame earnings as illustrative, contingent on SourceX fees, and always emphasize the referred company's ultimate control over the scope and approval process.

Article 10 of the EU AI Act requires providers of high-risk AI systems to apply documented data governance, with relevant, representative datasets and bias examination. The duty is the buyer's, but US data suppliers are asked for provenance, preparation logs, coverage and known gaps to support it. Counsel should read the current consolidated text.

The EU AI Act training data summary is a public document that general-purpose AI model providers must publish, using a Commission template, and licensed datasets are one section of it. The duty is the provider's, not the supplier's, but buyers may ask you for provenance, rights and redaction details to describe your dataset.

An evaluation-only license is generally lower risk than a training license because the data is used to test models rather than shape them, so less of it needs to persist inside a model. It usually carries narrower value and different terms, and whether a buyer will accept it is a matter to discuss, not assume.

Exception handling records are the logged cases where a process failed, with who decided, what they decided and why. AI agents handle routine cases and escalate exceptions, so these dispositions and reasons are scarce training material. Operating partners can scan portfolio companies for them and introduce qualifying businesses to SourceX.

Excluded assets are the items an asset purchase agreement expressly leaves with the seller, such as cash, tax refunds, corporate records and named contracts. Data can be excluded too, or the seller can keep copies or take a license-back, but only if the point is negotiated before the APA is drafted and its asset definitions are fixed.

In an asset purchase, records the buyer does not take, often historical email, archives and closed-file history, stay with the seller entity as excluded assets. If the seller keeps the rights and the data, and someone can still sign for it, those records may be licensable through SourceX after closing, producing additional proceeds for the seller entity.

An exclusive data license runs for a term the company and buyer agree in the contract, and the company keeps ownership throughout. There is no standard length. Term licenses end or renew as written, while perpetual ones have no end date, so owners should weigh flexibility and confirm every clause with counsel.

An exclusive data license gives one licensee the licensed rights, such as AI training, for an agreed term and stops the owner granting the same rights to anyone else; a non-exclusive license lets the owner license the same records to many buyers. SourceX deals are typically exclusive for AI training for an agreed term, and the company keeps ownership.

A non-exclusive referral agreement leaves an advisor free to recommend other providers; an exclusive one ties the advisor to one provider, or the provider to one partner, usually in exchange for protection or extra support. Most independent advisors keep the freedom to recommend, because their duty runs to the client. Each program's terms say which applies.

An exit planner introduction email about data licensing should be short, owner-controlled and free of client detail: one idea, one link, no promised outcome. Three templates below cover a follow-up after a meeting, a client mid-transition and a note to a co-advisor, with personalization rules and follow-up timing.

Exit planners should disclose a referral reward in writing before the introduction, inside the engagement documents the owner already signs, and say plainly that the owner decides. A dated clause, a one-line note at introduction and a closing record show the owner was informed and free to decline.