Demo listing. This page uses illustrative seed metadata to demonstrate the Atlas. Claims shown here are not verified product facts.
Formulary
Use-case formulary for insurance AI investment that admits a candidate only when its functionality, data, and addressed need are stated…
A use-case formulary for insurance AI investment that admits a candidate only when its functionality, data, and addressed need are stated precisely, forces the portfolio to hold positions in discovery as well as efficacy, and closes each use case against benefit booked into the loss and expense…
Last verified 15 Sept 2026 · Updated 23 Sept 2026 · Metadata v4
Problem
The first two years of an insurer's AI programme at a multi-line carrier with EUR 500M–5B gross written premium, entering through claims operations where the source shows the largest cost centre and the most mature applications, then extending to servicing, underwriting, and product.
Outcome
A deployment-ready foundation that teams can configure into production.
Who uses it
- Operations Analyst
- Solution Architect
Key capabilities
Core workflow
AI-assistedIncludedPrimary operating workflow for this foundation.
Document intelligence
AI-assistedIncludedExtract and ground decisions from operating documents.
Typical workflow
Primary operating flow
Trigger: An operator starts the primary use case
Task
Stage 1: Capture inputs
Operator
AI-assisted
Stage 2: Assist with draft
System
Human checkpoint
Stage 3: Human approval
Approver
Task Automated AI-assisted Human checkpoint Decision
About this foundation
Portfolio discipline for a capability the industry has barely started buying. Consultancies sell the use-case longlist and vendors sell the model; Formulary is the standing register that turns a longlist into a governed portfolio — data readiness before build, a conduct gate before anything touches pricing or claims decisions, and a booked-benefit close that lets a Chief Data Officer retire a use case without retiring the programme.
Related applications
- Coadjust
Claims-workforce operating system that assigns every claim decision to an adjuster, a model, or a paired review based on measured…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- Loadline
Premium-composition platform for life and health risk carriers in which every production model, engagement programme, and automation is…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- Nightshift
Actuarial production control plane that runs the valuation and reporting close unattended, attributes every movement in reserves and…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- Pilothouse
Innovation portfolio system for incumbent insurers that ties every insurtech pilot, partnership, and minority investment to the specific…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- Throughline
Operating-cost control plane for Irish-domiciled carriers serving multiple EU markets, which meters every inbound work item through…
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
- Planvector
Construction drawings intelligence
- • Addresses the same problem: Manual Workflow, Fragmented Systems
- • Shared capabilities: Workflow Automation, Document Intelligence
Primary operating flow
Trigger: An operator starts the primary use case
Task
Stage 1: Capture inputs
Operator
AI-assisted
Stage 2: Assist with draft
System
Human checkpoint
Stage 3: Human approval
Approver
Actors
Operator, Approver
Outputs
- Completed work item
Evidence generated
- Audit trail
Exceptions
- Incomplete inputs returned to operator
Task Automated AI-assisted Human checkpoint Decision
Included ships in the foundation · Configurable is switched or tuned per customer · Extension is customer-specific build scope · Planned is on the roadmap and not available today.
Core workflow
AI-assistedIncludedPrimary operating workflow for this foundation.
Document intelligence
AI-assistedIncludedExtract and ground decisions from operating documents.
- Architecture class
- Domain-driven design, OpenAPI-first
- Bounded contexts
- 5
- API-first
- Yes — OpenAPI contracts are authoritative
- Identity
- Enterprise OIDC / SAML via the fazeZERO identity blueprint; tenant-aware role-based access.
- Multi-tenancy
- Tenant-aware
- Service boundaries
- Bounded contexts behind one API server.
- Integration approach
- Ports-and-adapters: every external system sits behind an adapter; OpenAPI contracts for inbound APIs.
- Eventing
- Integration events via transactional outbox.
- Storage abstraction
- Repository interfaces; DynamoDB or relational adapters.
- Deployment pattern
- Containerized API + web application; infrastructure as code per cloud profile.
- Architecture version
- 1.0
Approved domain names
- identity
- catalog
- workflows
- Web Application
- API Server
- Application Services
- Domain / Generated Core
- Adapters
- Customer Systems
Generator source, templates and factory orchestration are proprietary and are not part of this listing.
Reference Adapter: shipped and tested · Previously Integrated: delivered before · Standard API Pattern: integrates via a documented pattern · Customer-Specific: built in your implementation.
APIs
| Integration | Status | Direction | Method |
|---|---|---|---|
| Customer systems of record | Standard API Pattern | bidirectional | REST API |
Deployment
- Deployment models
- Customer Cloud, Private Cloud
- Cloud profiles
- Azure Profile, Cloud-Neutral
- Containerized
- Yes
- Regions
- GLOBAL
Cloud profiles describe approved deployment patterns. They are not formal marketplace certifications.
Data handling
- Stores customer data
- Configurable
- Data leaves customer environment
- Configurable
- Uses external AI provider
- Configurable
- Sends logs externally
- No
- PII expected
- Determined during customer configuration
- Data-residency support
- Yes
- Subprocessors required
- Determined during customer configuration
Identity & access
- Authentication
- OIDC, Entra ID, SAML
- Authorization
- Role-Based, Tenant-Aware
- Source availability
- Proprietary
Support
- Implementation
- Delivered by fazeZERO or a certified partner during the Solution Definition and AI Production Sprints.
- Production support
- Production support available under a separate support agreement.
- Contact
- support@fazezero.com
Badges
fazeZERO Verified
Listing metadata and published technical claims have been reviewed by fazeZERO.
Issued 23 Sept 2026
Evidence shows that this listing represents real engineering. Internal metrics are only published when fazeZERO has approved them for publication.
Build
Automated tests
Deployment validation
- Last verification
- 15 Sept 2026
- Release
- 1.0.0
- Architecture version
- 1.0
- Listing metadata version
- 4
- Last published
- 23 Sept 2026