Comparisons
hx vs Convr: Choosing between point solutions and integrated platforms for commercial insurance
Mar 24, 2026

Compare hx's integrated platform with Convr's document extraction for commercial insurance submission automation. Expert analysis of architecture trade-offs.
Commercial insurance carriers evaluating underwriting technology face a choice between different architectural approaches. Convr is an AI-powered underwriting workbench focused on submission processing, data enrichment, and workflow automation. hyperexponential is an underwriting decision platform that combines underwriting infrastructure, triage, and portfolio analytics in a unified system.
With a workbench, enriched data flows to external pricing tools and raters. With an underwriting decision platform, submission data connects directly to pricing models and feeds back into portfolio-level insights, enabling better risk selection and model refinement over time.
Convr: AI-powered underwriting workbench
Convr is a modular AI underwriting workbench that enriches and expedites commercial insurance through data, underwriting insights, and risk scoring. The platform includes six core modules: Intake AI for document processing, Risk 360 AI for data enrichment, Answers AI for submission Q&A, Scores for risk evaluation, Insights for analytics, and Workflow for team collaboration and routing.
Convr's data enrichment ecosystem includes partnerships with Dun & Bradstreet, Experian, HazardHub, and other industry sources. Its proprietary data lake contains information on over 85 million businesses, so underwriters receive enriched submissions with firmographic data, business classifications, and risk signals without manual research.
Convr's business rules framework lets carriers configure submission routing, scoring, and prioritization based on risk appetite. Teams can set up auto-decline rules for out-of-appetite submissions, route specific lines of business to appropriate underwriters, and flag high-priority opportunities based on customizable criteria. The platform supports Excel Rater Templates and maintains a partnership with Coherent for rating integration, so carriers can connect existing pricing tools rather than replacing them.
hx: Underwriting decision platform
hyperexponential takes a different architectural approach, providing the underwriting infrastructure itself rather than orchestrating around external tools. The platform rests on three pillars: build better models faster through Python-native development, accelerate the underwriting workflow through API integrations and in-model safeguards, and make better underwriting decisions through automatic data capture that surfaces historical performance as input for portfolio analysis, benchmarks, and what-if scenarios.
hx covers the full underwriting workflow, from intake through pricing to portfolio analysis. The Ingestion Agent extracts data from broker submissions, triage ranks opportunities by expected profitability with indicative pricing at the point of intake, and pricing models deliver rate guidance within a single environment where underwriters progress from submission through quote without switching systems.
For actuarial teams, hx provides a native rating engine where models are built in Python rather than Excel or proprietary languages. Actuaries can deploy model updates without IT dependency, using reusable components and pre-built libraries. The Actuarial Agent provides a chat-based interface that lets actuaries build, edit, and ask questions about models using natural language.
Portfolio intelligence provides real-time analytics that connect underwriting decisions to book performance. Features like batch rating enable scenario analysis across the portfolio, helping leadership understand the impact of rate changes before implementation and track how individual decisions shape loss ratios.
Where the approaches diverge
The architectural differences between these platforms shape how carriers experience them day to day. Understanding where they diverge helps clarify which approach aligns with your organization's priorities and existing technology investments.
Pricing infrastructure
Convr connects to external pricing systems through Excel Rater Templates and its Coherent partnership. Carriers using Convr maintain their existing raters or integrate with other pricing platforms via API, which means the workbench enriches and routes submissions while the rating engine lives elsewhere.
hx provides the underwriting and rating infrastructure natively, so actuaries build and deploy models within the platform using Python, with version control, testing environments, and governance built in.
Data capture and feedback loops
Convr enriches submissions with external data and surfaces insights for underwriter decisions. The platform's data lake enables risk scoring and classification at the point of intake.
hx captures every underwriting decision and surfaces that data as input for model refinement. The automatic data capture creates feedback loops between underwriting actions and actuarial analysis, so portfolio performance, win/loss patterns, and underwriting trends become inputs for benchmarks and what-if analyses rather than separate reporting exercises.
Configurability and customization
Convr's business rules framework offers low-code configuration for submission routing, scoring, and workflow automation, enabling teams to adjust rules without deep technical expertise for standard use cases.
hx provides Python-based flexibility with low-code options for common patterns. This approach requires more technical capability but enables customization down to the schema, rules, and dashboard for each line of business, addressing complex commercial lines where low-code configuration alone cannot accommodate non-standard risk characteristics or bespoke rating logic.
Scalability
Convr's rating capabilities depend on the quality and performance of connected external raters, which means carriers inherit whatever limitations those systems bring.
hx's Python-native environment handles complex models at enterprise scale, so carriers processing high volumes or running sophisticated rating algorithms benefit from infrastructure designed for that workload rather than layered on top of existing tools.
Capability comparison
The table below summarizes how each platform addresses core underwriting workflow capabilities. These differences reflect the architectural distinction between a workbench that orchestrates external tools and a platform that provides native underwriting infrastructure.
Capability | Convr | hx |
|---|---|---|
Submission ingestion | AI-powered extraction across document types | Ingestion Agent with direct connection to pricing models |
Data enrichment | Proprietary data lake (85M+ businesses) plus third-party partnerships | API integrations with external sources; captures internal pricing data as input for model refinement |
Triage and prioritization | Business rules framework with scoring and routing | Indicative pricing at intake; one-click progression to full quote |
Pricing and rating | Connects to external raters (Excel templates, Coherent partnership) | Native Python rating engine with version control and governance |
Portfolio intelligence | Insights module for analytics | Real-time analytics with batch rating; decision data feeds back into pricing models |
Customization approach | Low-code business rules configuration | Python-based flexibility with low-code options |
The key difference appears in how data moves through each system. Convr enriches and routes submissions to external pricing tools, while hx connects ingestion directly to pricing and feeds decision data back into portfolio analytics.
When each approach fits
Convr fits better when you have existing pricing tools that work well and want to preserve that investment. If your primary pain point is submission intake efficiency and data enrichment rather than pricing transformation, a workbench addresses those needs without forcing broader change. Teams that prefer low-code configuration over custom development will find Convr's approach more accessible.
hx fits better when improving underwriting decision-making through better pricing, risk assessment, and strategic execution is the priority. The integrated approach drives loss ratio improvement across your entire book through better risk selection, not just efficiency gains that scale across your underwriting team. Complex commercial lines requiring deep customization often need the flexibility that Python-based development provides, and carriers who want underwriting decisions to feed back into portfolio analysis and model refinement benefit from data flowing through a single system.
How hx approaches underwriting transformation
Aviva built 20 pricing models in nine months after migrating commercial pricing to hx, integrated with existing systems via API. AEGIS London deployed 59 models in nine months, unifying pricing and underwriting workflows.
Actuarial teams gain independence in model development and deployment. Underwriters receive pricing guidance alongside real-time portfolio data and benchmarks against similar risks at the point of decision. Leadership gains visibility into how individual decisions affect book performance.
The platform serves over 50 customers globally, powering more than $50 billion in gross written premium annually. At Lloyd's, approximately half of the market uses hx for pricing and underwriting.
The hx platform closes the loop from model build to underwriting execution to portfolio feedback. For carriers evaluating underwriting transformation alongside workflow improvement, request a demo to see how hyperexponential approaches commercial P&C underwriting.
FAQ
What's the main difference between Convr and hx?
Convr is an AI-powered underwriting workbench that enriches submissions and orchestrates workflow around external pricing tools. hx is an underwriting decision platform that provides native underwriting infrastructure alongside triage and portfolio analytics, with data flowing from submission through pricing into portfolio insights.
Can Convr and hx integrate with the same core systems?
Both platforms offer API integrations with policy administration systems, data providers, and other core insurance technology. Convr emphasizes data partnerships for submission enrichment, while hx emphasizes integrations that connect underwriting decisions to workflow and portfolio intelligence.
Which platform is better for actuarial teams?
hx provides a Python-native environment for actuarial model development, with self-service deployment and version control built in. Convr connects to external rating tools rather than providing actuarial modeling capabilities.
How do implementation approaches differ?
Convr offers tiered packages from Essential to Enterprise, with lower tiers requiring no IT integration. hx implementations typically involve deeper integration with existing systems and migration of pricing models.
Which handles complex commercial lines better?
hx's Python environment provides greater flexibility for complex rating logic and non-standard risk characteristics. Convr's low-code business rules work well for standardized workflows.
What data enrichment capabilities does each offer?
Convr maintains partnerships with major data providers and operates a proprietary data lake for submission enrichment. hx integrates with external data sources through APIs and focuses on capturing internal pricing data as a feedback loop for model improvement.
How should carriers evaluate these platforms?
Assess your current pricing infrastructure and what you're trying to improve. If existing pricing tools meet your needs and the primary goal is intake efficiency, evaluate Convr. If improving underwriting decisions through better risk selection and portfolio visibility is the priority, evaluate hx.




