Will Spirent-attributed revenue exceed $50M in Q3 FY2026 (full 13-week quarter)?

Spirent's $200M annual run rate implies ~$50M per 13-week quarter. Q2 generated $43M in ~10 weeks, which annualizes to ~$224M — actually above the $200M run rate. The Q2 miss was partially a reporting artifact of fewer weeks. With a full 13-week contribution and government orders normalizing post-holiday, hitting $50M is mathematically straightforward. However, integration friction and the Consolidation Calibrator's MIXED assessment introduce execution uncertainty.

The $200M run rate was revised upward from $188M, which could reflect management optimism rather than demand reality. Q2's $43M miss (below even the low end of $45M) is a data point that shouldn't be dismissed solely as timing. Integration of three Spirent product lines (HSE, network security, channel emulation) is complex. The 5% headcount reduction may also temporarily disrupt go-to-market execution. The question asks specifically for >$50M — at the exact boundary of the $200M run rate.

The math favors YES: $43M/10 weeks = $4.3M/week; 13 weeks × $4.3M = $55.9M. But per-week extrapolation assumes linearity, which is unrealistic for enterprise test equipment. Government contracts are lumpy. The unresolved debate between timing vs. integration friction means this is genuinely uncertain. I weight the timing explanation slightly because management revised the run rate UP to $200M even after the miss, suggesting pipeline visibility.

The simplest analysis: Q2 was a partial quarter. $43M in 10 weeks extrapolates to $56M over 13 weeks. Even accounting for lumpiness, getting above $50M requires only matching the weekly run rate. Management wouldn't have revised the annual run rate to $200M if Q3 orders weren't tracking. Government order timing post-holiday should normalize. The restructuring removes $16M of Spirent synergy costs — this helps, not hurts, revenue attainment.

The Q2 miss should not be handwaved away. Management guided $45-55M and delivered $43M — that's a miss on a brand-new acquisition, which signals either forecasting inaccuracy or demand issues. Integration of acquired product lines typically sees a revenue dip in the first 2-3 quarters as sales teams restructure. The 5% headcount reduction adds noise. I anchor on the bottom of the range and give only modest credit for the full 13-week quarter.

Near coin-flip. The timing explanation for Q2 is plausible (December quarter = holidays + government fiscal year dynamics), but integration risk is real. Spirent's products (HSE, network security, channel emulation) serve the data center market which VIAV is bullish on, so end-market demand should be supportive. The question is whether the sales channel integration is smooth enough to capture that demand. I give slight edge to YES because the weekly run rate was above $50M/quarter pace.

Full 13-week quarter vs. 10-week partial is a significant tailwind. $43M in 10 weeks = $4.3M/week rate. At that rate, 13 weeks = $55.9M. Even with some integration friction, exceeding $50M is more likely than not. Management raised the run rate estimate, suggesting confidence.

Q2 came in below expectations, and it's the first data point for the acquired business. One quarter of data is insufficient to assess whether timing or integration is the driver. True uncertainty — near 50/50.

The mechanics favor YES — more weeks of contribution, government order timing normalization, and management confidence in run rate. But this is a recently acquired business with limited track record under VIAV ownership. Slight lean toward YES based on extrapolation.