The Index

← Website
Research preview — illustrative data · No official SPI index has been published
Find indexes, evidence & tools

CRX · v0.1-provisional

Commercial Readiness Index

Track whether qualified releases meet the commercial-readiness requirements of their class.

METHODOLOGY ONLYEvidence: UNVALIDATEDConfidence: U

Index and class measurements

Awaiting validated data

This index has a defined methodology but no validated observations yet. Values are published only after inputs are validated under the governance procedure — no illustrative figures are shown here.

Inputs
Defined
Evidence
Pending
Publication
Not established
  • CRX — Commercial Readiness Index

    Evaluates whether software meets the requirements for secure, supported commercial deployment.

    Status: METHODOLOGY ONLY · Awaiting validated data

    Availability: Awaiting validated data — no series drawn.

    Evidence: UNVALIDATED

  • S1 · Utility Software

    Narrow functionality, limited integration, low operational criticality.

    Examples: A file-conversion utility; a standalone calculator.

    Complexity, integrations and operational demands change production effort and quality requirements; compare like-for-like software within its class, not raw costs across classes. Examples illustrate scope, not automatic class assignments.

    Status: METHODOLOGY ONLY

    Availability: Awaiting validated data — no series drawn.

    Evidence: UNVALIDATED

  • S2 · Commercial Applications

    Customer-facing products, persistent data, defined commercial workflows.

    Examples: An online booking application; an e-commerce storefront.

    Complexity, integrations and operational demands change production effort and quality requirements; compare like-for-like software within its class, not raw costs across classes. Examples illustrate scope, not automatic class assignments.

    Status: METHODOLOGY ONLY

    Availability: Awaiting validated data — no series drawn.

    Evidence: UNVALIDATED

  • S3 · Enterprise Platforms

    Multiple roles, enterprise workflows, integrations, operational controls.

    Examples: An enterprise resource-planning platform; an integrated customer-management platform.

    Complexity, integrations and operational demands change production effort and quality requirements; compare like-for-like software within its class, not raw costs across classes. Examples illustrate scope, not automatic class assignments.

    Status: METHODOLOGY ONLY

    Availability: Awaiting validated data — no series drawn.

    Evidence: UNVALIDATED

  • S4 · Critical Infrastructure

    Elevated security, reliability, governance or regulatory requirements.

    Examples: A payment-processing system; an operational infrastructure-control system.

    Complexity, integrations and operational demands change production effort and quality requirements; compare like-for-like software within its class, not raw costs across classes. Examples illustrate scope, not automatic class assignments.

    Status: METHODOLOGY ONLY

    Availability: Awaiting validated data — no series drawn.

    Evidence: UNVALIDATED

  • S5 · Composite Systems

    Multiple integrated products or services with substantial orchestration.

    Examples: A multi-product enterprise ecosystem; an orchestrated logistics network.

    Complexity, integrations and operational demands change production effort and quality requirements; compare like-for-like software within its class, not raw costs across classes. Examples illustrate scope, not automatic class assignments.

    Status: METHODOLOGY ONLY

    Availability: Awaiting validated data — no series drawn.

    Evidence: UNVALIDATED

No validated observations are available for this index or its class comparisons. Selection never creates a series.

What this index will measure

Evaluates whether software meets the requirements for secure, supported commercial deployment.

Unit: To be defined

S1UtilityAwaiting data
S2CommercialAwaiting data
S3EnterpriseAwaiting data
S4CriticalAwaiting data
S5CompositeAwaiting data
Methodology — provisional, not validated
Formula / method
Under definition — commercial-readiness criteria per class not yet finalized
Inputs
  • Commercial-readiness gate results
  • Release inventory per class
Scope
Per software class, pending finalized readiness criteria.
S1–S5 class normalization (method only — no class comparison figures until validated observations exist)
To be defined with the readiness criteria.
Baseline
To be defined
Limitations
  • Readiness criteria vary by market context; a single cross-class scale may not be defensible.
Version history & limitations
  • v0.1-provisional2026-10-20Initial provisional definition drafted for research review. Not validated.

Continue your research