LangChain Software / SaaS United Kingdom

Wordsmith

Document Processing · Enterprise Knowledge Search

Wordsmith needed to observe, evaluate, and continuously optimize increasingly complex legal-assistant workflows that spanned multiple data sources, model providers, and experiment branches without slowing development or losing production visibility.

compare its performance to GPT-4o within an hour
reduced cost on particular tasks by up to 10x
reducing time to debug an inference from minutes to seconds
up to 100 nested inferences

Reported impact

Business outcome

Wordsmith can compare new models in under an hour, debug production problems in seconds instead of minutes, and cut costs on some tasks by up to 10x while keeping legal-assistant quality grounded in repeatable evaluations.

  • Cost Reduction
  • Productivity Improvement
  • Speed to Market

Solution

Wordsmith began with a configurable RAG pipeline for Slack and expanded into multi-stage inference chains over Slack messages, Zendesk tickets, pull requests, and legal documents. LangSmith became the control plane for this stack: hierarchical traces show what each nested step sends to and receives from the model, letting engineers debug bad intermediate behavior such as an invalid Dynamo query without trawling general logs. LangSmith datasets provide reproducible evaluation sets for RAG, agentic workloads, attribute extraction, and XML changeset targeting, so the team can compare models like Claude 3.5 and GPT-4o quickly and keep accuracy stable while pushing down cost and latency. Statsig experiment exposures are written into LangSmith tags, which makes online experiments queryable, exportable, and analyzable alongside development and production traces.

Data flow

Messages and documents from Slack, Zendesk, pull requests, and legal files enter Wordsmith’s inference chains, LangSmith records each nested step and evaluates datasets against model or prompt changes, and Statsig experiment tags let the team export and compare production cohorts for downstream analysis.

Solution architecture

4 components · 3 layers
  1. Ingest
    • Slack Acts as an early interaction surface and data source for Wordsmith’s configurable RAG pipeline.
  2. Serving
    • Wordsmith Delivers the legal assistant that reviews documents, drafts emails, and answers knowledge questions.
  3. Governance
    • LangSmith Provides tracing, datasets, filters, and experiment analysis across development and production.
    • Statsig Supplies experiment-exposure metadata that Wordsmith maps into LangSmith tags for analysis.

Architecture clues

  • Experiment cohorts are exported through LangSmith tags after Statsig exposure data is attached.
  • LangSmith indexed queries are used to isolate production inference errors.
  • Wordsmith organizes traces hierarchically to make deep inference chains inspectable.

Evidence from the source

These workflows can contain up to 100 nested inferences
Wordsmith’s first feature was a configurable RAG pipeline for Slack.
compare its performance to GPT-4o within an hour
reduced cost on particular tasks by up to 10x
reducing time to debug an inference from minutes to seconds
Transparency Evidence & methodology 100/100 reference value · 94% confidence · 3 sources

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 value100/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 impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence94%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability25/25
    12 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency9/10
    3 source references 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. LangChain

    Wordsmith customer story

    First-party
    https://blog.langchain.dev/customers-wordsmith/
    Source type
    Vendor-published customer story
    Published
    Jul 9, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date
  2. Wordsmith

    Wordsmith — AI for In-House Legal Teams

    First-party
    https://www.wordsmith.ai/

    The homepage JSON-LD lists addressLocality London, postalCode EC2A 4NE, and addressCountry GB.

    Source type
    Official company website
    Supports
    • Region
  3. LinkedIn

    Wordsmith AI | LinkedIn

    Third-party structured profile
    https://www.linkedin.com/company/ai-wordsmith/

    The LinkedIn Organization schema lists numberOfEmployees value 204.

    Source type
    Structured company profile
    Supports
    • Company size

Date evidence

  • Published on source page Jul 9, 2024 · LangChain · First-party
    Open date source
Not separately sourced Industry. Treat these normalized attributes as lower-confidence until a dedicated source is added.