Anthropic Financial Services Switzerland

Pictet

IT Operations Automation · Security and Compliance

Pictet wanted more than chat-based assistance: it needed agentic AI that could automate internal engineering, compliance, and business workflows inside a Swiss private bank without breaking data residency, risk, or training obligations.

700 people with Claude Code and Claude Cowork access
Around 700 people across the group now have access to Claude Code and Claude Cowork
Generated working prototypes in two hours instead of two weeks
Trained more than 500 people through 25 hands-on Claude Code workshops with Artefact

Reported impact

Business outcome

Pictet has given roughly 700 people access to Claude Code and Claude Cowork, trained more than 500 staff, reduced some prototype work from two weeks to two hours, and brought compliance, infrastructure, and business automation tasks into workflows that fit the bank's risk framework.

  • Compliance
  • Productivity Improvement
  • Speed to Market

Solution

Pictet rolled out Claude Code and Claude Cowork through a staged, persona-based program that began in its 1,500-person technology division and expanded across product and business teams. Artefact ran 25 hands-on workshops to help teams build with the tools rather than just query them. To satisfy banking controls, Pictet put business use cases behind a purpose-built API gateway that keeps processing in the EU or Switzerland and prevents data from persisting for model training. Early MCP connections expose internal systems such as GitHub, Jira, Figma, and the internal wiki, letting Claude participate in engineering, compliance, prototyping, and operational workflows. The same setup supports concrete jobs such as comparing more than 50 directives to current regulations, building alerting systems, creating custom thin-client UIs, and automating weekly marketwatch reports.

Data flow

Users invoke Claude Code or Claude Cowork, MCP pulls in the needed context from GitHub, Jira, Figma, or the wiki, and the purpose-built API gateway keeps sensitive business processing inside the EU or Switzerland while returning prototypes, analyses, or operational outputs back to the team.

Solution architecture

4 components · 4 layers
  1. Compute
    • Claude Code Drives agentic engineering, prototyping, and operational automation inside Pictet's teams.
  2. Serving
    • Claude Cowork Extends agentic workflows to product and business users outside engineering.
  3. Orchestration
    • MCP Connects Claude to systems such as GitHub, Jira, Figma, and the internal wiki.
  4. Governance
    • purpose-built API gateway Enforces residency and data-handling policies for sensitive banking use cases.

Architecture clues

  • Early MCP connections cover GitHub, Jira, Figma, and the internal wiki.
  • Pictet uses a purpose-built API gateway to keep some workloads in the EU and some only in Switzerland.
  • Rollout happens per persona and per kind of use case to simplify risk management.

Evidence from the source

Data can never persist for model training
Generated working prototypes in two hours instead of two weeks, with real code behind every screen
Kept business data processing in the EU and Switzerland behind a purpose-built API gateway
One standout application emerged from compliance, where a complex gap analysis—comparing over 50 internal directives against current regulatory standards—was completed in just hours using Claude Code.
Trained more than 500 people through 25 hands-on Claude Code workshops with Artefact
Transparency Evidence & methodology 75/100 reference value · 85% 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 value75/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 impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence85%
  • 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 provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/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

    Pictet customer story

    First-party
    https://claude.com/customers/pictet
    Source type
    Vendor-published customer story
    Published
    Sep 2, 2026
    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

Date evidence

  • Publisher catalog date Sep 2, 2026 · Anthropic · First-party
    Open date source
Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.