Skip to main content
Meytal Dahan
Back to insights

A Studio With MarTech Projects: Why It Pays to Bring In an Analytics Dashboard Expert

A product design studio that wins a MarTech project for a SaaS company or a large enterprise quickly realizes this is a different world from marketing sites or consumer apps. Marketers are expert users who expect a high level of analytics and efficiency. Generic or clunky design gets rejected fast. My experience working on the MarTech system gives a studio a Plug & Play answer for complex analytics systems. I know the principles of designing successful dashboards, the unique needs of marketers, and the professional requirements of working with marketing and sales teams. Another advantage is the ability to present my expertise as part of the pitch to the client. A studio that offers a MarTech project to a marketing-driven client — and presents my experience as part of the team — gains a significant competitive edge in the tender. Studio leaders weighing whether to enter the MarTech market: don't pass it up. It pays well, it offers complex and interesting projects, and it builds a professional reputation in the SaaS sector.

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.