[§1] Advisory scope
Build three defensible price scenarios for a data license
Create evidence‑based pricing ranges for proprietary data assets. We analyze rights, uniqueness, scale, and more to produce three clear scenarios.
The need for scenario‑based pricing
Data owners often face buyers who request a price without clear market data. A single number can be fragile. Multiple scenarios create a band that reflects uncertainty and buyer preferences. The band is built on evidence, not speculation. It helps sellers present a realistic range and buyers understand upside and downside.
The three standard scenarios
We use a three‑point framework. Each point is a complete, defensible offer that can be presented to a buyer.
Base scenario.
- Reflects current rights, typical usage, and average quality.
- Uses the most common discount factors (e.g., non‑exclusive license, standard refresh frequency).
- Serves as the “most likely” price if negotiations stay within typical parameters.
Upside scenario.
- Assumes stronger value drivers: exclusive rights, broader language coverage, higher refresh rate, or unique domain depth.
- Applies lower discount percentages and may add premium clauses.
- Shows the maximum price a seller could justify with the strongest evidence.
Downside scenario.
- Assumes weaker drivers: limited exclusivity, reduced quality, narrower scope, or longer lock‑up periods.
- Uses higher discount percentages and may remove premium features.
- Provides a floor that protects the seller if buyer demands concessions.
Each scenario is documented in a short pricing table. The table includes the driver list, the discount applied, and the resulting annual license fee. The numbers are transparent; the buyer can see why a scenario is higher or lower.
Step‑by‑step process
| Step | Action | Output |
|---|---|---|
| 1 | Collect rights and asset documentation. | Rights register |
| 2 | Map value drivers (rights, uniqueness, domain depth, language, quality, scale, refresh, exclusivity). | Driver checklist |
| 3 | Assign a baseline monetary value to each driver. | Driver value matrix |
| 4 | Apply scenario‑specific discount rates. | Discount schedule |
| 5 | Calculate three price points. | Scenario price table |
| 6 | Draft a concise briefing for the buyer. | Scenario brief |
We follow this workflow for every client. The steps are repeatable, and each produces a clear audit trail.
Checklist of value drivers
- Rights coverage – Full ownership vs. limited licenses.
- Uniqueness – Proprietary collection, not easily replicated.
- Domain depth – Breadth and granularity of subject matter.
- Language coverage – Number of languages and dialects.
- Quality – Accuracy, completeness, and validation processes.
- Scale – Record count, file size, and usage volume.
- Refresh frequency – Real‑time, daily, quarterly, or static export.
- Exclusivity – Exclusive field, region, or time‑limited rights.
Use the self‑assessment tool to score each driver: /workbench/readiness/. The scorecard feeds directly into the driver value matrix.
Discount logic
Discounts are not arbitrary. They follow documented patterns:
- Non‑exclusive license – a discount that grows with the lack of exclusivity.
- Limited refresh – a discount that grows with the reduction in refresh frequency.
- Partial language coverage – a discount that grows with the number of languages missing.
- Quality tier – a discount that grows with the reduction in quality.
- Scale reduction – a discount that grows with the reduction in data volume.
All percentages are applied to the driver‑based base value, not to the final price. This preserves the relationship between each driver and the overall scenario.
Deliverables
When the analysis is complete, we provide:
- Scenario price table – Base, Upside, Downside with driver breakdown.
- Driver evidence summary – Short notes linking each driver to supporting documents.
- Discount rationale memo – Explanation of each discount applied per scenario.
- Buyer briefing template – Ready‑to‑use document for initial outreach.
The deliverables are designed for quick review by legal counsel and for transparent discussion with potential buyers.
How we differ from a formal appraisal
We do not issue a fixed valuation. We do not guarantee a sale price. Our work is evidence‑based and scenario‑focused. It supports negotiation, not a statutory appraisal. Sellers retain control over which scenario to present.
When to start
If you have a dataset you plan to license, begin with a brief. The brief collects the essential facts we need for the driver checklist. Start here: /workbench/#request-review. After the brief, we will walk you through the process described above and produce the three pricing scenarios.
Additional resources
- Learn more about the overall workflow: /methodology/engagement/.
- Read research notes on scenario pricing: /research/.
- Explore related services, such as exclusive vs. non‑exclusive pricing: /methodology/exclusive-vs-non-exclusive-pricing/.
- For acquisition‑related valuation, see /methodology/data-valuation-for-acquisitions/.
Our approach is methodical and transparent. It lets data owners present a defensible price range and lets AI buyers understand the value they are purchasing. Use the tools and links above to move from idea to a concrete, evidence‑backed pricing proposal.
Questions at a glance
What is the purpose of multiple pricing scenarios?
They give sellers and buyers a structured range to test, reducing surprise and supporting negotiation.
Do you set a single price for the data?
No. We provide scenario ranges based on evidence, not a fixed appraisal.
How are discounts applied?
Discounts are tied to specific drivers such as non‑exclusive rights, limited refresh, or lower quality tiers.
What information do you need to start?
A brief description of the dataset, rights documentation, and any known buyer use cases. The [valuation brief](/workbench/#request-review) collects this.