Dataset
A legally usable corpus with defined structure, provenance, and rights.
Tracer Research / Research paper 01
How do you price data when its real value is the capability it adds to an AI system? Spirit's selected $10 million bid raises the question: could the package have been underpriced? The paper shows what must be measured to answer it.
Proprietary business records are becoming inputs for training, evaluating, and supervising AI systems. Their value depends on the task improvement they produce and the buyer's ability to turn that improvement into revenue or savings. This paper introduces Capability Alpha, a controlled estimate of a dataset's contribution to performance, and Price-Implied Uplift, the minimum commercial improvement required to recover an observed price. Spirit Aviation provides the worked case. Google's selected $10 million bid covers data and internally developed software. With 5% of annual Google Cloud revenue as an illustrative scope, it implies 0.236% persistent uplift over three years. Court approval remained pending, and Spirit's Capability Alpha remains unmeasured. Whether that amount understated the package's value to Google remains open.
The forward figure comes from chosen inputs. Evidence that value exceeded the bid would require a measured Capability Alpha and observed commercial capture.
In brief
Capability Alpha isolates how much a proprietary dataset changes performance on a defined, economically relevant task.
The same measured gain can be worth very different amounts depending on exposure, monetization, useful life, rights, and integration cost.
Price-Implied Uplift asks how much persistent commercial improvement would be needed to justify the price paid.
A $10 million package price, applied to a scenario where 5% of annual Google Cloud revenue is the relevant base, implies a three-year break-even uplift of about 0.236%.
This threshold comes from scenario inputs. An experiment would still be required to measure Spirit's Capability Alpha, and the package includes data and software.01 / The question
File, row, message, and token counts describe scale. Valuation begins with the task performance that changes because of the data: resolving a disruption, repairing software, forecasting demand, or completing another valuable task.
This distinction matters because data only creates economic value through a use. A billion disconnected records may be less useful than a smaller corpus that preserves what happened before a decision, which action was taken, which tools were used, and what happened next. For AI systems, that sequence can become a demonstration, a held-out evaluation case, a verifier, or post-training supervision.
Businesses have analyzed event logs and audit trails for decades. Today, workflow-linked records are being packaged for training, retrieval, evaluation, and verification across AI systems. One corpus may support several task families.
Earlier work already connects information and predictive improvement to economic value. This paper adapts that work to proprietary enterprise data transactions. It measures the corpus's incremental contribution, maps the result to a buyer's economics, and states the assumptions used to interpret an observed package price.
Which economically relevant task can this dataset improve, and by how much?
02 / The method
A dataset's price changes with the task, the experimental stack, and the buyer. Technical measurement belongs to the task and stack; economic translation belongs to the buyer.
A legally usable corpus with defined structure, provenance, and rights.
The task-level gain caused by access to the data under a controlled stack.
Exposure times monetization times persistence, adjusted for rights and cost.
Direct use value, a price-implied threshold, and supported strategic effects.
Capability Alpha answers this with a controlled evaluation. That result belongs to the experiment. Buyer size enters later, in the economic calculation.
Exposure, product fit, distribution, rights, useful life, and cost can make the same measured gain far more valuable to one buyer than another.
03 / The technical measure
Fix the model-adaptation procedure and total resource budget. The treatment replaces a pre-specified amount of reference data with the same amount of proprietary data.
In words: expected held-out performance after replacing k units of reference data with proprietary data, minus the equal-budget reference-data control.
DkThe pre-specified proprietary-data dose drawn from dataset D.
kThe amount of reference data replaced while the total adaptation budget stays fixed.
M0The control model adapted on B units of reference data.
M1The treatment model adapted on B-k reference units plus Dk.
YtThe pre-specified metric on an independent held-out task evaluation.
๐ผAn average over matched training seeds and evaluation outcomes.
Same base model, adaptation method, schedule, token or example budget, compute budget, and evaluation harness.
B units of pre-specified reference data
The same total budget, with provenance as the intervention
Suppose both arms use the same LoRA configuration and a 20-million-token adaptation budget. The control uses 20 million reference tokens. The treatment replaces 5 million of them with proprietary IT-support trajectories.
Across matched runs on 1,000 held-out incidents, control resolves 55.0% and treatment resolves 61.2%. Capability Alpha at a 5-million-token dose is +6.2 percentage points. That is a technical estimate under the declared stack, with no monetary assumption.
Data Shapley, Datamodels, TRAK, and LESS can help locate influential records or plan follow-up ablations. The paper treats them as diagnostics. The valuation input still comes from the direct matched experiment.
The paper first defines a diagnostic gap, Gt = Ht - Ft: the distance between a reference performance level and a practical baseline. A large gap shows room to improve. Evidence that dataset D contains the needed signal still requires a controlled experiment.
Pre-specify the task. Fix the target distribution, metric, and verifier before observing treatment results.
Hold out whole cases. Split by incident, customer, project, route, contract, or time period and screen for leakage.
Match the budget. Change the provenance of k units while model, optimizer, schedule, compute, and harness stay fixed.
Estimate uncertainty. Use paired seeds and intervals that reflect paired outcomes and run-to-run variation.
Keep contrary evidence. Retain negative effects and consider an equal-size irrelevant or shuffled placebo.
Test scale and transfer. Repeat across data doses, a second model or checkpoint, and adjacent tasks.
Outcome linkage describes whether records preserve that sequence. Verifiability describes whether success can be judged by an objective, expert, or reproducible criterion. These corpus properties shape usefulness. They enter valuation through measured performance and usable rights.
04 / From performance to money
A task-metric improvement acquires dollar value through its effect on revenue, cost, throughput, time, error, conversion, retention, or another economic outcome.
In words: add the buyer's expected task-level benefits over time, discount them to today, adjust for usable rights, then subtract the buyer's total costs.
CAD,t(k)How much dose k from dataset D improves task t in the matched evaluation.
Eb,t,h x ฮปb,tThe buyer's economic base and the mapping from one metric unit into commercial change.
dD,t,h / (1+r)hHow much of the data advantage survives, then what a future benefit is worth today.
ฯD - Cb(D)Usable access, less acquisition, legal, deidentification, cleaning, training, and deployment cost.
A dataset can have the same measured Capability Alpha for two firms and still have different values. A buyer with broader exposure, stronger distribution, better complements, or lower integration cost can turn the same technical gain into more money.
05 / Reverse the price
PIU starts with the observed price and calculates the persistent revenue-equivalent uplift required to break even.
In words: total package and integration cost, divided by the present-value profit base that the capability could affect.
A(T,r) = โh=1T 1 / (1+r)h
For a three-year useful life at a 12% discount rate, A(T,r) is approximately 2.402.PObserved transaction price.
CbBuyer-specific integration and transaction costs.
RscopeAnnual revenue base plausibly exposed to the capability.
mOperating margin applied to incremental revenue.
A(T,r)Discounted annuity factor across useful life T at rate r.
ฯRights-and-usability adjustment between zero and one.
Annual Google Cloud revenue inside the illustrative scope.
Annual operating profit associated with that revenue base.
Three-year present-value profit base at a 12% discount rate.
Persistent revenue-equivalent uplift required to break even.
The slider changes only the modeled business base. Aviation's actual share of Cloud revenue and Spirit's effect on that revenue remain unknown.
$4.954B annual scoped revenue produces a $4.23B three-year present-value profit base.
The base calculation sets integration cost to zero and the rights adjustment to one. The agreement assigns third-party deidentification costs to Google, so the headline omits those costs.06 / The case
The public record contains bid amounts and a detailed asset schedule. The corpus's contribution to any Google model or product remains unknown.
Spirit Aviation Holdings designated Google as the successful bidder at $10 million, subject to court approval and required deidentification. Mercor was identified as the $7.5 million alternate bidder. A later $12.5 million micro1 offer arrived outside the initial auction process. It records willingness to pay and had not become a completed transaction in the paper's record.
The selected bid covers data and internally developed software, with no disclosed allocation between them. The PIU exercise assigns the full $10 million to the package. If the software has positive standalone value, that convention is an upper bound on the amount attributed to data. If the components are complementary, a clean allocation may not be economically meaningful.
emails listed in the schedule
Microsoft Teams items
information-technology tickets
repositories with roughly 30M lines of code
booking-curve observations
revenue transactions
Pricing stateโdecisionโbooking outcome
IT ticketโcode changeโdeployment result
07 / Price and value
The auction records bids from a specific process. The forward model calculates value under explicit improvement and capture assumptions. Its output is a sensitivity, and the Spirit evidence leaves the question unresolved.
Choose an airline improvement and a Google capture rate. Airline revenue, Cloud margin, useful life, and discount rate remain fixed.
$116.5M in annual incremental Google revenue produces this present value under the fixed margin, life, and discount assumptions.
The forward exercise begins with $1.165 trillion of global airline revenue. It then assumes an improvement in airline economics and a share of that created value captured by Google as incremental revenue. Applying the reported 35.6% Google Cloud operating margin, a three-year life, and a 12% discount rate produces the present values below.
The 1% airline effect and 0.5% to 2.0% capture rates are chosen scenario inputs. The table shows how present value changes across them; it carries no central forecast.
| Modeled airline improvement | 0.5% capture | 1.0% capture | 2.0% capture |
|---|---|---|---|
| 0.25% | $12.5M | $24.9M | $49.8M |
| 0.50% | $24.9M | $49.8M | $99.6M |
| 1.00% | $49.8M | $99.6M | $199.2M |
| 2.00% | $99.6M | $199.2M | $398.4M |
Observable bid signals, a transparent reverse-DCF threshold, and a conditional scale sensitivity.
Spirit's fair value, the share of the $10 million bid attributable to data, and any conclusion that the asset was underpriced.
The selected and alternate package bids, the disclosed asset schedule, and published Google Cloud segment inputs.
Revenue scope, margin as a proxy, useful life, discount rate, airline effect, and buyer capture rate.
Actual Capability Alpha, post-deidentification usability, integration cost, data-software allocation, and realized commercial use.
08 / Who can use it
Legal access is one requirement. Monetization at scale also needs models, compute, post-training infrastructure, distribution, and commercial exposure.
Privacy rules, deidentification, license limits, and preserved linkage determine how much utility survives.
The corpus must improve performance on a task that still contains meaningful unsolved work.
The same gain is worth more when it can be applied across a larger economic base.
Compute, models, product surface, distribution, and integration capacity determine who can realize the gain.
Set the buyer index to the current owner and the framework produces internal retention value. A firm can rationally value its own data less than an outside buyer if it has less exposure, weaker commercialization channels, or higher integration cost.
Restrictive rights may create value by denying a close rival access. A preemption estimate requires transaction rights and competitive evidence. Add strategic value only when that evidence is available.
Vbtotal(D) = Vbuse(D) + Sb(D)
09 / Limits and falsification
A useful valuation should expose its missing evidence. In the Spirit case, the decisive quantity still lacks a measurement.
Representative Spirit-derived tasks are already solved near the required quality, leaving little capability gap to close.
Controlled access or post-training produces no reliable held-out improvement after the rest of the stack is fixed.
Measured gains disappear across model families or fail to change real production outcomes.
Deidentification, weak linkage, restrictive rights, or high integration cost remove most practical utility.
Capability Alpha, after economic translation, remains below the PIU threshold under defensible scope assumptions.
Capability Alpha is conditional on the evaluation stack. It requires controlled ablations, uncertainty intervals, contamination checks, and transfer tests.
The mapping from a task metric to revenue or cost may be nonlinear, and overlapping economic bases can create double counting.
A package can lose value through privacy constraints, broken linkage, legal limits, deidentification burden, and costly integration.
The advantage may decay as models improve, substitute data appears, or the underlying business process changes.
This article builds the intuition. The 19-page paper contains the literature review, formal model, matched-retraining protocol, sensitivity analysis, limitations, and bibliography.
Final PDF dated August 23, 2026. The source archive is being reconciled separately.
Open the paper