Skip to content
Data Deal Guide.Real Info. Trust. Independent.

Guide

Before you contact a provider

Prepare answers at a high level. You shouldn’t need to share any data to have a first conversation.

  1. 01

    Which systems hold relevant records

    CRM, help desk, ERP, project tools, shared drives. A list of systems is enough — no exports.

  2. 02

    Approximate history and volume

    Years of records and rough size. Ranges are fine at this stage.

  3. 03

    Whether you own or can license it

    Some material may belong to customers, partners or vendors, or be covered by their terms.

  4. 04

    Whether records include people’s information

    Customer, employee, patient, partner or client details raise extra obligations and may need removal or consent.

  5. 05

    Whether contracts or privacy notices limit reuse

    Customer agreements, NDAs and published privacy notices can restrict new uses of data.

  6. 06

    One-time payment or repeat licensing

    Decide whether you prefer an upfront sale, recurring license or revenue share — and whether you’d accept exclusivity.

  7. 07

    Which uses you’ll consider

    Training, post-training, evaluation, retrieval — and whether resale or sublicensing is acceptable.

What makes operational data valuable?

Polyshares argues that multi-year records showing how work unfolds — decisions, failures, corrections and outcomes — can matter more to AI buyers than sheer document volume. That is one provider’s view, not a universal pricing rule or a promise of buyer demand.

  • Look for connected workflows: identify records that link a task or decision to its revisions and eventual outcome, rather than counting disconnected files.
  • Describe the domain and provenance: note the specialized business work represented, where records came from, their time span and any gaps. Start with a high-level description, not an export.
  • Clear the rights first: check employee, customer, client and third-party restrictions with counsel. Possessing a record does not necessarily give you permission to license it.
  • Review privacy and confidentiality: ask how de-identification is checked and what sensitive business or client information may remain. Removing names does not automatically resolve privacy risk or confidentiality obligations.

Provider perspective: Polyshares — How much is company data worth? (opens in new tab) · Polyshares — Data licensing (opens in new tab)

Your data inventory

Assess your data before asking for a price

Turn the high-level answers above into a system-by-system inventory. Keep actual messages, files and identifying details out of the first conversation.

Map the systems and one complete episode

List Gmail or Microsoft email, Slack or Teams, CRM, shared drives, ticketing and call recordings. Note which records connect across apps: a support request arrives by email, is discussed in chat, links to a CRM account and ticket, then ends in a documented resolution. Describe that sequence without including a real customer’s details. Linked records may make decisions and outcomes easier to interpret than disconnected single-tool collections; there is no independently established price multiple.

Date the usable history, not the business

For each system, record the oldest continuous date you can actually retrieve, the approximate volume and any migration gaps, missing attachments, changed identifiers or deleted periods. A company founded ten years ago may have only two years of continuous email since a migration. Separate older fragments from an uninterrupted record; buyers’ history requirements vary.

Check what still identifies people or clients

Stable pseudonyms can link the same person or account across records without displaying their name, but they are not guaranteed anonymous or safe: context and cross-system links can still identify someone. Review raw records, employee/customer/client data, confidentiality duties, trade secrets and who can access each stage. Confirm licensing rights and the treatment of linking keys, not just the removal of obvious identifiers.

Agree how records leave each system

Some providers accept customer-prepared exports; others ask for a connector or account access. One practitioner describes a broker handling pseudonymization and exports without shared logins, but that is provider-specific, not a promise for every buyer or a waiver of rights. Prefer scope-limited exports where practical. Otherwise agree the exact permissions, date range, who extracts and reviews the records, secure transfer, access controls and when access is revoked. Do not hand over unrestricted credentials.

Review what exclusivity ties up

Compare a time-limited license with a perpetual one: which records, uses and recipients are exclusive, for how long, and what happens at expiry or termination? Ask what rights survive in trained models and derivatives and whether future licensing is restricted. Document restrictions for diligence in a future business sale. Perpetual exclusivity deserves extra counsel review because obligations may outlast the current deal; no single duration, including 24 months, is a universal standard.

Inspired by an Oct 15, 2026 practitioner post by Troy (@troyaitken_ (opens in new tab)) on X; pricing and process assertions vary by buyer and were not independently verified.

Download blank CSV worksheet

No account or upload. Keep your inventory privately; nothing you enter in the downloaded worksheet is sent to Data Deal Guide. Use rough counts and concern categories, not confidential text or personal details.

Diligence checklist

Questions to settle before you sign

Use these as prompts for your own review and for questions to the provider. What applies depends on your data, contracts and jurisdiction.

How buyer diligence and deal terms work

  • An introduction starts the review: a buyer still needs to assess licensing authority, data quality and technical usefulness. In the workflow example above, describe rejected fixes and why the final resolution worked—not only the successful outcome. Keep actual records private until rights, access and review scope are agreed.
  • Clarify roles and conflicts: ask whether the provider is the buyer, an intermediary or a seller’s adviser, who represents whom, and who pays each party. Request disclosure of finder fees, advisory fees and conflicts. A speaker’s suggestion to add advisory services to referrals is not approval for fee stacking or client-agency arrangements; have counsel review authority and compensation terms.
  • Confirm today’s buyer brief: Corey Ganim’s recap of the Oct 9, 2026 Ryan Lock interview describes prospecting for U.S., English-language firms with 50+ employees and 3+ continuous years on the same software, with remote-first knowledge work particularly legible to buyers. Those are anecdotal prospecting preferences, not blanket eligibility rules. Other buyers consider field or industrial video and physical operations. Sector requests can change quickly; ask which categories and workflows are actually sought now.
  • Make handling commitments specific: identify the de-identification processor and any subprocessors, who holds linking keys, and how stable pseudonyms could allow re-identification. Agree the exact raw-file retention period, backup treatment and evidence of deletion. The interview’s roughly one-week handling assertion is not a verified deletion commitment or a substitute for written terms.

Context: owner-supplied screenshot transcription of Corey Ganim’s X recap (opens in new tab) of the Oct 9, 2026 Build With AI interview with Ryan Lock; the X post was not independently fetched. Episode listings: Podscan (opens in new tab) · Castbox (opens in new tab). Listings establish episode context, not verification of the speakers’ claims. Pricing, retention, exclusivity and demand assertions are unverified; this is separate from Troy’s guidance above.

Rights and authority

  • Employee and contractor records: what your policies and agreements permit
  • Customer records: what contracts and privacy notices allow
  • Third-party material (vendors, partners, licensed content) you may not control
  • Who in your company can authorize the deal

Scope, uses and term

  • Exactly which datasets, systems and date ranges are included
  • Permitted uses (training, evaluation, retrieval) and any excluded uses
  • Exclusivity, duration and renewal
  • Onward recipients, resale or sublicensing, and geography

De-identification

  • Method used, who performs it, and whether you can review it
  • Residual re-identification risk
  • Confidential business information that survives de-identification

Security and data lifecycle

  • Security controls, access limits and subprocessors
  • Retention period and deletion on request or at term end
  • Treatment of derived data and trained model weights

Money and remedies

  • Payment formula and what triggers payment
  • Reporting and audit rights
  • Indemnities, termination rights and remedies for breach

This guide is not legal advice and offers no legal conclusions. Have counsel review your rights to the data and any contract terms before you share anything.

Compare providers