Check Who Is Behind AI Revenue Growth

Anthropic's filing defines net revenue retention as current-quarter revenue from qualifying existing customers divided by revenue from the same customers a year earlier. Qualification requires at least US$1 in the base period; Claude Pro and Max subscribers are excluded. This is a spending-cohort measure, not a customer-success rate. ²

The filing also says its five largest customers generated about 25% of revenue in the nine months to 30 September 2026, with no single customer above 10%. Separately, cloud-provider marketplaces accounted for 48% of revenue in the six months to 30 June. Those are different populations and periods. They must not be added or treated as competing estimates of the same concentration. ²

For a buyer, the inference is not that expansion is illusory. It is that a supplier's evidence needs to answer the question being asked. Revenue growth can support a judgement about demand for that supplier. It cannot, on its own, establish your expected margin, service quality or customers' willingness to pay. Nor does customer concentration alone establish that a supplier is unsafe to use.

For a business building on an AI platform, this distinction changes market sizing. Separate repeat spending by customers already able to integrate the product from demand among the customers you hope to reach next. The second group may need a different price, onboarding process, language or distribution partner. Test those conditions before carrying a supplier's growth rate into your own sales plan.

Imagine a software business using AI to draft replies to customer questions. Its end customers buy the service, while a cloud marketplace handles part of the commercial relationship. More customer activity could raise AI usage and supplier revenue. But the business still needs to know who sets its price, who handles support and what happens if that route changes. This is an illustration, not a reported customer outcome.

Map the end customer, contracting party, billing route and underlying service separately. A single organisation can occupy more than one role, but the roles should not disappear into one supplier name. Ask procurement to identify which relationship would need to change if access, terms or support changed. Do not assume that choosing another model automatically changes the whole chain.

A separate Bank of England and FCA survey published on 26 October makes the distinction concrete for UK financial services. Its top three cloud/compute providers represented 79% of reported relationships, versus 54% for the top three model/API providers. The study received 196 responses; 105 firms completed the full survey, with percentages generally based on valid question-level responses. These are reported relationships, not spending shares or a global market census. ³

The practical lesson is to examine the layer that matters to the decision. More model choices may be useful while leaving hosting or commercial concentration largely unchanged. Conversely, an existing channel may provide valuable support and integration. Diversity is not automatically worth its cost; it should address a named dependency rather than improve the appearance of a supplier list.

The US filing and UK survey answer different questions. One describes a company's business; the other describes participating financial firms, including UK operations of international firms. Neither establishes how much demand exists in every region or which local customer groups can sustain an AI service.

For North American and European operations, distinguish the relevant customer and channel from the location of the supplier's headquarters. For an Asia-Pacific launch, check the actual route to customers, language support and service terms. In Africa, the Middle East and Latin America, do not import an enterprise spending pattern without checking local purchasing power, implementation support and infrastructure. These are proposed diligence questions, not claims that all countries in a region share the same constraints.

The evidence gap is commercially important: this scan does not establish comparable regional end-customer returns. A global business can use one method of assessment while reaching different rollout decisions. Local data handling, contractual rights and sector obligations require their own review; a US public filing does not settle them.

Ask the commercial sponsor to bring one proposed expansion, not a new dashboard for its own sake. Write down the customer group expected to pay, the useful work it will receive, the route through which it will buy and the evidence already available. Mark the difference between an observed result and an assumption about future customers.

Finance should challenge the denominator and reporting period. Procurement should challenge the channel dependency. The operating owner should challenge whether the service can deliver the promised outcome at its full cost. Fund the smallest test that resolves the disagreement: a customer interview, a limited paid trial or a review of the actual commercial terms may be more informative than another market-size slide.

Stop using supplier growth as a substitute for these answers. Continue investments supported by their own customer evidence, even when a headline is less exciting. The aim is not to dismiss strong AI demand. It is to understand whose demand it is, what keeps it durable and which part of the story your organisation can responsibly rely on.