Search guides, questions and resources

Cost segregation referral fees range from a white-label revenue share, where the CPA firm bills the client for a study a provider performs, to a one-time fee per completed study, and some providers pay nothing. Before accepting any of them, a CPA should check attest relationships, disclosure duties under the AICPA Code and state board rules.

Under ASC 340-40, costs to fulfill a contract become an asset only if they relate directly to an identified contract, create resources used to deliver it and are expected to be recovered. For a one-time data license, legal review and pre-signing work are expensed as incurred, while direct export and redaction costs usually reach the P&L at delivery.

Licensing company records can lead to a dispute, but the risk is concentrated in five places: employee privacy, customer contracts, third-party IP, regulated data and misstatements in the agreement. Each has a control and an owner, and your own counsel should review them before you sign.

Yes, a licensed dataset can point back to its supplier if identifiers such as client names, product names, distinctive projects and email domains are left in. Redaction choices are agreed with the company before any work begins, and buyers generally do not need the supplier's identity inside the training copy.

A covenant compliance certificate is a signed statement from a responsible officer to the lender confirming the borrower met its financial covenants for the period, with calculations attached. This template adds a schedule for non-recurring income so a possible data license is footnoted and checked against the agreement's definitions before anything is signed.

CPA commission and referral fee rules are set state by state: some boards adopt the AICPA's 1.520 rule by reference, as Kansas does, while others legislate their own, as Florida does by statute. Before accepting any referral reward, read the current rule in every state where you are licensed or serve the client, and record what you checked.

Before a CPA or firm joins a referral partner program, confirm which rules bind you (AICPA Code, every state board where you are licensed, firm policy), screen out attest clients, fix a written disclosure method, settle client consent and confidentiality, decide where compensation is booked, and read the program terms. Clear these before the first introduction.

CPA firms can use four short newsletter blurbs to explain data licensing to clients: an explainer, a year-end angle, a succession angle and a disclosure-first version. Each invites interested owners to reply to the firm. Check AICPA and state board rules on referral fees first.

A timely CPA firm client webinar topic is company data in the AI era: which operational records AI developers license, which businesses qualify, and the rights questions owners must settle first. This page gives a 40-minute outline, invitation and slide copy, a Q&A bank and a follow-up plan built to produce permissioned introductions, not cold leads.

A credit bid under section 363(k) lets a secured lender bid its allowed secured claim, instead of cash, for collateral sold in a section 363 sale, unless the court limits it for cause. Lenders use it to acquire IP and data collateral, then decide what to do with the records, subject to the sale order's privacy terms.

First-day critical vendor and section 366 utility motions are built around suppliers and utilities, yet SaaS, cloud and telecom providers often hold a debtor's email, files and call records. Debtor counsel should list those vendors before filing, choose the right relief for each and budget postpetition invoices so archives survive into the sale or wind-down.

In a CRM consolidation after an acquisition, move current accounts, contacts and open deals into the surviving instance, but export and archive the acquired CRM's full activity history first: logged emails, calls, meeting notes, tasks, stage changes and loss reasons. Migrations routinely drop that history, and years of it can be a licensable asset.

CRM data cleanup before migration should merge duplicates and delete junk but keep closed-lost deals, old activities and notes until someone assesses their value. Export everything with record IDs first, then run a short screen with the owner, because long deal histories are what AI data buyers look for.

Good CRM discovery questions cover how long the CRM has run, prior systems, deal stages and outcomes, activity and call capture, users and planned clean-ups. This template adds two closing questions that show whether the client's sales records could fit a SourceX data licensing review before any purge or migration.

A data opportunity handoff checklist for a CRM migration should verify the company against SourceX's baseline criteria, confirm data licensing rights, identify an authorized sponsor, and categorize data archive types. Partners never handle company data directly.

A chief restructuring officer can ask the board or lender group for approval of a metadata-only records assessment before systems are retired. The email states that nothing is sold or binding, excludes mainly personal data, and sets a decision date so exports can be preserved first.

