Where AI Belongs in a Field-Heavy Product

Every founder I talk to wants an AI story. After working across Menora's flows, my honest view is that the most valuable place for AI in a product like this isn't a chatbot bolted onto the homepage — it's in taming complexity the user shouldn't have to carry. Think about the agent zone: many fields, many roles, many conditional rules. The cognitive load isn't in finding information, it's in knowing which slice of a multi-axis space applies to the decision in front of you. That's precisely the kind of narrowing a well-scoped AI layer could assist — surfacing the relevant fields for a given role and context, suggesting the filter path, flagging a combination that doesn't add up. The strategic discipline is to keep AI inside the boundaries of the real domain rather than inventing capabilities the product was never meant to have. I'm wary of AI features that ask users to trust opaque output in a regulated, high-stakes setting like insurance. The strategy I'd advocate to founders: use AI to reduce the distance between a user and the right answer they could have reached themselves — and keep them able to verify it. Augment the expert; don't replace their judgment.
Related articles

About
Making complicated into easy for users.
Senior product designer with a decade of work across complex systems - financial risk platforms, legal operations, healthcare apps, manufacturing tooling and insurance portals. The common thread is depth: products where the data is rich, the users are expert, and the interface has to disappear into the work.