Reliance Industries LimitedReliance Intelligence · AI CloudConfidential — internal
GPU Cloud Billing Cockpit
Paper · optimal combination of pricing levers
Commercial Strategy · Pricing Science

Finding the Optimal Combination of Pricing Levers

Maximizing gross margin and revenue-weighted utilization across a depreciating GPU fleet.

Companion to the P&L primer, the strategy & GTM document, the compute futures memo and the billing cockpit.

Abstract

Gross margin on a GPU cloud is not set by a rate card. It is the output of four interacting commercial levers applied to different slices of the same physical fleet: how much capacity is sold as certainty, how much is multiplexed into tokens, how the perishable residual is priced and hedged, and how tightly the discount waterfall is governed. Optimizing any one lever in isolation moves revenue between slices rather than raising fleet margin.

This paper sets the unit cost floors from the cost stack, then walks the four levers in the order they must be decided, with the arithmetic for each threshold: the 60–75% take-or-pay anchor, the 21.3% token crossover density, the $2.10 hedge strike against a $1.70 spot clear, and the 237,442-token outcome-versus-metered crossover.

1. The four levers & cost floor baseline

No lever can be evaluated without the floors it must clear. From the cost stack in the primer, per GPU-hour:

Cost basis$ / GPU-hrComposition
Cash opex floor$0.485Power/cooling $0.243 + network $0.082 + software $0.094 + support $0.066
Fully loaded, ex-interest$1.495Cash opex $0.485 + 5-yr straight-line depreciation $1.010
Fully loaded, inc. interest$1.899$1.495 + $0.404 debt service @ 70% LTV, 8% interest

Gross margin % = (achieved $/GPU-hr − cost-to-serve $/GPU-hr) ÷ achieved $/GPU-hr.

  • Lever 1 — contract mixThe share of installed capacity sold as multi-year take-or-pay certainty versus held merchant.
  • Lever 2 — packagingWhether a given slice is sold as GPU-hours or multiplexed into tokens, endpoints and outcomes.
  • Lever 3 — dynamic priceThe sequential price path on residual capacity, plus the financial hedge on hours that would otherwise perish.
  • Lever 4 — discount governanceThe list-to-realized waterfall: what the desk is allowed to concede, and under what control.

2. The optimization walkthrough

The levers are decided in order, because each one sizes the slice the next one operates on.

┌────────────────────────────────────────────────────────────────────────┐
│ 1. Set Take-or-Pay Floor  ──► 2. Token Multiplexing ──► 3. RL Residual │
│    (60–75% @ $2.05/hr)         (Density > 21.3%)        & Futures Hedge│
└───────────────────────────────────┬────────────────────────────────────┘
                                    ▼
                         4. Discount Waterfall
                         (Cap leakage < 0.5%)

3. Step 1 — anchor 60%–75% of capacity in take-or-pay

Target rate: list $2.35, realized $2.05, hard floor $1.95 per GPU-hour. The role of this lever is not margin maximization — it is transferring utilization risk to anchor customers so that fixed depreciation is covered before any merchant hour is sold.

1,024-GPU cluster at 100% contract coverage ($45.3M capex)

LineValueNote
Gross revenue$18.84M / yr$2.05/GPU-hr realized
Cash EBITDA$14.49M76.9% margin over the $0.485 cash floor
Depreciation-$9.06M5-yr straight line, $1.010/GPU-hr
Interest-$2.54M70% LTV @ 8%
Pre-tax income$2.89M15.3% pre-tax net margin

Rule. Never let take-or-pay drop below 60% of installed capacity. Below that, fixed depreciation of $1.01/GPU-hr is spread across too few contracted hours and dilutes fleet gross margin regardless of how well the merchant book prices.

4. Step 2 — overlay token serving on flex capacity

Token serving is a multiplexing arbitrage: the same node is sold many times over to concurrent requests, so revenue per GPU-hour scales with traffic density rather than with the rate card.

