You do not need to be a technology company. You need to have run the same workflows, in the same systems, for a few years. Eight record types carry most of the value, and most established companies have at least four of them.
No dataset needed to start. The manifest describes what exists; nothing leaves your systems.
Client threads, approvals, scheduling, decisions in writing.
Playbooks, templates, proposals, checklists, process docs.
How your team solves problems in real time.
Sales and support calls, and how they ended.
Deal stages, notes, and why customers said yes or no.
Issue → diagnosis → resolution, thousands of times over.
Invoices, approvals, exceptions, and how work actually gets done.
Issue triage, code review, release and incident records.
The tier on each card mirrors the weight that record type carries in our estimator, which is calibrated to what vetted buyers are currently asking for. A steady-demand record type with eight years of history and outcomes attached will outrank a highest-demand type with thin, unlinked records. The detail pages show what moves each one.
| Tier | What it means |
|---|---|
| Highest | Buyers are actively short of this record type and price it at the top of the range. Calls with outcomes and resolved support tickets. |
| High | Strong, specific buyer briefs. Engineering records for coding agents; team chat for problem-to-fix trajectories. |
| Strong | Consistently requested, usually as part of a linked set. Email threads and CRM histories. |
| Steady | Valued most when paired with the records that show them in use. Documents and SOPs; billing and operational systems. |
Indicative range observed across the market for single-company operational data licenses. Not a quote. Actual value depends on buyer demand, data quality, rights, and exclusivity.
Seven questions. No dataset. First offer in 24 to 48 hours of a complete manifest.
Measured from a complete data manifest. A first offer is a process target, not a guarantee; buyers decide eligibility, price, and terms.