Live from Git

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
✓ Impel✓ Zapier✓ 1Password
Clear all

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 questionImpelZapier1Password
What was rolled out
  • Impel deployed Claude Enterprise to more than 400 seats across knowledge work and engineering.Vendor-reported · Read entry 1
  • The story cites 89% AI adoption across all Zapier employees and more than 800 internally deployed AI agents.Vendor-reported · Read entry 1
No source-linked detail in this snapshot
Business workflow
  • Impel deployed Claude Enterprise to more than 400 seats across knowledge work and engineering.Vendor-reported · Read entry 1
  • Its teams use Claude Code for product development and a Claude-based roleplay agent to train over 150 customer-facing staff using scenarios informed by recorded dealer calls.Vendor-reported · Read entry 1
  • Anthropic's customer story reports that Zapier adopted Claude Enterprise for work across product marketing, engineering, strategic research, and design.Vendor-reported · Read entry 1
  • 1Password deployed Codex across planning, implementation, review, testing, and production investigation.Vendor-reported · Read entry 1
Reported result
  • Anthropic's customer story says new-product ramp time fell from three to six months to roughly one month of roleplay and certification.Vendor-reported · Read entry 1
  • It reports 20% more support cases handled with Claude-based triage and monthly business-review preparation falling from three to four hours to around 30 minutes.Vendor-reported · Read entry 1
  • Zapier says its support team's AI ticket-summarisation tool, Sidekick, halved average handle time.Adopter-published · Read entry 1
  • Its OpenAI customer story reports a 20.9% productivity improvement for a core engineering cohort and a 10.9% reduction in median pull-request cycle time.Vendor-reported · Read entry 1
  • For its Finance AI Hackathon, 1Password says 90 team members built 21 agents and that those agents save the team 5–10 hours per person per week.Source-reported · Read entry 1
Measurement basisNo source-linked detail in this snapshotNo source-linked detail in this snapshot
  • The company estimates a 553% ROI and about $784,000 of annual engineering capacity for a modelled group of 50 consistent users.Vendor-reported · Read entry 1
  • The ROI is modelled, not a realised cash saving or an independently verified causal effect.Vendor-reported · Read entry 1
Limits and unknowns
  • These are vendor-published customer examples, not an independently controlled estimate of company-wide productivity.Vendor-reported · Read entry 1
  • Impel prioritises agent opportunities by business problem and still uses other models, so the account does not establish that every benefit or workflow is attributable solely to Claude.Vendor-reported · Read entry 1
  • Anthropic's earlier customer story reported 89% AI adoption; the figures refer to different dates and should not be treated as competing estimates for the same moment.Adopter-published · Read entry 1
  • Its claims are vendor-published and should not be presented as an independent outcome evaluation.Vendor-reported · Read entry 1
  • Expansion to finance and marketing is described as a rollout, but the published productivity figures concern engineering and should not be generalized to those teams.Vendor-reported · Read entry 1
  • The ROI is modelled, not a realised cash saving or an independently verified causal effect.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.

ClassificationImpelZapier1Password
Adoption stageProductionProductionProduction
Business functionsNot establishedResearch, Sales MarketingFinance, Software Delivery
Outcome categoriesCycle TimeCycle TimeCycle Time, Productivity
Source date2026-09-162026-01-082026-09-08

Impel

Zapier

1Password

Add or change entities53 available