Resources
Business data pricing: records, documents and project licences
Compare business-data quotes by accepted records, documents, thread completeness, preparation work and refresh scope.
Published 2026-10-27 · 6 min read
| Quote component | Comparable definition |
|---|---|
| Accepted unit | Message, complete thread, case, document or page |
| Source scope | Named systems, date range, languages and restrictions |
| Preparation | Extraction, redaction, labels and correction work |
| Refresh | Static version versus separately scoped future updates |
There is no verified universal price per business record, document or support ticket. An export’s size does not establish its value. Pricing needs a defined subset, a relevant model task, usable structure and a licence covering the intended use.
Large publisher or platform deals are not a rate card for ordinary business records. Troveo’s public guide describes limited comparable transactions; it is a vendor explanation, not evidence of what Fiund or a buyer will pay you. Use the scope worksheet below to make actual proposals comparable.
Choose a unit that cannot be inflated by exporting differently
A ticket may be one message, a whole conversation or a resolved case with several attachments. A document may be one file, one page or a version history. State the unit explicitly and preserve source relationships rather than billing every export row as independent data.
For example, 100 threads containing 1,000 messages are 100 threads and 1,000 messages, not interchangeable quantities. If resolution context is required, incomplete threads should be identified before an accepted-case count is agreed.
Separate the underlying licence from preparation
Request distinct lines for the reviewed dataset subset, extraction, deduplication, redaction, normalization, annotation and delivery. An existing collection may still require paid preparation; that work is not automatically included in the licence price.
A useful quote also states minimum scope, acceptance rules, excluded categories, rework responsibilities and whether sample evaluation is included. A seemingly low per-record rate may refer to raw fragments while another quote includes a complete reviewed case.
Work through an illustrative quote
Hypothetical arithmetic, not a market rate or Fiund offer: a $2,000 licence for 10,000 accepted cases implies $0.20 per accepted case. If preparation costs $700, $1,300 remains before other costs or contractual sharing. Do not mistake the gross licence amount for a contributor payout.
If each case averages five messages, the same assumed total implies $0.04 per message. That conversion changes the denominator, not the economic value. Record what happens if acceptance reduces the case count or if missing attachments make a case incomplete.
Quote refreshes and evaluation labels separately
For changing business data, define whether a purchase covers a static snapshot or future updates. Specify update cadence, version IDs, removal handling, schema changes and whether new preparation work is included. Do not promise a continuous feed when only a historical export exists.
For evaluation datasets, define whether labels describe routing, issue category, successful resolution or human review. Document how the answer was obtained. A closed ticket is not automatically a verified correct answer, and an internal outcome field is not a substitute for an annotation policy.
Ask for an assessment or a scoped buyer quote
Owners should describe source systems, record groups, unique counts, languages, available schema and the status of permissions. Keep confidential examples out of the initial intake. Buyers should provide the task, required fields, accepted unit and excluded material in a brief.
Fiund confirms availability and scope after review; no inventory or transaction is implied by this guide. Standard buyer licences are non-exclusive. Do not budget on assumed exclusivity premiums or an anticipated sale before commercial terms are agreed.
Before requesting an assessment or quote
- Define the billable unit and duplicate policy.
- Separate licence, preparation and refresh costs.
- Confirm acceptance and rework rules.
- Evaluate permissions before pricing a raw export.
Frequently asked questions
Can I use a publisher deal to estimate my ticket archive’s value?
No dependable per-record conversion follows from a publisher’s overall deal. Compare the actual task, material, rights and deliverables.
Is per-token pricing a dataset valuation?
It is a possible billing denominator, but tokenization and included content must be defined. API inference prices do not determine a dataset licence price.
Does Fiund publish a fixed business-data purchase rate?
This guide does not offer one. Submit a description or sourcing brief for a scope-specific review.