Pricing for Regional Carriers and MGAs

A claim is counted when a FNOL record is created and routed through Claimflint's enrichment engine. Reopened files from a prior period count as new intake in the new billing cycle. Monthly volumes are metered — if you consistently run above your tier cap, we'll reach out proactively to discuss the next tier.

Yes. Most pilots start with one line — typically personal auto or homeowners — to validate cycle time reduction on a defined dataset. Once results are confirmed, adding additional lines is a configuration change, not a new implementation. Multi-line bundling is included in the Enterprise tier.

The Pilot tier is designed to go live within 30 days. The first two weeks cover API integration and data mapping to your carrier core; the second two weeks cover validation testing and adjuster training. Growth tier adds the full bi-directional integration, which typically adds 5–10 business days.

The Pilot tier is month-to-month. Regional carriers run formal internal pilots before committing to vendor contracts, and our pricing reflects that procurement reality. Growth and Enterprise are typically 12-month agreements, which enables the dedicated implementation rep, the full bi-directional carrier core integration, and the SLA guarantees that come with those tiers.

Yes. Claimflint supports on-premise carrier cores via our batch connector — flat-file exchange over SFTP or direct API call through your VPN. The batch connector covers Guidewire on-prem, Duck Creek on-premise, and Insurity legacy environments. Real-time REST integration requires outbound API access from your core, which most modern on-prem environments support.