Claude partner customer deployments and public stories: what the tier requirements count

Claude partner customer deployments, tier by tier

The three Services Track tiers ask for two customer counts, set out in Anthropic’s announcement of 3 June 2026. Select asks for at least 2 joint customers and 1 public customer story. Preferred asks for at least 15 and 3. Global Premier asks for at least 100, across three or more regions, and 15.

Only the certified count rises tenfold between tiers: customers run 2, 15, 100 and stories run 1, 3, 15. Only Select’s line says in production or carries the trailing 12 months. The announcement states no customer or story count for Registered, the entry level where it says new applicants start.

The announcement says every firm is measured against the same requirements. Claude Partner Network requirements has the full tier table, and the Claude Partner Network overview maps the programme.

Certified people are a separate count. On Anthropic’s FAQ, Claude Certified Developer - Foundations (CCDV-F), Claude Certified Architect - Foundations (CCAR-F) and Claude Certified Architect - Professional (CCAR-P) count towards Claude Partner Network eligibility.

Anthropic’s certifications page says CCDV-F, CCAR-P and Claude Certified Associate - Foundations (CCAO-F) will include updated content from 7 December 2026, and that notice omits CCAR-F: see Claude certification changes.

What qualifies as a production customer deployment for Claude partner requirements?

A Claude partner production deployment, in Anthropic’s announcement of 3 June 2026, is a customer “the firm has taken live with Claude”. That sentence sits under the label “Customers running Claude in production”. It is the fullest description on the official pages Cred Farmer could read on 6 November 2026, and it does not define production.

Anthropic’s pages also say “customer deployments”, “production deployments” and “deployed customers”. Cred Farmer reads these as one count, and reads joint as a customer shared by the firm and Anthropic. No page read confirms either reading.

The announcement also says a firm can see “exactly what the next tier requires” in the Partner Hub, which returned HTTP 403, so more detail may exist. Cred Farmer’s advice is to read your own dashboard first, which the announcement says “shows the same numbers we see”.

Pilots, second projects and older go-lives: what no page read settles

Anthropic’s announcement of 3 June 2026 sets a pilot apart from a running system: “a successful pilot is not the same as a system a business can run on”. That sentence opens the announcement and is not part of a tier line, so it does not rule on whether a pilot counts.

• Adoption work. The announcement says the ladder counts “adoption and enablement work” and does not define it. Anthropic’s Pictet story credits “Anthropic partner Artefact” with running the training, tying it to no tier count.
• A second project. The tier lines say customers. No page read says whether two projects at one customer count twice, or how a customer’s parent and subsidiary are treated.
• A customer that stops. The count’s label says “running Claude in production” and its sentence says “has taken live”. No page read says whether a customer that later stops still counts.
• An older go-live. No page read says which date Select’s 12 months run back from, whether they test the go-live or a customer still running, or whether a go-live before a firm joined counts.

If Select’s window tests the go-live, a firm at exactly 2 customers would need new go-lives to stay level, on Cred Farmer’s reading. Moving down has its own rule, with narrow exceptions: see losing a Claude partner tier.

Can we qualify if our customers run Claude via AWS Bedrock or Google Vertex AI?

No official page Cred Farmer could read on 6 November 2026 says that a firm can qualify with customers who run Claude via AWS Bedrock or Google Vertex AI, and none says it cannot. Anthropic’s tier lines say joint customers and name no route. Its count line says only “taken live with Claude”.

• The partners page. Under Cloud partners it says companies access Claude “on AWS, Google Cloud, and Microsoft”, and it names no tier.
• The Service partners page. Its Deployment Surface filter lists Amazon Bedrock, Claude API (direct), Google Vertex and Microsoft Foundry. That describes how firms are listed, and no page read ties it to a tier count.
• Two customer stories. Anthropic’s Cox Communications story of 29 June 2026 calls Accenture its “strategic transformation partner” and says “Cox accesses Claude through Amazon Bedrock”. Its Caylent story says Caylent, as an AWS partner, “runs Accelerate inside customers’ own AWS environments through Amazon Bedrock”.

Neither story says whether those customers counted toward a tier, and neither mentions Vertex AI. That silence neither allows nor bars such a customer.

On Cred Farmer’s reading the open word is joint. Its advice is to record each customer’s route, ask your partner contact in writing, and plan the count with and without those customers. Exam coverage is a separate question: does the Claude exam cover Bedrock.

What qualifies as a “public customer story” or reference?

A Claude partner public customer story, in Anthropic’s announcement of 3 June 2026, comes from a customer who “will vouch for the firm’s work in a published customer story”. No official page Cred Farmer could read on 6 November 2026 sets a format, a publisher or a length, or separates a story from a reference.

Anthropic’s pages also call this count public endorsements, public references, public customer references and public customer endorsements. Cred Farmer reads them as one count.

The tier lines count stories, while the line describing them counts customers: “How many customers will vouch”. On Cred Farmer’s reading, two stories from one customer may count once. No page read settles that.

The nearest published pattern Cred Farmer found is Anthropic’s own Customer stories page, which listed 286 stories on 6 November 2026. Its Partner filter names six, including Accenture, AWS and Google. No page read says a tier’s story must appear there, or that appearing there counts.

The Cox and Pictet stories name the customer, quote named people and print results. No page read says either story counted toward a tier.

What evidence and customer permissions are needed for a public Claude implementation reference?

Claude partner customer reference requirements beyond the count appear on no official page Cred Farmer could read on 6 November 2026. None lists the evidence or customer permissions needed for a public Claude implementation reference. Anthropic’s announcement says it verifies standing every quarter, without saying what it checks or what a firm submits.

One line may bear on permission. The announcement says every partner’s standing, “their tier, certified team, customer deployments, and public references”, is visible in the Hub’s public directory. That directory returned HTTP 403, so Cred Farmer cannot say whether a deployment appears as a number or a name.

On Cred Farmer’s reading, the Certification Terms bear on a story’s wording. Section 10(d) says a Partner will not misrepresent anyone’s certification status, or state or imply that the Partner itself is certified without Anthropic’s written authorisation.

Cred Farmer’s advice, not an official list, is to hold four things per customer.

No page read names a route for a customer count. The nearest is your partner contact, or partner-support@anthropic.com, which Anthropic’s eligibility page gives for the partner record.

The business case for certifying a team costs the people side. See also the Claude certification eligibility guide and the Claude certification cost guide.

Key takeaways

• Anthropic’s three Services Track tiers ask for at least 2, 15 or 100 joint customers. Only Select’s line carries the trailing 12 months.
• Anthropic’s announcement describes a deployed customer as one “the firm has taken live with Claude”. No official page Cred Farmer could read on 6 November 2026 defines joint or production.
• No official page Cred Farmer could read on 6 November 2026 says whether a customer on Amazon Bedrock or Google Vertex AI counts toward a Claude partner tier. That silence neither allows nor bars one.
• Anthropic’s three Services Track tiers ask for at least 1, 3 or 15 public stories. Its announcement describes customers who “will vouch” in a published story.
• Cred Farmer’s advice is to get a written answer before a tier plan relies on a customer.