Anthropic Automotive North America

Impel

Sales Automation

Impel's product and engineering teams were shipping new automotive AI capabilities faster than 150-plus customer-facing reps could learn them, while monthly business reviews and strategic projects still consumed hours of manual prep.

85% less prep time per dealer business review
Built the flagship roleplay agent in about 3 weeks
Handles 20% more support cases
Ramp time cut to 1 month

Reported impact

Business outcome

Impel cut new-product ramp time from three to six months to about one month, reduced dealer business-review prep by roughly 85 percent, increased support-case throughput by 20 percent, and built its flagship roleplay agent in about three weeks while scaling Claude to more than 400 internal users.

  • Productivity Improvement
  • Revenue Growth
  • Speed to Market

Solution

Impel uses Claude as the reasoning layer behind a portfolio of internal agents selected by business impact. For the highest-priority training problem, Claude analyzed more than 150,000 Gong calls plus Salesforce data to create a dealer roleplay agent that simulates hard conversations, speaks through speech-to-text and text-to-speech, and scores objection handling, rapport, product knowledge, and next steps before DMing scorecards in Slack. The company routes reasoning-heavy design work to Opus 4.5 and Fable 5.1 across MCP-connected workflows, then tests lighter Sonnet models as executor agents once a flow is proven. Beyond training, Snowflake-backed briefs reduce monthly business-review prep, and 400-plus Claude Enterprise seats extend the same agentic patterns into support, migrations, and knowledge work. This lets Impel treat agent building as an investment portfolio rather than a one-off experiment.

Data flow

Recorded Gong calls, Salesforce records, and Snowflake business data feed Claude-powered agent workflows; Fable or Opus reason over the hard parts, Sonnet executes stabilized tasks, and outputs such as roleplay scorecards or review briefs are delivered back to teams in Slack and other internal workflows.

Solution architecture

7 components · 3 layers
  1. Compute
    • Claude Code Accelerates the engineering work that originally triggered Impel's broader AI rollout.
    • Opus 4.5 Handles multi-step reasoning work across complex agentic workflows.
    • Fable 5.1 Tackles unmapped problems and higher-reasoning design work before flows are simplified.
    • Sonnet Runs proven executor flows once Impel has validated the workflow design.
  2. Storage
    • Snowflake Feeds the data used to draft monthly business-review briefs.
  3. Serving
    • Claude Platform Provides the model platform behind Impel's internal training and business-workflow agents.
    • Claude Enterprise Extends Claude usage to more than 400 engineering and knowledge-work users across the company.

Architecture clues

  • Claude analyzed more than 150 thousand Gong calls and the entire Salesforce instance to build the roleplay agent.
  • Impel maps 30 to 40 agent opportunities into six root-cause problem clusters and funds them in priority order.
  • The roleplay agent uses speech-to-text and text-to-speech and DMs scorecards in Slack.

Evidence from the source

Cut new-product ramp time from 3 to 6 months to an average of 1 month of roleplay and certification
Once a flow is proven, we test lighter models like Sonnet and routinely find they deliver sufficient results as executor agents.
Reduced monthly business review prep from 3 to 4 hours to about 30 minutes with Claude-drafted briefs from Snowflake
We use frontier models like Opus 5 and Fable 5.1 where stronger reasoning matters most
digging through more than 150 thousand Gong calls and our entire Salesforce instance
Transparency Evidence & methodology 100/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 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
    4 metrics 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

    Impel customer story

    First-party
    https://claude.com/customers/impel
    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 Sep 22, 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.