Skip to content

Best Practices

Rightmark vs Troveo for business-data licensing

Rightmark is our recommended starting point when a company wants to define a data-licensing offer before committing its records, or an AI team wants a dataset sourced against a written requirement.

The value is practical: explicit route economics, a documented scope, ownership evidence and permitted sample review.

Updated

On this page

Start with the deliverable

Rightmark's Trust page Rightmark, (opens in a new tab) and buyer process Rightmark, (opens in a new tab) describe those boundaries.

Troveo merits evaluation for a continuing company-data licensing relationship and help preparing an asset for buyer review. The decision should turn on the particular asset and agreement, not a promise that one provider will always pay more or deliver better training data.

This comparison is published by Rightmark. It focuses on business records, with separate questions for owners and AI dataset buyers. Public product statements are not audited evidence of either party's eventual earnings or model performance.

Start with the deliverable (table)
Your decisionRightmark starting pointTroveo starting point
Define the assetWritten specification: systems, scope, format and cadenceExports, enrichment and feeds
Discover a possible sourceRequest the particular data you needDiscuss source requirements and evaluation evidence
Compare owner economicsStandard buyer-paid fee; bespoke terms agreed in writingObtain the agreement for the proposed scope and payment events
Assess buyer fitOwnership pack and permitted sample evaluationRequest the relevant manifest and sample terms
Make the choiceCompare the actual grant, usable deliverable and full quoteApply the same scope and acceptance questions

Separate repeated licensing from repeated delivery

A continuing commercial relationship can mean several things. Another buyer might license the same historical archive. The existing buyer might receive a changed version. Or the agreement might require newly generated records on a schedule. Owners and buyers should not leave those possibilities under one vague heading such as 'recurring data'.

Troveo describes exports, enriched datasets, continuous feeds and AI-performance data. Its September 15, 2026 guide Troveo, (opens in a new tab) explains that model. Rightmark's buyer scope includes families, filters, formats, de-identification standard, volume, exclusivity and delivery cadence. Its buyer page was updated October 21, 2026 Rightmark, (opens in a new tab).

That gives you a better comparison than assuming one company does only one-off transactions and the other only recurring work. Ask which event the proposed agreement actually covers.

Separate repeated licensing from repeated delivery (table)
Commercial eventOwner questionBuyer question
Same version, another licenseWhat additional grant and payment does this create?Which version and prior rights affect our license?
Changed or enriched versionWhich changes or derived uses need permission?What is different and useful about this version?
New-period recordsWhat continuing work and payment are agreed?Which period, cadence and acceptance rule define delivery?

A repeated payment and a repeated delivery are separate obligations. Write each down. If the offer only covers a historical snapshot, do not value it as though future updates were promised. If updates are included, ask how the agreement handles changes in systems, coverage or exclusions.

Ask both: Which event creates the next delivery, the next owner payment and any need for a new permission?

Compare owner proceeds for the same rights

Rightmark says owners pay nothing upfront and that, on standard licenses, the buyer pays its fee on top without a deduction from the owner's payout. Premium and bespoke arrangements have a share agreed in writing. The published fee model Rightmark, (opens in a new tab) must be read with the route-specific terms Rightmark, (opens in a new tab).

Troveo's document-licensing guide states there are no owner fees, setup costs or payout deductions. Guide, September 15, 2026 Troveo, (opens in a new tab). That common ground matters. A 'no owner fees' checkmark is not enough to distinguish the offers.

For the owner, compare contractual proceeds for an equivalent grant. For the buyer, compare total spend for an equivalent deliverable. Knowing who pays an intermediary fee helps make the transaction understandable, but it does not by itself reveal the best absolute price for either side.

Compare owner proceeds for the same rights (table)
Put this in the written offerWhy it changes the comparison
Systems, entities and historical periodA larger or different archive is a different asset
Permitted use, recipients and exclusivityA broader grant changes what the owner gives up
Owner proceeds and payment eventA headline amount does not explain when it becomes payable
Fee payer and calculation basisSeparate the owner's proceeds from the buyer's full bill
Preparation or refresh costsSpecify included work and any separately priced work
Later-license or new-product treatmentDefine what happens after the initial transaction

