BCX · v0.1-provisional
Build Cost Index
Track the attributable cost of producing qualified software, independent of output volume.
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.
DefinedEvidence
PendingPublication
Not established
- BCX — Build Cost Index
Measures the fully loaded cost of developing and delivering software that meets defined quality standards.
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
Measures the fully loaded cost of developing and delivering software that meets defined quality standards.
Unit: Index level (base period = 100)
Methodology — provisional, not validated
- Formula / method
- BCX(c,t) = 100 × (cost per qualified unit)(c,t) / (cost per qualified unit)(c,0)
- Inputs
- Attributable incremental production cost
- Qualified output units
- Shared-infrastructure allocation (counted once)
- Scope
- Per software class; both incremental and fully allocated cost variants are defined.
- S1–S5 class normalization (method only — no class comparison figures until validated observations exist)
- Cost per qualified unit is normalized within class to the class base period.
- Baseline
- First validated observation period per class = 100
- Limitations
- A falling BCX is a possible outcome, not an assumption — the index measures the frontier, it does not predict its direction.
- Shared-infrastructure allocation rules are provisional.
Version history & limitations
- v0.1-provisional2026-10-20Initial provisional definition drafted for research review. Not validated.