A chief restructuring officer is an officer of the company with fiduciary duties and, in chapter 11, a court-approved retention; a turnaround consultant is an outside adviser engaged by contract; an interim CEO runs the business as its top executive. Officers and court-retained professionals face the tightest limits on accepting any referral reward.

A cross-border introduction email should confirm the referred company meets SourceX's baseline criteria, highlight their interest in licensing data, and mention the referrer's involvement. The handoff checklist ensures all critical information is shared for a smooth transition.

For cross-border M&A advisors, one of the best post-acquisition opportunities is the window between closing and system migration. While the acquirer moves the US company onto group email, CRM and ERP, the advisor can ask the US CEO to assess years of records first and, with the new owner's approval, introduce the company to SourceX.

Before joining a referral program from outside the US, confirm six things: professional rules, employer approval, who registers and gets paid, home-country tax and VAT or GST, lawful handling of contact details, and which US companies in your network could qualify. Rewards arrive only after the buyer pays and SourceX receives its fee, so early mistakes surface late.

Before signing an international referral agreement, check ten things: governing law and dispute forum, the payout trigger, attribution rules, reward currency and transfer costs, tax forms and any withholding, confidentiality, data protection for the contact details you share, anti-bribery and conflict duties, public-disclosure rules, and what survives termination.

In a CTO due diligence interview, buyers ask about architecture, repositories, engineering process, incidents, security, contractor IP, open source and AI coding tools, then test each answer against the data room. Prepare by pairing every likely question with a document or repository link. The same engineering history, such as pull requests, tickets and postmortems, is what AI developers license.

When a Delaware corporation's owners or directors deadlock, the Court of Chancery can appoint a custodian under DGCL section 226, and the appointment order then defines who can approve a data license. A custodian normally continues the business rather than liquidating it, so a significant license usually needs clear authority in the order or the court's approval.

Buyers discount customer concentration by lowering price, adding earnouts or escrow, or requiring customer consent. There is no universal threshold. Concentrated businesses also hold dense, customer-confidential records, which narrows what can be considered for an AI data license and makes a rights review of contracts essential.

Customer contract data use restrictions usually decide what a company can license. Before licensing records for AI training, counsel should read each customer agreement's definitions, confidentiality, data use, aggregated-data, ownership and return-or-destroy clauses, keep customer-owned information out of scope, and check privacy promises. The contract text controls, and this is general information, not legal advice.

Run a customer profitability analysis by taking revenue and direct cost from the ERP, adding cost to serve from CRM activity and support tickets, and ranking contribution margin by customer. The join also shows a fractional CFO how many systems and years a client keeps, a fit signal that stays inside the company.

A cyber insurance renewal questionnaire already asks about systems, backups, retention, cloud vendors and incident response, and some answers reveal years of well-kept operating records. Commercial brokers can note those signals, then raise a SourceX introduction with the owner in a separate conversation after binding, without using or sharing any underwriting information.

A cybersecurity due diligence checklist for M&A covers incident history, access control, authentication, backups, vendors and governance. Advisors use it before launch so sellers can answer buyer questions fast. The same controls decide whether records can be exported safely if the company later licenses them to AI developers.

In a PE roll-up of MSSP and MDR firms, the SIEM and SOAR platforms you retire hold years of triage history that a qualifying company may license. Screen for separable process records, then exclude client logs, CUI and CMMC-scoped work. Companies need 50+ full-time employees at peak and an authorized sponsor.

D&O tail or run-off coverage extends protection for claims made against directors and officers after a company closes, and defending those claims needs the company's records. Directors can keep originals for defense while a scoped SourceX license covers copies, once the insurer, counsel and any court or lender are told.

Data archiving keeps selected records for years in a searchable store, while backup keeps recent copies of whole systems so they can be restored after a failure. For retrieving or exporting old records, an archive is usually what makes it possible; most mature businesses need both, set up with separate retention rules.

