hx vs Optalitix: Excel migration versus pricing transformation

Commercial insurance carriers evaluating Excel migration face a fundamental choice: preserve existing spreadsheet logic in cloud infrastructure, or rebuild pricing models on a Python-native foundation. Optalitix and hx represent these two approaches respectively.

Optalitix converts Excel models to cloud-hosted systems, maintaining familiar workflows while adding governance and API connectivity. hx requires rebuilding models in Python but removes Excel's architectural limitations at the foundation level. Both platforms serve carriers migrating from spreadsheet-based pricing, but the migration paths lead to different long-term capabilities.

This comparison examines where each platform excels, where they differ on core capabilities, and how to determine which approach fits your carrier's strategic objectives.

Optalitix: Excel models hosted in cloud infrastructure

Optalitix converts existing Excel pricing models to cloud-hosted systems, adding governance and connectivity while preserving spreadsheet logic. The platform targets carriers seeking operational improvements without rebuilding their actuarial infrastructure.

The migration path works by uploading Excel models, defining named input and output ranges, and deploying through Optalitix's cloud environment. Actuarial teams continue working in familiar Excel syntax while gaining version control, audit trails, and the ability to expose models via API.

For Excel migration specifically, Optalitix offers:

• Cloud hosting that claims 30x faster model run times than native Excel

• Version tracking and audit trails for regulatory compliance

• API connectivity to expose Excel logic to external systems

• Batch rating capabilities, though VBA models require conversion to Python first

• Risk Vision dashboards for monitoring model usage and outputs

The platform has a strategic collaboration with PwC for implementation support and maintains Lloyd's market presence with 81 syndicates using its catastrophe reporting portal.

The core tradeoff: Optalitix accelerates the path from Excel to cloud, but Excel's architectural constraints travel with the models. Row limits and formula complexity remain embedded in the converted systems. The inability to efficiently run sophisticated simulations or distribution fitting persists as well.

Advanced portfolio analytics like marginal risk impact analysis, benchmarking against complex risk parameters, and the data feedback loops that enable continuous model refinement fall outside what a spreadsheet converter can deliver. VBA models require conversion to Python before batch rating, and data ingestion capabilities remain limited. Optalitix addresses model hosting rather than end-to-end pricing and underwriting workflow.

For carriers willing to invest in migration effort, the question becomes whether that effort should preserve existing architecture or enable full pricing transformation. The implementation work required to migrate spreadsheets into Optalitix could instead deliver a Python-native foundation with hx. The investment is comparable; the long-term ceiling is not.

hx: Pricing models and raters rebuilt on Python-native architecture

hx takes a different approach to Excel migration: rather than converting spreadsheets to cloud, the platform provides a Python-native environment where actuaries rebuild models from the ground up. As an underwriting decision platform, hx connects model development, underwriting workflows, and portfolio analytics in a single environment. This requires more initial effort but means the platform operates without Excel's architectural constraints from day one.

The rebuild process leverages actuarial-specific libraries, pre-built components, and the Actuarial Assistant AI to accelerate development. Models deploy without IT dependency, moving from test to production in clicks rather than weeks. Aviva built 20 pricing models in 9 months using this approach, reducing policy creation time from over an hour to under 10 minutes.

For carriers migrating from Excel, hx's Python foundation provides:

• No row limits or processing constraints on portfolio size

• Access to the full Python data science ecosystem, including pandas, scikit-learn, and statsmodels

• Git-based version control with peer review workflows and granular audit trails

• Simulation and distribution fitting capabilities that Excel cannot support efficiently

• Automatic data capture that feeds pricing and underwriting decisions back into model refinement

Celent's independent analysis validates hx as a modern pricing solution with strong GLM and GAM modeling capabilities, positioning it for carriers requiring sophisticated modeling depth.

The core tradeoff: hx requires rebuilding models rather than converting them, but the platform reduces the Python learning curve through actuarial-specific libraries, pre-built components, and the Actuarial Assistant AI. Most actuaries with analytical backgrounds can build production models within weeks of training, and underwriters interact through purpose-built interfaces without needing Python knowledge. The payoff is a pricing and underwriting infrastructure that isn't bound by the architectural ceiling Excel creates for complex modeling and large-scale portfolio analysis.

Capability comparison

Both platforms address Excel migration but with different architectural foundations. The following comparison highlights where capabilities concentrate and where gaps exist.

The architectural distinction matters most for carriers with growth ambitions. Optalitix optimizes Excel workflows but cannot address constraints like the 1,048,576 row limit or VBA processing limitations. hx sidesteps these limitations entirely through its Python foundation but requires model rebuilding.

Pricing architecture and model development

Pricing architecture represents the most significant divergence between the two platforms, determining what types of models actuaries can build and how quickly they can deploy changes.

Optalitix preserves Excel model logic, converting spreadsheets to cloud-hosted systems that run faster and integrate via API. Actuaries continue working in familiar Excel environments. The platform acknowledges that GLMs have limitations in large data contexts, emphasizing gradient boosting tree-based models as an alternative for predictive performance.

hx opens access to Python's full data science ecosystem: pandas for portfolio aggregation, scikit-learn for predictive modeling, statsmodels for GLM development. Actuaries work in a language used across data science globally, making skills transferable and solutions easily searchable. For carriers where pricing sophistication or speed-to-market on model changes provides competitive advantage, native Python capabilities matter.

The practical implication: Optalitix gets you to cloud faster with existing models. hx takes longer initially but provides a foundation without the architectural ceiling that Excel creates for complex modeling, multi-line portfolio analysis, and catastrophe model integration.

Portfolio intelligence and data feedback

