Earnings preview · AI security spend moves from narrative to renewal math
The investable signal isn’t “AI security exists” — it’s whether Zscaler’s billings engine speeds up
Investors can hear plenty about AI security roadmaps in any cybersecurity earnings call. The harder—and rarer—proof is whether new AI-oriented capabilities convert into faster contract starts, upgrades, and renewals that show up in quarterly revenue plus billings-linked metrics like deferred revenue and remaining performance obligations.
For Zscaler, the “billings” question matters because its business model is contract-driven and recognition is lumpy: deferred revenue captures prepayments and billed fees that will be recognized later. Remaining performance obligations (RPO) is the forward backlog that can become future revenue as customers consume the service. When investors say “AI security should show up in billings,” they’re really asking whether these mechanics accelerate after customers decide they need AI-grade protections.
What changed in the market bar
CrowdStrike’s agentic-cyber beat puts a higher bar on conversion speed
The “agentic cyber” discussion moved from marketing to measurable pull-through when CrowdStrike showed strength in its most contract-sensitive reporting sections, including deferred revenue behavior tied to billing/prepayment mechanics.
| Company | What to watch | What the filing actually discloses |
|---|---|---|
| CrowdStrike | Deferred revenue level and movement | Total deferred revenue and how it moves during the quarter (which reflects invoicing/prepayments vs. revenue recognition) |
| Zscaler | Deferred revenue level and movement + RPO trajectory | Balance sheet deferred revenue (current/noncurrent) and forward backlog proxy for future revenue |
On CrowdStrike’s most recent disclosures in this window, the company reports deferred revenue totals and discusses that billed fees/prepayments sit in deferred revenue until revenue recognition criteria are satisfied. The practical investor takeaway: if “agentic cyber” is real demand, the billing motion should appear as sustained deferred revenue and supportive recognition patterns rather than just conference-call language.
Zscaler’s contract math baseline
Zscaler already has a large deferred-revenue structure — the quarter-level issue is whether it accelerates
Revenue (fiscal Q3’26)
$850.5M
Quarter ended Apr 30, 2026, reported May 26, 2026
Revenue (fiscal Q2’26)
$815.8M
Quarter ended Jan 31, 2026, reported Feb 26, 2026
Deferred revenue (as of Apr 30, 2026)
$2.48B
Reported in Zscaler’s SEC filing for the quarter ended Apr 30, 2026
Deferred revenue split (current vs. noncurrent)
$2.10B / $0.38B
Current $2,097.1M; noncurrent $380.1M as of Apr 30, 2026
Zscaler’s deferred revenue base is already substantial, which means the bar is not “will deferred revenue exist?” It’s whether the next filing shows an improving billings-to-revenue bridge (deferred revenue sustaining while revenue continues to grow). If Zscaler’s AI-oriented products are converting faster, you’d expect supportive revenue growth alongside stable or strengthening deferred revenue dynamics.
In the most recent quarter-end disclosure available here, Zscaler reported deferred revenue of $2.4772B as of Apr 30, 2026, with $2.0971B current and $0.3801B noncurrent. That’s the baseline contract liability investors use to judge how much future work is already paid-in vs. yet to be recognized.
Earnings preview lens
The “AI security shows up in billings” test for Zscaler’s late-August report
- Look for whether revenue growth rate holds or re-accelerates versus the prior two fiscal quarters (fiscal Q2’26 to Q3’26). Revenue stayed near the same run-rate window, so re-acceleration would be the tell.
- Check deferred revenue movement (balance sheet change from prior quarter end). If deferred revenue rises faster than revenue, it usually signals more billings ahead of recognition.
- Track RPO trajectory in the earnings materials or accompanying disclosures. RPO strength is the forward “billings reservoir” before it becomes recognized revenue.
- Separate “AI narrative” from product packaging: Zscaler’s reported revenue is still the final accounting endpoint, so investors need corroboration in billings-linked disclosures, not just product names.
Supply-chain aware: where AI security conversion actually comes from
Why the billings conversion pathway runs through telemetry, identity, and workload enforcement
Even though “AI security” sounds like a standalone product category, the billings conversion typically depends on three supply-chain layers that Zscaler participates in: (1) the telemetry/control plane that sees risky behavior, (2) identity and policy enforcement that stops it, and (3) workload-to-workload segmentation for modern deployments. If those layers get adopted as part of a broader customer rollout, AI capabilities ride along as upgrades or add-ons.
That’s why deferred revenue and RPO are the investor’s shortcut. They compress time: contract signing and billed usage arrive before revenue recognition. If agentic-cyber demand is truly converting to spend, it should show up as more contract starts and upgrades that increase the future recognition pipeline—exactly what deferred revenue and RPO are designed to reflect.
Fundamentals check (what the numbers already imply)
Zscaler’s revenue scale is growing, but investors should still demand faster forward visibility
From the quarterly income statement data available for the latest three quarters in this window, Zscaler reported revenue of $788.1M (fiscal Q1’26), $815.8M (fiscal Q2’26), and $850.5M (fiscal Q3’26). That progression implies continued demand, but it also sets the benchmark: the late-August report needs to show whether AI security conversion is lifting growth rate or simply sustaining it.
| Fiscal quarter | Revenue | Reported |
|---|---|---|
| Q1 FY2026 | $788.1M | Nov 25, 2025 |
| Q2 FY2026 | $815.8M | Feb 26, 2026 |
| Q3 FY2026 | $850.5M | May 26, 2026 |
Horizons for investors
Short-term catalyst: billings-linked disclosures; long-term bet: AI upgrades sustaining renewals
Short-term (days to the next quarter): Zscaler will likely move the stock on whether its revenue growth and billings-linked indicators (deferred revenue movement, RPO) confirm AI/security conversion speed. Long-term (1–3 years): the market will care whether AI-oriented upgrades become embedded in renewal cycles—meaning customer retention and contract expansion show up in consistently strengthening forward backlog.
Synthesis: the thesis in one line
Zscaler’s AI-security upgrade story is only investable if the accounting pipeline looks like agentic-cyber demand
The core question isn’t whether Zscaler can describe AI risk controls. It’s whether, after the market’s agentic-cyber proof point from CrowdStrike, Zscaler’s next disclosures show faster conversion from billed contracts into revenue visibility. The late-August quarter is where “narratives” must translate into the mechanics investors can model.
Listed companies most directly exposed to the AI-security billings conversion question
- Sustains revenue growth from Q1 FY2026 through Q3 FY2026, setting a benchmark for whether AI/security conversion re-accelerates in the late-August report.
- Deferred revenue base is $2.48B as of Apr 30, 2026; stronger-than-normal movement would signal more billings ahead of recognition.
- If RPO confirms backlog acceleration, Zscaler can pull forward future revenue recognition rather than relying on narrative upgrades.
- Deferred revenue mechanics demonstrate how billed/prepaid arrangements become recognized revenue, setting the bar for “agentic cyber” conversion into contract-sensitive reporting.
- If deferred revenue behavior remains supportive, it implies durable upgrade/renewal demand rather than one-off project spend.
- CrowdStrike’s performance shifts expectations across peers, increasing the probability that Zscaler is judged on similar billings-to-revenue evidence.
- As a diversified security platform, Palo Alto can convert AI-era security spend across multiple products; however mix and execution risk can blur billings signals.
- If platform-level subscription renewals remain strong, it can buffer revenue growth even when standalone AI adds are slower.
- If customers consolidate security vendors, Palo Alto’s billings may strengthen; if not, AI security budgets may shift toward pure-play execution.
- Fortinet’s packaging and global channel footprint can turn AI-security demand into measurable renewals, but channel timing can delay billings signals into the next quarter.
- If backlog/contract liability metrics expand in line with AI-driven security upgrades, Fortinet may benefit via faster recognition.
- If AI-security budgets concentrate in cloud-first models, Fortinet could face mix pressure despite stable core demand.
- Cloudflare is exposed to how quickly enterprises adopt AI-era security controls at the edge, but evidence timing can differ from Zscaler’s zero-trust model.
- If Cloudflare shows faster contract starts through deferred revenue/RPO-like indicators, it would support a sector-wide AI-security conversion thesis.
- If results lag, it would imply AI security is still narrative-heavy across some cloud security budgets.
