We built an underwriting copilot over 16 weeks: (1) Document processing: the copilot processes all submission documents using: document classification (automatically identifying: which document is the broker slip, which is the loss history, which is the financial statement — regardless of format), intelligent extraction (extracting from each document type: the relevant data fields; from the broker slip: named insured, coverage type, limits, deductibles, inception date, expiry date, and broker details; from loss history: claim dates, types, amounts, reserve status, and open/closed status; from financial statements: revenue, total assets, employee count, and key financial ratios), data validation (cross-referencing extracted data: does the broker slip limit match the loss history policy limit? Do the financial statement dates align with the policy period? Are there gaps in the loss history?
), and structured output (all extracted data presented in the company's standard underwriting worksheet format — the underwriter sees a pre-populated worksheet rather than a stack of documents).
(2) Risk assessment: the copilot performs preliminary risk assessment by: comparing against appetite (the submission data compared against the company's underwriting appetite for: industry type, geography, loss history, and risk size — instantly flagging: submissions outside appetite for rapid decline, and: confirming appetite for in-appetite submissions), peer comparison (the proposed risk compared against: the company's existing portfolio of similar risks — showing: how this risk compares on: key rating factors, historical loss experience, and current pricing — giving the underwriter: immediate context for pricing decisions), loss development (historical losses projected to ultimate using: standard actuarial development patterns — the underwriter sees: incurred-but-not-reported estimates and ultimate loss projections without waiting for: actuarial department calculations), and referral identification (automatically identifying: factors requiring senior referral — risk size exceeding authority levels, industries on the watch list, and unusual coverage features — routing to the appropriate authority with: context pre-gathered).
(3) Pricing support: the copilot generates a preliminary price using: the company's rating models (applying: the approved rating algorithm with the extracted risk data — producing: a technical price based on: exposure, loss history, and risk characteristics), market intelligence (comparing the technical price against: recent market pricing for similar risks — using: the company's own quote history to show: where the market is pricing similar risks), and pricing memo (drafting a pricing memo explaining: the technical price, adjustments for specific risk features, and: the recommended quoted premium with: supporting rationale — the underwriter reviews, adjusts, and approves).
(4) Quote generation: the copilot generates the quote document: pre-populated terms (the quote document pre-filled with: all risk details, coverage terms, conditions, and subjectivities — in the company's standard format), underwriter review (the underwriter reviews the complete quote, makes adjustments, adds: judgment-based conditions, and approves — the copilot handles: document formatting, consistency checking, and: version control), and broker distribution (the approved quote formatted and prepared for: broker communication — including: cover note, quote schedule, and: any supplementary documentation). (5) Consistency monitoring: the copilot enables the CUO to: see aggregated underwriting decisions (which risks are being quoted, at what prices, with what terms — across all 25 underwriters), identify inconsistencies (underwriters applying: different interpretations of the same guideline — flagged for: coaching or guideline clarification), and track pricing trends (portfolio pricing trends by: line, industry, and geography — ensuring: the portfolio reflects the intended risk appetite).
All deployed on Swiss infrastructure (Azure Switzerland — Zurich datacenter). The model (Mixtral 8x7B fine-tuned on insurance domain data) runs within the Azure Swiss region. No submission data leaves Switzerland.