How PagerDuty Makes Money

PagerDuty: Building the Operating System for Digital Incident Management

How It Started

PagerDuty was founded in 2009 in Toronto, Ontario, by University of Waterloo graduates Alex Solomon, Andrew Miklas, and Baskar Puvanathasan. The problem was deeply rooted in their experience at Amazon. When Alex Solomon worked as an engineer at Amazon, he witnessed major transformations including moving from a monolithic codebase to a microservices-based architecture, where engineers were now responsible for testing, deploying, and managing code in production. This meant they were on call to respond when their code broke something, which eventually became known internally as “pager duty.”

The solution was elegant: the founders built a SaaS alerting platform to solve the fragile on-call processes they experienced under Amazon’s “you build it, you run it” model. The company was incubated at Y Combinator, and PagerDuty launched its initial release as a beta on Hacker News in August 2009. The target audience was clear — DevOps teams managing distributed systems and cloud infrastructure at scale. What began as a niche tool for engineers quickly evolved into an enterprise necessity.

Competitive Advantage

PagerDuty’s competitive moat stems from several reinforcing factors. First, growth hinged on integrations with hundreds of monitoring, ticketing, and communication tools, making PagerDuty the glue of modern stacks and accelerating adoption across IT operations. This ecosystem lock-in makes switching prohibitively expensive for enterprises. Second, PagerDuty reached the number one position in the space on account of a well-designed, easy-to-use product and a lack of any strong competition until recently. Third, the company demonstrated exceptional unit economics, with 136% year-over-year growth, 0.5% gross MRR churn, and 103–104% monthly net negative churn with upsells.

Additionally, in 2015 PagerDuty opened offices in London and Sydney and added Modern Incident Response and Analytics capabilities, evolving the platform into a data-driven management solution. Net dollar retention exceeded 120% by the 2017 Series C era. This expansion into analytics and intelligence created higher switching costs while improving customer lifetime value.

Marketing Technique

Product-Led Growth: PagerDuty’s initial marketing strategy leveraged its technical users directly. Customers would visit the website, learn about the product, sign up for a free trial, and eventually pay via credit card — an approach built on the assumption that customers were engineers who preferred not to speak with salespeople. This self-serve motion resonated strongly with DevOps communities.

Enterprise Sales: As the company matured, the founders quickly discovered that not all customers were like them. Some wanted to speak with someone directly. At that point, without a dedicated sales team, the founders handled sales themselves, mostly over email. This approach eventually evolved into a full enterprise sales organisation targeting large organisations.

Community and Integration Marketing: After the typical Y Combinator process of selling to other Y Combinator startups, PagerDuty found success selling to both startups and enterprises, and later expanded into non-tech enterprises. The company’s integration ecosystem became a marketing channel in its own right, broadening its reach across diverse operational stacks.

The company generates revenue predominantly from cloud-hosted software subscription fees and term-licence software subscription fees. Their initial pricing was based on both the number of users and the number of alerts, with their most expensive plan priced at $299 per month for 25 users. The platform employs a multi-tiered SaaS model with expansion revenue derived from additional users, alerts, and premium features.

Market Share

Company	Market Position	Key Strength
PagerDuty	Market Leader	Integration ecosystem, ease of use
BigPanda	Strong Competitor	Correlation and automation
Resolve.ai	Emerging Challenger	AI-driven incident resolution
Incident.io	Emerging Challenger	Modern incident response
New Relic	Adjacent Competitor	Observability platform

Business Model Canvas of PagerDuty

Value Proposition: Real-time visibility into critical applications and 24/7 incident management automation that reduces mean time to resolution.

Customer Segments: Over 10,000 small, mid-size, and enterprise global customers, including Comcast, eHarmony, Slack, and Lululemon.

Revenue Streams: Subscription-based SaaS model with tiered pricing and expansion revenue from additional users and modules.

Key Resources: A workforce of 1,155 employees, a broad integration ecosystem, AI and AIOps technology, and cloud infrastructure.

Key Activities: Platform development, integration partnerships, customer success, and AI-driven incident intelligence.

Channels: Self-serve product-led growth, direct enterprise sales, integrations marketplace, and community engagement.

Key Partnerships: Hundreds of monitoring, ticketing, and communication tool integrations.

Cost Structure: Cloud infrastructure, research and development, sales and marketing, and customer support.

Conclusion: Is It a Viable Business?

PagerDuty represents a highly viable and defensible business. Analysts forecast the AIOps market to reach nearly $40 billion by 2028, and PagerDuty’s Operations Cloud strategy positions the company to capture a meaningful share through AI-driven incident prevention and remediation. The company has achieved market leadership through a superior product experience, a broad integration ecosystem, and exceptional unit economics. With 28,000 customers by 2025 and a focus on GAAP profitability, the company aims to balance growth with sustainable margins as it scales its AI and automation capabilities. Despite competitive pressures from emerging AI-native startups, PagerDuty’s network effects, high switching costs, and expanding platform vision make it a sustainable and profitable business well positioned for long-term dominance in digital operations management.