Document RA-WP-001 · Version 1.0 · January 2026
Platform Architecture & Pricing Methodology
Transparent pricing based on industry-typical baseline models, conservative improvement deltas, and value-aligned subscription structures.
1. Purpose
This document provides a transparent view of Reality Anchors pricing assumptions, baseline models, and subscription structures. Its purpose is to support buyer due diligence, provide contractual stability, and establish a clear causal link between platform value delivery and subscription cost.
Pricing is not based on self-reported scrap rates or percentage-of-savings models. Instead, it references industry-typical ranges and applies conservative deltas to arrive at a modeled value from which subscription tiers are derived.
2. Baseline Model Assumptions (Scrap + Rework)
Segment classifications and baseline scrap/rework rates are modeled from industry-typical ranges. All rates are conservative mid-points intended for pricing illustration, not guaranteed outcomes.
| Segment | Scrap range | Scrap model baseline | Basis |
|---|---|---|---|
| Small commercial shop | 6–10% | 8.0% | Mid-point, conservative |
| Prefab yard | 4–7% | 5.5% | Mid-point, conservative |
| Industrial | 2–5% | 3.5% | Mid-point, conservative |
| Rework metric | Industry range | Model baseline | Basis |
|---|---|---|---|
| Fabrication remake rate (% of pieces) | 1.0–3.0% | 1.5% | Conservative benchmark midpoint |
| Blended remake cost per affected piece | $8–$40 | $20 | Material + labor + bench disruption allowance |
Contracts reference the baseline model version number for contractual stability.
3. Conservative Improvement Deltas
Improvement deltas represent modeled reduction targets for scrap and preventable rework based on structured workflow enforcement. Values are set conservatively for pricing purposes and are not guaranteed outcomes.
| Segment | Baseline | Conservative delta | Post-deployment model |
|---|---|---|---|
| Small commercial shop | 8.0% | 2.0 pts | 6.0% |
| Prefab yard | 5.5% | 1.5 pts | 4.0% |
| Industrial | 3.5% | 1.0 pt | 2.5% |
| Rework metric | Baseline | Conservative delta | Post-deployment model |
|---|---|---|---|
| Remake rate (% of pieces) | 1.5% | 0.8 pts | 0.7% |
| Relative improvement | — | 40–70% | Steady-state target band |
4. Value-Aligned Subscription Structure
All tiers are priced per bench, per month. Pricing scales with execution complexity and governance requirements, keeping the value proposition clear at every level.
| Tier | Monthly per bench | Notes |
|---|---|---|
| Pilot | $1,200 | Solo operators and small crews |
| Production | $3,200 | Fabrication yards and multi-bench shops |
| Enterprise | $4,800 | High-volume plants with ERP integration |
| Device Add-Ons (per device, any tier) | ||
| Context Camera | $200/device/mo | Wider coverage, multi-angle capture |
| LiDAR-Equipped Device | $450/device/mo | Sub-mm precision depth |
Final pricing depends on bench count, instrumentation scope, calibration governance requirements, and multi-project optimization complexity.
5. Plan Designations and Enforcement Status
Public pricing uses "included in [Plan]" language to show the intended commercial boundary for each capability. Where product-level gates are still rolling out, that status is disclosed here rather than implied away.
| Capability | Included in | Enforcement status | Current note |
|---|---|---|---|
| AR Execution Guidance | Pilot, Production, Enterprise | Available now | Core workflow module already live across plans. |
| Daily Dashboards | Pilot, Production, Enterprise | Available now | Core reporting module already live across plans. |
| Analytics & QA | Production, Enterprise | Progressive enforcement | Public plan designation is live; feature-gate wiring is still rolling out. |
| Custom Calibration | Production, Enterprise | Progressive enforcement | Custom profile gating is documented but not fully wired yet. |
| Compliance Export | Enterprise | Progressive enforcement | Enterprise designation is public; export gating is still being wired. |
| Audit Trails | Enterprise | Progressive enforcement | Enterprise designation is public; access enforcement is still rolling out. |
FAQ: Why use "included in" before every gate is enforced?
Because the pricing page is describing the commercial plan boundary, not claiming that every entitlement check is already complete. The enforcement note makes the rollout state explicit so buyers can see both the intended plan designation and where gate wiring is still in progress.
6. Governance & Compliance Framework
Versioning
- ›Baseline model versioned and referenced in contracts
- ›Regime releases after internal QA review
- ›Machine calibration profiles versioned
- ›Subscription tier recalibration at 60-day window
Auditability
- ›Immutable event streams
- ›Per-run scrap and time reports
- ›Exception registry for drift and overrides
- ›Role-based access controls