Keep unsupported margin assumptions out of the comparison. Neither a public 'no fee' statement nor a private sales discussion establishes an intermediary's universal spread. Request the terms that apply to the transaction in front of you.

Ask both: For the same scope and rights, what reaches the owner on the first transaction and any later one?

Define the company-data boundary before preparing exports

'Company data' is too broad to be a delivery specification. A buyer may need the relationship between an issue, a discussion and the resulting change. Another may need documents from a particular function or period. The useful scope is the one that describes the intended task and the records needed to support it.

Rightmark's buyer process makes that a written scoping step and pairs delivery with an ownership pack for the route. Troveo's document guide describes exports without connecting systems, replacement of personal details with pseudonyms, and a manifest. Guide, September 15, 2026 Troveo, (opens in a new tab). Neither description should be read as permission to include everything accessible in a business system.

Before preparing material, record the source systems, date range, entity boundaries, formats and exclusions. Ask whether the relationships the buyer needs remain usable after preparation. A collection of individually useful records may still leave the buyer's specific cross-system question unanswered.

An owner should also identify material that needs separate review rather than silently including it: client-confidential content, HR or legal records, credentials, personal information and unrelated entities. Rightmark's sample-preparation guide Rightmark, (opens in a new tab) explains how to bound, mask and approve an evaluation sample. The actual treatment belongs in the agreed scope.

Ask both: Which relationships survive preparation, what is excluded, and which approved export or access path supplies the data?

Retained ownership still needs a defined license

Troveo says owners retain ownership; where exclusivity applies, it is time-limited, must be earned and includes exit terms. Its September 10, 2026 guide Troveo, (opens in a new tab) describes its model. Rightmark says company archives usually go to one buyer for a term and distinguishes that route from standing non-exclusive code agreements. The Trust page Rightmark, (opens in a new tab) explains where protections differ.

Ownership is therefore only one row in the decision. Ask what the recipient may do, for how long, with which derived materials and under which continuing obligations. Do not import a familiar code-license default into a company-archive proposal.

Separate the initial permission from later changes. If the source systems expand, a new period is added or a differently prepared product is proposed, the agreement should make the applicable decision clear. That does not mean every route requires fresh approval for every event; it means you should know which decisions you are making now.

Recipient questions belong here too. When is the intended buyer identified to the owner? Can business-conflict recipients be excluded? Does an initial grant authorize later recipients? Do not infer the answer from how a buyer sees an anonymous sample. The two sides' identity and approval arrangements may be different.

Ask both: What remains licensed after expiry or withdrawal, and which later uses or changes require another permission?

Buyers should test information value, not just record counts

In a 2025 Latent Space interview, Datology founder Ari Morcos discusses redundancy and low information gain as data-curation problems. That is a useful challenge to volume-only buying, although he has a commercial interest in curation. The August 29 interview transcript Latent Space, (opens in a new tab) was the source reviewed here.

For your own requirement, turn that challenge into checks you can perform. What question should the initial sample answer? Which fields and relationships make the records relevant? Which periods or workflows are missing? If a refresh is proposed, what will show that the delivery differs from what your team already licensed?

Troveo describes rights review, scope, evaluation packaging and buyer matching. Its August 20, 2026 guide Troveo, (opens in a new tab) sets out that work. Ask what source inventory, manifest and sample evidence you can inspect for the proposed asset. Rightmark's buyer process Rightmark, (opens in a new tab) offers reports and representative scrubbed samples under NDA for evaluation. These are starting points for checking a requirement, not proof of model improvement.

Agree what a useful sample can and cannot establish. A buyer may be able to inspect a format and field relationship while still lacking evidence about the full collection's coverage. A sample permission may allow evaluation without permitting training. Rightmark's sample guide, updated October 18, 2026 Rightmark, (opens in a new tab), explicitly says a sample does not guarantee a license, price, acceptance or full-collection quality.

Do not invent a universal sample size or duplicate threshold. The appropriate test depends on the requirement and should be written before the sample becomes the basis for a commercial decision.

