Key takeaway
Compare defined restrictions and usable alternatives. A larger entered receipt does not establish that archive-wide exclusivity is worth granting.
Find the edge of the restriction
The word exclusive leaves most of the executive decision unanswered. Does it cover a frozen export or every future record? Does it bar another external license, internal analytics or a customer’s own use? A commercial headline can conceal a restriction far beyond the material the recipient will actually evaluate.
US copyright law distinguishes exclusive grants from nonexclusive licenses and permits particular exclusive rights to be divided. That supports examining the actual grant where protected material is involved. It does not establish that every operational fact is copyrightable, the company owns all included content, or copyright is the only relevant law.
Ask counsel to mark each restriction and tie it to a named package version. Keep confidentiality, contractor content, privacy and competition questions in the review. The boundary is an executive negotiation artifact, not a clearance certificate.
A completed hypothetical boundary table
This illustration concerns a frozen 2023–2025 maintenance package. The proposed use is training an internal fault-classification model at the fictional Example Analytics Ltd. Neither the company nor its offer is real. The table records a narrower proposal for discussion; it is not a clause to copy into a contract.
| Boundary | Proposed position | Unresolved question |
|---|---|---|
| Material | Package M-03 and listed fields only | Does wording reach source systems or future records? |
| Recipient | Example Analytics Ltd only | Can affiliates exercise the restricted use? |
| Restricted use | One specified external training use | Are evaluation, derived models or sublicensing included? |
| Duration | 12 months from agreed effective event | What survives expiry? |
| Internal use | Seller analytics/service operations retained | Does the text preserve these activities? |
| Other commitments | Existing customer uses excluded | Do customer agreements permit this proposal? |
| Future releases | No implied refresh exclusivity | Would a new release need a new grant and price? |
Compare cash without inventing a premium
Assume two alternative, hypothetical USD offers for one package and one recipient over twelve months: $25,000 for a bounded nonexclusive license, or $36,000 for the bounded exclusive proposal above. Each assumes one payment after agreed acceptance, $5,000 initial preparation, no ongoing refresh, and zero other external license fees. VOID’s upfront seller referral fee is zero. No actual seller has received these offers.
The nonexclusive alternative gives $25,000 − $5,000 = $20,000 before tax. The exclusive alternative gives $36,000 − $5,000 = $31,000. The $11,000 difference compares entered receipts under stated assumptions. It is not an observed market premium or a valuation of every future route the seller could lose.
A possible second license is not cash merely because nonexclusivity permits it. Here it contributes $0 because no accepted, payable second offer is entered. A public estimate is not an offer either: Handshake’s licensing page makes its estimates conditional rather than an offer to purchase or license.
An unpriced option can change the decision
Suppose the same package supports a planned customer diagnostic product. The sponsor cannot reliably estimate that product’s earnings, but can identify the dependency: training and operating its model use the same fault fields. Name that dependency and require a confirmed carve-out before approving the external restriction.
The completed recommendation is conditional: consider the higher entered receipt only if counsel confirms the bounded package, recipient and use, and the product owner confirms the retained internal activities. If wording restricts all diagnostic models using the archive, return it for revision. The spreadsheet’s $11,000 difference does not resolve that conflict.
Record whether the recipient will accept a narrower grant. Do not add an unsupported dollar amount for lost flexibility to make the arithmetic look complete. A clearly described, unpriced dependency is more useful than a fabricated number.
Also ask who can change the source-system scope. If an acquired business contributes a new archive next year, that archive should not accidentally join this proposal through a definition of company data. Put acquisitions and future records on the review agenda rather than assuming the package identifier controls every clause.
Keep the downside visible through signing
If neither offer proceeds after preparation, this scenario incurs $5,000 with no license receipt. If the recipient asks for new fields or refreshes, recompute the comparison. Changed work and changed rights can make apparently comparable offers different transactions.
Use offer comparison to preserve terms alongside the earnings calculation. Bring the boundary table, actual proposed wording and unresolved dependencies to counsel. A named introduction through VOID can open a discussion without committing exclusivity; evaluation access and a signed license require their own decisions.
Approve a restriction only when its edges can be explained to the people operating the archive. Ask engineering to describe what it could still export, the product owner what it could still build, and finance which receipts are conditional. If those answers describe different grants, the decision is not ready.