Palantir’s contract pipeline: read TCV, remaining deal value and RPO on their own terms

The question is conversion, not the largest contract headline

Palantir’s second-quarter 2026 disclosures support a strong U.S. commercial growth observation, but they do not make every contract-related number interchangeable. The useful research question is how potential contract value becomes recognized revenue, and what evidence is available at each stage. A larger headline can describe more opportunity without describing more revenue in the next quarter.

This is a review of the quarter ended June 30, 2026, using the results released August 3 and the accompanying filings and presentation. It is not a new earnings announcement or a claim about unpublished third-quarter results. Our assessment is that the commercial momentum deserves attention, while the conversion assumptions need their own, explicitly dated record.

The analysis below keeps three dimensions separate: which customers a figure covers, whether it measures activity during a period or value at a date, and which contractual conditions affect it. Losing any one of those dimensions can make an apparently precise ratio answer the wrong question.

Start with what was actually reported as revenue

For Q2, Palantir reported U.S. commercial revenue of $764 million, up 149% year over year. The same release reported $2.132 billion of U.S. commercial total contract value, or TCV, and $6.238 billion of U.S. commercial remaining deal value, or RDV. These three figures share a customer-market label, but they measure different things.

Revenue describes recognized business for the quarter. TCV describes the potential lifetime value of contracts closed in the period. RDV describes remaining contract value at the reporting date. The release’s definitions assume options are exercised and contracts are not terminated when calculating TCV and RDV, subject to the stated qualifications. Those assumptions belong next to the numbers.

In a research sheet, put each observation on its own row rather than ranking them from smallest to largest. Label the revenue row completed-quarter performance, the TCV row period contracting activity and the RDV row remaining potential value. This preserves the information needed to discuss momentum without claiming that all three are current sales.

Why a bookings-to-revenue shortcut is not a forecast

Dividing $2.132 billion of U.S. commercial TCV by $764 million of quarterly U.S. commercial revenue gives approximately 2.79. The scopes match geographically and commercially, but the time dimensions do not: potential lifetime contract value is being compared with one quarter of revenue. The result is not 2.79 quarters of guaranteed future sales.

A reader might use that calculation as a prompt to investigate contract duration and conversion, provided it is labeled accurately. It cannot establish when delivery occurs, how much option value is included or which contracts will remain in place. Those questions need contract and accounting evidence, not a more elaborate version of the same division.

For the same reason, multiplying one strong quarter’s contracting activity by four would introduce an assumption about repeatability. If you use an illustrative annualization in your own work, identify it as an exercise and test the assumption. We do not use such an annualization here to forecast Palantir’s revenue.

RPO provides a different boundary around the evidence

The June 30 Form 10-Q reports company-wide remaining performance obligations, or RPO, of $4.9 billion. It describes RPO as noncancelable contracted revenue not yet recognized, excludes cancelable amounts, and omits contracts originally lasting twelve months or less under the disclosed practical expedient. The filing expects approximately 43% to be recognized over the following twelve months, 36% in months thirteen through thirty-six and the rest later.

This is a differently defined population from U.S. commercial RDV. Comparing company-wide RPO directly with U.S. commercial RDV does not reveal a commercial conversion percentage. Both the contractual boundary and the customer scope change. A precise-looking answer obtained by dividing the two would conceal that mismatch.

Nor is the disclosed RPO schedule a complete forecast of company revenue. It addresses the obligations included in that disclosure as of the measurement date. Keep the schedule as one piece of evidence, then ask what other business falls outside its stated scope. Treating a narrower accounting disclosure as the whole sales outlook would discard relevant boundaries.

The nearer-term portion is useful when read with rounding

The investor presentation’s additional-metrics table shows total RPO rising from $4.45 billion in Q1 2026 to $4.90 billion in Q2. Short-term RPO rises from $1.75 billion to $2.09 billion, while long-term RPO rises from $2.70 billion to $2.81 billion. On these rounded disclosed amounts, total RPO increased about 10.1% sequentially and short-term RPO about 19.4%.

That comparison supports a narrower observation: the nearer-term disclosed component grew faster than the total during this interval. It does not establish the cause, identify every contributing customer or guarantee that the same pattern continues. A helpful next question is whether subsequent disclosures retain this balance as contracts are recognized and new obligations enter the measure.

The $2.09 billion short-term amount is approximately 42.7% of $4.90 billion, consistent with the filing’s rounded 43%. Multiplying two rounded disclosures can give a slightly different result. Use the table’s stated amount when describing that table, and do not portray a rounding difference as a newly discovered accounting inconsistency.

Keep government funding and older reference dates visible

The 2025 annual report provides another boundary: its discussion of government RDV excludes certain awarded IDIQ contracts whose funding was not determined or guaranteed. IDIQ means indefinite delivery, indefinite quantity. That disclosure is a warning against treating every government award headline as an equivalent amount of committed revenue.

This annual-report reference supplies background on definitions, not a September 2026 update to the size of those awards. An older balance does not become current merely because a later document refers to it. Preserve the original measurement date when carrying the definition into a new research note.

For a future government-contract announcement, start with a short evidence trail: the award document, the funded or ordered portion if disclosed, the period of performance and the issuer’s subsequent reporting. If a needed detail is unavailable, leave the corresponding row open. Do not fill the gap by assuming the maximum contract ceiling will be ordered, funded or recognized immediately.

Test the investment interpretation in both directions

A constructive interpretation would look for recognized U.S. commercial revenue to remain supported by customer commitments, while the nearer-term company-wide RPO disclosure continues to provide useful visibility on its own scope. This is a research condition, not a claim that the two series represent an identical contract cohort or can be mechanically reconciled.

A more cautious interpretation would ask whether increasingly long durations, unexercised options or difficult implementation assumptions explain a growing contract headline. These are possibilities to test against new documents. The figures reviewed here do not establish that such problems are occurring. Describing a risk as a confirmed deterioration would be as misleading as treating all RDV as guaranteed sales.

A slower RDV growth rate by itself would also need context. Revenue recognition can reduce remaining value while new contracts add to it. Look for a company explanation before treating a movement in the balance as a single-cause signal. A useful thesis leaves room for multiple mechanisms and identifies which additional disclosure would distinguish them.

Consider a deliberately simplified, fictional balance: remaining contract value starts at 100 units, new commitments add 30 and recognized revenue reduces it by 20. With no other changes, the ending balance is 110. It grew 10%, even though the additions were 30% of the opening balance. If recognition were 35 instead, the balance would end at 95 despite the same additions. This is not a reconstruction of Palantir’s RDV, which can involve additional adjustments. It illustrates why a changing balance alone cannot identify the strength of new contracting or the pace of revenue recognition.

Build a follow-up record that can survive the next quarter

Keep a compact record with separate rows for U.S. commercial quarterly revenue, U.S. commercial TCV, U.S. commercial RDV, company-wide total RPO and the disclosed nearer-term RPO component. Alongside every number, store its source, date, unit and definition. Keep management expectations in a separate field from reported results.

At the next release, update the matching rows before writing a conclusion. Check whether the company changed a definition, provided a new explanation or revised an earlier figure. If a number is not disclosed, mark that field unavailable in the document reviewed; do not derive it from a different customer scope to maintain a visually complete table.

The resulting research question is specific: does later evidence show that the reported contracting momentum is accompanied by recognized business and a useful schedule of noncancelable obligations? Answer it with the appropriate series rather than collapsing all commitments into one backlog number. That approach preserves the strength of Palantir’s reported commercial growth while keeping the unproven conversion assumptions visible.