Rgl8r Pricing Strategy V3

# RGL8R Pricing Strategy v3 (Snapshot Extract)
 
Source artifact: `/Users/dan/rgl8r-platform/RGL8R_Pricing_Strategy_v3.docx`  
Snapshot date: 2026-03-03  
Scope: internal strategy input for launch pricing decisions
 
---
 
## 1. Executive Positioning (from v3)
 
- Recommended model: hybrid pricing:
  - usage-based metering for high-volume API operations,
  - gain-share for recovered SHIP value,
  - fair-use limits on read/discovery endpoints.
- Packaging recommendation:
  - Sandbox (free, capped),
  - Professional (committed minimum + usage),
  - Enterprise (custom contract + negotiable gain-share).
- SHIP pricing anchor:
  - `15%` gain-share is positioned as competitive versus traditional full-service auditors.
 
## 2. Competitive Benchmark Confidence Rubric (adopted)
 
The v3 strategy uses mixed evidence quality. For launch and publication safety, apply this rubric:
 
- `Verified`: official vendor pricing pages or official product documentation.
- `Estimated`: industry benchmark ranges where vendor pricing is not publicly confirmed.
- `Third-party`: reviewer/analyst/forum-reported values not confirmed by the vendor.
- `Modeled`: internal cost-to-serve or margin simulations.
 
Public-facing docs and pricing pages should use:
 
- verified numbers, or
- qualitative comparison language.
 
Estimated, third-party, and modeled figures remain internal unless clearly caveated.
 
## 3. Launch-Safe Commercial Guardrails
 
- SHIP default gain-share remains `15%`.
- Negotiated enterprise range remains `10%` to `15%`.
- Do not approve below `10%`.
- If discounting below `15%`, require explicit approval and documented forecast.
- Keep `CREDITED + confirmation payload` as the only billable SHIP trigger.
 
## 4. Billing Integrity Alignment
 
The v3 strategy table uses legacy wording in one section (`creditReference`).
Canonical implementation and operator docs now use:
 
- `confirmation.source`
- `confirmation.referenceId`
- `confirmation.confirmedAt`
 
Reference docs:
 
- `docs/BILLING_TRIGGERS.md`
- `docs/runbooks/ship-billing-controls.md`
- `docs/runbooks/ship-claims-operations.md`
 
## 5. What Was Not Adopted for Launch
 
- Hard-coded public ROI statistics that can go stale.
- Public publication of estimated competitor price ranges.
- Launch commitments that depend on unshipped features.
 
## 6. Follow-up Plan Mapping
 
- Pricing policy hardening: `P19-D`, `P19-E` supporting docs work.
- Self-serve + billing execution: `P17`, `P18` (already merged).
- Ongoing strategy-to-plan synchronization tracked in:
  - `docs/strategy/README.md`
  - `docs/strategy/CHANGELOG.md`