LLM Integration Glossary for Fintech AI Automation in Switzerland

Scope and Context

The terms in this glossary describe the components of an AI automation engagement for a 201-500 person fintech firm in Switzerland. The scenario involves integrating LLMs into existing systems to reduce cost per support ticket, cut first-response time, and automate lead qualification, while maintaining PCI DSS compliance and Swiss data residency. The delivery model is a fixed-scope pilot, and the AI stack uses Anthropic Claude for quality-critical tasks and open-weight models for regulated data. The glossary is organized alphabetically and covers the technical, compliance, and operational terms that appear in the engagement.

A-D: Core Technical Terms

Anthropic Claude API is a hosted large language model service that provides high-quality text generation, classification, and reasoning capabilities. In this scenario, Claude is used for lead qualification scoring and content generation where output quality and instruction-following are critical. The API is accessed over HTTPS, and the client’s pre-processing layer masks PCI DSS-scoped fields before sending data to the model.

Data enrichment and cleanup refers to the process of taking raw, unstructured records and adding structured attributes or correcting inconsistencies. In a fintech context, this might involve extracting company size, industry, and payment method preference from email signatures and website text, then populating CRM fields. The LLM reads the unstructured input and outputs normalized values, reducing manual data entry by 60-80%.

Fixed-scope pilot is a two-week engagement where the vendor and client agree on one specific workflow, a defined dataset, and measurable success criteria before any broader rollout. For a fintech firm, this might mean testing lead qualification on 500 historical tickets to measure first-response time reduction and error rate, without touching production systems or live customer data.

G-L: Operational and Workflow Terms

Google Workspace integration means the LLM layer reads and writes to Gmail, Google Docs, and Google Sheets through the Google API. For a fintech firm, this might involve auto-drafting responses to inbound lead emails, extracting structured data from shared spreadsheets, or generating content briefs in Docs. The integration is additive: existing Gmail workflows continue to function, and the AI layer operates as an assistant within the tools the team already uses.

Human-in-the-loop model means the LLM drafts, classifies, or enriches data, but a human approves any output that touches money, health data, or contracts. In a fintech lead qualification workflow, the model might auto-respond to clearly low-intent inquiries, but any lead involving payment processing, regulatory questions, or enterprise contracts is flagged for human review. This keeps the system compliant with PCI DSS and internal risk policies while still reducing first-response time for routine cases.

Lead qualification uses an LLM to score and categorize inbound inquiries based on predefined criteria: company size, budget range, product fit, and urgency. In a fintech setting, the model might classify a lead as ‘high-intent payment integration’ versus ‘general inquiry’ and route it to the appropriate sales engineer. The human-in-the-loop model ensures that any lead flagged for compliance review is escalated to a human before outreach.

M-P: Compliance and Architecture Terms

Model-agnostic architecture means the system does not hard-code calls to a single LLM provider. Instead, it uses an abstraction layer that can route requests to OpenAI, Anthropic, or local open-weight models based on data sensitivity, cost, or quality requirements. For a Swiss fintech firm, this means marketing content generation can use Claude for quality, while PCI DSS-scoped data processing runs on a local Llama instance, all through the same API interface.

PCI DSS (Payment Card Industry Data Security Standard) is a set of security requirements for organizations that handle cardholder data. Requirement 3 mandates that cardholder data be rendered unreadable wherever it is stored. When an LLM processes payment-related documents, any PAN, CVV, or track data must be masked or tokenized before the data reaches the model API. For Anthropic Claude, this means the client’s pre-processing layer strips sensitive fields, and the model only sees the non-sensitive context needed for classification or enrichment.

Process audit is the first phase of an AI automation engagement, where the vendor maps existing workflows, identifies bottlenecks, and scores each process on automation potential, data availability, and business impact. For a fintech firm, this might reveal that lead qualification is 70% manual, that 40% of support tickets are repetitive, and that data entry from invoices takes 3 hours per week. The audit output is a prioritized list of workflows, each with a recommended pilot scope and success metric.

S-W: Scaling and Compliance Terms

Scaling across departments means moving from a single-team pilot (e.g., marketing lead qualification) to multiple use cases (support ticket triage, content generation, data cleanup) while maintaining consistent governance. The key challenge is that each department has different data sensitivity levels, approval workflows, and success metrics. A model-agnostic architecture helps here because the same orchestration layer can route different departments’ requests to different models based on data classification.

Swiss data residency requirements, under the Federal Act on Data Protection (FADP), mandate that personal data be processed in Switzerland or in countries with an adequacy decision. For a fintech firm, this means that customer data, including lead information, cannot be sent to US-based LLM APIs unless the data is anonymized or the vendor has a Swiss data center. Open-weight models on local hardware are the standard solution for PCI DSS-scoped and personal data workloads.

First-response time is the interval between a customer or lead sending an inquiry and receiving a substantive reply. An LLM triage layer can classify and draft a response in seconds, while a human reviews and sends it. For a 201-500 person fintech firm, this might reduce first-response time from 4 hours to 15 minutes for routine inquiries, while complex cases still go to a specialist. The cost per ticket drops because the human spends less time on initial triage and drafting.