Loading…

Intapp (INTA) backlog: remaining performance obligations

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

Data as of .

Intapp backlog history

$0$250M$500M$750MDec 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$799M$600M1.3 yrs$290M
30 Jun 2026$833M$578M1.4 yrs$318M
31 Mar 2026$791M$560M1.4 yrs$278M
31 Dec 2025$777M$543M1.4 yrs$283M
30 Sep 2025$715M$524M1.4 yrs$238M
30 Jun 2025$720M$504M1.4 yrs$259M
31 Mar 2025$622M$484M1.3 yrs$220M
31 Dec 2024$615M$465M1.3 yrs$235M
30 Sep 2024$549M$448M1.2 yrs$203M
30 Jun 2024$566M$430M1.3 yrs$219M
31 Mar 2024$468M$411M1.1 yrs$196M
31 Dec 2023$448M$392M1.1 yrs$196M

Questions

What is Intapp's backlog?
Intapp reported $799M of remaining performance obligations at 30 Sep 2026, up 12% from a year earlier and down 4% from the previous quarter. That is 1.3 years of trailing revenue already under contract. Book-to-bill last quarter: 0.79.
How fast does Intapp's backlog turn into revenue?
Over the last twelve months Intapp recognised revenue equal to about 77% 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.