Small print.
Wide open.

Table of Contents

capable  model.  The  most  demanding  deployments  need  intelligence  that  is  reliable,  connectable,  and 
deployable  within  the  specific  data  environments,  regulatory  constraints,  and  workflow  patterns  of  each 
organization.  Intelligence  is  one  limiting  factor,  but  so  are  connectors  that  do  not  yet  exist,  governance 
frameworks that are not yet written, and orchestration logic that needs to be built from scratch. Our platform 
seeks to close these gaps, and we believe the breadth and speed with which we have done so is a primary reason 
customers build on Claude.

Our platform provides our customers with direct access to the primitives to build, deploy, and scale AI-native 
applications. At the foundation are model capabilities that make Claude’s autonomy possible: native tool use, 
computer  use  for  desktop  control,  memory,  and  extended  thinking.  Long  context  and  low-latency  model 
variants make that action sustainable: for example, an agent could hold an entire codebase, a full data room, or 
hours of accumulated task state in working memory and iterate fast enough that autonomy persists rather than 
stalls.  Above  these  sit  composition  primitives  such  as  our  Agent  Software  Development  Kit  (“SDK”),  Claude 
Managed Agents, agent skills, multi-agent orchestration, and the Model Context Protocol (“MCP”) for universal 
connectivity to enterprise data and tools. Together, these assemble into complex production workflows.

These building blocks are composable and interoperable. The same primitives that power a coding agent also 
power  a  research  agent,  a  financial  analyst  agent,  or  a  compliance-review  agent.  While  these  agents  have 
different  connectors  and  agent  skills,  they  have  the  same  SDK,  protocol,  and  orchestration  framework.  That 
composability is one of the reasons our customer base spans across industries and why customer expansion can 
happen seamlessly across additional use cases without significant integration work. 

Applications That Meet Users Where They Are

Our portfolio of applications sits on top of our platform and is deliberately broad to meet users across a number 
of key dimensions:

•

•

•

In  their  Work.  Claude  Code  works  with  software  developers  in  the  terminal,  while  Claude  Cowork 
extends the same agentic paradigm to knowledge workers.

In their Domain. Claude for Financial Services, Claude for Financial Advisors, Claude for Healthcare, 
Claude  for  Life  Sciences,  Claude  for  Legal,  Claude  for  Education,  and  Claude  for  Government  come 
with domain knowledge, data connectors, skills, and compliance controls pre-loaded.

In their Applications. Claude for Microsoft 365 and Claude in Chrome are embedded into the software 
that knowledge workers use every day.

A Platform Customers Build Their Businesses On

Customers of all sizes and across every major industry have adopted Claude. Fortune 500 companies, including 
American  International  Group,  Inc.  and  Bristol  Myers  Squibb,  rely  on  Claude  for  mission-critical  workflows. 
Research  institutions,  such  as  the  Garvan  Institute  of  Medical  Research,  Gladstone  Institutes,  and  the 
University of California, San Francisco, are applying Claude to some of the world’s hardest scientific problems. 
In addition, prosumers around the world use Claude as a daily tool. 

As enterprises adopt our platform and applications, we become deeply embedded in their businesses over time. 
Software developers build applications and internal tools on our platform, and they encode their workflows and 
institutional  knowledge  into  Claude-powered  agents.  Organizations  integrate  Claude  into  essential  business 
processes. Each additional integration deepens the relationship and increases the value customers derive from 
the  platform.  This  dynamic  extends  beyond  our  direct  customers.  Leading  companies  such  as  Legora  and 
Salesforce have built AI-powered products on Claude that reach millions of end users. This reach can increase 
awareness  of  Claude,  which  we  believe  drives  adoption  far  beyond  our  direct  customer  base.  When  such  end 
users  experience  Claude,  it  can  build  preference  and  familiarity  that  travel  with  users  across  roles  and 
organizations.

The result is an ecosystem where we build on our own platform and applications, our customers build on us, 
our  partners  build  on  us,  and  their  end  users  experience  Claude  across  surfaces,  creating  the  kind  of  deep 
workflow  integration  that  makes  our  platform  and  applications  increasingly  central  to  how  organizations 
operate. We believe the revenue we generate today does not reflect the full economic value Claude creates for 

192