Compliance-monitoring AI is deployed in production at 2% of financial services firms and rising by 6 percentage points per quarter — Early Signal. That velocity matters, but so does the starting point: every measured production use case remains at 3% adoption or below.
What’s moving
The production data shows a broad cluster of workflows advancing at the same reported quarterly rate:
- Wireframing and prototyping: deployed at 3% of firms, up 6 points per quarter — Early Signal.
- Content technology management: 3%, up 6 points per quarter — Early Signal.
- Vendor negotiation: 2%, up 6 points per quarter — Early Signal.
- Compliance monitoring: 2%, up 6 points per quarter — Early Signal.
- Vendor and third-party compliance: 2%, up 6 points per quarter — Early Signal.
- Business process mapping: 1%, up 6 points per quarter — Early Signal.
- Supplier relationship management: 1%, up 6 points per quarter — Early Signal.
- Warehouse operations oversight: 1%, up 6 points per quarter — Early Signal.
This is production deployment, not software availability or employee experimentation. The uncomfortable reading is that financial services adoption is moving quickly while remaining scarce. A reported quarterly increase of six points is larger than the current installed base for every listed task, so the next measurement will be important. These figures are Early Signal, not a stable long-term adoption curve.
Capability vs deployment
Capability evidence must stay separate from firm-level deployment.
For vendor negotiation, arcships/aimux provides a unified API for accessing 325 AI service providers. GitHub Trending assigns this 50% quality — Plausible, as of 17 August 2026. That indicates relevant infrastructure, but it does not show that the system negotiates successfully, meets financial-services controls or operates inside regulated production environments.
The production evidence is different: vendor-negotiation AI is running at 2% of financial services firms, with growth of 6 points per quarter — Early Signal. One measure concerns system availability; the other concerns organisational use.
A second GitHub Trending project, wanmol/goal-flow, can transpile Dify DSL definitions into runnable Python code for the ethics and code-of-conduct task. Its assessed quality is 50% — Plausible, as of 19 August 2026. No corresponding financial-services production-deployment rate is provided. Treating this as deployed compliance automation would exceed the evidence.
Roles most exposed in Financial Services
Current exposure sits with people who own the measured workflows:
- Compliance analysts and third-party risk teams, because compliance monitoring and vendor compliance are each at 2% production deployment — Early Signal.
- Procurement and vendor-management staff, because vendor negotiation is at 2% and supplier relationship management at 1% — Early Signal.
- Business analysts and process-improvement teams, because business process mapping is at 1% — Early Signal.
- UX and product-design teams, because wireframing and prototyping has the highest measured rate at 3% — Early Signal.
- Content-platform owners and operations teams, tied respectively to 3% content technology management and 1% warehouse oversight — Early Signal.
These figures identify task exposure, not job elimination. The input contains no headcount, redundancy or role-removal data.
What to watch
The central uncertainty is whether the uniform 6-point quarterly increase persists across eight different workflows. Current bases of 1% to 3% leave little evidence about repeatability, scale or control performance.
Career Runway’s 2026-Q3 scorecard contains 17 published calls, of which 8 have resolved; all 8 called the direction correctly, with an average of 90 days to resolution. The resolved grade mix is A 0% · B 6% · C 94% · D 0%. One resolved call anticipated portfolio property-structure transfers towards Finance Manager because Customer Segmentation & Targeting was the most-exposed core task (record).
What to do differently: track production use by task, not vendor count. If your role owns compliance monitoring, vendor governance, prototyping or process mapping, document where human approval remains mandatory and build evidence of judgement, exception handling and auditability before the next quarterly reading.