Skip to main content
Meytal Dahan
Back to insights

Digitizing a Factory One Configurator at a Time

ZammitFoundersFrom MVP to Full VersionManufacturing / 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 ask me how you take something as messy as a custom manufacturing business and turn it into self-serve software without boiling the ocean. With Zammit, the honest answer is: you don't ship all forty configurators at once. You prove the model first. The premise was bold — let engineers, architects, contractors and retail professionals order complex made-to-order laser-cut products with no sales intermediary. That's a big claim to validate. So the work staggered naturally from a defensible core toward the full catalog of roughly forty configurators across ten categories, plus the e-commerce flows around them: quote, account, OTP, checkout, tracking. The flagship Retail Shelving Planner was where the full-version ambition became real — a spatial configurator usable without CAD. Two things kept the expansion honest. First, the DriveWorks engine's constraints forced discipline; you can't promise a configuration the factory can't fabricate. Second, I visited the factory, because an MVP built on a fantasy of how things are made collapses at full scale. The lesson for founders: let real manufacturing rules, not your roadmap optimism, decide what 'full version' is even allowed to mean.

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.