Meytal Dahan
Partners
Back to products

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.

See it live

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.

Moran Feldman

Product: Menora Insurance

Next product

Ichilov Hospital's Movement

Patient-facing app for corporate health checkups — the entire arc in one calm, consumer-grade interface

Insights

More on Menora Insurance.

View all insights
Menora Insurance
Engineering LeadersIndustry-Specific Accessibility

Accessibility in Field-Dense Insurance Flows

Most accessibility talk stops at contrast on landing pages. In insurance, the hard surface is the field-dense internal tool. On Menora's agent zone — many fields, conditional rules, five role lenses — WCAG means keyboard order through multi-axis filters, screen-reader announcements as conditional fields appear, focus that survives constant state changes. That's architecture, not a finishing pass. The deepest a11y debt hides in the internal tools everyone assumes are 'just for power users.'

Read
Menora Insurance
Project ManagersDocumentation & Organizational Handoff

Documentation That Outlives the Engagement

As an outsource designer on Menora, I knew I'd eventually leave. So I documented for the people who'd stay. Not pretty specs — the reasoning. Why a field appears for an underwriter but not a team lead. Why the fee flow's rules are shaped the way they are. For a PMO: with outside contributors, documentation isn't admin. It's how the work becomes something the organization actually owns.

Read
Menora Insurance
Project Managers

Managing UX in Enterprise Giants: Owning Milestones and Integrating Multi-Stakeholder Requirements

Project managers (PMOs), how many times has your enterprise project stalled because legal or marketing suddenly remembered to weigh in at the 90th minute? The work with Menora Insurance demanded a structured approval method. You lock down a smooth architecture in Figma, get sign-off from every department, and only then run forward. That's how you protect the Gantt.

Read
Menora Insurance
FoundersAI Strategy in the Product

Where AI Belongs in a Field-Heavy Product

Founders keep asking for an AI story. In a field-heavy product like Menora's agent zone — many fields, many roles, many conditional rules — the real opportunity isn't a homepage chatbot. It's using AI to narrow a complex space: surface the right fields for this role and context, suggest the filter path, flag a combination that doesn't add up. In regulated, high-stakes domains, augment the expert and keep them able to verify. Don't replace judgment with opaque output.

Read
Menora Insurance
Engineering LeadersInternationalization (i18n)

i18n Starts in the Layout, Not the String Table

i18n is not a string table. Designing Hebrew-first, RTL interfaces for Menora taught me the expensive part is structural — label placement, filter alignment, data tables, which way affordances point. None of that is fixed by a translation layer. To CTOs: bake direction-neutrality into your components, not into late patches. The teams that internationalize cheaply designed the skeleton to flex from day one.

Read
Menora Insurance
Product ManagersMicro-interactions & Animation

The Quiet Feedback Loop: Micro-interactions in High-Stakes Forms

Micro-interactions get sold to PMs as delight. I'd reframe them as feedback. In Menora's agent-fee flow — depth driven by multi-axis filtering — every adjustment has to be acknowledged: state changed, results updating, here's what's in scope now. Without that, users click twice because nothing confirmed the first click. My test for any animation: does it answer a question the user is silently asking? "Did that work? What changed? Where am I?" If yes, it earns its place. If it's there to look modern, it's just friction in a nice coat.

Read
Menora Insurance
CEOs

Digital Transformation in the Enterprise: ROI Through User Experience

CEOs, outdated legacy systems are the 'black hole' of your budget. The digital transformation we carried out at Menora Insurance shows that redesigning core interfaces means one thing: enormous savings in support costs and a full migration of customers to self-service. UX is your engine of operational efficiency.

Read
Menora Insurance
Engineering LeadersR&D Collaboration

Designing Around Conditional Logic, With R&D in the Room

On Menora's insurance platform, the UI is the tip of a huge rules engine — many roles, many conditional states. So I designed with R&D in the room, not for them after the fact. For engineering leaders: the win is fewer surprises. "That state can't happen" is a cheap sentence early — and an expensive bug late. Share the model, not just the mockups.

Read
Menora Insurance
FoundersFrom MVP to Full Version

Earning the Right to Add Complexity

MVP to full version isn't 'add more features.' On Menora's multi-role sales system, the durable approach was proving one data model served one role first — then layering agent, district manager, underwriter, each with its own rules, onto that proven spine. Complexity should be earned, not front-loaded. Ship the spine, let real users lean on it, then grow along the axes that matter. Front-loaded complexity calcifies; earned complexity scales.

Read
Menora Insurance
CEOsPersonalization & Tailored Models

One Dataset, Five Tailored Lenses

Personalization in enterprise isn't a recommendation engine. At Menora, five roles — agent, marketing, district manager, team lead, underwriter — consumed one dataset, each needing its own lens. The move wasn't building five products. It was modeling the data once and tailoring presentation, defaults, and emphasis per role. One spine, many lenses, no duplicated truth. The most valuable personalization is often disciplined role-awareness over a single source of truth.

Read
Menora Insurance
Engineering LeadersProject-Specific Data Visualization

Same Data, Five Lenses: Visualization Under Multi-Axis Filtering

