Skip to main content
Meytal Dahan
Back to insights

Color Earns Trust Before Your Feature Set Does

Founders selling into the enterprise often ask me to make a B2E app 'feel premium.' My honest answer: in field tooling, color's job isn't premium, it's trust and legibility. Your buyer is a procurement committee, but your actual user is a technician who has been handed yet another app they didn't ask for. Color is one of the first signals that tells them whether this tool respects their day. I use a restrained, functional palette where color carries meaning — status, success, warning, sync state — rather than decoration. That's also a reciprocity move: clear color-coded confirmation that 'your photo uploaded, your hours logged' tells the employee the app is doing something for them, not just extracting data. I never lean on color alone to convey state, because a meaningful share of users are colorblind and WCAG demands a redundant cue. And I design for the harsh case first: high-contrast palettes that hold up in direct sun and on cheap rugged-device screens. Get color right and the app feels credible in the first ten seconds — which, for a founder, is exactly the window where adoption is won or lost.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Enterprise Mobile
Engineering LeadersIndustry-Specific Accessibility

Accessibility in the Field Means Gloves, Glare, and One Free Hand

WCAG is the floor for frontline apps, not the ceiling. The real accessibility test is the field: gloves that defeat small tap targets, sunlight that erases low-contrast text, one free hand on a noisy loading dock. Situational and permanent disability collapse into the same requirements out there. Big targets, glare-proof contrast, camera/QR over forms, a single confirming tap. Bonus for R&D: fewer input errors at the source means cleaner data into payroll. Design for the glove and the glare — you'll clear WCAG along the way.

Read
Enterprise Mobile
CEOsSpecific Feature ROI

The ROI Hides in the Feature Nobody Mandated

CEOs often ask me to justify a B2E feature in isolation. Wrong frame. The mandated features get compliance, not adoption. The feature that gives the field worker something back — offline schedules, a camera report that kills minutes of typing, a payslip without a call to HR — is what makes them open the app at all. And once they open it, your mandated workflows finally get used. Don't price a feature by its own ROI. Price the adoption it unlocks across the whole product.

Read
Enterprise Mobile
Engineering Leaders

B2E Apps With Complex Integrations: How Do You Design Mobile-First So It Doesn't Break on Legacy Systems?

Engineering leaders on B2E apps: the challenge isn't the build – it's the integrations with legacy systems. In our enterprise mobile app project, we designed "Cached Display" for latency situations and full Offline Mode for field workers. Design + technical reality = an app that works in production.

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.