Skip to main content
Meytal Dahan
Back to insights

A Grounded AI Strategy for Analytics Products

Every founder I talk to wants AI in their analytics product. The question I push back with is: AI to do what, exactly? Because in MarTech the easy win — a chatbot bolted onto a dashboard — usually solves a problem nobody had. The strategy I advocate uses the structure already in the product. The Insights-Before-Numbers pattern is, at its heart, a layer that interprets raw numbers into meaning. That's precisely where AI belongs: generating and prioritizing the interpreted insights, spotting the anomaly in a campaign worth surfacing, drafting the 'why' behind a shift. The raw numbers stay as the verifiable ground truth underneath. Critically, AI shouldn't end at narration. Each AI-generated insight carries the same action button as any other — so the model isn't just talking, it's routing the user to a decision. That keeps AI accountable: an insight that produces no action is one to question. For a founder, this is a defensible strategy because it's measurable and trustworthy. You're not promising magic; you're using AI to do the interpretation work at scale, with the numbers always one click away to check it. Augment the judgment, don't hide it.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Marketing & Campaign Analytics
Product ManagersUser Research

Researching the Marketer, Not Just the Metric

In analytics products, users don't want data. They want to know if it's working and what to do next. Every time I run discovery for a marketing dashboard, the same thing surfaces: people get raw numbers before meaning, so they burn energy interpreting instead of acting. That single insight reframes the roadmap, from "more charts" to "faster decisions." Research isn't a quote deck. It's the thing that tells your PM what NOT to build.

Read
Marketing & Campaign Analytics
Engineering Leaders

Data Visualization in MarTech: How Do You Design Charts That Don't Collapse Under Massive Data?

Engineering leaders on MarTech systems: dashboards with real-time visualizations are a performance nightmare. In our campaign management system project we built "Skeleton Loading" — every chart loads separately, a fast experience even under load. Every visualization passed through a "Performance Impact" filter. Design + performance = a system that works in production.

Read
Marketing & Campaign Analytics
Project ManagersDelivery & Handoff to Development

A Handoff the Team Can Actually Build From

A handoff isn't the moment you share a file. It's a quality gate. If I only hand over the happy path, the team builds the happy path, and every loading, empty, and error state becomes a clarification ticket mid-sprint. So I spec the states, the interactions, the shared-vs-specific components, all on existing Design System tokens. A good handoff makes delivery assembly, not archaeology.

Read
Meytal Dahan

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.