Insurance
Menora Insurance
A sample of selected flows across Menora's agent zone and customer-facing website - fees, sales, profile, login.
Type
B2B2C
Role
UX/UI Designer (via code-oasis)
Scope
- Agent zone UX
- B2C self-service flows
- Role-based views
- Form & filter design
Across multiple engagements as an outsource UX/UI designer for code-oasis, I shipped a wide range of work for Menora Insurance - far more than fits on one case study, so this entry is a sample. The flows below sit on two different sides of the product: the agent zone (an internal-facing portal with deep, role-based functionality) and the B2C website (consumer-facing self-service). What ties them together is the constraint Menora's products operate under - many fields, many roles, many conditional rules - and an audience that needs the interface to disappear into clarity.
01 · Section
Agent Fee
Inside Menora's agent zone, this flow lets agents see their fees - but the depth is in the filtering. The data behind agent fees is structurally complex: many variation axes, many product lines, many ways an agent might want to slice the same numbers. The design problem was reducing that complexity surface without hiding the power. Filters had to be discoverable, multiple view modes had to coexist, and the entire flow had to stay navigable both for an agent who knows exactly which slice they want and for one still figuring it out.
02 · Section
Profile Setting
On Menora's B2C website, profile settings is where a customer manages everything about themselves the insurer needs to know: contact details, address, family information, payment methods, and a handful of less-touched but high-importance fields underneath. The challenge wasn't any single form - it was the breadth. Insurance asks for a lot, and a customer who just wanted to update an address shouldn't feel like they've opened a tax return. The flow groups sections so that updating one thing doesn't surface ten other things you weren't planning to deal with.
03 · Section
Sales System
The sales system lives in the agent zone, but it's not just for agents. The same surface serves five different roles - agent, marketing, district manager, team lead, underwriter - each looking at the same underlying sales data through their own lens. Designing for five role-based views inside one product is a small architecture problem disguised as a layout problem. Each role needs its relevant data surfaced first, with the rest available but not noisy. The visual chrome stays consistent across roles so the system reads as one product, while the content adapts to who's logged in.
Testimonial
Working with Meytal was one of those rare collaborations where everything simply clicks - strategic thinking, high-level visual execution, smooth communication, and endless patience. She has a gift for taking complex ideas and turning them into clear, precise, user-focused experiences, while maintaining sharp attention to detail throughout the process. Beyond her impressive design skills, she's a joy to work with.