Living landscape

Enterprise AI Adoption

Explore documented AI business activity, including adoption, partnerships and deployments—and see what each source actually establishes.

Published snapshotBuilt from current wiki evidence

Compare

Compare evidence

Choose 2–4 entities for a side-by-side matrix. Unknowns stay visible instead of being inferred.

3 of 4 selected

Decision view

What the wiki can establish

Evidence gaps remain visible as “Not established” instead of being filled by inference.

Use this matrix to compare published evidence—not to rank organisations or products. Each detailed claim links to its supporting wiki entry. Documented means that a source reported it, not that the wiki independently verified a causal outcome.

Business questionDoorDashCyberArkPictet
What was rolled outNo source-linked detail in this snapshotNo source-linked detail in this snapshot
  • Pictet deployed Claude Code and Claude Cowork across engineering, product, and business teams, with access for about 700 people.Vendor-reported · Read entry 1
Business workflowNo source-linked detail in this snapshotNo source-linked detail in this snapshot
  • Pictet deployed Claude Code and Claude Cowork across engineering, product, and business teams, with access for about 700 people.Vendor-reported · Read entry 1
Reported result
  • A separate AWS case study describes Anthropic Claude 3 Haiku in the solution; the quantified 49% transfer reduction and 12% first-contact improvement discussed there relate to DoorDash's earlier Lex/Connect IVR, not a causal result of the new generative-AI assistant.Vendor-reported · Read entry 1
  • AWS and DoorDash say they built the solution in about two months and reduced the need for live-agent assistance.Vendor-reported · Read entry 1
  • The authors report up to a 95% reduction in the time from support-case assignment to resolution: simple cases reportedly moved from 4–6 hours to 15–30 minutes, and complex cases from as long as 15 days to 2–4 hours.Source-reported · Read entry 1
  • Anthropic reports working prototypes built in two hours rather than two weeks in selected examples.Vendor-reported · Read entry 1
Measurement basisNo source-linked detail in this snapshotNo source-linked detail in this snapshotMeasurement basis included in reported result above
Limits and unknownsNo source-linked detail in this snapshot
  • These results are customer/vendor-reported, not independently verified; the reported "up to" figure must not be read as an average.Source-reported · Read entry 1
  • These examples are not an independently measured bank-wide productivity gain; the compliance comparison is against a projected effort, not a completed control-group baseline.Vendor-reported · Read entry 1

Not directly comparable: reported results may use different measures, populations, baselines, methods or dates. Read each measurement basis and source before drawing a conclusion.

Snapshot classificationsContext, not cited per-cell claims

These classifications summarise each entity dossier; they are not individually cited claims. Open a linked claim above for source-specific detail.

ClassificationDoorDashCyberArkPictet
Adoption stageUnknownProductionProduction
Business functionsNot establishedCustomer ServiceNot established
Outcome categoriesNot establishedCycle TimeCycle Time
Source date2024-09-242026-02-182026-09-02
Add or change entities53 available