procurement · education · workflow
Anthropic scales procurement 5x without scaling headcount using Zip and Claude
During hypergrowth that grew company headcount by more than 5x over 18 months, Anthropic had no standardized vendor onboarding or payment process, relied on fragmented workflows across disconnected systems and payment platforms, and had limited ability to track renewals or prevent duplicate software spending.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · P2P request submitted in Zip
Employees submit procurement requests through a full procure-to-pay process in Zip, replacing corporate cards.
Tools used
ZipClaudeModel Context Protocol (MCP)Claude Code
Outcome
Within the first year, Anthropic achieved 95% policy adoption and more than doubled procure-to-pay volume while keeping procurement headcount flat, establishing self-service vendor onboarding and automated renewal tracking.
Results
Volume95%
Grounding & classification
Source type: vendor customer story
30 fields verified against source quotes, 1 dropped as unverifiable.
agentic workflowai agentcontent generationdata extractionsummarizationcontractinvoicepolicy documenthuman review describedmetric backednamed customerproduction runtime claimedsource backedtools describedworkflow describedsoftwareautomation rateemployee productivitythroughput increasevendor customer storycontract managementfinance opsprocurementagentic task executiondata sync enrichment