What affects the value of a data licence?

There is no universal price per record

A count tells a reviewer something about scale. It does not show whether the material is relevant, usable or available on acceptable terms. Two collections of the same size can describe completely different work.

The Open Data Institute's discussion of data value highlights the importance of use and context. It is background research, not a current pricing benchmark. Fairlode does not publish a market-calibrated dataset price list or treat headline deals elsewhere as comparable sales.

The questions below are a framework for a commercial discussion, not a valuation formula.

1. What does this buyer need?

Ask for a description of the task the collection would support. Is the interest in examples of specialist reasoning, a particular workflow, or material for testing a system? Does the proposed use concern training, evaluation or both?

A dataset can be carefully maintained and still miss the requirement. Ask what would rule it out before investing in preparation. Buyer interest in one category is not proof of interest in every record your company holds. The training and evaluation guide helps separate these uses.

2. How much is actually usable?

An initial outline can use an approximate size band. A later review may need to distinguish complete records from duplicates, empty entries, excluded material and unsupported formats.

Look for links that make an example understandable: a problem and resolution, a change and its reason, or a task and the checks applied. Those are questions about structure, not a claim that a buyer will pay more for any particular feature.

For example, an illustrative support archive may contain many closed tickets but no reliable resolution field. A reviewer needs to know that limitation. Do not export ticket text to demonstrate it during an initial enquiry.

3. What permissions are being requested?

A narrow evaluation licence and a wider training licence are not interchangeable. Nor are a one-time extract and a continuing supply with updates.

Put the proposed recipient, purpose, duration, exclusivity, onward use and treatment of derived material alongside any price. Ask your adviser to identify which rights the company can grant and which require somebody else's permission. An NDA and a data licence serve different purposes; signing one is not a substitute for agreeing the other.

Do not assume that wider permissions will produce a better overall deal. Consider the effect on your own product, customers and future options.

4. What would the business keep, and owe?

Compare the proposed payment with preparation costs, adviser fees, staff time and any continuing obligations. Ask who pays if a sample review or acceptance test does not succeed. Confirm whether updates, corrections or support are included.

An illustrative comparison is a one-off delivery against a lower initial payment with recurring updates. The second arrangement adds future work and uncertainty. Neither is automatically preferable: write out what must happen before each payment and what the supplier must keep doing afterwards.

Fairlode's introduction process and referral-fee basis are explained on the main page. The partner, fee arrangement and sharing scope are confirmed before an introduction. A referral is not a licence or a payment.

How to ask for an indicative range

Ask: “Based on this non-confidential description, is there an active requirement? If so, what indicative range would you consider, for which permissions, and subject to which checks?”

Keep three outcomes separate: interest in discussing the collection, an indicative range subject to review, and an offer with defined terms. Record the date, assumptions and outstanding questions. It is also possible that no price can be given yet, or that there is no demand.

Start with the data licensing checklist. Do not send code, customer records or an archive to obtain an early opinion. If the description itself needs an NDA, raise that first.