PagerDuty Expanded from Incident Alerting to $467.5M Operations Cloud by Building AIOps Platform Across Customer Base
PagerDuty grew revenue 26% to $467.5M and $100K+ ACV customers 25% by expanding alerting into an AIOps Operations Cloud.
PagerDuty, Inc., a Enterprise Cloud Infrastructure & DevOps company, created value through Packaging and Bundling and Customer Expansion.
PagerDuty is a digital operations management company providing the Operations Cloud — a platform integrating incident response, AIOps, automation, and stakeholder communications for technology-driven enterprises. Founded in 2009 and headquartered in San Francisco, PagerDuty established its market position as the dominant on-call alerting and incident management tool used by DevOps, SRE, and IT operations teams at over 14,000 companies. PagerDuty went public in April 2019.
By FY2023 (ended January 31, 2023), PagerDuty faced a strategic inflection: its core incident alerting product had reached near-saturation within its existing customer base, and point-solution alerting vendors (OpsGenie, VictorOps) plus hyperscaler-native monitoring services represented commoditization pressure from below. Net Revenue Retention Rate, which had peaked above 125% in FY2021 during the pandemic-era digital acceleration, had declined to approximately 119% by FY2023 as expansion opportunities within the alerting product became constrained (PagerDuty 10-K FY2023, p. 59). Total revenue in FY2023 was $370.8M, representing 31.5% growth, but growth was decelerating.
The trigger for PagerDuty's platform expansion was the recognition that incident management represented only the reactive layer of a broader opportunity in operations intelligence and automation. AI/ML capabilities could transform PagerDuty from a notification routing tool into a proactive operations intelligence platform — expanding the addressable problem and justifying enterprise-tier pricing.
PagerDuty executed a platform expansion strategy between FY2022 and FY2025 centered on three levers: building AIOps capabilities into the core platform, expanding the Operations Cloud product suite, and reorienting enterprise sales toward multi-product platform deals.
Lever 1: AIOps and machine learning integration. PagerDuty acquired Catalytic in 2021 (process automation) and Rundeck (operations runbooks/automation) to add automation capabilities alongside its ML-driven noise reduction. PagerDuty's Intelligent Alert Grouping, Event Intelligence, and AIOps capabilities used machine learning to correlate related alerts, suppress noise, identify root causes, and surface predicted issues before they generated customer impact. These capabilities transformed the PagerDuty value proposition from alert routing to intelligent operations — addressing the alert fatigue crisis that affected DevOps and SRE teams at scale.
Lever 2: Operations Cloud suite expansion. PagerDuty built out the Operations Cloud as a multi-product platform: PagerDuty Incident Management (core alerting), PagerDuty AIOps (ML-driven operations intelligence), PagerDuty Automation Actions (runbook automation), PagerDuty Process Automation (workflow orchestration), PagerDuty Status Pages (stakeholder communication), and PagerDuty Customer Service Operations (connecting technical incidents to customer-facing teams). Each product expanded the platform's footprint from purely technical users (SRE, DevOps) into adjacent organizational functions (customer success, business operations).
| Metric | FY2023 | FY2025 |
|---|---|---|
| Total revenue | $370.8M | $467.5M (+26.1%) |
| $100K+ ACV customers | 681 | 849 (+24.7%) |
| Net Revenue Retention | ~119% | ~106% |
| Non-GAAP operating income | — | $82.7M |
| Subscription revenue share | — | >90% |
NRR compression from 119% to 106% reflects deliberate SMB customer optimization — fewer, larger enterprise accounts generating better unit economics.
PagerDuty's challenge entering FY2023 was a classic point-solution maturity problem: the core incident alerting product had high penetration in its market, and NRR had declined from above 125% to 119% as expansion opportunities within existing alerting deployments ran out. The Operations Cloud expansion (AIOps, Automation Actions, Process Automation, Status Pages, Customer Service Operations) was the revenue growth response — each product extended PagerDuty's addressable problem from reactive alerting to proactive operations intelligence and organizational communication. The 24.7% growth in $100K+ ACV customers from 681 to 849 quantifies the enterprise upsell working: accounts that once bought alerting were adding AIOps and automation capabilities at higher aggregate contract values.
The AIOps investment addressed the alert fatigue crisis that was simultaneously PagerDuty's largest churn risk and its largest expansion opportunity. Large engineering organizations were receiving thousands of daily alerts, making the product counterproductive at scale. Intelligent Alert Grouping and ML-driven noise reduction converted this problem from a defection catalyst into a premium feature: customers considering switching to reduce noise could instead pay more to have PagerDuty manage it intelligently. The ML capabilities were defensible precisely because they required historical alert data to train effectively — a competitive moat built on data accumulated over years of existing deployments, not replicable by a new entrant.
The NRR decline from 119% to 106% is the measurable cost of deliberately optimizing away from SMB toward enterprise, visible in both the retention metrics and the non-GAAP profitability improvement to $82.7M. Fewer, larger accounts produce better unit economics: lower support costs, higher average contract values, better gross retention. The question is whether enterprise platform growth can sustain $100K+ ACV customer additions above 20% annually — the rate at which the mix shift toward enterprise compensates for SMB base contraction and sustains overall revenue growth above 20%.
MongoDB Grew Atlas Cloud Revenue 724% to $1.4B and Total Revenue to $2.0B by Shifting to Consumption-Based Developer Data Platform
HashiCorp Grew Subscription Revenue 80% to $565M and Attracted $6.4B IBM Acquisition by Converting Open-Source Infrastructure-as-Code to Enterprise Subscriptions
Lever 3: Enterprise-focused go-to-market. PagerDuty restructured its go-to-market to target large enterprise accounts with multi-product platform deals rather than individual product expansions. The company introduced platform licensing tiers (Business, Enterprise, Enterprise for IT Service Management) that bundled multiple Operations Cloud products at higher price points, increasing average ACV in enterprise accounts. PagerDuty also expanded internationally, growing non-U.S. revenue from 20% to approximately 23% of total revenue.
The strategy PagerDuty explicitly rejected was remaining a point-solution alerting vendor: management assessed that the market was commoditizing at the alerting layer and that long-term revenue growth required justifying PagerDuty's pricing through platform-wide operational value, not just notification speed.
In FY2023 (ended January 31, 2023), PagerDuty reported total revenue of $370.8M with NRR of approximately 119% and approximately 14,700 customers (PagerDuty 10-K FY2023, p. 59).
By FY2025 (ended January 31, 2025), total revenue grew 26.1% from $370.8M to $467.5M (PagerDuty 10-K FY2025, p. 54). Customers with $100K+ ACV grew from 681 in FY2023 to 849 in FY2025 — a 24.7% increase representing the enterprise platform expansion (PagerDuty 10-K FY2025, p. 57). Subscription revenue represented over 90% of total revenue, reflecting the SaaS model's revenue quality. Non-GAAP operating income reached $82.7M in FY2025 — a significant improvement from non-GAAP operating loss in FY2022 — demonstrating the margin expansion potential as platform product gross margins improved (PagerDuty Q4 FY2025 Earnings Press Release). NRR declined to approximately 106% by FY2025 as PagerDuty optimized its customer mix toward larger enterprise accounts while cycling through SMB churn (PagerDuty 10-K FY2025, p. 57).
NRR declining from 119% to 106% reflects a deliberate trade-off: losing SMB customers to reduce support costs and churn drag while expanding per-account revenue in enterprise segments. Industry benchmark for operations management and ITSM platforms is NRR of 105–115%, making 106% at PagerDuty's revenue scale consistent with mature platform positioning.
Three causal factors explain PagerDuty's Operations Cloud expansion.
First, PagerDuty's installed base of 14,000+ organizations provided a platform distribution advantage. The company had existing relationships with DevOps and SRE teams across a cross-section of technology-driven enterprises — teams that had budget authority, understood the PagerDuty platform, and were receptive to expanding automation and AIOps capabilities from a trusted vendor. New product introductions within the existing customer base faced lower sales friction than competing for new logos.
Second, the alert fatigue problem created genuine demand for AIOps capabilities. As monitoring tool proliferation generated tens of thousands of daily alerts across complex microservices architectures, DevOps teams needed ML-driven noise reduction rather than more notifications. PagerDuty's Intelligent Alert Grouping addressed a real operational pain point that customers were already experiencing — demand was pull-driven from practitioners, not push-driven by sales.
Third, PagerDuty's status pages and customer service operations products expanded the platform's stakeholder footprint beyond technical users into customer success and executive communication roles, increasing the number of organizational functions with a direct dependency on PagerDuty during incidents. This broadened the platform's organizational footprint and made renewal decisions more complex to reverse.
What was adjusted mid-execution: PagerDuty initially attempted to maintain both SMB and enterprise customer bases but pivoted in FY2024–FY2025 to focus resources on enterprise accounts, accepting NRR compression from SMB churn in exchange for higher-ACV enterprise platform deals.
Counterfactual: Without AIOps and automation capabilities, PagerDuty would have faced continued pricing pressure from lower-cost point-solution alerting competitors and commoditization by monitoring tools building notification features.
GitLab Grew NRR to 123% and Revenue 31% to $759M by Consolidating 1,400-Feature DevSecOps Toolchain into a Single Platform