← back to the archiveCover illustration for “Palantir’s contract value needs its cancellation clause attached”
POSTday 74·4w ago·by Andy Padia

Palantir’s contract value needs its cancellation clause attached

Total contract value includes potential contract value under stated assumptions. Compare it with noncancelable obligations and recognised revenue before treating it as committed demand.

I would ask for the cancellation assumptions before using a vendor's contract-value number as evidence of committed demand. Palantir states those assumptions clearly enough that the metric should never travel without them.

Its Q2 2026 earnings release reports $3.373 billion in total contract value closed during the quarter. The definition measures potential lifetime contract value and assumes customer options are exercised and contracts are not terminated. The company also notes that most contracts include termination provisions.

The June 30 Form 10-Q reports a different measure: $4.9 billion of remaining performance obligations, representing noncancelable contracted revenue not yet recognised. It expects about 43 percent to become revenue over the following twelve months and excludes certain short-duration contracts under a disclosure expedient.

Those figures answer different questions. Neither is a substitute label for the other, and their amounts should not be subtracted to manufacture a cancellation rate.

The option is part of the value story

A customer option can represent a promising commercial relationship. It can also remain unexercised. Including it in a potential-value measure is not inherently misleading when the definition is visible.

The analytical mistake happens when a retelling removes “potential” and leaves “committed.” That changes the claim from the opportunity inside signed arrangements to an obligation that the disclosed definition does not establish.

Consider a hypothetical software agreement with an initial term and optional extensions. The sales team may reasonably discuss its full potential value. A delivery plan needs to know which periods have actually been ordered, and a revenue forecast needs its own recognition assumptions.

The same agreement can therefore support several useful numbers. The discipline is to retain the question each number answers instead of selecting whichever is largest for every purpose.

I would also resist interpreting a gap between contract metrics as proof of weak demand. Different coverage, timing and accounting rules can produce differences without identifying an adverse event. The definitions have to be reconciled before the comparison can carry that conclusion.

Ask for conversion, not just a larger headline

In vendor diligence, my follow-up would be how the company tracks conversion from potential value into exercised work and recognised revenue over time. A consistent history can make a broad commercial metric more informative.

If that history is unavailable, record the limitation. Do not replace it with the assumption that every option will be taken, or with the opposite assumption that none will. The uncertainty belongs in the assessment.

This also applies when comparing vendors. Two companies may both publish “backlog” while including different cancellation rights or contract periods. A side-by-side chart looks precise only after those definitions have been checked.

For an enterprise buyer, the relevance is practical: financial momentum can inform a supplier assessment, but it does not prove production adoption, customer outcomes or delivery capacity. Those need evidence suited to those questions.

Palantir's disclosures provide a useful example of the boundaries. The original documents preserve distinctions that an enthusiastic sales slide can flatten in a sentence.

Carry the option and termination assumptions with total contract value; potential sales, noncancelable obligations and recognised revenue are different evidence.

#enterprise-ai#revenue#vendor-diligence#metrics
← older drop
A financing target is not funded compute capacity
newer drop →
Revenue outgrowing customer count does not prove deeper AI adoption

related drops

explore all 243 drops →
← back to the archiveday 106