Back to News
Market Impact: 0.15

PagerDuty, Inc. (PD) Q3 2026 Earnings Call Transcript

PDMS
Corporate EarningsCorporate Guidance & OutlookCompany FundamentalsManagement & GovernanceAnalyst InsightsInvestor Sentiment & PositioningTechnology & Innovation
PagerDuty, Inc. (PD) Q3 2026 Earnings Call Transcript

PagerDuty held its Q3 FY2026 earnings conference call on November 25, 2025, with CEO Jennifer Tejada and CFO Howard Wilson participating alongside sell‑side analysts; the excerpt contains the participant list and the customary forward‑looking statements and non‑GAAP disclosure notice. The provided text does not include any reported revenue, earnings, margins or guidance — investors should consult the company's earnings release and the investor relations site for the quantitative results and management commentary to assess near‑term fundamentals and guidance.

Analysis

Market structure: PagerDuty (PD) is positioned as a mission‑critical SaaS workflow for incident response, so winners from stable trends are cloud-native infra teams, observability partners and managed service providers that integrate PD. If PD sustains ARR growth north of ~15–20% and net retention >110% over the next two quarters, it will gain pricing power vs. lower‑end alerting tools; conversely, broad enterprise IT spend cuts or aggressive bundling by hyperscalers would be direct negatives. Cross‑asset: a meaningful guidance miss would pressure high‑beta software names, lift short‑end US rates volatility in corporate credit, and widen IG tech bond spreads over 3–6 months. Risk assessment: Tail risks include a major security incident, loss of a top 3 customer accounting for >5–10% of revenue, or enterprise budget freezes that could drop ARR growth by >500–800 bps within a year. Immediate (days) risk is a volatile post‑earnings repricing; short‑term (weeks/months) risk centers on analyst downgrades and churn signals; long‑term (quarters/years) risk is competitive displacement or failure to convert usage into expansion revenue. Hidden dependencies: large‑account concentration, integrations with observability stacks, and dependence on platform uptime — monitor 90‑day logo churn and top‑10 customer revenue share. Trade implications: Direct play — establish a 2–3% long position in PD within 3–7 trading days if management reconfirms FY guidance or beats ARR growth; add on pullback >10%, trim into strength toward a 12‑month target of +30–40% if net retention >110%. Hedge / protection — buy 3‑month ATM puts or a 1:1 collar if owning; triggers: buy puts if next quarter ARR guidance misses by >150 bps. Pair trade — long PD (1.5% portfolio) vs short DDOG (Datadog) same notional for 6–12 months to express relative value between incident‑response SaaS and observability premium valuation. Contrarian angles: Consensus may underprice PD’s margin expansion potential from scaling SaaS gross margins and lower sales efficiency cash burn; a 200–400 bps improvement in non‑GAAP operating margin over two quarters could be underestimated. Conversely, the market may be complacent about multi‑year usage risk (historical parallel: usage‑dependent SaaS re‑rates like TWLO), so downside can be quick if expansion ARR stalls. Unintended consequence: aggressive cost cuts to protect margins could slow product cadence and reduce long‑term ARR visibility — validate by tracking R&D spend cadence and large deal ramp timing over the next 90 days.