The paper trail

Small print.
Wide open.

A clear path from a claim to the page it came from. Here’s the filing, the research, and how we read it.

The documentS–1Anthropic, PBC26 OCT 2026 · 421 PP.
01The original SEC filingThe authoritative source, in your browser.SEC · HTML 02Download the saved filingThe complete 421-page document, optimized for downloading.PDF · 46 MB 03Download the full researchFindings, customer examples, calculations, and source references.Markdown

Page by page

Go straight to the source.

Page references count physical pages in the saved PDF, starting at 1. The printed filing number is shown separately when available.

Enter a page from 1 to 421. No PDF download needed.

From the filing

PDF page 89

Printed filing page 78 · Extracted page text

View on the SEC
Read the page text
Table of Contents

Collaborators, like Claude Code and Claude Cowork, within enterprise environments, these systems will require 
broad permissions and deep integrations with customers’ internal tools, data, and workflows in order to operate 
effectively.  The  scope  of  access  required  for  extended  autonomous  operation  within  enterprise  environments 
increases  the  potential  consequences  of  any  security  incident,  unauthorized  action,  or  system  error,  and 
customers  may  be  reluctant  to  grant  the  level  of  access  necessary  for  these  systems  to  operate  as  designed  if 
they are unable to satisfy themselves regarding the security, reliability, and controllability of such systems.

Our sales efforts targeted at enterprise customers also involve risks and challenges that may not be present, or 
that are present to a lesser extent, with sales to individuals or smaller organizations. These customers typically 
have  longer  decision-making  cycles,  require  greater  security,  functionality,  and  scalability,  expect  a  broader 
range  of  services,  demand  that  providers  take  on  a  larger  share  of  risks,  require  higher  levels  of  customer 
service  and  support,  and  expect  greater  payment  flexibility  from  vendors.  We  are  often  required  to  spend 
significant  time  and  resources  to  familiarize  potential  customers  with  the  value  proposition  of  our  models, 
platform,  and  applications,  and  this  process  can  take  substantially  longer  with  enterprise  customers. 
Enterprises may also require extensive customization, integration support, and vendor evaluations and demand 
more  features  than  we  currently  offer  or  than  we  can  deliver  within  their  expected  timeframes,  including 
enterprise-grade functionality such as audit logs, compliance features, security controls, and monitoring tools, 
which may require us to make additional investments in product development or services capabilities, before 
committing to a purchase. As a result of these factors, sales opportunities with enterprises require us to devote 
greater sales and administrative support and professional services resources to each such enterprise customer, 
which increases our costs, lengthens our sales cycle, and diverts our sales and customer service resources to a 
smaller number of enterprise customers. We may spend substantial time, effort, and money in our sales efforts 
without  successfully  producing  any  sales.  In  addition,  many  enterprise  customers  procure  and  deploy  our 
models,  platform,  and  applications  through  third-party  CSP  marketplaces,  which  can  introduce  additional 
complexity into the sales and deployment process, including reliance on the CSPs’ procurement, security, and 
billing workflows and coordination with multiple counterparties. As a result, our ability to attract, retain, and 
expand relationships with enterprise customers may also depend in part on factors outside of our direct control, 
including the policies, priorities, and operational requirements of such CSPs.

A  number  of  factors  influence  the  length  and  variability  of  our  sales  cycle.  The  need  to  educate  potential 
customers  about  the  uses  and  benefits  of  our  models,  platform,  and  applications,  the  discretionary  nature  of 
purchasing  and  budget  cycles,  competitive  evaluation  and  purchasing  approval  processes,  procurement 
requirements,  legal  review  of  contract  terms,  and  internal  budget  authorization  procedures  all  contribute  to 
sales cycle variability. The length of our sales cycle, from identification of the opportunity to deal closure, may 
vary significantly from customer to customer. Sales to enterprises typically take longer to complete than sales to 
individuals or smaller organizations.

A  meaningful  portion  of  our  revenue  is  attributable  to  a  relatively  small  number  of  such  enterprise  customer 
relationships, which increases the variability of our financial results. Our revenue in any given quarter could be 
substantially affected if these customers decide to significantly reduce their spend.

