Loading…

C3.ai (AI) backlog: remaining performance obligations

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

Data as of .

C3.ai backlog history

$0$200M$400MOct 2022Apr 2023Oct 2023Apr 2024Oct 2024Apr 2025Oct 2025Apr 2026Jul 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 Jul 2026$200M$232M0.9 yrs$53.7M
30 Apr 2026$203M$250M0.8 yrs$36.4M
31 Jan 2026$225M$307M0.7 yrs$40.0M
31 Oct 2025$232M$353M0.7 yrs$34.7M
31 Jul 2025$223M$372M0.6 yrs$29.9M
30 Apr 2025$235M$389M0.6 yrs$36.6M
31 Jan 2025$208M$367M0.6 yrs$33.0M
31 Oct 2024$260M$346M0.8 yrs$35.8M
31 Jul 2024$204M$325M0.6 yrs$40.3M
30 Apr 2024$244M$311M0.8 yrs$39.0M
31 Jan 2024$287M$296M1.0 yrs$41.3M
31 Oct 2023$304M$285M1.1 yrs$40.6M

Questions

What is C3.ai's backlog?
C3.ai reported $200M of remaining performance obligations at 31 Jul 2026, down 10% from a year earlier and down 2% from the previous quarter. That is 0.9 years of trailing revenue already under contract. Book-to-bill last quarter: 0.94.
How fast does C3.ai's backlog turn into revenue?
Over the last twelve months C3.ai recognised revenue equal to about 105% 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.