Back to Forecasting
PDActive

Will PagerDuty's customers >$100K ARR decline below 850 by Q2 FY2027?

Resolves September 30, 2026(201d)
IG: 0.64

Current Prediction

12%
Likely No
Model Agreement96%
Predictions9 runs
Last UpdatedMarch 12, 2026

Why This Question Matters

Competitive displacement is the most significant untested assumption. The Black Swan Beacon found that 4/6 lenses noted absence of displacement evidence but treated it as evidence displacement is not happening — classic absence-of-evidence error with 12-18 month lag risk. The >$100K customer count (867 in Q3) is the best available proxy for enterprise-level displacement. A decline below 850 would be the first concrete displacement evidence, validating the CONTESTED assessment and potentially escalating to ERODING. Continued growth would strengthen the Myth Meter's finding that competitive fears are narrative-driven.

COMPETITIVE_POSITIONREVENUE_DURABILITYCONSENSUS_BLINDSPOT

Prediction Distribution

0%25%50%75%100%
opus
sonnet
haiku
Range: 8%15%Aggregate: 12%
Individual Predictions(9 runs)
opusRun 1
12%

The >$100K customer count grew from 849 to 867 (+5% YoY) with no documented enterprise displacement. Even with CONTESTED competitive position and DBNR at 100%, dropping 18 customers in 2 quarters requires a sharp reversal that the 700+ integrations creating switching friction make unlikely. The Black Swan Beacon's lag concern is valid but the question asks for a near-term decline from a still-growing metric.

5% YoY growth in >$100K count (849 to 867)700+ integrations create switching friction preventing rapid displacementDBNR at 100% shows spend compression not customer departure
opusRun 2
8%

The question requires reversing +5% YoY growth to negative in just 2 quarters. DBNR at 100% means customers are staying but not expanding — this is spend compression, not departure. Switching costs from 700+ integrations make wholesale departures unlikely even with cheaper competitors. Even pessimistically assuming growth decelerates to 0%, staying at 867 still resolves NO.

Reversal from growth to decline in 2 quarters is structurally difficultDBNR at 100% = spend compression, not churnEven 0% growth still resolves NO at 867
opusRun 3
15%

To drop below 850, PD needs to lose 18 net customers from a base that just grew by 18 in the prior year. The most plausible path is not outright churn but threshold contraction — customers near $100K reduce spend below the threshold as DBNR at 100% implies flat-to-declining per-customer revenue. However, even this scenario needs to be widespread enough to overwhelm new customer additions, which remains unlikely in a 2-quarter window.

Need 18+ net customer losses from a +18 growth baseThreshold contraction path via DBNR=100% is more plausible than outright churn12-18 month lag risk suggests displacement is a medium-term, not near-term threat
sonnetRun 1
10%

The count was 867 and growing 5% YoY. Even with all the bearish competitive signals — CONTESTED position, narrowing moat, cheaper competitors — dropping below 850 in 2 quarters is a dramatic reversal. The switching costs from 700+ integrations are real and enterprise rip-and-replace cycles simply don't happen this fast.

867 with 5% growth is far from the 850 thresholdEnterprise switching cycles exceed the 2-quarter resolution windowNo documented displacement cases to anchor a decline estimate
sonnetRun 2
13%

The threshold requires a metric that just hit 867 (up from 849 YoY) to decline below 850 within 2 quarters — a complete trend reversal. DBNR at 100% shows spend is flat, not declining precipitously. The competitive displacement lag concern from Black Swan Beacon is valid but even aggressive estimates suggest deceleration, not reversal, in this timeframe. The CEO's admission of cheaper competitors is concerning but hasn't translated to customer losses yet.

Complete trend reversal needed in compressed timeframeDBNR at 100% = flat spend, not customer departuresBlack Swan lag risk is medium-term, not near-term
sonnetRun 3
11%

Two paths to below 850: (1) enterprise customers churn entirely — unlikely given 700+ integrations, or (2) customers near $100K contract below threshold — possible given DBNR=100% but would need 18+ net losses from a growing base. New customer additions should partially offset any threshold contraction. The Black Swan Beacon scenario is more of a 6-12 month risk than a 2-quarter risk.

700+ integrations prevent rapid wholesale churnThreshold contraction possible but offset by new customer addsCompetitive displacement timeline is longer than resolution window
haikuRun 1
14%

867 growing at 5% YoY with 700+ integration switching costs. DBNR at 100% means no expansion but no mass churn. The 2-quarter window is too short for the 12-18 month competitive displacement lag to produce a drop below 850. Low probability of trend reversal.

5% YoY growth provides buffer above 850 thresholdSwitching costs protect installed baseResolution window too short for displacement lag
haikuRun 2
9%

The count grew 18 customers YoY and would need to lose 18+ in 2 quarters. Enterprise rip-and-replace with 700+ integrations takes longer than 2 quarters even with cheaper alternatives. No documented displacement provides no base rate for sudden decline.

Need to reverse full year of growth in half the timeIntegration depth prevents rapid switchingNo historical precedent for sharp decline in this metric
haikuRun 3
12%

Growing metric (849 to 867), narrow but real switching costs from 700+ integrations, no documented displacement. DBNR decline affects spend not customer count at this threshold. Two quarters is too short for the 12-18 month lag risk identified by Black Swan Beacon to manifest in >$100K count.

Still-growing metric with 17-customer bufferDBNR affects spend level not customer departureLag risk timeline exceeds resolution window

Resolution Criteria

Resolves YES if PagerDuty reports fewer than 850 customers with ARR exceeding $100,000 in either Q1 FY2027 or Q2 FY2027 earnings. Resolves NO if customer count remains at 850 or above in both quarters.

Resolution Source

PagerDuty Q1 FY2027 and Q2 FY2027 earnings press releases, earnings call transcripts

Source Trigger

Confirmed major customer displacement to competitor — competitive displacement assumed rather than actively tested

moat-mapperCOMPETITIVE_POSITIONHIGH
View PD Analysis

Full multi-lens equity analysis