Enterprises may have deep existing relationships with our competitors for models, platforms, and applications 
we do not offer, or relationships with others in the ecosystem, which may delay our sales process or cause us to 
not succeed with such enterprises. 

Enterprise customers are particularly sensitive to our ability to maintain the uptime of our models, platform, 
and applications, and any degradation in uptime could adversely affect our ability to retain and expand with our 
enterprise customers. Sustaining the uptime, performance, and scale that enterprise customers expect can place 
additional  demands  on  our  overall  compute,  and  any  failure  of  our  capacity  management  systems  to  direct 
sufficient compute to support such demands could adversely affect our ability to serve all workloads. For more 
information  about  the  foregoing,  see  the  section  titled  “—If  we  fail  to  manage  our  technical  operations 
infrastructure,  or  experience  service  outages,  interruptions,  or  delays  in  the  deployment  of  our  models, 
platform, and applications, our results of operations may be adversely affected.”

Our sales strategy for these enterprise customers also depends on our ability to build and maintain an effective 
sales organization. If we fail to effectively manage these risks associated with sales to enterprises, our business, 
financial  condition,  and  results  of  operations  could  be  adversely  affected.  For  additional  discussion  of  our 
personnel  related  risks,  see  the  section  titled  “—We  may  not  successfully  build,  expand,  and  deploy  our  sales 

78

Text is provided for reference. Check the original for tables, images, and exact formatting.

Find a section 16 starting points

Section links may begin before the exact paragraph cited in a finding. PDF numbers below use physical pages.

  1. Founders’ letterp. 3SEC
  2. Defined termsp. 12SEC
  3. Prospectus summaryp. 16SEC
  4. Risk factorsp. 38SEC
  5. Management’s discussion & analysisp. 144SEC
  6. Businessp. 190SEC
  7. Governancep. 254SEC
  8. Executive compensationp. 275SEC
  9. Related-person transactionsp. 293SEC
  10. Principal & selling stockholdersp. 299SEC
  11. Capital-stock rightsp. 303SEC
  12. Shares eligible for future salep. 318SEC
  13. Underwritingp. 327SEC
  14. Auditor change & expertsp. 345SEC
  15. Financial statements & notesp. 347SEC
  16. Part II & exhibit indexp. 413SEC

How this was made

Read in full.
Kept in context.

A snapshot of the filing dated , rather than a live record of later events.

3primary reviewers
421pages reviewed
43image instances checked

The review

Three primary reviewers read non-overlapping ranges of the complete main filing. All 43 embedded image instances were transcribed and visually reviewed, including the founders’ letter, charts, and customer case studies. Financial tables were also checked visually for dates, units, and column alignment.

A separate reviewer checked the draft’s calculations, accounting interpretations, and customer qualifications. An additional check covered the later merged findings. The result is 62 findings and 21 customer examples.

The boundary

Companion contracts and other exhibits named in the filing’s index are separate documents and were not independently reviewed. Customer outcomes, technical benchmarks, forecasts, and scientific priority claims remain attributed company or customer disclosures.

The numbers

Dollar figures are U.S. dollars. H1 means the six months ended June 30; Q2 means the three months ended June 30. The 2026 interim financial statements are unaudited. Our calculations show their inputs and are labeled separately from reported values.

Blank fields stay undisclosed. Figures with different periods, conditions, or potentially overlapping scopes are kept separate. An earlier tender price is not an IPO price.

What the evidence labels mean
Reported in filing
A company disclosure, with the period and accounting basis retained.
Company estimate / company claim
An estimate or assertion attributed to the company, with its uncertainty preserved.
Our calculation
A derived figure using cited inputs. It is not a separately reported company metric.
Customer example
A selected case study, with its measurement limits. It is not representative ROI.
Proposed / conditional
A status qualifier for an arrangement that is not yet effective or depends on stated conditions.

About updates. This edition is tied to the October 26, 2026 filing. Any later revision should identify its new source date and preserve the basis of earlier claims.

The footnotes are only the beginning.Explore the findings Read the story
The original, in context

Open the footnote.

A closer look at the filing

Anthropic · Form S-1PDF 1

Opening page 1…

Filed October 26, 2026. PDF is approximately 46 MB and opens only when requested. Section links may precede the exact cited paragraph.