Anthropic Software / SaaS North America

Spellbook

Document Processing · Risk Management

Spellbook needed to review, redline, and route very large volumes of contracts fast enough for lawyers and legal teams, while keeping issue spotting consistent and aligning recommendations with each team's preferred review style.

10x faster agreement turnaround time
530,000 contract reviews per month
more than 700,000 chat messages from practicing lawyers each month
roughly 15 Claude agent configurations on its review surface alone

Reported impact

Business outcome

Spellbook now runs about 530,000 contract reviews and more than 700,000 lawyer chat interactions per month, cuts agreement work from roughly 10 hours to about one, and extends the same Claude stack into autonomous contract-management workflows that move agreements through the organization.

  • Productivity Improvement
  • Risk Reduction
  • Speed to Market

Solution

Spellbook runs a mostly-Claude contract workflow on the Claude Platform. Contracts can be pulled in from email, Slack, or Salesforce before a lawyer opens them, then Claude-powered agents flag risks, draft redlines inside Microsoft Word, compare terms to market, and feed newer autonomous contract-management flows that move agreements through triage, review, negotiation, storage, and ongoing monitoring. Roughly 15 Claude agent configurations handle the review surface alone, matching model depth to task complexity: Opus 5 and Opus 4.6 on the hardest subtasks, Sonnet 4.6 where speed and tone matter, and Fable 5 as the oracle model in evaluation pipelines. Spellbook judges production quality by user acceptance of suggestions and repeated consistency checks, while its engineering team uses Claude Code with Fable planning and review to keep shipping new legal workflows.

Data flow

Contracts arrive from email, Slack, or Salesforce, Spellbook routes them through its Claude review agents to flag issues and draft redlines in Microsoft Word, and the same normalized contract context can continue into triage, negotiation, storage, and monitoring workflows.

Solution architecture

6 components · 3 layers
  1. Compute
    • Claude Code Supports Spellbook's own engineering workflow as it ships new legal automation features.
    • Opus 5 Handles the most complex contract-review subtasks on the review surface.
    • Opus 4.6 Runs demanding review tasks where quality matters more than speed.
    • Sonnet 4.6 Covers faster review and conversational tasks where tone and throughput matter.
  2. Serving
    • Claude Platform Provides the base model platform for contract review, redlining, and autonomous contract-management flows.
  3. Governance
    • Fable 5 Acts as the oracle model in Spellbook's evaluation pipeline and helps plan and review engineering work.

Architecture clues

  • Autonomous contract management now moves agreements through triage, review, negotiation, storage, and monitoring.
  • Spellbook measures model quality by how often lawyers actually accept suggestions.
  • The review surface uses about 15 different agent configurations matched to subtask complexity.

Evidence from the source

Cuts the time to complete an agreement 10x, from roughly 10 hours of lawyer work to about one
Roughly 15 agent configurations just for reviewing contracts
Runs its Claude-powered review agents across about 530,000 contracts every month
Spellbook recently launched autonomous contract management, which moves agreements through an organization
We'll use Fable as an oracle model to generate a set of criteria
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

    Spellbook customer story

    First-party
    https://claude.com/customers/spellbook
    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 29, 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.