1. Standardized MSP Service Catalog (vendor-neutral by design)

A vendor-neutral service framework built from:

• The Info-Tech Management & Governance Framework (Info-Tech + COBIT) mapped for SMB-focused MSPs
• Cross-validation against MSP 501 service offerings
• Structured normalization so service definitions are consistent and reusable

Structure:

• 6 Service Categories
• 30 Subcategories
• 125 Service Line Items

Each service line item includes:

• Description
• Pain Points
• Business Value
• Ideal Customer Profile
• Benefits

Service definitions are intentionally product-agnostic. Products are not baked into services—services stay stable while tools evolve.

2. Vendor & Product Catalog

The Vendor & Product Catalog contains:

• 1,318 Vendors
• 2,339 Products
• 20 standardized product categories

Each vendor includes:

• Three description lengths (long / medium / short):
  • Short: tagline-style identification for lists and cards
  • Medium: quick summary of what they do and who they serve
  • Long: a fuller vendor profile for detail pages and evaluation
• Official website reference (used as the canonical identity anchor)
• Standardized naming to reduce duplicates and improve matching across integrations

Each product includes:

• Three description lengths (long / medium / short) using the same intent (tagline → summary → fuller profile)
• Dedicated product URL (best-effort maintained)
• Exactly one primary product category (chosen based on the product's core MSP value proposition)
• Structured mapping to MSP service line items, including a support label and confidence signal

Inclusion criteria (important):

Only separately licensable software products are included (standalone SKU/billing + dedicated product presence). The dataset excludes:

• Services (MDR/SOC, training, support, professional services)
• Feature tiers and configuration variants of the same product
• Bundled modules without independent licensing
• Infrastructure-native cloud management components (generally excluded to avoid noise)

3. Product → Service Mapping

Each product is evaluated against the MSP Service Catalog using structured mapping logic. Mappings include:

supportLabel (choose one):

• Native — the product is the primary tool that directly delivers the service outcome
• Integrated — supports delivery through a typical integration workflow (handoff/sync/evidence)
• Partial — supports part of the service; other tools and/or manual work required
• Adjacency — related, but not in the delivery workflow for the outcome

evidenceScore (confidence signal):

• 100% — direct, obvious match
• 75% — strong match, one key detail uncertain
• 50% — plausible match; inference required
• 25% — weak support but commonly adjacent in MSP practice

This mapping layer allows applications to:

• Identify which products support which services
• Analyze service coverage gaps
• Model MSP stack alignment against a stable service framework
• Power StackPilot-style workflows where clarity scales with growth