Loading…

Pegasystems (PEGA) backlog: remaining performance obligations

How much revenue Pegasystems already has under contract, how fast it converts, and who it is with.

Data as of .

Pegasystems backlog history

$0$1B$2BDec 2022Jun 2023Dec 2023Jun 2024Dec 2024Jun 2025Dec 2025Jun 2026Sep 2026Backlog (RPO)Trailing 12-month revenue
Remaining performance obligations at each quarter end (bars) against trailing twelve-month revenue (line).
Amounts in USD. Source: SEC XBRL filings.
Quarter endBacklog (RPO)TTM revenueCoverageCustomer prepayments
30 Sep 2026$2.01B$1.75B1.1 yrs$434M
30 Jun 2026$2.02B$1.74B1.2 yrs$468M
31 Mar 2026$2.01B$1.70B1.2 yrs$565M
31 Dec 2025$2.07B$1.75B1.2 yrs$519M
30 Sep 2025$1.75B$1.73B1.0 yrs$407M
30 Jun 2025$1.84B$1.68B1.1 yrs$422M
31 Mar 2025$1.73B$1.64B1.1 yrs$473M
31 Dec 2024$1.62B$1.50B1.1 yrs$426M
30 Sep 2024$1.48B$1.48B1.0 yrs$348M
30 Jun 2024$1.41B$1.49B0.9 yrs$355M
31 Mar 2024$1.42B$1.44B1.0 yrs$384M
31 Dec 2023$1.46B$1.43B1.0 yrs$380M

Questions

What is Pegasystems's backlog?
Pegasystems reported $2.01B of remaining performance obligations at 30 Sep 2026, up 15% from a year earlier and down 0% from the previous quarter. That is 1.1 years of trailing revenue already under contract. Book-to-bill last quarter: 0.98.
How fast does Pegasystems's backlog turn into revenue?
Over the last twelve months Pegasystems recognised revenue equal to about 90% of the backlog it started each quarter with.

About these numbers

Remaining performance obligations (RPO) are revenue a company has contracted but not yet recognised, as reported in its SEC filings (XBRL tag RevenueRemainingPerformanceObligation). Coverage = backlog ÷ trailing twelve-month revenue. Book-to-bill = (change in backlog + revenue) ÷ revenue. Conversion = revenue recognised ÷ the backlog at the start of each quarter, summed over four quarters. Counterparty values come from company filings and releases.