InputValue
Output tokens$2.19 / M tokens
Input tokens$0.55 / M tokens
Cached input$0.055 / M tokens
Internal capacity transfer cost$2.10/GPU-hr = $16.80/node-hr (8×H100)
Throughput, 70B class~10,000 output tokens/sec = 36M tokens/node-hr
Revenue at 100% density$2.19/M × 36M = $78.84/node-hr ($9.85/GPU-hr)

Crossover density

crossover = $16.80 base cost ÷ $78.84 peak revenue ≈ 21.3%

At 60% traffic density the node earns $47.30/hr ($5.91/GPU-hr) — a 75.6% gross margin against roughly 33% on the same silicon sold as reserved capacity.

Rule. Route uncommitted capacity into token serving only when sustained traffic density is expected to exceed 21.3%. Below that threshold the endpoint destroys value relative to simply renting the node.

5. Step 3 — price the residual dynamically and hedge it

The remaining 15–25% of the fleet is spot and on-demand. Pricing here is sequential, not static: a customer priced out today defers and may return, so today's discount destroys tomorrow's price. That is the structure a contextual bandit exploits in the RL simulation tab.

CohortWillingness to payElasticityPatience
Anchor AI lab (burst)$2.900.90.25
Enterprise / BFSI$3.100.60.55
Developers / self-serve$1.902.40.70
Batch / research$1.601.60.85
  • Dynamic policyHold price at $2.40–$2.60 while the deferred-demand backlog is high; discount to $1.60–$1.80 only into soft demand weeks, to clear perishable hours above the $0.485 cash opex floor.
  • Hedge the tailShort compute index contracts on 30–35% of uncommitted volume at a $2.10 strike. If spot clears at $1.70 the hedge returns +$0.40/hr, holding cash EBITDA margin above 70%.
  • Never hedge the coreTake-or-pay hours are already fixed; hedging them converts a stable book into a speculative one.

6. Step 4 — govern packaging and discount waterfalls

Outcome versus metered pricing

Pricing an agent workflow at $0.52 per resolved task, against a token cost of $0.63/M and a metered list of $2.19/M:

crossover = ($0.52 ÷ $2.19) × 1,000,000 = 237,442 tokens per task

Sell outcome-based pricing for agent tasks consuming under 237k tokens, where it carries the higher margin; revert to metered token rates for long-context tasks above that line.

Waterfall discipline

StageValueControl
List$141.6MGoverned price book, versioned
Contracted$113.9MApproved standard discount bands
Realized$111.8MConcessions, credits and leakage

Cap non-standard concessions below 3% and enforce four-eyes database gates (control C-11) to prevent unapproved discounting. Target billing leakage below 0.5%.

7. Target optimal lever mix

Fleet sliceCommercial wrapperTarget realized rateUtilization targetExpected gross margin
60% – 75%Reserved take-or-pay$2.05 / GPU-hr100% (take-or-pay)27.1% (ex-interest)
15% – 25%Token-as-a-service$2.19 / M tok ($5.91/GPU-hr eq.)> 50% density68% – 75%
10% – 15%On-demand / RL spot / hedged$1.70 – $2.60 + $2.10 strike65% – 85%45% – 60%
Blended fleetMulti-tier portfolio$2.40 – $2.70 / GPU-hr eq.82% – 88% RWU50% – 58%

Illustrative synthetic economics, internally consistent but not any specific company's numbers.

8. Where to inspect and model this in the cockpit

  • Dynamic policies & cohort elasticityThe RL simulation tab on the cockpit.
  • Cluster hedge & payback sensitivityThe compute futures page.
  • List-to-realized discount waterfallsThe pricing & packaging tab on the cockpit.
  • Full unit-cost economics and worked P&LsThe P&L primer, sections 4 and 5.

All figures are illustrative — synthetic data built from public benchmarks, consistent with each other but not any specific company's economics.