Number of Seats/Users: PagerDuty offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows PagerDuty that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from PagerDuty. PagerDuty reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: PagerDuty offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from PagerDuty. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: PagerDuty often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that PagerDuty is seen as a “must‑have” rather than a “nice‑to‑have” for most teams running critical services, but there are clear signals where cost and configuration effort can be optimized.

Overall sentiment
Our clients consistently rate PagerDuty highly for reliability and incident management depth. The main trade‑offs are price and setup complexity.

Key strengths our clients highlight
– Rock‑solid alerting & reliability
– Very dependable at waking the right person up, via calls, SMS, email, and app push.
– Strong escalation chains and rotation policies reduce missed alerts and “paging everyone.”

• On‑call scheduling & coverage
• Easy to manage 24/7 rotations across multiple time zones.
• “Set and forget” schedules once they’re configured.

• Quick overrides and swaps are appreciated for vacations and ad‑hoc changes.

• Integrations & workflows

• Deep integrations with monitoring tools, Slack, Jira, email, etc.
• Flexible notification rules (e.g., push → SMS → call) that can match each engineer’s preference.

• Incident lifecycle (triggered → acknowledged → resolved, plus snooze) feels natural and trackable.

• Visibility & analytics

• Incident history and basic reporting help teams reduce repeat issues and track MTTR and responsiveness.

Main friction points we see
– Price & plan structure
– Frequently called out as expensive, especially for smaller companies or when advanced analytics are locked behind higher tiers.
– Some clients report noticeable price increases over time.

• Usability & configuration
• Initial setup of services, teams, escalation policies, and schedules is confusing for many.
• Web UI and documentation make advanced features hard to discover.
• Mobile app occasionally slow to refresh or missing some web features.

How we at Spendbase use these insights
– Identify teams overpaying for higher tiers just to access one or two features.
– Spot unused seats and redundant incident tools running alongside PagerDuty.
– Use pain points around pricing and support responsiveness as leverage in vendor talks.

Net result: PagerDuty delivers strong operational value, but there is usually room to trim costs and simplify usage without losing core capabilities.