type: pattern tags: [hardware, rpo, backlog, demand-visibility, hyperscaler, connectivity, semiconductor, po-driven] confidence: medium created: 2026-03-31 source: CRDO stock-analysis 2026-03 persona: bert provenance: legacy source_analysis_path: null source_paragraph_quote: null source_transcript_span: null source_loss_log_path: null

Near-Zero RPO Ratio as Structural Demand-Visibility Risk in Hardware Companies

Hardware companies selling into AI data center infrastructure on short-cycle purchase orders may display exceptional trailing growth metrics while carrying near-zero forward demand certainty. When RPO (remaining performance obligations) is a fraction of a single quarter's revenue, the company has no contracted visibility beyond the current PO cycle. This creates asymmetric risk: trailing revenue growth looks like durability; forward demand is structurally opaque. This is the inverse of the contracted-backlog-as-guide-confidence pattern (AXON).

Evidence

• CRDO Q3 FY26: RPO of $33.9M against $407M quarterly revenue = 0.08x quarterly coverage. Despite 201% YoY growth and five consecutive beat-and-raise quarters, the company explicitly flagged this as its most significant vulnerability. Business operates on short-cycle POs from hyperscalers — no multi-year committed contracts, no FCB.
• Contrast: AXON Q4 FY25 FCB of $14.4B at 5.2x TTM revenue — guidance is effectively a revenue recognition schedule. CRDO's RPO/quarterly revenue of 0.08x means the same quarter's revenue is essentially uncontracted 90 days out.
• The risk materializes during hyperscaler capex pauses (DeepSeek shock, budget reallocations) or demand rescheduling — strong trailing metrics provide no protection because there is no backlog absorbing the shock.

Implication

For any hardware or connectivity company, calculate RPO/quarterly revenue as a demand-certainty ratio. Thresholds to watch:

• RPO < 0.25x quarterly revenue: near-zero visibility — treat forward growth as uncontracted and demand-dependent, not structural
• RPO 0.25–1.0x quarterly revenue: moderate visibility — one quarter of partial coverage
• RPO > 2x quarterly revenue (or FCB > 4x annual revenue): high visibility — backlog analysis replaces demand forecasting

When RPO < 0.25x quarterly revenue, apply a higher discount to forward estimates during periods of hyperscaler capex uncertainty, even if trailing beats are exceptional. Widening beat magnitude in this regime reflects real demand strength but not contractual certainty — size positions accordingly. The correct analytical move: track whether RPO is building (growing contract terms) or flat (permanent PO-cycle structure).