Optalitix aggregates and visualizes data from Excel models through Risk Vision dashboards. Carriers can track model usage, monitor performance, and generate reports. However, data flows in one direction: out of models for reporting, not back into models as input for refinement.

hx captures every underwriting decision automatically, creating a longitudinal dataset connecting submissions to quotes to bound policies. Actuaries can run rate adequacy monitoring, what-if scenario testing across their book of business, and segment-level performance analysis using captured data as direct input for model iteration. These feedback loops improve pricing accuracy over time.

For carriers focused primarily on workflow efficiency and governance, Optalitix's reporting capabilities may suffice. For carriers where continuous model refinement drives combined ratio improvement, hx's feedback architecture provides capabilities Optalitix cannot replicate.

When Optalitix fits

Evaluate Optalitix if your primary objective is operational improvement without architectural transformation:

• Your Excel models work well and you need cloud governance, not model rebuilding

• Your actuarial team lacks Python expertise and isn't positioned for upskilling

• You want faster implementation with minimal workflow disruption

• Your data volumes stay within Excel's structural limits (under 1 million rows per model)

• You're an MGA or smaller insurer where Optalitix's price point aligns with budget constraints

Implementation contexts where Optalitix excels include carriers seeking quick wins on governance and collaboration, teams overwhelmed by Excel version control challenges, and organizations piloting cloud migration before broader transformation.

When hx fits

Evaluate hx if your strategic objectives require capabilities that Excel architecture cannot provide:

• You need sophisticated modeling (simulations, distribution fitting, GAMs) that Excel cannot support efficiently

• Your data volumes exceed Excel's row limits or will as you grow

• You want pricing data to feed back into model development, not just flow out for reporting

• Your actuarial team has Python capability or is ready to develop it

• Pricing sophistication and model deployment speed directly impact your competitive position

Strategic contexts where hx excels include carriers transforming both pricing and underwriting operations together, organizations requiring portfolio-wide visibility across multiple lines, and teams where combined ratio improvement depends on continuous model refinement. The platform was built for specialty and commercial P&C, where high-touch underwriter and actuary collaboration requires flexible data integration throughout the underwriting workflow.

Integration and deployment considerations

Both platforms integrate with policy administration systems, but documentation depth varies.

Optalitix claims pre-built integrations supporting Duck Creek and Guidewire, though detailed architectural documentation and production implementation examples are limited. The platform emphasizes auto-discoverable APIs for no-code integration configuration.

hx has established a Duck Creek Technologies partnership with an Anywhere Enabled Integration announced in 2025. For Guidewire, hx maintains a partnership relationship. The platform provides 30+ documented integration examples for third-party data sources.

Implementation timelines vary based on organizational factors rather than platform architecture alone. Pool Re completed Optalitix implementation in 6 months; Aviva and AEGIS London completed hx implementations in 9 months, but the time taken to launch a first model in hx is significantly shorter, with Antares releasing their first model in just 32 days. Both platforms benefit from consulting partnerships: Optalitix with PwC, hx with Deloitte and EY. Request reference customers for realistic timeline expectations specific to your environment.

How hx connects underwriting decisions to portfolio outcomes

hx's architecture creates a closed loop between pricing models, underwriting execution, and portfolio performance. Submissions flow through AI-powered ingestion directly into the underwriting environment. Actuaries build and refine models in native Python with full access to the data science ecosystem. Every pricing and underwriting decision is captured automatically, creating the dataset that drives portfolio intelligence and model improvement.

Carriers using hx can identify which pricing factors actually predict loss outcomes, test rate changes across the portfolio before deployment, and continuously refine models based on real underwriting results rather than assumptions.

See how hyperexponential's underwriting decision platform moves beyond Excel constraints for commercial insurance.

Frequently asked questions

Can Optalitix and hx work together?

Technically possible but rarely practical. Both platforms address pricing model deployment, creating redundancy rather than complementary capabilities. Carriers typically choose one approach based on whether Excel preservation or Python transformation better fits their strategic objectives.

Does Optalitix eliminate Excel's limitations?

Optalitix optimizes Excel performance and adds governance, but Excel's structural constraints remain. The 1,048,576 row limit, VBA processing limitations, and formula complexity that make multi-million-row portfolio analysis difficult cannot be solved through cloud hosting alone.

How long does Python upskilling take for actuarial teams?

hx provides actuarial-specific libraries, pre-built components, and AI assistance that reduce the Python learning curve. hx provides a range of training courses and certifications allowing most actuaries with analytical backgrounds to build complex production models within weeks. Underwriters and other users interact through pre-built interfaces without requiring Python knowledge.

Which platform has stronger independent validation?

Celent independently profiles hx as a modern pricing solution with strong actuarial modeling capabilities. Optalitix demonstrates market credibility through Lloyd's catastrophe portal adoption (81 syndicates) and PwC partnership, though independent analyst coverage is limited.

What determines which platform provides better ROI?

The answer depends on your primary constraint. If Excel governance and workflow efficiency drive your business case, Optalitix's faster implementation may deliver quicker returns. If pricing sophistication, portfolio analytics, and model deployment speed drive combined ratio improvement, hx's deeper capabilities justify longer initial implementation.

Can existing Excel models be partially migrated to hx?

hx includes spreadsheet upload tools that can import Excel data and logic as a starting point, though full capabilities require rebuilding in Python. Carriers often run parallel environments during transition, validating Python model outputs against existing Excel models before full cutover.

How do the platforms handle catastrophe model integration?

Excel's row limits create challenges for catastrophe modeling, which often involves millions of event records. Optalitix's cloud hosting improves processing speed but cannot address row constraints. hx's Python architecture handles large catastrophe model outputs without segmentation, enabling direct integration with tools like RMS and AIR.