SellYourAIData.com
Get started Contact
METHODOLOGY

Useful numbers need context.

How market information should be collected and presented.

Build an evidence trail
  1. 01
    Locate the sourceClaim and date
  2. 02
    Describe the scopeUnit and terms
  3. 03
    Identify the eventStage and limitations
Illustrative workflow
AN EVIDENCE TRAIL

A number is only useful with its context.

Use the same sequence for every reported transaction. Keep different pricing units and transaction stages separate.

  1. 01

    Locate the source

    Keep the public record URL or permissioned evidence, its date and who supplied it.

  2. 02

    Describe the scope

    Record category, volume, unit, history and the preparation included.

  3. 03

    Identify the event

    Separate an indication of interest, an offer, a signed agreement and completed payment.

  4. 04

    Preserve the terms

    Record exclusivity, duration, permitted use and conditions that affect the number.

  5. 05

    Apply the right label

    Source-backed information needs its citation and date. A report awaits review. An illustration explains a concept.

What this site currently shows

The market examples are illustrative. A downloaded deal report is a local draft, not a reviewed or published transaction record.

01SOURCE FIRST

Keep the evidence attached to the claim

A useful market record begins with the source rather than the number. Identify the public document, announcement, or permissioned evidence supporting the claim, and record when it was published or obtained. Explain who supplied the information and what the source actually establishes. A secondhand summary can be a research lead, but it should not silently become equivalent to the underlying transaction evidence.

Keep a direct connection between each claim and its supporting material. If the source establishes a signed agreement but does not disclose payment completion, record the agreement without adding the payment claim. If it mentions a broad partnership without isolating a dataset price, do not invent an allocation. Where a detail is unavailable, preserve that absence instead of manufacturing a precise benchmark from incomplete information.

Keep claims attached to evidence
SOURCEOriginal recordDate retained
CLAIMSupported statementBoundary explicit
GAPMissing detailNo inference
Example record structure
02DESCRIBE THE SCOPE

Record what the number covers

The scope should explain the data category, unit, approximate volume, historical coverage, and preparation included. A price for an entire archive cannot be treated as a per-record price without knowing how the archive was defined. Likewise, a figure covering services and data together does not automatically establish a standalone data rate. Keep mixed components separate whenever the evidence supports that distinction.

Record commercial conditions that materially affect interpretation. These can include permitted use, exclusivity, duration, acceptance, and responsibilities for preparing the material. You may not have every detail, especially when relying on public information. State the limitations clearly and avoid comparing records whose missing terms could explain most of the difference. A smaller set of well described observations is more useful than a large but ambiguous chart.

Define the transaction scope
RecordContext required
DatasetUnit and volume
ServicesSeparate components
RightsDuration and use
Example planning view
03IDENTIFY THE STAGE

An offer is not a completed payment

Transaction stages should remain distinct throughout the evidence trail. An expression of interest shows that a conversation occurred. A bid or offer proposes terms. A signed agreement records commitments. Delivery and acceptance concern performance under those commitments. Payment evidence establishes a further event. Do not move a record from one stage to another merely because the later event seems likely or because time has passed.

When new evidence arrives, add the date and explain what changed. Preserve the earlier understanding so readers can follow the progression. If a proposed figure was revised before signature, keep the distinction between the initial and agreed amounts. If only part of an agreement has been completed, describe that part. The goal is an accurate account of the evidence, not the most impressive possible transaction label.

An agreement is not payment
Signed terms

Commitments recorded clearly

Performance still separate

Completed payment

Further event established

Evidence required independently

Illustrative comparison
04PRESENT WITH LIMITS

Make uncertainty readable

Use clear labels that reflect the information available. An illustration explains a concept and is not evidence of market activity. A reported figure needs review and supporting context. Source-backed information should retain its citation, date, scope, and limitations. Avoid pooling these categories into one average or displaying them with identical certainty. A reader should understand the status without needing to interpret a footnote defensively.

This preview currently displays illustrative examples and provides a local deal-report brief. It does not operate a live submission or publication process. Preparing a report creates a file for your use; it does not establish that a transaction has been verified. Apply the same discipline in your own research: preserve the source, describe the scope, identify the event, and keep unresolved details visible beside any conclusion.

Present the certainty clearly
Evidence labels
01Illustration explains concepts
02Report awaits review
03Source supports claim
04Limits stay visible
Illustrative connected archive