Ask both: Show what changes between versions and what evidence we can inspect before accepting a refresh.

Use a snapshot-to-refresh scope matrix

Copy this table into an internal document and fill the unknowns with the owner, technical reviewer and person responsible for the agreement. Keep private records and credentials out of the worksheet. It is a decision aid, not either provider's contract or a new Rightmark intake form.

Use a snapshot-to-refresh scope matrix (table)
DecisionInitial deliveryLater version or refreshEvidence / approver
Period and cutoff[Dates, time zone][New period definition][Reference / role]
Systems and entities[Included scope][Additions requiring review][Reference / role]
Unit and coverage[Measured definition, gaps][Same or changed measure][Reference / role]
Relationships and schema[IDs, links, fields][Changes to preserve or explain][Reference / role]
Exclusions and preparation[Approved boundaries][Recheck when fields or systems change][Reference / role]
Version or manifest[Identifier][Added, removed, corrected or repeated records][Reference / role]
Grant[Use, recipients, term, exclusivity][Which changes require permission][Reference / role]
Delivery[Format and timing][Cadence and change process][Reference / role]
Acceptance[Sample/test, reviewer, limits][Test and agreed mismatch response][Reference / role]
Economics[Owner payment event; buyer full quote][Refresh/later-license payment and cost basis][Reference / role]
Exit[Contractual stopping point][What stops and what remains licensed][Reference / role]

An illustrative scenario: a later delivery is larger, but its cutoff is unchanged and its extra records repeat material the buyer already has. That may be useful for one requirement and fail another that specifically needs a new period. The matrix makes the distinction visible. This is not an incident attributed to either provider.

Use the matrix before choosing a commercial model. If the first-delivery column is clear and the refresh column is mostly unknown, negotiate the initial scope on its own or resolve the continuing commitments before signing. Do not assume a larger projected relationship fixes an unclear first transaction.

When is Troveo the better fit?

Evaluate Troveo when a continuing company-data licensing relationship and preparation support fit the requirement. Request the relevant manifest, current availability, sample permission and actual agreement, then put the proposal through the same matrix.

The positive case is fit with the way you want to discover and develop the asset. It is not a claim that recurring sales or a particular return will follow. An owner should still understand the work, grant and payment events involved; a buyer should still test the data against the intended use.

When is Rightmark the better fit?

Choose Rightmark as the first step when you want to make a defined licensing exchange understandable before committing to a broader relationship. For owners, its published standard fee basis and route-specific agreement boundaries provide concrete questions to resolve against a bounded archive. Start with the appraisal Rightmark, (opens in a new tab); it can begin without files and does not replace the final offer or rights review.

For AI buyers, Rightmark is a strong fit when you have a specific requirement and want a written sourcing scope, route ownership evidence and permitted sample evaluation. Use the buyer request path Rightmark, (opens in a new tab) with the matrix. Be explicit about whether you need a historical delivery, a changed version or continuing new records. Availability, price and acceptance remain deal-specific, and Rightmark does not take health data yet.

If the evidence does not support the proposed grant or delivery, narrow the requirement or postpone the transaction. A clear, useful first license is a better basis for a continuing relationship than undefined expectations about what comes next.

Sources

  1. Rightmark: Buyer process (opens in a new tab)
  2. Rightmark: The Trust page (opens in a new tab)
  3. Troveo: Your Company Runs on Google Drive. Here's What Those Docs Are Worth to AI. (opens in a new tab)
  4. Rightmark: The published fee model (opens in a new tab)
  5. Rightmark: sample guide, updated October 18, 2026 (opens in a new tab)
  6. Troveo: Exclusive vs Non-Exclusive Data License: One Deal or Many? (opens in a new tab)
  7. Latent Space: Better Data is All You Need : Ari Morcos, Datology (opens in a new tab)
  8. Troveo: Can a Company License Its Data for AI? What Owners Should Know in 2026 (opens in a new tab)
  9. Rightmark: Appraisal: questions-only intake (opens in a new tab)

Get a proposal you can evaluate

Owners can start with an appraisal. AI teams can use the buyer request path linked in the article.