Anthropic Healthcare North America

League

IT Operations Automation

League needed to accelerate product development and internal operations in a regulated healthcare environment, but prompt tuning, multi-agent experimentation, and back-office work still required manual effort and strict security controls.

98% Claude adoption, up from 80% when League's company-wide rollout began
Under a quarter for a 12-year-old regulated healthcare company to go company-wide on Claude Enterprise
more than 60 automated processes for month-end, quarter-end, and payroll
roughly 48,000 lines across 271 files

Reported impact

Business outcome

League cut product development cycle times in half, pushed Claude adoption from 80% to 98% across the company, automated prompt repair for underperforming agents, and expanded AI-driven automation into finance, design, compliance, and legal workflows without relaxing healthcare-grade controls.

  • Compliance
  • Productivity Improvement
  • Speed to Market

Solution

League standardized on Claude Enterprise and Claude Code to make agentic work safe enough for a regulated healthcare software company. Engineers use Claude through an internal Swarm orchestration layer that can run up to 50 parallel agents against real build tasks, write code, run tests, and open pull requests, while engineers review every change before it ships. For a critical prompt-optimization workflow, League paired Fable exploration with Claude Code implementation across four codebases and two languages so a failing agent can read evaluation scores and rewrite its own prompt automatically. The rollout also extends beyond engineering: finance automates month-end, quarter-end, and payroll workflows, and teams use Claude Design for branded decks. Claude Security controls model tiers, connectors, and usage boundaries across the company.

Data flow

League feeds evaluation scores, source code, and MCP-connected tool context into Claude Enterprise and Claude Code. Fable explores prompt-improvement strategies, Swarm agents implement changes across codebases, and engineers review the resulting pull requests before release; separate finance and design flows run on the same controlled platform.

Solution architecture

5 components · 4 layers
  1. Compute
    • Claude Code Powers Swarm agents that write code, run tests, and open pull requests across multiple codebases.
  2. Serving
    • Claude Enterprise Provides the company-wide AI workspace League uses across regulated product, finance, and operational workflows.
    • Claude Design Generates branded slides and first drafts for non-engineering teams using the same controlled platform.
  3. Orchestration
    • Fable Handles exploratory multi-agent sessions that design new prompt-optimization workflows before implementation.
  4. Governance
    • Claude Security Enforces model-access tiers, connector boundaries, and spend visibility for regulated deployment.

Architecture clues

  • League merged the implementation as eight stacked pull requests for reviewability.
  • League's Swarm layer runs up to 50 parallel Claude Code agents against the same problem.
  • The prompt-rewrite system spans four codebases in two languages.

Evidence from the source

All eight merged, roughly 48,000 lines across 271 files.
Our engineers do that through Swarm, our own orchestration layer built on Claude Code.
They now have more than 60 automated processes for month-end, quarter-end, and payroll
roughly 98% of League's code is AI-authored.
we can tier model access, manage which connectors are available and to whom, and set the boundaries we need.
Transparency Evidence & methodology 90/100 reference value · 79% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value90/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact15/25
    1 metric describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence79%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance0/10
    The publication date has no documented provenance.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. Anthropic

    League customer story

    First-party
    https://claude.com/customers/league-qa
    Source type
    Vendor-published customer story
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes

Date evidence

  • First archived Aug 27, 2026 · Internet Archive · Independent First Wayback Machine capture; confirms the page existed by this date, not when it was published.
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.