Anthropic Software / SaaS North America

HubSpot

Enterprise Knowledge Search · IT Operations Automation

HubSpot's engineering, marketing, and customer success teams were spending too much time on migrations, maintenance, content creation, troubleshooting, and personalized follow-ups that did not scale across the organization.

Built hundreds of Claude projects across teams
From 3-5 days to under an hour
Up to 40% productivity increase

Reported impact

Business outcome

HubSpot reports productivity gains across engineering, marketing, and customer success, including up to 40 percent productivity improvement, complex troubleshooting cut from three to five days to under an hour, faster onboarding to production, and more strategic customer conversations.

  • Customer Experience
  • Productivity Improvement
  • Speed to Market

Solution

HubSpot adopted Claude across multiple departments, with Claude Code doing the deepest integration work. Engineering connects Claude Code to internal services and the distributed codebase through MCP, using it for migrations, maintenance tasks, onboarding, and debugging. The team benchmarked real HubSpot engineering tasks and found Claude consistently needed the least human intervention, with Sonnet 4.5 reducing back-and-forth by asking for more missing context up front. Outside engineering, teams package reusable context in Claude projects and artifacts so marketing can centralize campaign information and create content faster, while customer success managers prepare for escalations, troubleshoot workflows, and generate tailored follow-ups in minutes instead of hours. This turns one-off manual knowledge work into reusable, shared AI workflows backed by HubSpot's own systems.

Data flow

HubSpot connects Claude Code to internal services and repositories via MCP for engineering work, while other teams feed campaign context, escalation details, and customer notes into Claude projects so the outputs can return as content drafts, troubleshooting guidance, or follow-up actions.

Solution architecture

5 components · 3 layers
  1. Compute
    • Claude Code Connects to HubSpot's internal services and codebase for migrations, debugging, and onboarding.
    • Claude Sonnet 4.5 Improves engineering task flow by gathering more needed information in each interaction.
  2. Serving
    • Claude Platform Provides the model platform HubSpot uses across engineering, marketing, and customer-success teams.
    • Claude projects Package reusable context and instructions so marketing and customer-success teams can reuse best practices.
  3. Orchestration
    • MCP Links Claude Code to HubSpot's existing services and internal systems.

Architecture clues

  • Benchmarks used a battery of engineering tasks from real HubSpot work.
  • Claude Code connects to HubSpot infrastructure through MCP.
  • HubSpot uses hundreds of Claude projects to centralize context and best practices.

Evidence from the source

Achieved up to 40% productivity increases across web development and content creation workflows
Built hundreds of Claude projects across teams to centralize context and best practices
Claude consistently required the least human intervention to reach finished solutions.
Reduced complex technical troubleshooting from 3-5 days to under an hour
When Claude Code came out with Model Context Protocol (MCP) first-class citizen support, we were excited to give it a go
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
    2 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

    HubSpot customer story

    First-party
    https://claude.com/customers/hubspot
    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 Feb 10, 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.