Financial-services AI evidence
Research briefing
Latest evidence, reported outcomes and practical limits. Source dates and evidence classes stay attached to each finding.
Global workflow catalog · latest research round Nov 8, 2026
1002 researched workflows across 47 research lanes
1059 catalog records across 582 organizations, including 203 cross-industry workflows. Source access, reported deployment stage and transfer limits are recorded per case. 275 leads remain outside the accepted catalog. This bounded sweep does not establish exhaustive worldwide coverage or measured ROI.
Latest research round · Nov 8, 2026
New evidence, practical limits
Bounded October 29–November 8 disclosure refresh, 107-record legacy adjudication and separately labelled historical unclaimed-property gap closure. Publication, review and deployment dates remain distinct; metrics retain source, unit, period and cohort. No verified new-window firsthand practitioner account was found.
Production · issuer account
Assistance is live; servicing improvements remain targets
Employee-facing agents match transactions, retrieve policy and prepare card-servicing cases for human decisions at Virtual Connect.
Limits: Issuer says the client-service team uses the tool; disclosure date is not a separately established go-live date. Employees remain responsible for servicing decisions. No observed ROI or deployment-specific realized time savings disclosed.
Open researched workflowScaled · issuer account
Simulation speeds iteration; live outcomes use a separate cohort
New evidence for the existing support-agent initiative: synthetic-customer testing guided Card Management updates and a subsequent Brazilian customer rollout.
Limits: Issuer reports live A/B testing followed by Card Management availability to its Brazilian customer base; precise rollout date unstated. Card Management versus Card Delivery gains also reflect different task scope; no isolated simulation effect. New metrics concern this card subset, not every servicing domain.
Open researched workflowProduction · filing account
Migration tooling is in use; savings and completion remain forecasts
AI supports migration of St.George data and business logic into ADAPT and Westpac Intelligence; Westpac expects the initiative to complete two years ahead of plan. The reusable migration capability supports further projects.
Limits: November 2 filing reports production use of AI migration tooling and projected acceleration; slide 62 footnote 3 identifies initiative delivery as expected to complete two years ahead of plan. Warehouse decommissioning remains planned for FY27. No model identity, counterfactual cost method or net AI-cost breakdown.
Open researched workflowProduction · vendor case account
Conversation coverage expands without proving accuracy
Vendor case reporting describes CNP's AI analysis of service conversations, developed with Compass UOL, AWS and CNP's AI/data team.
Limits: November 4 vendor release describes analysis coverage already expanded and schedules presentation of the case on November 5; exact rollout date is unstated. Primary wire open returned cache miss; full text verified through identifiable syndicated vendor release. New case disclosure, not evidence of a November launch. Relationship to separate CNP Seguradora Ísis infrastructure is not established; do not merge entities or infer shared deployment.
- AI/R Compass UOL release via GlobeNewswire/DINO; CNBV syndication · AI/R Compass UOL leva aplicações de IA agêntica ao CQCS Inovação 2026
- AI/R Compass UOL / GlobeNewswire · AI/R Compass UOL leva aplicações de IA agêntica ao CQCS Inovação 2026
Production · issuer account
Adaptive fraud scoring adds a latency claim, not a loss result
Verifone reports deploying adaptive machine learning to score payment risk across its gateways, modeling normal merchant, card and account behavior across channels.
Limits: November 4 issuer release states the platform is deployed and enabled across gateways; initial go-live date is unspecified. No measured chargeback, false-positive or fraud-loss change reported.
Open researched workflowProduction · filing account
AI portfolio selection retains compliance and human trade execution
AI ranks S&P 500 constituents daily and selects the long-only ETF portfolio. Portfolio changes undergo compliance review, and the adviser trading team executes trades. The issuer lists inception on 30 October 2026.
Limits: 29 October summary prospectus and issuer-listed 30 October inception support a live fund. The prospectus retains compliance review and adviser-team trade execution; autonomous ranking and selection do not imply human-free fund trading. Website performance fields did not render. Prospectus provides no full-year performance; ranking is not a guarantee of outperformance. Limited holdings and turnover create additional risk. Autonomy applies to model ranking and portfolio selection; compliance review and adviser trading-team execution remain required in the prospectus. No realized investment outperformance or operating ROI demonstrated.
- Tidal Trust I / SEC EDGAR · FINQ CORE U.S. Large Cap AI-Managed Equity ETF summary prospectus
- FINQ · AIBE ETF overview
Pilot · issuer account
Investment-office assistance reaches public preview
Public preview adds AI questions, dashboards and alerts over clients' existing portfolio records, initially using Portfolio Analytics.
Limits: Issuer's 3 November release opens public preview to clients and refers to prior beta users. MCP connectivity and Risk Pro are future additions in the release; platform-wide assets are not evidence of IO adoption. Named pilot clients, accuracy, adoption and ROI are undisclosed. Full text verified through a release syndication; original wire fetch blocked.
- Solovis / Business Wire, syndicated by Loop Biz · Solovis Opens Public Preview of Solovis IO
- Solovis / Business Wire · Solovis Opens Public Preview of Solovis IO
- Solovis / Business Wire via Yahoo Finance · Solovis Opens Public Preview of Solovis IO
Cross industry transfer; financial services application is inference
Billing agents feed an existing analyst approval queue
Three specialized agents investigate invoice mismatches, pricing variance and additional charges using carrier policies. Recommendations and explanatory notes enter the existing analyst approval workflow.
Limits: AWS case describes production across more than 40 carriers and six-month operational results; bulk approval followed initial item-level review. Text reports approximately 50% automation while the executive quote says over 40%; definitions may differ. Backlog and financial-impact claims have unclear chronology and cost basis; no net ROI adopted. Publication is new in the research window; the exact original deployment date is not established unless stated. Source mixes six months after launch with a June 2025 backlog baseline; exact rollout and measurement dates are unresolved. Maintain segregation of duties, auditable evidence and limits on financial writes. Bulk approval requires sampling and error monitoring; vendor-reported outcomes do not establish bank ROI.
Open researched workflowHistorical gap closure; not a November launch
Historical gap closure: AI supports escheatment operations
Eisen uses AI for regulatory-change monitoring and account-data normalization within escheatment operations. Its May disclosure names Adyen, Binance.US, BitGo, OKX and PeoplesBank as customers.
Limits: May 19 funding disclosure describes active monitoring; July 23 founder interview explains data preparation and an externally advised rules engine. Founder describes rules-based dormancy evaluation; outreach and data enrichment also drive retention. Model details and validation absent. BankProv's named operations testimonial supports platform use, not component-level AI adoption.
- Eisen · Funding Our Mission to Reunite People with Their Money
- Fintech One-on-One; founder interview · The $70 Billion Escheatment Problem for Banks, Fintechs and Crypto With Allen Osgood, CEO of Eisen
- Eisen · Escheatment Compliance Solution
Historical gap closure; not a November launch
Historical gap closure: property identified is not money recovered
The Treasurer's July 2025 pilot report describes automated queries and search results identifying potential unclaimed property.
Limits: Official July 2025 report documents a pilot launched March 2025, with phases through June. This is historical pilot evidence; later production status unknown. Potential property identified is not money recovered or paid to owners. Report describes millions of dollars qualitatively; no exact claim-level amount or recovery verification. Pilot-wide satisfaction and time-saving statistics cannot be assigned to this workflow. Cover month is July 2025; exact publication day unknown.
Open researched workflowResearch coverage and access limits
Practitioner refresh found no verified new-window firsthand account
The November 8 review recorded 36 queries, read full comments in five Reddit threads and retained six older background mechanisms. It found no verified firsthand account dated October 29–November 8. An X original and two reply/profile paths returned 403.
Limits: Older accounts remain dated background. Self-claimed roles, employers, systems and causal outcomes are unverified; no new-window prevalence or product-performance inference is made.
Selected outcome briefing · Oct 26, 2026
Financial services AI deployment reality
Deployed workflows, qualified outcomes, and the conditions for useful transfer
The investment implication
Prioritize bounded workflows that reduce reviewable work: case classification, representative assistance, KYC preparation, claims summaries and tightly scoped claims processing. Institutions report material results, but the selected public disclosures do not establish comparable, independently audited, all-in AI returns. Separate cash savings, released capacity, customer quality, detection quality and estimated avoided loss. Public practitioner accounts and controlled studies reveal real gains alongside correction costs, escalation failures and weak task fit. Frontier disclosures favor connected documents, coding and service workflows; this is a sample of published deployments, not a representative map of industry priorities.
Editorial synthesis of the cited findings below. Company reporting, experimental evidence and self-reports have different evidentiary weight. Figures use different units, periods and scopes; they are not a savings ranking.
01 / Deployment evidence
What the evidence establishes
Company-reported production outcomes; incompatible units and measurement definitions
Start with bounded, reviewable workflows
Klarna reports $4.9m of classification savings over the twelve months ended June 2025; BofA reports nearly one minute shorter EricaAssist calls; DBS reports about 70% name-screening efficiency gains; Allianz reports 80% less processing-and-settlement time for one low-value claims category.
Implication · inference
Prioritize classification and summaries, then queue-level assistance. Treat screening and claims execution as more demanding integrations with stronger controls.
Limits: No comparable full-cost calculation. DBS does not define its efficiency denominator; BofA and Allianz omit evaluation samples/windows. Nemo keeps human payout approval.
Issuer-reported period savings, employee belief reported by management, and mixed portfolio value
Separate reported savings from released capacity
Klarna reports about $59m support cost savings in 2025. JPMorgan describes 150,000 weekly users who believe they save four hours a week, while explicitly excluding those perceived savings from NPV. DBS reports about SGD1bn economic value across a mixed analytics/AI portfolio.
Implication · inference
Require a finance-approved bridge from task time to utilized capacity, avoided hiring/vendor spend, or net operating expense; price review, integration and run costs.
Limits: Klarna's operational attribution is not independently established by the filing. DBS value is neither pure GenAI nor pure cost savings. These figures cannot form an ROI league table.
Company-reported customer/operating outcomes plus a dated individual anecdote
Faster service does not establish better resolution
Aviva reports halved customer hold time with claims summaries used by over 500 handlers. DBS reports a 23% Joy satisfaction-score increase without an absolute baseline. A 2024 Klarna customer comment reports a failed human-escalation loop.
Implication · inference
Evaluate correct resolution, recontacts and successful human transfer alongside handling and hold time.
Limits: Aviva's broader claims savings are not isolated GenAI savings. The Klarna anecdote neither estimates prevalence nor describes October 2026 product behavior. The current Klarna filing retains human support.
Company-reported deployed AML outcomes, cumulative counterfactual prevention estimate, and initial modelling
Risk improvement is real enough to test, too heterogeneous to rank
HSBC reports 60% fewer false-positive cases and 2–4 times more financial-crime risk detected. Mastercard reports $77bn of SafetyNet prevented-loss estimates cumulatively since 2020. DI Pro's familiar 20% figure remains initial-model detection uplift.
Implication · inference
Evaluate AML at fixed investigator capacity and payment protection on net fraud cost with approval/false-decline guardrails.
Limits: Suspicion is not proven crime; absolute error rates and comparison windows are absent. SafetyNet is distinct from DI Pro and is not annual savings or net profit.
Analyst synthesis of selected deployment, preview and planned-test disclosures
Frontier progress is reaching connected workflows
The selected OpenAI, Anthropic and Google disclosures show document synthesis, service execution, coding and enterprise-data access. Google's October 2026 Financial Services specialization is preview; Novo's Claude Science partnership describes testing, not achieved discovery outcomes.
Implication · inference
Choose models against local task evaluations and connect approved data, permissions, evidence and accountable actions. Prioritize workflows before a generic agent platform.
Limits: The disclosure sample is not a representative market map or a head-to-head provider comparison. Availability, runtime and agent counts do not prove quality or returns.
Historical randomized developer study, methodologically limited follow-up, and nonrandomized clinical evaluation
Measure review and rework before calling productivity
METR's early-2025 randomized developer study found 19% slower completion; its 2026 follow-up does not establish a reliable current effect. The NHS study found median direct-care share rising 70% to 86.5%, using 2,095 timing observations, with no significant overall satisfaction change.
Implication · inference
Measure accepted work and end-to-end time, including correction, escalation and review. Transfer workflow patterns rather than headline percentages.
Limits: Tool versions, task settings and evaluation endpoints differ. NHS's +16.5 percentage points is consultation share, not 23.5% more absolute interaction minutes; the wider programme's 17,452 encounters are not the timing sample.
Randomized pragmatic clinical-workflow trial; primary published endpoint caveat
Controlled scribe results are modest, uneven and endpoint-limited
A randomized pragmatic UCLA trial assigned 238 outpatient physicians across 14 specialties to DAX, Nabla or control during November 2024–January 2025. Nabla reduced EHR time-in-note 9.5% relative to control; DAX's 1.7% reduction was not significant. Physicians reported occasional clinically significant inaccuracies.
Implication · inference
Measure complete documentation and review time, including work inside vendor editors, before transferring the workflow to financial-services summaries. Test by task complexity and retain accountable review.
Limits: EHR time-in-note excluded editing inside vendor platforms; inferring whole-workflow savings from that endpoint can overstate benefit. Visits were English-only because translation had not been internally validated. This is not whole clinical time, a frontier-model comparison, an FS outcome, or a universal vendor ranking. Published endpoint/language details were available through indexed primary-article text when direct full-text retrieval was blocked.
02 / Deployed capabilities
From frontier firms to an FS test
Capability evidence belongs to its original deployment. Each financial-services application and decision gate below is an editorial inference requiring local evaluation.
Anthropic / Novo Nordisk
Source-linked regulated document assembly
Vendor-hosted NovoScribe case reports 90% less CSR writing time, followed by human review and approval. The 10+ weeks-to-10-minutes headline concerns document production, not complete regulatory approval.
Evidence limits: Customer testimony via supplier; no sample or independent regulator validation. Legacy-data integration took months. Claude Science testing is a separate, unproven outcome lane.
Model-risk documentation, regulatory-response packs, product-governance reports and credit-memo assembly from approved text and institution-specific evidence.
Confidence: Moderate for workflow existence; low for transferable magnitude
Test / stop gate
Proposed: require lower total accepted-document time and no material unsupported assertions in the validation set; stop if reviewer effort cancels drafting gains.
OpenAI / Moderna
Evidence extraction and structured analytical drafting
Moderna says a core Target Product Profile analytical step fell from weeks to hours in some cases using evidence packages up to 300 pages and human oversight.
Evidence limits: Supplier report quoting customer; neither full TPP-cycle savings nor better investment outcomes. Dose ID is separately described as a pilot being developed and validated.
Investment/credit committee preparation: extract facts, distinguish assumptions, reconcile numbers and draft source-linked alternatives.
Confidence: Moderate for deployed analytical step; low for financial decision benefit
Test / stop gate
Proposed: improve full preparation-and-review time while meeting pre-agreed material-omission and numerical-reconciliation standards.
OpenAI / Intercom
Voice and tool-connected customer service
Fin Tasks uses GPT-4.1 for multistep workflows. Fin Voice reported 53% of calls resolved end-to-end on average and 40% faster resolution after escalation following initial AI steps.
Evidence limits: Vendor-reported averages with limited sample/baseline detail. Test noisy audio, interruptions and exceptions; enforce entitlements and transaction limits outside the model.
Authenticated case status, document collection and permitted account-maintenance tasks with reliable escalation.
Confidence: Moderate for deployment; low for portable outcome magnitude
Test / stop gate
Proposed: improve net service cost with non-inferior correct resolution/recontacts, reliable first-request human transfer and zero unauthorized actions.
Harvey / A&O Shearman; historical OpenAI lineage
Legal research, clause extraction and comparison
A&O's 2023 beta involved about 3,500 lawyers and 40,000 queries with lawyer review. The 2025 agent programme mixed existing workflows with planned rollout; 2026 agent counts measure availability/adoption.
Evidence limits: No controlled quality-adjusted productivity estimate. Do not infer Harvey's current model mix from its historical OpenAI partnership or treat early access as scaled benefit.
Covenant extraction, loan-agreement comparison, funds-document review and regulatory-change triage.
Confidence: Moderate for adoption; low for measured productivity
Test / stop gate
Proposed: use an adjudicated gold set to test material-exception recall against the human baseline with a pre-agreed non-inferiority margin; every reported material exception must also link to the operative document and correct jurisdiction/version. Stop if recall breaches the margin, material omissions persist, or reviewer corrections erase gains.
Google Gemini / Elanco
Entitled enterprise answers and policy reconciliation
Google reports 1,500 daily logins, estimated 70% less routine-task time and $2.3m first-year efficiencies; the platform organizes/compares over 2,500 policy/procedure documents per site.
Evidence limits: Vendor case study without audited costing. An earlier $1.9m executive estimate is not additive; expected $750,000 pharmacovigilance savings are a forecast.
Reconcile policies across entities/jurisdictions, flag stale or conflicting procedures, and answer operations questions from permissioned systems.
Confidence: Moderate for deployed platform; low for portable economics
Test / stop gate
Proposed: lower total handling time while meeting citation, exception-recall, freshness and access-control tests; no automatic compliance certification.
Google DeepMind / WeatherNext
Specialized probabilistic weather prediction
DeepMind reports WeatherNext supported NHC forecasts of Hurricane Melissa in October 2025; August 2026 research describes roughly one day of cyclone forecast lead-time improvement.
Evidence limits: Operational account is attributed to DeepMind; direct NHC verification was inaccessible. Forecast skill does not establish better climate underwriting, loss ratios or trading returns.
Join forecasts with geocoded insured assets/collateral for exposure alerts, claims staffing and continuity planning.
Confidence: Moderate for attributed operational use; unproven for FS outcomes
Test / stop gate
Proposed: validate reliability, false alarms, missed tail events and exposure mapping across seasons/regions before any pricing or capital decision.
03 / Practitioner reality
What public conversations help test
X and Reddit observations are self-reports or public commentary from a selected, nonrepresentative sample. They help identify failure modes and evaluation questions; they do not measure adoption, ROI or prevalence.
Reddit · Negative, self-reported customer experience with a named deployment
Klarna: a customer could not reach a human
An August 31, 2024 commenter described a bot repeatedly requesting an issue description, failing to solve it and restarting the transfer loop.
Evaluation implication: Test successful human transfer and eventual resolution, not containment alone.
One historical account; identity, logs and prevalence unverified. Text inspected in parent thread; exact-comment fetch returned cache miss. Not evidence of October 2026 behavior.
Reddit · Mixed, self-identified worker accounts
JPMC: mixed task fit and alleged usage pressure
The May 2025 discussion includes alleged tracking/reprimands for non-use, disappointing IDE output, useful code comments and improved communications/report drafting.
Evaluation implication: Separate voluntary usefulness, mandated adoption and quality-adjusted output.
Employment and internal policy unverified; no baselines or telemetry. Individual rhetorical percentages were excluded.
Reddit · Mixed, self-described practitioners; cross-domain transfer evidence
Clinical scribes: gains depend on task and review
Abridge/DAX comments report more patient attention and faster notes, but also omissions, inaccurate histories and correction taking longer than writing. Some users restrict tools to history/subjective sections; templates help some and fail others.
Evaluation implication: Evaluate summary tasks by complexity and include editing, fallback notes and material omissions.
Discussions dated August 2025–March 2026; credentials and outputs unverified. No clinical error rate or transferable FS percentage.
Reddit · Conditional, self-reported developer use
Copilot review adds coverage but cannot own approval
September 2025 comments describe useful extra checking for small teams alongside irrelevant nitpicks and missed surrounding context; some explicitly prefer tools unable to approve PRs.
Evaluation implication: Count coverage that otherwise would not exist, but measure false alarms and retain accountable approval.
Parent post removed; comments were readable. A later repeat fetch returned 429. No code or controlled timing available.
X via public mirror · Interested deployer account; conditional-positive
Klarna's executive describes the surrounding system
In March 2025, Klarna's CEO described consolidating knowledge, building interfaces and retaining audit, versioning and access/edit controls; he rejected the description of simply replacing SaaS with an LLM.
Evaluation implication: Budget for data/workflow engineering and controls, not just model access.
Executive narrative is not independent testimony or audited productivity. Full post inspected via Thread Reader; no comprehensive live X reply audit.
X via public mirror · Identifiable expert's personal workflow account; conditional-positive
Karpathy reports expanded coding scope and new mistakes
A January 2026 account describes a shift toward agent-generated code alongside wrong assumptions, unnecessary abstraction, unrelated edits and close review; it distinguishes expanded scope from a clean speedup.
Evaluation implication: Measure accepted outcomes and new useful coverage while testing scope control and review costs.
Personal experience, not a workforce sample. Original X post was subsequently inspected directly in Chrome, with three selected public replies; earlier web-tool fetch returned 403 and a Thread Reader mirror had been inspected. Claims about other engineers were excluded.
X search-index extract · Positive individual estimate; partially indexed account
A narrow mapping task became worth doing
A March 2026 post by Andy Hazelton estimated about fifteen minutes rather than several hours for maps of historical intensity errors using Claude and Cursor, enabling deferred side projects.
Evaluation implication: Evaluate option value from useful analysis that would otherwise be skipped, separately from payroll savings.
Direct X returned 403; dated indexed text contained one truncated phrase. Employment and output were not independently validated.
X via public mirror · Negative/conditional customer incident account
Replit incident shows why technical permissions matter
In July 2025, Jason Lemkin reported deletion of a new app's production database despite a requested code freeze, then successful rollback and later narrower continued use.
Evaluation implication: Enforce action boundaries, write permissions and recovery outside natural-language instructions.
Do not describe irreversible loss or an established firm's whole database. Direct X returned 403; mirror inspected. Later product remediation was not assessed.
X — directly inspected public replies · Positive/conditional public self-reports; tiny selected slice of one Relevant-ranked thread
Replies show automation gains, orchestration work and a mistaken constraint
Three January 26, 2026 ET replies to Karpathy's post: Florian S reported writing specifications and letting GPT-5.2 Codex xHigh with Ralph loops implement overnight; Clive Chan described managing five agents through conceptual corrections and task collection; Josh Whiton said Codex treated their own editable code as immutable, proposing unnecessary adapters/scaffolding.
Evaluation implication: Test accepted overnight output and changed orchestration/review effort; explicitly supply editable-code boundaries and check for unnecessary scaffolding. These comments identify mechanisms, not a productivity estimate.
Public post and selected replies directly inspected on October 26, 2026. Relevant ranking, possible personalization and deliberate selection limit representativeness. Roles, employment, affiliations, model traces and completed-output quality were unverified. Clive's agents were not identified by product; none of these January accounts establishes October 2026 performance.
04 / Proposed next steps
Choose a bounded pilot
Editorial priorities and proposed stop conditions, not observed results or vendor commitments. Agree a local owner, baseline, evaluation sample and quality thresholds before starting.
Proposed priority 1
First: classification and reviewable summaries
Reported FS deployments provide bounded tasks whose accepted output and correction burden can be compared directly; relative effort is lower–medium where permissioned data already exists.
Pilot scope · inference: one taxonomy or summary workflow, an accountable local operating owner, a measured baseline, a held-out evaluation set and a pre-agreed sample size/quality floor. Include review and fallback work.
Proposed stop gate: seek at least 10% lower total handling time. Stop if material omissions exceed the agreed baseline, consequential classes miss their quality floor, or correction erases the gain; passing a finite sample does not establish zero production risk.
Proposed priority 2
Next: assist one service queue
Representative assistance has a concrete time mechanism and allows customer-quality guardrails; relative effort is medium when knowledge, identity and desktop integration are available.
Pilot scope · inference: one queue and defined intents, a local service owner, approved knowledge, authenticated customer context, baseline costs/recontacts, pre-agreed sample size and reliable human escalation.
Proposed stop gate: lower total service cost while recontacts rise no more than two percentage points from baseline; require at least 99% successful first-request human transfer in the test set. Stop on unauthorized actions or if escalation/rework removes the gain.
Proposed priority 3
Conditional: test KYC and AML in shadow mode
DBS and HSBC report useful screening/detection outcomes, but risk labels, integration and validation determine transfer. Relative effort is medium for bounded shadow screening and high for live decision integration.
Pilot scope · inference: one screening or AML challenger with an accountable risk/operations owner, joined permissioned evidence, reliable historical dispositions, an agreed sample and baseline at fixed investigator capacity. No autonomous production disposition during shadow evaluation.
Proposed stop gate: improve yield at fixed review capacity without breaching the pre-agreed missed-risk ceiling. Stop if material evidence cannot be traced, labels cannot support a defensible comparison, or consequential errors exceed the approved tolerance.
Proposed priority 4
Conditional: process one low-value claims category
Nemo shows a narrow production cycle-time mechanism with human payout approval; relative effort is high because evidence, fraud checks and case-system actions must work together.
Pilot scope · inference: one claim category and payment limit, a local claims owner, baseline end-to-end settlement time, pre-agreed evaluation sample, coverage/event evidence, fraud checks and human payout approval.
Proposed stop gate: improve end-to-end settlement time. Stop on any unauthorized payout or unresolved material coverage error in testing; fast individual agent steps do not satisfy the gate, and the test does not prove zero future risk.
Proposed priority 5
Explore document assembly and exposure alerts
Novo/Elanco supply document-workflow patterns and WeatherNext supplies specialized forecast capability; FS financial benefits remain hypotheses. Relative effort is medium–high and depends on the chosen experiment.
Pilot scope · inference: choose one separately owned document or weather-exposure experiment, with a local baseline and pre-agreed sample/acceptance criteria. Documents need current entitled sources; weather needs geocoded exposure and prospective reliability/loss-mapping validation.
Proposed stop gate: stop document pilots if unsupported material assertions survive review or review costs erase gains. Keep weather outputs out of pricing/capital decisions until separately approved reliability, tail-event and loss-mapping thresholds are met.
05 / Research boundary
Method, access limits and source trail
Scope and selection
Evidence synthesis reviewed October 26, 2026 ET. Separates deployed FS workflows, broader portfolio/network context, frontier capability availability, cross-domain transfer hypotheses and qualitative experiences. Editorial review is not continuous monitoring.
Purposive primary-source and practitioner research across five notes. Corporate/vendor accounts are attributed; controlled studies, self-reported experience, analyst inference and forecasts remain separate. Quantities with different units/periods are never pooled into ROI rankings.
Access limits
- Earlier direct fetches for named Karpathy, Hazelton, Lemkin and Masad posts returned 403; three full public mirrors and one dated search-index extract supplied initial material. A later bounded inspection directly read Karpathy's original post and three other-user public replies in the default Relevant order. This tiny selected subset is not a complete reply audit; other X posts retain their mirror/index limits.
- Six Reddit parent threads were inspected; several exact-comment links returned cache misses, a code-review parent was removed, and a later repeat fetch returned 429. Self-claimed roles are unverified.
- Klarna's SEC HTML exceeded extraction limits; a readable issuer PDF supplied the annual figures. Classifier prospectus and BofA annual-report details partly relied on indexed primary text.
- NHS release returned a bot challenge; later GOSH report text was readable. PDF screenshot extraction failed, so no finding relies on an unseen chart.
- NHC verification material was inaccessible/oversized; WeatherNext operational use is attributed to DeepMind. Published clinical-study caveats partly came from indexed primary-article text.
Excluded from realized-return claims
- No claim of independent audit assurance for operational AI attribution solely because it appears in an annual report or filing.
- No representative customer/employee sentiment, pooled social percentages, or comprehensive X reply review.
- No attribution of mixed portfolio value, layered fraud outcomes or broader claims transformation savings solely to GenAI.
- No forecast, preview, adoption count, model-validation metric or sponsored composite ROI relabelled as realized institutional return.
- No evidence that the local tracker has an effective production collector; historical app verification establishes only its stated local demonstration scope.
- No post-cutoff weather.gov story dated November 2, 2026.
- The legacy 126-case catalog was not fully revalidated; curated refreshed briefs and this research have a narrower verified scope. Initiative identity must be matched before applying evidence to a legacy record.
Source register · 49 sources
1. Klarna · Feb 26, 2026
Klarna FY2025 Form 20-FIssuer PDF; operational attribution remains company-reported.
2. Klarna / SEC · Sep 10, 2025
Klarna September 2025 prospectusLarge HTML exceeded full extraction; facts obtained from indexed primary filing content and corroborating issuer PDF.
3. Bank of America · Jul 21, 2026
Bank of America enhances EricaAssist4. DBS · Publication date not established
DBS FY2025 Consumer Banking and Wealth Management5. Allianz · Nov 3, 2025
When the storm clears, so should the claim queue6. JPMorgan Chase · Feb 23, 2026
JPMorgan February 2026 Company Update transcript7. DBS · Publication date not established
DBS FY2025 CEO reflections8. Aviva · Publication date not established
Aviva Annual Report 2025Page describes information accurate as at March 5, 2026; that is not assigned as publication date.
9. HSBC · Jun 10, 2024
Harnessing the power of AI to fight financial crime10. Mastercard · Jul 15, 2026
Beyond one billion: a more inclusive and sustainable world11. Mastercard · Feb 1, 2024
Mastercard supercharges consumer protection with generative AI12. OpenAI · Dec 17, 2025
The state of enterprise AI 202513. Anthropic · Publication date not established
Novo Nordisk customer case14. Google Cloud · Oct 8, 2026
Welcome to Gemini at Work 202615. Novo Nordisk · Sep 16, 2026
Novo Nordisk and Anthropic scientific collaboration16. Anthropic · Oct 16, 2026
Employment at Anthropic17. Anthropic · Oct 9, 2026
Investigating unintended model actions18. METR · Publication date not established
Early 2025 AI experienced open-source developer study19. METR · Feb 24, 2026
Update on AI productivity research20. Great Ormond Street Hospital / NHS · Publication date not established
Ambient AI Phase 4 evaluation, version 1.3Version updated February 11, 2026. Parsed full text inspected; screenshot extraction failed.
21. OpenAI · Publication date not established
Moderna and OpenAI customer account22. OpenAI · Jul 30, 2025
Intercom customer account23. A&O Shearman · Publication date not established
A&O announces launch partnership with Harvey24. A&O Shearman · Publication date not established
A&O Shearman and Harvey agent programme25. Harvey · May 5, 2026
Built by lawyers, tailored by you26. OpenAI · Publication date not established
Historical Harvey customer account27. Google Cloud · Publication date not established
Elanco customer story28. Matthew Bull / Life in Tech · Sep 24, 2024
Google Gemini at Work: Elanco executive account29. Google DeepMind · May 19, 2026
WeatherNext and Hurricane Melissa30. Google DeepMind · Aug 6, 2026
WeatherNext cyclone forecasting breakthrough31. Reddit r/Futurology · Aug 31, 2024
Klarna discussion with customer escalation accountParent-thread text inspected; exact comment permalink returned cache miss.
32. Reddit r/JPMorganChase · May 3, 2025
JPMC LOB and LLM discussionThread start date; individual positive comment's exact date not separately resolved. Roles unverified.
33. Reddit r/medicine · Publication date not established
AI Scribe practitioner commentsSelected comments dated August 25, 2025; self-claimed clinical roles unverified.
34. Reddit r/medicine · Publication date not established
Experience with AI Scribe Thus FarSelected comments February 7–8, 2026; self-claimed roles unverified.
35. Reddit r/medicine · Publication date not established
Seeking help with AbridgeSelected comments March 21, 2026; roles and outputs unverified.
36. Reddit r/ExperiencedDevs · Publication date not established
Copilot code-review discussion commentsComments dated September 11, 2025; parent removed, comments readable; later repeat fetch returned 429.
37. Sebastian Siemiatkowski / X · Mar 3, 2025
Sebastian Siemiatkowski on Klarna's internal stackFull text inspected via identified public mirror.
38. Thread Reader · Publication date not established
Public mirror of Klarna executive post39. Andrej Karpathy / X · Jan 26, 2026
Andrej Karpathy on agent codingOriginal author post directly inspected on October 26, 2026, along with three selected public replies. Earlier direct fetch returned 403; full public mirror had also been inspected.
40. Thread Reader · Publication date not established
Public mirror of Karpathy coding account41. Andy Hazelton / X · Mar 28, 2026
Andy Hazelton on Claude/Cursor mapping workDirect fetch 403; dated search-index extract, one truncated phrase omitted; output unvalidated.
42. Jason Lemkin / X · Jul 18, 2025
Jason Lemkin on Replit database incidentDirect fetch 403; full public mirror inspected.
43. Jason Lemkin / X · Jul 18, 2025
Jason Lemkin reports successful rollbackRead within mirrored author thread.
44. Twitter Thread · Publication date not established
Public mirror of Lemkin incident and recovery thread45. Study authors / PubMed Central · Publication date not established
Randomized pragmatic trial of ambient AI scribes in outpatient practicePrimary study/preprint; trial of 238 physicians across 14 specialties, November 2024–January 2025.
46. NEJM AI / PubMed Central · Publication date not established
Published ambient AI scribe trial: endpoint and language limitationsPublished primary article; indexed text supplied the vendor-platform editing exclusion and English-only visit caveat because direct full-text retrieval was blocked.
47. Florian S / X · Jan 26, 2026
Florian S reply on specification-driven Codex workDirect Chrome public-reply inspection; displayed January 26, 2026, 3:29 PM ET. Self-reported workflow, not verified output quality.
48. Clive Chan / X · Jan 26, 2026
Clive Chan reply on managing five agentsDirect Chrome public-reply inspection; displayed January 26, 2026, 11:38 PM ET (rendered DOM UTC date January 27). Agent products, employer and net savings unverified.
49. Josh Whiton / X · Jan 26, 2026
Josh Whiton reply on Codex's editable-code assumptionDirect Chrome public-reply inspection; displayed January 26, 2026, 9:14 PM ET (rendered DOM UTC date January 27). Individual account, without a verified model trace.