Loading…

Progress Software (PRGS) backlog: remaining performance obligations

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

Data as of .

Progress Software backlog history

$0$500M$1BNov 2022May 2023Nov 2023May 2024Nov 2024May 2025Nov 2025May 2026Aug 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
31 Aug 2026$498M$1,000M0.5 yrs$406M
31 May 2026$519M$1.00B0.5 yrs$423M
28 Feb 2026$528M$988M0.5 yrs$425M
30 Nov 2025$536M$978M0.5 yrs$425M
31 Aug 2025$592M$940M0.6 yrs$381M
31 May 2025$498M$869M0.6 yrs$389M
28 Feb 2025$478M$807M0.6 yrs$400M
30 Nov 2024$488M$753M0.6 yrs$404M
31 Aug 2024$346M$715M0.5 yrs$285M
31 May 2024$344M$712M0.5 yrs$292M
29 Feb 2024$348M$715M0.5 yrs$296M
30 Nov 2023$296M$694M0.4 yrs$295M

Questions

What is Progress Software's backlog?
Progress Software reported $498M of remaining performance obligations at 31 Aug 2026, down 16% from a year earlier and down 4% from the previous quarter. That is 0.5 years of trailing revenue already under contract. Book-to-bill last quarter: 0.91.
How fast does Progress Software's backlog turn into revenue?
Over the last twelve months Progress Software recognised revenue equal to about 184% 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.