ZTABS builds AI copilots for Zurich financial institutions across insurance underwriting, banking compliance, wealth management and asset management. A copilot augments professionals by retrieving relevant information from enterprise knowledge bases, processing documents and data, and presenting analysis for human review and decision. The copilot preserves professional decision authority in domains where regulatory requirements, professional liability and organisational governance mandate human oversight.
Zurich copilot demand spans insurance submission processing and risk analysis, banking regulatory monitoring and KYC refresh, wealth management client review preparation, and asset management research and compliance support. ZTABS is remote-first by design, with an office in Houston, Texas. Our AI copilot development services cover enterprise copilot automation across markets.
Scope and requirements
| Need | What we build | Key requirement |
|---|
| Insurance underwriting | Submission processing, risk analysis, pricing support, treaty management | FINMA governance, actuarial calculation validation |
| Banking compliance | Regulatory monitoring, KYC refresh, AML investigation support | FINMA proportionate governance, FADP processing |
| Wealth management | Client review preparation, portfolio analysis, tax documentation | Banking confidentiality, multilingual output |
| Asset management | Investment research, ESG analysis, fund documentation, trade compliance | Licensed data sources, regulatory reporting |
How copilots work
A copilot integrates into the professional's existing workflow tools. It retrieves relevant information from enterprise knowledge bases using RAG (retrieval-augmented generation), processes and synthesises data, and presents analysis for human review and decision.
RAG architecture. The retrieval pipeline indexes the organisation's authorised documents, databases and other sources using semantic and keyword search. A pretrained language model uses the retrieved context to produce task-specific responses grounded in the organisation's actual data. The engagement agrees which tenant data, object permissions, provider products, APIs, versions and licences the copilot may access. Retrieval and write operations are separately scoped.
Citation and provenance. RAG, citations, schema and guardrails reduce errors but cannot prevent hallucination or guarantee completeness or faithfulness. Calibrated confidence scores do not establish correctness or grant action permission. Users should verify cited original sources, clause revisions and numerical calculations independently. A qualified professional reviews any consequential advice before the organisation acts on it.
Deterministic calculations. Insurance pricing, SST (Swiss Solvency Test), SCR, IBNR reserves, loss development and actuarial calculations require deterministic, versioned calculation engines. These calculations are validated and reconciled separately from LLM-generated narrative. The copilot may present calculation results alongside narrative analysis, but the calculation logic is implemented as separate, auditable code with qualified actuarial or professional review.
Building a copilot for Zurich insurance, banking or wealth management?
Tell us about your professional workflows, data sources and regulatory requirements. We start with domain analysis and workflow observation.
FINMA governance and proportionate AI expectations
FINMA Guidance 08/2024 (published 18 December 2024) addresses governance and risk management when using AI. As of the Federal Council's 12 February 2025 decision, Switzerland pursues a sector-specific, technology-neutral approach and ratification of the Council of Europe AI Convention rather than introducing horizontal AI legislation.
FINMA Guidance 08/2024 operationalises existing organisational duties for AI use. It covers governance, inventory, data quality, testing, documentation, explainability and independent review. FINMA expects proportionate governance aligned with the materiality of the AI application and the institution's risk profile. The guidance is not a legally binding circular and does not constitute product approval.
Outsourcing framework. Where the copilot uses third-party services, FINMA's outsourcing circular applies for material functions. The actual outsourcing classification depends on the function's materiality to the institution, not on the vendor's product category. Whether regulatory notification or approval is required depends on the institution type, the function being outsourced and the applicable FINMA circular or entity-specific rules. The engagement supports the institution's outsourcing inventory, due diligence, contractual requirements and audit access obligations.
Data flow mapping. The copilot data flow maps all processing locations including inference, embedding, vector storage, logs, backups, telemetry, model updates and admin support. Each processing location's applicable jurisdiction and contractual terms are documented. On-premises or Swiss-region deployment may reduce cross-border transfer complexity but does not by itself guarantee zero data egress across the entire stack.
FADP and cross-border data transfer
Swiss cross-border data transfer is governed by the FADP (Federal Act on Data Protection). The Federal Council makes adequacy decisions; countries listed in Annex 1 of the Data Protection Ordinance are recognised as providing adequate protection, including EU/EEA states and US organisations certified under the Swiss-US Data Privacy Framework. The FDPIC publishes guidance and assessments but does not itself make adequacy determinations.
For destinations without adequacy recognition, transfer mechanisms include: contractual data protection clauses notified to the FDPIC, FDPIC-recognised standard data protection clauses, and approved binding corporate rules. Banking confidentiality provisions under Swiss banking law apply to client-identifying information and must be assessed alongside FADP transfer conditions.
The copilot's data processing arrangements document the applicable transfer mechanism for each cross-border data flow. Banking confidentiality and FADP requirements are complementary, not redundant; satisfying one does not automatically satisfy the other.
Insurance underwriting copilots
Zurich's insurance and reinsurance sector creates demand for copilots supporting underwriting workflows at commercial and specialty insurers.
Submission processing copilot. Ingests broker submission packs including slips, loss history, financial statements and supplementary information. The copilot extracts key risk factors, classifies the business using the insurer's scheme and identifies information gaps. The underwriter reviews the copilot's extraction and classification rather than processing documents from scratch.
Risk analysis copilot. Compares submission risk factors against the insurer's portfolio data, historical loss experience and rating model parameters. The copilot identifies anomalies, concentration risks and factors the rating model may not capture. Risk analysis and underwriting decisions remain the underwriter's professional responsibility.
Pricing support copilot. Applies the insurer's rating model to extracted risk factors using deterministic, versioned calculation engines. The copilot presents preliminary pricing with rationale for the underwriter to review, modify or override. Actuarial calculations (loss development, IBNR, SST) are implemented as separate validated code, not generated by the language model. The underwriter owns the pricing decision.
Treaty management copilot. For reinsurance operations: processes quarterly accounts, calculates premium and loss allocations per treaty terms using deterministic calculations, reconciles with cedant statements and flags discrepancies for human review. Treaty wording interpretation requires qualified professional review. Licensed treaty data access terms govern what the copilot may process.
Banking compliance copilots
Regulatory monitoring copilot. Monitors FINMA, SBA, SNB and cantonal publications for regulatory changes relevant to the institution. The copilot classifies each publication by applicability and drafts impact assessments. Compliance officers review and refine the copilot's analysis, applying professional judgment to nuanced regulatory interpretation.
KYC refresh copilot. Periodic KYC review for existing clients: the copilot gathers updated information from approved public sources, checks sanctions lists and reviews transaction patterns. The copilot drafts the refresh assessment for compliance officer review. AML decisions and suspicious activity reporting remain the compliance function's responsibility under applicable Swiss AML legislation.
Wealth management copilot. Assists relationship managers with client review preparation: aggregating portfolio performance from custodians, calculating returns against benchmarks and drafting review presentations. The copilot accesses licensed portfolio data within agreed terms. Investment advice responsibility and suitability assessments remain with the relationship manager.
Illustrative Example
Hypothetical: Zurich specialty insurance underwriting copilot
A Zurich specialty insurance company handling commercial property, marine cargo and professional liability needs a copilot to augment the underwriting workflow for new business and renewal submissions.
The copilot would ingest broker submission packs, extract key risk factors and classify each submission using the insurer's underwriting scheme. It would compare extracted data against the company's portfolio of similar risks, identify concentration risks and generate a structured underwriting memo with preliminary pricing from the deterministic rating model. The underwriter would review, modify and decide on each submission.
Assumptions: the copilot accesses the insurer's rating models as separate deterministic calculation engines with versioned parameters, actuarial calculations are validated independently of LLM output, FINMA governance requirements are addressed within the insurer's existing risk management framework, broker submission formats vary and extraction accuracy is evaluated against agreed test sets, and licensed data source agreements are confirmed. Residual risks include rating model parameter currency, extraction errors for non-standard document formats, source data lag between insurer system updates and copilot index refresh, and underwriter adoption timelines. No guarantee of specific turnaround improvement, volume increase, premium impact or financial return.
This is a hypothetical scenario for illustration. Actual scope, timeline and cost depend on your requirements.
Cost and timeline
Copilot development as general custom platform engineering uses four guide tiers.
| Scope | Cost range | Timeline |
|---|
| Internal Tool | $25K to $60K | 6 to 14 weeks |
| Business Application | $60K to $150K | 14 to 28 weeks |
| Enterprise Platform | $150K to $300K | 28 to 40 weeks |
| Large-Scale System | $300K to $500K+ | 40 to 60+ weeks |
Insurance underwriting copilots with multi-document extraction and actuarial integration typically scope to the business application or enterprise platform tier. Banking compliance copilots with multi-regulator monitoring may scope to enterprise platform. Actual scope depends on integration count, compliance requirements and domain complexity. See the full custom software cost guide for details.
2026 US vendor benchmark
Ranges are 2026 US-buyer guide-based planning benchmarks for a mid-complexity business application: multi-role access, 3 to 5 integrations, custom workflows and a modern web frontend.
| Vendor type | Typical cost | Timeline |
|---|
| Freelancer or dev collective | $20K to $75K | 4 to 10 months |
| Offshore agency | $40K to $120K | 5 to 11 months |
| Nearshore agency | $70K to $200K | 4 to 8 months |
| US/EU agency (ZTABS tier) | $90K to $280K | 4 to 8 months |
| Big 4 or systems integrator | $250K to $800K+ | 8 to 16 months |
Ranges are 2026 US-buyer guide-based planning benchmarks for the scoped business-application comparison. Where applicable to the agreed engagement, legacy-system integration and compliance engineering or readiness preparation (SOC 2, HIPAA safeguards or PCI DSS controls) carry an additional guide allowance of $20K to $80K across vendor paths. Independent CPA SOC 2 examination and opinion are scoped and priced separately from internal readiness engineering. The guide uses 15 to 25 percent of build cost annually as an ongoing-maintenance planning estimate; actual support scope and fees are agreed separately. These are scoped planning allowances, not an empirical market survey or copilot-package rate card.
Need a scoped estimate for Zurich copilot development?
Share your insurance, banking or wealth management use case. We provide a scoped estimate after reviewing both four-tier scope and vendor benchmark context.
Proposal evaluation criteria
- Relevant domain copilot experience in insurance underwriting, banking compliance or wealth management with supporting project evidence
- RAG pipeline reliability including citation provenance, retrieval accuracy and hallucination mitigation with disclosed source coverage, missing sources and retrieval lag
- Data and security boundaries with clear FINMA governance support, FADP cross-border architecture, banking confidentiality handling and independent assurance responsibilities
- Domain-specific evaluation with held-out test cases covering insurance, banking and financial terminology against agreed acceptance criteria and actual selected model evaluation
- Transparent scope, milestones, change control, operating fees and ongoing support terms
- Provider team identifies who trains agreed users, delivers technical documentation and provides ongoing support; customer team identifies who validates domain outputs, accepts delivery milestones and handles agreed internal support; both parties agree staff and user languages, documentation scope and translation responsibilities
How delivery works
ZTABS is remote-first by design, with an office in Houston, Texas. Delivery uses overlapping working hours between US Central and Central European Time for scheduled collaboration.
Discovery and access inventory. The engagement begins with source system and API access review covering policy administration systems, claims platforms, portfolio management tools, custodian data feeds and regulatory monitoring sources. Licence entitlements, banking confidentiality scope and permitted data use purposes are verified for each source. Domain workshops with underwriters, compliance officers or relationship managers establish vocabulary requirements, workflow scope and evaluation criteria.
Model selection and runtime. Candidate models are evaluated against domain-specific held-out test sets covering insurance terminology, Swiss financial vocabulary and multilingual capability across German, French, Italian and English. Runtime and infrastructure choices are confirmed based on latency, throughput and data residency requirements.
Permission-boundary testing. Test sets verify access controls, client data isolation and scope boundaries. Negative tests confirm the copilot refuses out-of-scope queries and does not surface restricted client or counterparty data.
Pilot and acceptance. Pilot deployment targets a single agreed workflow (for example, submission processing or regulatory monitoring) with acceptance testing including hallucination detection, retrieval accuracy and citation correctness. Rollout extends to additional workflows with rollback capability at each stage.
Training and handover. Agreed user training sessions for each user group, domain validation methodology transfer to customer owners, and operations documentation with monitoring configuration and support escalation procedures.
When ZTABS is not the right fit
- Off-the-shelf copilot deployment for this engagement. We build custom copilots; generic copilot configuration is different scope.
- On-site embedded team for this engagement. ZTABS is remote-first by design. On-site presence is separately agreed where required.
- Independent actuarial or legal advice for this engagement. Compliance engineering is part of delivery; independent professional advice is separately agreed.
- FINMA product approval for this engagement. FINMA regulates institutions, not copilot products; institution governance is the institution's responsibility.
- Ongoing managed hosting or admin for this engagement. Identify hosting provider or internal team for post-handover operations; ongoing retainers are separately agreed.
White-label AI products
ZTABS builds custom white-label AI products for clients to brand and resell. Zurich enterprises can commission white-label copilot platforms for distribution.
Data governance
Each engagement agrees which tenant data, provider products, APIs, versions and licences the copilot may access, with retrieval and write operations separately scoped. Permission changes propagate across indexes, embeddings, caches, logs and fine-tuning data with a disclosed residual lag and agreed mitigations. Customer data is not automatically reused across other customers for model training.
Deletion and revocation across chunks, index entries, cached results, log entries, backup copies and fine-tuned model artifacts requires coordinated procedures. Trained model weights may retain residual memory that is not automatically reversible through simple deletion. The engagement specifies the deletion scope, verification method and residual risk acceptance.
Monitoring and operations
Quality dashboards. Retrieval accuracy, response quality, citation correctness, latency. Per-domain metrics for insurance, banking, wealth management and asset management copilots.
Model updates. Tested in staging with evaluation against held-out test cases and agreed acceptance criteria before production deployment. Rollback capability maintained.
Knowledge base. Ongoing ingestion of new documents, data and feedback. Index freshness and coverage tracking with disclosed gaps and source version currency.
Handover
Copilot handover includes runbooks, RAG pipeline configuration, model versions, provider accounts, monitoring dashboards, evaluation methodology and escalation procedures.
Ready to build a Zurich AI copilot?
Share your professional workflows, data sources and regulatory requirements. We start with domain analysis and workflow observation.