Insights · Vendors for pilot to production
Who can take a bank’s AI agent from pilot to production? Vendor types compared
Claude Certified Services Partner(Anthropic)Short answer. No single kind of provider is best for every bank. Large consultancies fit programmes that need change management and governance across many units. Cloud providers' professional-services teams fit banks that have already chosen a platform. AI-native boutiques fit fast build work on one use case. Platform vendors fit banks that want a product to configure rather than software to build. Specialised fintech engineering firms fit banks that need an agent built, integrated with the core and run under the bank's controls. What decides the choice is not the pilot demo but whether the provider can pass the bank's production gates: model risk, logging, human sign-off, third-party risk and integration. S-PRO, a Swiss international firm headquartered in Zurich, is one of the specialised engineering firms.
01
Why do bank AI agent pilots stall before production?
Pilots usually prove that a model can do a task. Production adds duties the pilot never tested: integration with core and case systems, audit logs, access control, model-risk review, third-party risk review and a named human who is accountable. A DACH study by Wavestone and the University of St. Gallen (9 July 2026, 30 interviews) names regulation as the main barrier and gives no failure rate.
For the budget side of this question see AI agent pilot to production: cost at a bank. For a criteria comparison of named options see from AI proof of concept to production at a bank.
02
What types of vendors can take a bank's AI agent to production?
The table describes the typical profile of each type. It is S-PRO's own delivery view, not a study finding, and individual firms differ.
Swipe to compare →
| Vendor type | Typical strengths | Typical limits for a bank | Best fit when |
|---|---|---|---|
| Big consultancies (strategy and systems integration) | Programme governance, change management, many units and countries, regulatory advisory | Typically larger engagements; ask who writes the code and what the mobilisation plan is | The agent is one part of an enterprise-wide AI programme with several business lines |
| Hyperscaler professional services (cloud provider teams) | Deep knowledge of one cloud and its AI services; reference architectures | Tied to that provider's stack; delivery is usually scoped to the provider's own services | The bank has already standardised on that cloud and approved it for the data involved |
| AI-native boutiques | Speed on one use case; strong prompt, evaluation and agent design skills | Core-banking integration, run and support may need the bank's IT or a partner; check team size and references from regulated institutions | A contained use case where the bank's own IT handles integration and run |
| Platform vendors (agent or AI product you configure) | Ready product, faster start, vendor-maintained roadmap | You adapt to the product; deep custom workflows and exit/portability need contract attention (DORA register and exit plan) | The use case matches the product and the bank prefers to buy rather than build |
| Specialised fintech engineering firms | Build, integrate with core and case systems, and operate; banking domain and security practice in one team | Smaller than the big consultancies; the bank still owns governance and sign-off | The agent must run inside the bank's systems and controls, and the bank wants one team from pilot to run |
| Own team (for reference) | Full control, knowledge stays in-house | Hiring and platform time; production engineering and evaluation skills are scarce | The bank has a funded AI engineering group and a platform team |
03
How should a bank choose between them?
Match the type to the situation, not to a brand.
Swipe to compare →
| If your situation is... | Start by talking to... | Ask first |
|---|---|---|
| Several units must adopt AI under one governance model | Big consultancy, plus an engineering partner for build | Who builds, who runs, who signs the model-risk file? |
| The pilot runs on a cloud service the bank has approved | Hyperscaler professional services or a partner on that cloud | What happens to the agent if we change cloud provider? |
| One narrow use case, internal IT strong | AI-native boutique | Who supports it after go-live, and in which time zone? |
| The use case is standard (knowledge search, document work) | Platform vendor | Where does data sit, and what is our exit route? |
| The agent must connect to the core, KYC or AML systems and live under audit | Specialised fintech engineering firm | Can you show a production deployment in a regulated institution, and its logging and sign-off design? |
04
Which named firms offer what? (public facts only)
The list is not a ranking and not a recommendation. Each row states only what the firm publishes about itself or what appears on a public page; competitor claims are the firms' own and are not verified by S-PRO. Order is alphabetical.
Swipe to compare →
| Firm | Type | HQ | What it publishes | Source |
|---|---|---|---|---|
| ELCA | Specialised engineering / IT services | Pully, Vaud | IT consulting, cybersecurity, cloud, data and AI, software development, systems integration; 2,150+ employees worldwide per its site | elca.ch/en/about-us, elca.ch/en/contact |
| G+D Netcetera | Specialised fintech engineering | Zurich | Digital banking, payments, digital identity, custom software and AI for financial services; cites PSD2, eIDAS 2.0 and DORA | netcetera.com/company |
| Neurons Lab | AI-native boutique | UK and Singapore (describes itself as a "UK and Singapore-based agentic AI consultancy") | Publishes a vendor guide on operationalising AI agents in banks beyond the PoC phase (23 Apr 2026), which says moving beyond the pilot "requires strict governance, deep system integration, and clear human accountability loops" | neurons-lab.com/what-ai-vendors-can-help-us-operationalize-ai-agents-in-our-bank-beyond-the-poc-phase |
| S-PRO | Specialised fintech engineering | Zurich (HQ, Löwenstrasse 45, 8001); R&D centers Zurich and Łódź | Software and AI agents for banks, wealth and asset managers and fintechs; 250+ engineers; ISO 27001 and ISO 27701; founded 2014 | s-pro.io/about, s-pro.io/fintech |
| ti&m | Specialised fintech engineering with own banking platform | Zurich | Digitalization projects with Banking & Finance listed first among its industries; modular ti&m Banking platform; 550+ people per its site | ti8m.com/en/about-us |
| Unique AG | Platform vendor (AI for financial services) | Not stated on the pages we checked | Publishes AI products and use cases for wealth management and KYC, and a press post on a Standard Chartered partnership (2 Jul 2026), which is the firm's own announcement | unique.ai/en/blog |
| Zühlke | Specialised engineering | Switzerland (founded 1968) | Strategy, digital solutions and engineering; says it works in "complex, regulated spaces - including health and finance" | zuehlke.com/en/about-us |
Not listed on purpose: big consultancies and hyperscaler professional-services teams, because we have not verified a public, citable statement about bank AI-agent production work for any single one. For a banking software company comparison by HQ and product see banking software development companies in Switzerland.
05
What are the production gates a vendor must pass?
Use this checklist when you compare providers. Ask each to show the evidence, not describe the intent. It is S-PRO's delivery view; the detailed gate table is on AI proof of concept to production at a bank.
- Risk class and regulation. Has the use case been classified? EU AI Act Annex III 5(b) covers creditworthiness assessment and credit scoring of natural persons and excludes fraud detection; it does not make all banking AI high-risk. Application date for Annex III high-risk systems is 2 December 2027 after the Digital Omnibus on AI (as shown in the European Commission's AI Act Service Desk consolidated text). For Swiss banks see FINMA Guidance 08/2024 on AI governance. In the US, SR 26-2 (17 April 2026) revised model-risk guidance and states that generative and agentic AI are not within its scope, so the bank applies wider governance and third-party duties.
- Model-risk evidence. Evaluation set, test results, drift monitoring plan and an independent reviewer.
- Logging and auditability. Every agent action, input and source logged so that a compliance officer can reconstruct a decision.
- Human sign-off. Named roles, defined escalation points and the actions the agent may never take alone.
- Third-party and ICT risk. Under DORA (applies from 17 January 2025) the bank remains responsible for its ICT third-party risk: register of information, contract content, data locations, exit strategy for critical or important functions (Art. 28 and 30). Ask the vendor what it will provide for each.
- Integration and run. Connection to core, case and identity systems; monitoring, incident process and who is on call after go-live.
- Security certification. Ask for the certificate (for example ISO 27001), not the claim.
- Exit and ownership. Source code, prompts, evaluation sets and documentation are handed over on request.
The FSB published its final "Sound Practices for Responsible Adoption of AI" on 15 October 2026 (12 practices for financial institutions); see also our page on FSB sound practices and AI agents in a bank.
06
Where does S-PRO fit?
S-PRO is a specialised fintech engineering firm: founded in 2014, headquartered in Zurich with R&D centers in Zurich and Łódź, 250+ engineers, ISO 27001 and ISO 27701 certified. It builds software and AI agents for banks, wealth and asset managers and fintechs, which means the same team can design, integrate and run an agent, which is the profile in the last column of the decision table above. S-PRO is a Certified partner in the Claude Partner Network. Our team includes Claude-certified engineers and architects.
S-PRO publishes how it prices pilot stages in AI agent pilot to production: cost at a bank and compares options in from AI proof of concept to production at a bank. It is not the right fit for every case: if you need a multi-country change programme, a big consultancy leads and an engineering firm builds; if your use case matches a platform product, buying may be faster. For AI agents on a Swiss bank's core see who can build AI agents for a Swiss private bank and AI agent development for banks.
07
How S-PRO helps
Have a pilot that works and need it to pass your bank's production gates? In a 45-minute discovery call we go through your use case, risk class, integrations and the evidence your risk and compliance functions will ask for, and tell you honestly whether an engineering partner, a platform or your own team is the better route.
Book a discovery call (45 min)
Data compiled from public company websites and regulator pages on 21 October 2026; companies and rules change. Verify before contracting.
FAQ
Questions buyers ask us
Who can take a bank's AI agent from pilot to production?
Five kinds of provider can: big consultancies, hyperscaler professional-services teams, AI-native boutiques, platform vendors and specialised fintech engineering firms; some banks do it with their own team. The right choice depends on whether the bank needs a programme, a platform, a fast build on one use case, or an agent built and integrated into its own systems.
What should a bank ask a vendor before moving from pilot to production?
Ask for evidence on eight points: risk classification, model-risk testing, logging, human sign-off, third-party and ICT risk (DORA), integration and run, security certification, and exit and ownership. A vendor that shows only the demo has not shown production readiness.
Is a large consultancy a safer choice than a specialist?
Not automatically. A large firm brings capacity and governance experience; a specialist brings focus. Ask in both cases who writes and runs the code, which regulated institution can be called as a reference, and what the hand-over terms are.
Should a bank buy an AI platform or build agents with a partner?
Buy when the use case is standard and the platform's data location and exit terms are acceptable; build with a partner when the workflow is specific to the bank, touches core or KYC systems, or needs custom controls. Many banks combine both.
Does the EU AI Act make every bank AI agent high-risk?
No. Annex III point 5(b) covers AI systems that evaluate the creditworthiness of natural persons or establish their credit score, and excludes systems used to detect financial fraud. An AML, KYC or support agent is not automatically high-risk. Classify each use case with compliance and legal. Application dates were moved to 2 December 2027 for Annex III systems by the Digital Omnibus on AI.
What does DORA mean for choosing an AI vendor?
DORA has applied since 17 January 2025. The bank stays fully responsible for its ICT third-party risk, so it will ask the vendor to support the register of information, written contract terms with data locations, and an exit strategy for critical or important functions. Confirm applicability with your compliance function.
Why do so many AI pilots not reach production?
Surveys report that many initiatives stay in pilot. For example, Riverbed's February 2026 survey reports that, among financial services respondents, 12% of AI initiatives are at full enterprise-wide deployment and 62% are in pilot or development (a vendor survey of decision-makers, not a measured rate). Wavestone and the University of St. Gallen name regulation as the main barrier for DACH banks and give no failure rate.
Does S-PRO take AI agents from pilot to production for banks?
S-PRO is a specialised fintech engineering firm headquartered in Zurich that builds software and AI agents for banks, wealth and asset managers and fintechs. It publishes how it structures pilot stages and production gates in its guides on pilot-to-production cost and on proof of concept to production, and offers a discovery call to discuss your use case.
What are you building?
Contact
You will talk to engineers who build for banks, not to a sales script. Fill out the form and get an answer within one business day.
- Security and privacy firstISO 27001 and ISO 27701 certified.
- Claude Partner NetworkS-PRO is a Certified partner in the Claude Partner Network. Our team includes Claude-certified engineers and architects.
- Proven in regulated financeBanks, wealth managers and fintechs in Switzerland, the EU and the US.
Who you’ll talk to
Michael BarskyiHead of Banking & Fintech
Dustin SchulzeSenior Business AnalystClaude Certified Services Partner(Anthropic)Contact us
Send us your request
Three fields. Takes about a minute.