The hardest data-viz problem on Menora wasn't a chart. It was the agent-fee flow, where complexity comes from multi-axis filtering across many fields and conditional rules. Visualizing that means making the query itself legible: which axes are active, how they combine, what the result set actually represents. Then add five roles — agent, marketing, district manager, team lead, underwriter — each needing the same data through its own lens. For R&D: treat the view as a function of data + role + active filters, not a fixed layout. Faithful representation beats decoration every time.

Read
Menora Insurance
Engineering Leaders

Design Systems in the Enterprise: Saving 40% of Development Time

Engineering leaders, tired of every new screen in the project forcing you to write front-end code from scratch? At Menora Insurance we solved it with a comprehensive, rigorous Design System in Figma. When the designer speaks in fixed components, your developers save 40% of their time and focus on logic, not pixels.

Read
Menora Insurance
FoundersColor & Psychology

Color as Trust Infrastructure on a Big-Five Insurer's Site

Founders ask me about color expecting a branding chat. On a big-five insurer's site, color is trust infrastructure. On the customer-facing flows, color tells people what's safe to touch and what just went wrong. Errors, required actions, confirmed saves — each needs one unambiguous meaning, applied consistently. Overuse color and everything shouts. Reserve it, and a single accent does real work. Your palette is a budget, not a paint set. In insurance, the psychology that matters isn't excitement — it's reassurance.

Read
Menora Insurance
Project ManagersUsability Testing

Testing Complexity You Can't Simplify Away

On Menora's agent-fee flow, the complexity was real — multi-axis filtering, many fields, conditional rules. You can't simplify it away. So we tested it as checkpoints through delivery, not one gate at the end. For a PMO, usability testing isn't about a clean score. It's about retiring uncertainty on a schedule — so your dates survive contact with real users.

Read
Menora Insurance
Product ManagersTypography & Visual Hierarchy

When the Screen Has 40 Fields: Hierarchy as a Product Decision

Every PM eventually says it: "this screen has too many fields." On Menora's role-based flows, most of those fields were load-bearing. You couldn't cut your way to clarity. So the real question wasn't how to remove fields. It was how to rank them. Type scale, weight, spacing — hierarchy turns a dense screen from crowded into calm without deleting a single requirement your stakeholders fought for. Before you argue scope, invest in hierarchy. It's the cheapest way to make complexity feel simple.

Read
Menora Insurance
Engineering LeadersDesign Systems

One System, Five Roles: Designing for Reuse in Menora's Agent Zone

On Menora's Agent Zone, one sales system serves five roles — agent, marketing, district manager, team lead, underwriter — each seeing the same data through its own lens. The temptation is five tailored screens. The cost is five codebases your R&D team maintains forever. We built role-agnostic components and treated permissions and visible columns as configuration, not forks. The interface adapts; the components stay shared. A design system isn't a style guide. It's a promise that the same data, seen five ways, comes from one source of truth — and that your maintenance surface doesn't quietly multiply behind it.

Read
Menora Insurance
Product Managers

Form Engineering in Legacy Systems: How to Beat Abandonment Rates in Insurance

Product managers, are your forms long and exhausting for your users? In the work for Menora Insurance we proved that even heavy insurance systems can be turned into dynamic, smart, and lightweight forms. It all starts with a field architecture built on conditional logic that shows the user only what's relevant to them at that exact moment.

Read
Menora Insurance
Project ManagersDelivery & Handoff to Development

Handing Off Many Fields, Many Roles, Many Rules

Handing off a Menora screen meant handing off the states behind it — what an underwriter sees vs. a team lead, what each filter combination produces. The layout was the smaller half of the package. For a PMO: on conditional systems, handoff is a contract about behavior, not a picture. Spell out the rules and rework stops eating your schedule.

Read
Menora Insurance
Founders

Learning from the Giants: How to Design a B2B2C Product That Holds Up in the Institutional Market

Founders, trying to sell your startup to enterprise companies and can't understand why it's taking a year? Your product has to speak their architectural language. My experience inside systems like Menora Insurance lets me package your product so it fits the rigid enterprise requirements exactly.

Read
Menora Insurance
Product ManagersFirst-Run Onboarding

First Run in a Role-Based System: Onboarding Without a Tour

First-run onboarding usually means a coach-mark tour. In a role-based system like Menora's Agent Zone, that breaks immediately — an agent, a district manager, and an underwriter each have a different "first run." So onboarding became less about an overlay and more about the first screen being self-evident for whoever you are: good defaults, clear initial states, an obvious entry point. PM reframe: if you need a tour to explain a screen, the screen needs work — not the user. The best first run is the one nobody notices they had.

Read
Menora Insurance
Product ManagersUser Research

Researching Five Roles That Share One Screen

On Menora's sales system, the same data is read by five roles: agent, marketing, district manager, team lead, underwriter. The research question was never "what does the user want." It was "which user?" For a PM, that reframing is the whole roadmap. Research the lenses, not just the screens — and you'll know exactly where to standardize and where to specialize. One data model, five points of view. Prioritize accordingly.

Read
Menora Insurance
Studio & Agency

Reinforcing Your Team for Enterprise Projects: A Senior Designer as an Immediate Execution Arm

Studio leaders, closed a heavy enterprise client and your team can't get on top of the complexity? Instead of taking on juniors and babysitting them, bring a senior contractor onto the project. My experience with systems like Menora Insurance guarantees a smooth onboarding, independent work, and a delivery that protects your studio's reputation.

Read