Loading…

AppFolio (APPF) backlog: remaining performance obligations

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

Data as of .

AppFolio backlog history

$0$500M$1BDec 2022Mar 2023Jun 2023Sep 2023Dec 2025Mar 2026Jun 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$161M$1.09B0.1 yrsn/a
30 Jun 2026$115M$1.04B0.1 yrsn/a
31 Mar 2026$104M$995M0.1 yrsn/a
31 Dec 2025$93.9M$951M0.1 yrsn/a
30 Sep 2023$30.0M$573M0.1 yrs$1.00M
30 Jun 2023$24.0M$532M0.0 yrs$1.10M
31 Mar 2023$20.0M$503M0.0 yrs$1.00M
31 Dec 2022$15.0M$472M0.0 yrs$900,000

Questions

What is AppFolio's backlog?
AppFolio reported $161M of remaining performance obligations at 30 Sep 2026 and up 41% from the previous quarter. That is 0.1 years of trailing revenue already under contract. Book-to-bill last quarter: 1.16.

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.