The challenge
What needed to be easier.
Customers needed to understand very different insurance products, compare plans, and buy with confidence without losing their place as they moved between categories.
Our contribution
This case describes our earlier contribution to EasyInsurance. The company now has its own in-house engineering team; its current website and features have continued to evolve.
We built marketplace experiences and integrations connecting multi-line insurance discovery, plan comparison, purchase pathways and claims-assistance journeys. Our contribution brought customer-facing flows and insurer-dependent steps into a consistent product.
The connected workflow
- Customers explore health, travel, auto or life insurance through one marketplace.
- Product-specific questions and comparison journeys help them evaluate available plans.
- Integrations and digital purchase pathways connect the customer’s selection with the next insurer-dependent step.
- Claims-assistance journeys provide a route to help after purchase.
What the delivered workflow enables
Customers can move from exploring different insurance categories to comparison, purchase and claims assistance in a consistent marketplace experience.
Engineering considerations
Different insurance categories ask different questions and expose different plan details. A consistent interface still needs room for those differences. Comparison content, purchase states and support handoffs should be reviewed with the business owners responsible for the underlying products.
A relationship beyond the first project
The relationship continued into additional projects for the founder, who also recommended our work personally. This is Rubix’s account of the working relationship, rather than a verbatim client quotation. The founder’s name remains private.
Public product references
- Visit EasyInsurance ↗
The live client website, now maintained by its in-house team.
- EFU Life’s EasyInsurance integration announcement ↗
Public context for the marketplace’s insurer integrations. This announcement does not independently attribute the integration implementation to Rubix.
