Seller field guide · 3 min read
Can you evaluate a data license without live system access?
Ask prospective buyers whether they can evaluate a scoped export or sample before discussing a connector. An export can create a clear review boundary, but it still requires permission, appropriate handling and validation. The permitted delivery method is a program-specific question to settle in writing.
Separate the buyer’s information need from its access request
Scale describes using structured, de-identified records rather than raw systems. That provides a concrete example of an export-oriented discussion, but it does not establish what every buyer or every proposed scope will require.
Ask the buyer to identify the information needed for its next decision: system coverage, record types, a representative sample or a final approved package. The least information required for initial fit may be a written inventory. Avoid treating a request to assess the opportunity as automatic permission to access production systems.
Source notes: Scale: data partnerships, criteria and data sources
Compare the boundaries of each delivery approach
Prism advertises read-only connectors. Read-only describes an ability to modify a system, not the sensitivity of everything an integration can read. Review its scopes, accessible populations, credentials and removal process before deciding whether the approach fits your requirements.
The comparison below is a diligence aid. Export and connector approaches can both be appropriate or inappropriate depending on their actual design. A file transfer is not automatically secure, and a connector is not automatically broad.
| Approach | Boundary to verify | Question before proceeding |
|---|---|---|
| Written inventory | Descriptions and aggregate coverage only | Can this establish initial buyer interest? |
| Reviewed sample | Selected approved records and stated purpose | What will the sample be used for and when removed? |
| Scoped export | A fixed, versioned package | Can we review everything before external transfer? |
| Live connector | Configured permissions and ongoing access | Which records can it read and how is access revoked? |
Source notes: Labelbox Prism: enterprise licensing and rights · NIST: Privacy Framework
Make the handover testable
Platform export options can depend on permissions and account configuration, as Slack’s documentation illustrates. Confirm the route is available and permitted for your situation; do not assume a standard export bypasses restrictions on reuse or training.
For an export, record the scope, package version, recipient and validation result. For a connector, record the granted scopes, identity, authorized duration and revocation owner. In either case, define what happens if the buyer asks for additional material so the scope cannot expand without review.
Source notes: Slack: exporting workspace data
Illustrative scenario · fictional company
A fictional support team starts with a reviewed sample
Brook Software is asked to discuss a support-history partnership. The team first provides an inventory and then a small approved package showing problem, internal reasoning and resolution. When the buyer asks for broader access, IT requests a permissions list and an export alternative. The business owner decides only after comparing the actual boundaries. This example does not assume that the buyer accepts an export or that read-only access would be unsuitable.
When to pause or narrow the scope
Client work and customer files are excluded from this starting scope. Assess company-owned internal records separately from personnel, health, privileged or NDA-restricted material.
- The requested access cannot be limited to the approved population.
- No one can explain the connector’s permissions or revoke its access.
- The export route or the proposed downstream use conflicts with applicable terms.
Your preparation checklist
- Ask what information is necessary for the next evaluation step.
- Offer an inventory or reviewed sample where sufficient.
- Compare actual export and connector boundaries.
- Approve the recipient, purpose, duration and removal process.
- Require a new scope review for requests for additional records.
Start with a description of the records. The quote form does not ask you to upload a dataset.
Discuss your dataSources and further reading
- Scale: data partnerships, criteria and data sources · Checked October 26, 2026
- Labelbox Prism: enterprise licensing and rights · Checked October 26, 2026
- NIST: Privacy Framework · Checked October 26, 2026
- Slack: exporting workspace data · Checked October 26, 2026
This is general information, not legal advice or confirmation that a buyer will accept your records. Published buyer ranges describe their programs, not an offer for your dataset. Buyers may pay QuoteMyData when a deal closes; see how we are paid.
