Skip to main content
Meytal Dahan
Back to insights

The Honest AI Question for a Made-to-Order Platform

ZammitFoundersAI Strategy in the ProductManufacturing / B2B Procurement
Zammit — Designed the Retail Shelving Planning System - the platform's most demanding configurator, where every dimension, shelf, edge profile, and placement rule is defined - into a spatial design tool retail professionals could use without CAD knowledge.
Founders almost always want to talk about where AI goes in the product. With Zammit, the most useful thing I can offer is a disciplined answer rather than a hopeful one. This was a platform built on the DriveWorks configurator engine, where the value came from deterministic, rule-bound configuration: a contractor or retail professional sets dimensions, shelf count, edge profiles and placement, and the output has to be fabricable on a laser-cut line every single time. In a domain like that, the bar for any AI is whether it respects those manufacturing constraints. The honest place to look isn't replacing the configurator — it's reducing the cognitive load of self-serve. The real friction we designed against was non-experts configuring complex made-to-order products without CAD knowledge and without a sales intermediary. That's exactly the kind of guidance, interpretation and 'did you mean this configuration' assistance an AI strategy should be aimed at — never at generating specs the factory can't cut. The founder takeaway: anchor AI ambition to the actual job the product removed a human from doing, and let the engine's hard constraints, not the hype cycle, set the boundary.

Get in touch

Have a project in mind?

Drop a line. Meytalyav@gmail.com

Related articles

Zammit
Project ManagersUsability Testing

Testing a Spatial Configurator Without CAD

On Zammit's shelving configurator, we asked people to lay out custom shelving — dimensions, shelf count, depth, placement — with zero CAD knowledge. That is a usability risk you cannot hand-wave. So I ran testing as a recurring checkpoint tied to delivery milestones, not a one-off before launch. The payoff is for project managers as much as designers: testing turns a scary, vague risk ('can buyers do this without a salesperson?') into specific, scheduled, fixable issues. And inside an engine with real constraints, testing early tells you which problems are worth engineering time and which a better sequence solves for free. Predictability beats surprises.

Read
Zammit
Product ManagersMicro-interactions & Animation

Micro-interactions That Made an Engine's Rules Feel Like Feedback

Rule-heavy configurators feel like the system is fighting you — unless feedback shows why. On Zammit, micro-interactions turned the engine's logic into a conversation: a value recalculating, the summary shifting, an invalid option visibly settling out of reach instead of vanishing. PMs, the test for every animation: does it explain the system's behavior, or just decorate it? Only the former protects flow completion.

Read
Zammit
Project ManagersDelivery & Handoff to Development

Handing Off 40 Configurators Without Losing the Thread

Handing off ~40 configurators, 25 e-commerce flows, and 6 onepagers — solo, over ~2 years — taught me that handoff isn't an event, it's a rhythm. At that volume the real risk a project manager loses sleep over is drift: checkout behaving one way here, another way there. My defense was deliberate pattern reuse and handing off the decision logic, not just visuals — especially for configurators bound to the DriveWorks engine's rules. Shared patterns are schedule insurance: estimates hold, review cycles shrink, and developers implement without guessing. Clear intent plus clear constraints beats a backlog of clarifying questions every time.

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.