Borrower records can fall within a secured lender's collateral, typically through an all-asset lien covering general intangibles, but their value depends on ownership, privacy promises and whether anyone can still export them. Because many credit agreements restrict exclusive licenses of collateral, a borrower usually needs lender consent before licensing records, which can turn a license into a negotiated paydown source.

In an assignment for the benefit of creditors, a company transfers its assets, including databases and system archives, to an assignee who holds them in trust and liquidates them for creditors. Subject to state law and the assignment document, the assignee can sell or license those data assets, but privacy promises, client contracts and system shutdowns limit what remains.

A data broker sells lists or profiles about individuals, often to many downstream buyers. AI data licensing grants AI developers defined rights to a company's own de-identified operational records for an agreed term. The company keeps ownership, approves scope and price, and signs before anything is delivered.

A data broker collects or buys data, often about people, and resells copies on its own terms; a data marketplace lists datasets so sellers and buyers can transact with limited platform involvement; a data transaction layer such as SourceX manages one company's licensing end to end, from rights review to delivery and payment, while the company keeps ownership.

A data inventory is what owners need first for data licensing: a metadata-only list of systems, years covered, owners and export routes. A data catalog and a data map are optional. Neither is required to start, and a spreadsheet is enough for a licensing-ready inventory.

A data controller decides why and how personal data is processed; a data processor handles it on the controller's behalf and only on its instructions. California's CCPA uses business and service provider for similar roles. For licensing, the line is decisive: records a company holds as a processor for its clients are generally not its own to license.

Data governance for a private equity portfolio company can start with four controls rather than a data office: a named owner for every system, a written retention schedule, quarterly admin access reviews and a rights register showing who created the records and what contracts allow. The same four documents are the base of a defensible data license.

A company can build a data inventory by interviewing each department head for 20 to 30 minutes about systems, start years, owners, rough volumes and export ability, never about record contents. The sponsor consolidates one list, flags rights questions and unknown archives, and shares it only after agreeing to proceed.

Data licensing earns money from records a company already has, paid as a one-time fee while the company keeps ownership. Data labeling sells human hours tagging a buyer's data. For an established company with years of operational records, licensing is the model SourceX supports, and it needs no annotation team.

A data license agreement grants another party rights to use data the licensor controls, usually for a fee and a defined purpose; a data sharing agreement sets rules for an exchange between independent parties; a DPA instructs a vendor how to process personal data for you. An AI training license is a rights grant, not a DPA.

A data license indemnification clause decides who pays when licensed records turn out to infringe someone's rights, break a privacy promise or leak. For a company licensing records to an AI developer, counsel should tie each indemnity to a specific warranty, cap it sensibly, match security duties to real controls and check how insurance responds.

A data license term sheet should state the dataset scope, exclusivity field and term, one all-in price, payment timing, de-identification duties, delivery method, deletion and return, and liability. Owners should confirm each in writing and have counsel review. With SourceX, nothing is binding until the company agrees price and terms and signs.

An NDA keeps information confidential while parties evaluate a deal; it does not give anyone the right to use a dataset. A data license agreement defines permitted use, term, exclusivity and payment after signing. In a SourceX process, early talks use metadata only and nothing is delivered before an executed agreement.

A foreign buyer's due diligence on a US target should be expected to ask whether the company has licensed records for AI training, to whom, on what exclusivity and for how long, what was delivered, whether personal data was involved and how the payment was booked. Sell-side advisers should have the agreement, inventory, delivery record and rights analysis ready.

This template helps fractional COOs introduce clients to potential data licensing opportunities without making specific financial or timeline promises. It emphasizes the client's control over the process and the nature of SourceX's services.

Management consultants can use a neutral email to introduce their clients to SourceX, focusing on the opportunity to license data and maintaining the client's control over the process. This template helps explain the potential without making specific promises about income or timelines.

A CRM migration can surface sales and customer workflow histories. Migration access is not licensing permission. The company must approve any assessment and resolve rights and privacy questions before records can be considered.