Marketplace/Asset #1741IN DILIGENCE

AI data asset · anonymous listing

#1741

ServiceNowJiraMicrosoft 365Slack
AI Data Asset Score9 interested parties
75/100
Potential data value
Assessment available after diligence
Licensing readiness
REVIEW REQUIRED
Preferred structure
Restricted-environment evaluation only
Data room

Seller identity is never disclosed at this stage. Introduction requires buyer qualification, seller approval and executed confidentiality.

Data overviewListed 2026-02-25
Industry
IT / MSP
Region
Canada
Company size
50–100 employees
Years operating
30+
Historical data
13 years
Estimated records
3.2M+ records
ERP
QuickBooks
CRM
HubSpot
Approx. employees
74
Data types3 categories
  • Support Tickets
  • Engineering Workflows
  • Invoices
Workflow familiesDepth: excellent
  • Ticket triage and routing
  • Change and patch approval
  • Root-cause investigation
  • Client reporting

Cross-system connectivity

ServiceNow → Jira → Microsoft 365

Score composition75 / 100

Volume

3.2M+ records in scope.

78

weight 12

Historical depth

13 continuous years of operating history.

86

weight 12

Workflow complexity

Multi-step decisions with real exception handling.

69

weight 12

Cross-system connectivity

Records join across 4 systems on shared keys.

63

weight 11

Uniqueness

IT / MSP operational reasoning is scarce in open corpora.

70

weight 10

Data quality

Structured fields are strong; free-text completeness varies by year.

74

weight 9

Outcome labels

Outcomes are recoverable from downstream records.

92

weight 9

Industry value

Active buyer demand for it / msp agents.

85

weight 8

AI-agent relevance

Tool-using, multi-system workflows suit agent training and evaluation.

71

weight 8

Licensing readiness

Client agreements require consent for reuse.

57

weight 5

Privacy / de-identification complexity

Client user identities in tickets.

71

weight 4

Why this asset scored 75

This it / msp asset covers 13 years of ticket triage and routing and related decisions across ServiceNow, Jira, Microsoft 365. Scarcity is the strongest factor: this class of operational reasoning is largely absent from public corpora. The score is held back by de-identification work on party identifiers and uneven free-text completeness in earlier years.

Potential AI applications
  • Support deflection
  • Vertical AI agents
  • Evaluation benchmarks
Data rights & provenanceNot a legal determination

Ownership

Company-generated operational records in owned tenants.

READY

Source systems

ServiceNow, Jira, Microsoft 365, Slack.

READY

Third-party data

OEM vendor case notes.

REVIEW REQUIRED

Customer / client data

Client user identities in tickets.

REVIEW REQUIRED

Employee data

Approver identities appear in workflow audit trails.

REVIEW REQUIRED

Potential PII

Names and work contact details appear in free text.

REVIEW REQUIRED

Contract restrictions

Client agreements require consent for reuse.

REVIEW REQUIRED

Licensing permissions

Pending rights review.

NOT VERIFIED

Retention period

13 years retained; no scheduled destruction.

READY

Geographic restrictions

Canada operations only.

READY

Intended AI use

Seller prefers training plus evaluation, no resale.

REVIEW REQUIRED

De-identification requirements

Entity and person pseudonymisation required pre-sample.

REVIEW REQUIRED

Status indicators reflect seller-reported information and SentryRights screening only. No asset is represented as legally licensable until rights and privacy diligence is completed with the seller and, where applicable, its counsel.

Demo data — illustrative sample listings, not live marketplace records

Data readiness
Volume
MODERATE
Historical depth
HIGH
Workflow complexity
MODERATE
Cross-system connectivity
MODERATE
Industry uniqueness
MODERATE
Data quality
MODERATE
Outcome labels
HIGH
PII risk
MODERATE
De-identification difficulty
MODERATE
Licensing readiness
REVIEW REQUIRED
Introduction process
  1. 1

    Buyer submits request

    Identity, funding stage and entity are verified before the request moves.

  2. 2

    Buyer provides intended use

    Specific model, application and downstream distribution limits stated in writing.

  3. 3

    Platform reviews buyer

    SentryRights qualifies the buyer and screens the intended use against seller preferences.

  4. 4

    Seller receives request

    Seller sees the buyer profile and intended use while remaining anonymous.

  5. 5

    Seller approves or declines

    No identity is disclosed without an explicit seller approval.

  6. 6

    NDA / confidentiality

    Mutual confidentiality executed through the platform.

  7. 7

    Identity revealed

    Counterparties are introduced only at this point.

  8. 8

    Data diligence begins

    Rights review, privacy review and de-identification are coordinated by SentryRights.