PagerDuty booked two announcements into one release after the close on August 27. Q2 fiscal 2027 revenue of $124.4M, up 1% and above the top of guidance. Annual recurring revenue past $500M for the first time. And a workforce reduction of about 15%.
Against the 1,155 headcount PagerDuty last disclosed, on January 31, 2026, that lands on roughly 170 people.
The quarter, first
Revenue $124.4M, up 1% year over year. ARR closed at $501M, adding $6M in the quarter. Dollar-based net retention 98%, up sequentially, with annualized gross retention also improving. GAAP net income $4.7M, the fifth consecutive profitable quarter. Cash from operations $37M, free cash flow $33M at a 26% margin. Customers above $100K in ARR rose by 24 to 884. International is about 30% of revenue.
The line that moved in guidance is the margin line. Full-year non-GAAP operating margin went from 24%–25% to 25%–26%. Revenue guidance sits at $491.5M–$496.5M, a midpoint that is roughly flat year over year.
A company guiding to flat revenue raised its margin outlook by a point. The 170 people are what raised it.
Half a sentence worth the whole release
Most layoff releases say “operational efficiency” and “aligning resources with strategic priorities,” which hides the mechanism. PagerDuty named it.
The reduction, the company said, was concentrated in non-customer-facing roles, including support functions being automated and areas where process simplification and tool consolidation reduced staffing needs. Quota-bearing sales capacity and core product-development expertise were preserved.
That inverts the usual causal order. These roles did not go because money got tight. They went because the work moved into the system, and that made them available. CFO Eric Prengel said the savings fund sales, engineering and AI product development, and accelerate the company toward a long-term 30% non-GAAP operating margin.
$32K to $43K a head
PagerDuty guided restructuring charges of $5.5M to $7.5M, mostly severance, mostly landing in Q3 and substantially complete by the end of Q4.
Divide by 170 and the cost per exit is $32K to $43K.
That number only means something next to the cohort. HP’s AI restructuring plan, disclosed the day before, runs about $130K per exit at the 5,000-person midpoint, with $280M of it sitting on the special-termination-benefits line. That is money paid to senior staff to leave voluntarily. Oracle’s 21,000-person reduction cost roughly $86K a head against $1.8B in charges.
PagerDuty is paying a quarter of what HP is paying. No buyout, no tenure premium, straight severance. That price point does not describe senior expensive people. It describes mid-band support work that somebody decided was substitutable.
98% is the actual story
Net retention of 98% means existing customers paid 2% less this year than last. Management called the trend stabilizing because it improved sequentially. That is accurate, and the direction is still down.
PagerDuty sells incident response, historically priced per seat. A customer’s seat count is close to a census of how many engineers and operations staff sit on that customer’s on-call rota.
Which closes a loop. This automation cycle shrinks engineering and operations teams, the rotas get shorter, and PagerDuty’s seat count follows them down. The first-order result of the displacement wave shows up on PagerDuty’s own top line as 1% growth.
The answer management gave on the same call was to rename the product and change what it bills for. Operations Cloud becomes the PD Reliability Platform at general availability this fall, priced on usage. At the center sits the SRE Agent, which reads customer application and infrastructure context, production telemetry and prior incident history, then detects disruptions and opens investigations on its own.
Stack those two facts. A company that charges per person watched its customers run out of people, so it moved the billing unit from people to events and pointed an agent at the work those people used to do.
The fourth quarter of its kind this month
August has produced this pairing repeatedly. Cisco cut 4,000 and three months later named the metric, earnings per employee, posting a 30-year high. SentinelOne cut 8% inside a record Q1. Salesforce trimmed the people selling its AI agents.
PagerDuty went deeper than any of them. 15% is close to double SentinelOne’s cut, and SentinelOne was posting a record quarter while PagerDuty is posting 1%. Once revenue stops growing, margin comes out of headcount because there is nowhere else for it to come from.
CEO John DiLullo, 100 days in, calls the operating framework build, sell, optimize: build the product, sell it, and cut spend that does not directly serve those two. The layoff is the third word.
Who sits on this line
“Non-customer-facing” resolves to specific desks inside a software company: tier-two technical support, operations support, internal IT, business systems administration, finance and HR shared services, and the platform-operations roles covered by “tool consolidation.” The shared trait is clean process, structured inputs, and decisions with precedent. That is the first band this generation of systems picks up.
On-call deserves its own paragraph. The SRE Agent’s three jobs — detection, investigation, remediation orchestration — are exactly what a frontline SRE does after the 2 a.m. page. PagerDuty is packaging that work as a product for customers and ran it against its own org first. Shipping the product and cutting the staff in a single release is not a coincidence of the calendar. It is one decision printed twice.
On timing, charges land mostly in Q3 and finish by the end of Q4. The next real data point is usage disclosure after the PD Reliability Platform reaches general availability. Prengel already flagged that the company does not plan to regularly disclose a usage metric for the product. A usage-priced product that does not report usage is itself a disclosure.
Sources
