5. Prioritized Roadmap
The 5 gap buckets from Task 3, RICE-scored using the competitive urgency signal from Task 4, sequenced into roadmap horizons.
RICE Scoring
Each bucket scored on Reach (1-10), Impact (0.25-3), Confidence (%), and Effort (T-shirt size: S = 1, M = 2, L = 4, a relative weight and not a time estimate). RICE = (Reach × Impact × Confidence) / Effort.
| Bucket | Reach | Impact | Confidence | Effort (S/M/L) | RICE Score |
|---|---|---|---|---|---|
B1 · Real-Time Enforcement & ScaleTop Priority | 9 | 3 | 90% | L | 6.08 |
B2 · Pricing & Plan Flexibility | 7 | 2 | 80% | M | 5.6 |
B3 · Billing Cycle & Scheduling Constraints | 6 | 1.5 | 70% | M | 3.15 |
B4 · Data Integrity & Audit | 5 | 2 | 50% | M | 2.5 |
B5 · Subscription Lifecycle Operations | 3 | 1 | 80% | S | 2.4 |
Roadmap Horizons
Now
B1 · Real-Time Enforcement & Scale + B2 · Pricing & Plan Flexibility
B1 is the top RICE score and the entry ticket to Segments 1 & 3: billing competitors (Metronome, Orb) already publish ingestion at scale and give live balances, while hard-stop enforcement is being solved by separate runtimes (Stigg, Credyt). B2 goes with it because it removes the incompatibilities between usage billing and ramps, mixed frequencies, mid-term changes and overrides, and builds directly on B1's balance and limit model — together they make usage billing work end to end.
Later
B3 · Billing Cycle & Scheduling Constraints
B3 completes the core-engine work (calendar billing, backdating, trial metering with usage billing). It is enterprise-leaning and offers the least differentiation, but it finishes the job of making usage billing a first-class citizen of the subscription engine.
B4 (Data Integrity & Audit) and B5 (Subscription Lifecycle Ops) are intentionally not sequenced in this roadmap; their order relative to each other is left open. RICE inputs were revised after the competitor and dependency review: B2 and B3 reach rose, B3 impact rose (trial metering shares B1's enforcement model), and B4 confidence and B5 effort and confidence moved to reflect no proven UBB-3 solution and B5's dependency on B1. Scores are judgment-based inputs, not measured data.