THE SHORT ANSWER
A company’s headcount, revenue or raw file count does not establish a licensing price. Start with a specific collection and a buyer’s intended use, then compare the rights granted, acceptance conditions, preparation costs and net proceeds. A price becomes decision-useful when you can explain what must happen to receive it.
For owners and finance leads assessing a potential licensing opportunity.
What you’ll leave with
- A seven-part brief to request a meaningful offer.
- A worked calculation separating headline payment from cash retained.
- Questions that expose exclusivity, recurring work and conditional payments.
Price the proposed transaction, not the whole company.#
An archive can support several very different proposals. One buyer may want a fixed collection of resolved support cases to evaluate a model. Another may want a continuing feed and broad training rights. Even if the files overlap, those are different products with different obligations. Ask for the use, recipient, collection and duration before comparing the numbers.
Public marketplace mechanics illustrate the distinction: AWS Data Exchange lets providers define offer pricing, subscription duration and usage terms. That is evidence of how a transaction can be structured, not a published price benchmark for your archive. See the AWS provider documentation.
| Factor | Evidence to prepare | Question for the buyer |
|---|---|---|
| Useful context | Examples of the relationships between a task, decisions and outcome | What capability or test would this collection support? |
| Coverage | Period, workflows, languages and known gaps | Which portions matter, and which would you exclude? |
| Usable volume | Counts after duplicates, exclusions and incomplete records | Are you pricing delivered rows, accepted cases or something else? |
| Rights | Documented authority and unresolved restrictions | What uses and recipients must the license cover? |
| Preparation | A scoped work plan with owners and estimates | Who pays for cleaning, review and rejected material? |
| Duration | Snapshot versus update obligations | Is the payment one-time, recurring or conditional? |
| Exclusivity | The exact collection, use and period affected | Which future opportunities would the restriction prevent? |
Ask for a price against a seven-line brief.#
Send a description first. A buyer should be able to identify obvious mismatches without receiving your production records. Use the inventory worksheet to distinguish verified facts from estimates. For a first brief, fill in these seven lines:
- Collection: one workflow, service line or record family.
- Coverage: dates, language and business context.
- Unit: what counts as one complete case, including linked records.
- Volume: counted total, estimated usable total and how each was obtained.
- Restrictions: exclusions, unresolved permissions and allowed recipients.
- Delivery: possible format, whether updates are proposed and who prepares it.
- Commercial request: proposed use, acceptance test, payment trigger and scope of rights.
If the buyer needs more detail, request a written list of the missing facts. That turns a vague interest signal into a bounded preparation task. If no one can explain the intended use or the acceptance decision, hold off on a large export or an expensive cleanup project.
Calculate the amount your business actually keeps.#
For a simple one-time offer, a useful planning calculation is: gross payment minus percentage fees on that payment, minus fixed fees, preparation and review costs. Keep taxes, timing, contingent amounts and ongoing obligations separate. The net-proceeds calculator lets you compare two scenarios without submitting your figures.
| Item | Scenario A | Scenario B |
|---|---|---|
| Gross payment if accepted | $50,000 | $40,000 |
| Percentage fee on gross | 15% / $7,500 | 10% / $4,000 |
| Fixed fees | $1,000 | $500 |
| Preparation and review | $12,000 | $4,500 |
| Illustrative net before taxes | $29,500 | $31,000 |
Scenario B retains more cash under these assumptions despite the lower headline payment. It is still not automatically the better offer: A and B may buy different rights, carry different payment risks or require different future work. First calculate the economics; then compare the obligations using the offer evaluation guide.
Do not enter a speculative renewal as if it were cash already owed. Keep guaranteed amounts, milestone payments and potential renewals on separate lines. Likewise, an acceptance-based offer needs a rejection scenario: how much preparation cost remains yours if the buyer accepts nothing?
Give the non-price terms their own decision.#
Treat exclusivity as a specific restriction to evaluate, not a word that automatically justifies a premium. Write down the affected records, users, geography, activities and duration. Then ask your team which realistic business options it would remove. Do not invent an opportunity cost using hypothetical buyers you have never spoken with.
A recurring license also creates recurring work. Estimate the hours needed for fresh exports, validation, support, withdrawal requests and schema changes. Assign an owner and a budget. A subscription that looks attractive in the first month can become an operational burden if the update duty is open-ended.
- Acceptance: measurable checks, deadline, rejection reasons and remediation limits.
- Payment: payer, currency, invoicing event, due date and any holdback.
- Intermediaries: who contracts, who pays, and which amounts fees apply to.
- Rights: permitted use, recipients, sublicensing and any exclusivity.
- Exit: delivered files, future updates and treatment of models or other derivatives.
Leave the review with a decision, not just a number.#
Use three outcomes: ready for a scoped offer, worth a limited diligence step, or pause pending a named issue. For every open item, record an owner, the evidence needed and the maximum work you will authorize before reviewing again. That protects the team from spending weeks preparing a collection for an undefined request.
If you are starting without a buyer or a documented collection, request a data licensing review. Describe the business and its records. There is no need to upload source files to make that first request.
Questions owners ask
Is there a standard price per employee or per gigabyte?
Those measures do not define the collection, permitted uses or buyer’s requirements. This guide does not use them to predict a payout. Compare a written scope and an actual proposed payment instead.
Does more data always mean a larger offer?
Raw volume can include duplicates, excluded material and incomplete cases. Show usable coverage and the counting method. Ask the prospective buyer what it would actually accept.
Can I compare an exclusive and non-exclusive offer?
Yes, but compare the restriction separately from the money. Record exactly what future use or licensing would be limited and take that scope into your commercial and legal review.
Sources & scope
This guide combines original planning tools with the primary references below. Examples are illustrative. Source material was checked on October 9, 2026; agreements and legal obligations need review for your circumstances.
- AWS: Providing data productsPrimary documentation on provider-defined products and offers. It does not establish market prices for operational business data.
YOUR NEXT STEP
Start with what you know.
Tell us about your business and the records you have. The first request needs no file uploads or system access.
Request a data licensing review →