Skip to main content
Meytal Dahan
Back to products

Manufacturing

Zammit

A B2B platform that digitizes custom laser-cut manufacturing - letting engineers, architects, and retail professionals configure and order without going through sales.

Type

B2B

Role

Lead Product Designer

Scope

  • End-to-End Product Design
  • 40 Product Configurators
  • 25 E-commerce Flows
  • 6 Segment Onepagers
  • Web + Mobile

Zammit transforms a traditional custom laser-cut manufacturing business into a digital procurement platform - where engineers, architects, contractors, and retail professionals can configure complex made-to-order products and place orders without going through a sales intermediary. The most demanding design challenge of the engagement was the retail shelving planning system - a configurator that lets users design intricate shelving systems for commercial spaces, defining everything from overall dimensions and shelf count to edge profiles, individual shelf depth, and placement logic. That single configurator distilled what the entire platform was trying to be: deep parametric control made operable by a human, not an engineer with CAD software.

01 · Section

The challenge

Custom laser-cut manufacturing carries some of the most technically dense decision-making in B2B commerce. Each product type has its own dimensional constraints, material rules, fabrication tolerances, and pricing logic. Traditionally, this conversation happens between a buyer and a sales engineer, over email, with quotes assembled by hand. The brief was to digitize that entire interaction - across approximately ten product categories spanning structural systems, retail fixtures, architectural elements, industrial components, and logistics solutions - and serve six distinct professional audiences, each arriving with different needs: engineers sourcing structural components, mid-sized factories procuring industrial parts, maintenance personnel and contractors ordering replacements and custom fits, architects specifying bespoke elements, retail professionals designing in-store displays and fixtures, and logistics professionals procuring infrastructure. The challenge was simplifying product configuration and adaptation processes deeply enough that any of these audiences could navigate them seamlessly, without prior learning - while preserving the technical precision their work demands.

02 · Section

Approach & collaboration

The project ran solo on design across approximately two years, in tight collaboration with the Zammit team. The technical foundation was DriveWorks - a manufacturing configurator engine with its own rules and constraints for how parametric logic can be exposed in a UI. Every flow had to be designed not only for user clarity but for compatibility with the system's underlying configuration architecture. To design the configurator flows credibly, I spent significant time learning the manufacturing domain itself - meeting with the engineering team, studying fabrication logic, and visiting a factory to understand the products from the floor, not just from spec sheets. The visit changed how I thought about several flows: when you've watched a sheet of metal become a finished part, you design the configurator that orders it differently.

03 · Section

The Retail Shelving Planning System

The shelving planning system is a configurator for designing complete in-store shelving installations - not a single product, but an entire fixture system inside a commercial space. Users define a wide range of parameters: overall system width, number of shelves, where each shelf sits in the system, shelf edge types, the depth and size of each individual shelf, and how the whole composition fits inside the store's footprint. The complexity was layered: every parameter affected the geometry of the others, every change had cascading effects on cost and feasibility, and the entire interaction had to remain comprehensible to a retail professional thinking about their store - not an engineer thinking about CAD constraints. The design solution surfaces parameters progressively, lets users see the system updating as they configure, and keeps the underlying manufacturing rules invisible until they actually matter. Configuration becomes a spatial design exercise, not a technical specification task.

04 · Section

Forty configurators, one system

Designing forty product configurators across ten categories without fragmenting the experience required treating the configurator itself as a system. Shared interaction patterns, consistent parameter controls, a unified preview model, and predictable flow steps run across all forty flows - so that learning one configurator effectively teaches you all of them. Variation lives only where the product genuinely demands it.

05 · Section

Segmented entry - six onepagers

Engineers and architects don't arrive at a manufacturing site with the same questions. Six dedicated onepagers - one per professional segment - translate Zammit's offering into the language each audience already speaks. The onepagers route users into the configurators most relevant to their work, with framing, vocabulary, and visual hierarchy adjusted to the segment's mindset. The same products, surfaced through six different doors.

06 · Section

The full purchasing workflow

Beyond the configurators themselves, the platform needed a complete e-commerce backbone - twenty-five flows covering quote generation, account management, OTP verification, checkout, and order tracking. The transition from 'configuring a custom part' to 'completing a transactional purchase' had to feel like one continuous experience, despite combining two very different interaction models.

07 · Section

Deliverables

End-to-end design of the Zammit platform across web and mobile: forty configurator flows across approximately ten product categories; twenty-five e-commerce flows covering the full purchasing lifecycle - quote, account, OTP verification, checkout, and success states; six segment-specific onepagers for the platform's professional audiences; and mobile variants for every surface. The work was grounded in a factory-floor visit and designed inside the architectural constraints of the DriveWorks configurator engine.

Next product

Shibolet & Co.

Designed the firm's internal community hub - balancing the gravitas of a top legal practice with a social tone inviting enough that employees would actually use it - into a space precise enough to belong inside the firm and warm enough to feel lived-in.

Insights

More on Zammit.

View all insights
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
Zammit
Product Managers

Designing Planning Systems for the Factory Floor: How Do You Translate Industrial Logic Into an Interface Operators Actually Love?

Product managers in industrial domains, don't impose a consumer-product UX paradigm on production operators. They're professionals with years of experience who work in shifts. In the manufacturing platform project we designed a system with aggressive shortcuts and a screen flow tailored to repetitive actions. Respect for professionalism = fast adoption.

Read
Zammit
Product ManagersFirst-Run Onboarding

First-Run Onboarding for People Who'd Never Configured Without a Rep

Every Zammit user's first run shared one fear: they'd always bought custom products through a salesperson, now they're alone with a configurator. So onboarding wasn't a feature tour — it started them from sensible defaults on a valid product they could react to, not a blank canvas. Editing something concrete beats building from nothing. PMs: first-run success isn't 'saw the tooltips.' It's 'reached a configuration they trusted enough to request a quote.'

Read
Zammit
Engineering LeadersDesign Systems

One Design System Across 40 Configurators and a Rigid Engine

Solo designer, ~40 configurators, one rigid configurator engine underneath. The only thing that made that survivable was a Design System built around the engine's constraints — not against them. Standard inputs, validation, quote and checkout components meant engineering stopped re-deciding the same interaction forty times. A Design System isn't visual polish for CTOs. It's a smaller surface area to build and test.

Read
Zammit
Engineering LeadersR&D Collaboration

Designing Inside the DriveWorks Engine, With R&D

Every Zammit screen lived inside the DriveWorks configurator engine. That meant I could not design in a vacuum and hand it to R&D — the engine's rule model decided what was cheap, costly, or impossible. So I learned its grammar and designed in conversation with the people maintaining the configurations. A per-shelf depth control isn't a visual question; it's 'can the rule tree express this without becoming unmaintainable?' For engineering leaders, that's the collaboration that saves you: a designer fluent in the constraint stops shipping requests that quietly explode complexity. The best design inside a constrained engine makes the buildable product easy — and the unbuildable one obviously not worth chasing.

Read
Zammit
Founders

Industry 4.0 Startups: How Do You Crack the Reluctance of Manufacturing Plants to Adopt New Technology?

Founders in Industry 4.0, manufacturing plants are a conservative market that rejects new technologies. In the manufacturing platform project we proved that the secret is to design an experience that feels 'familiar' to the veteran operator — while being revolutionary beneath the surface. Rollout design = 50% of your startup's success.

Read
Zammit
Engineering LeadersProject-Specific Data Visualization

Visualizing a Shelving Configuration Without Requiring CAD

Zammit's flagship: a spatial shelving configurator for people with zero CAD knowledge. The visualization had to faithfully represent a manufacturable object while hiding everything CAD-scary. The engineering-interesting part: the picture is bound to the same constrained model the engine enforces, so what the user sees can never drift from what the factory can build. Configurator data viz isn't a chart on top — it's a real-time projection of the product model.

Read
Zammit
FoundersAI Strategy in the Product

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

Founders always ask where AI goes in the product. The disciplined answer beats the hopeful one. Zammit ran on a configurator engine where value came from deterministic, fabricable output — a contractor sets dimensions and edge profiles, and a laser cutter has to make it, every time. So the bar for any AI is simple: does it respect the manufacturing constraints? The opening isn't replacing the configurator. It's reducing the cognitive load of letting non-experts configure complex made-to-order products without CAD and without a salesperson. Anchor AI to the human job you removed — and let the engine's hard constraints, not the hype, set the boundary.

Read
Zammit
Project Managers

Digitizing Production Processes: How Do You Manage a Project That Changes Decades-Old Habits?

Project managers in industrial digitization, the hard challenge isn't technical — it's cultural. In the manufacturing platform project we brought veteran operators onto the design team as true partners, and built a phased rollout with overlap. An excellent system that no one uses = total failure.

Read
Zammit
CEOs

Industrial Digitization as a Competitive Lever: The ROI of Modern Planning Systems in Manufacturing Plants

CEOs of industrial companies, digitization isn't an 'upgrade' — it's an existential requirement for competing with international plants. In the manufacturing platform project we proved that cutting a production order from 30 minutes to 5 minutes = hundreds of thousands of shekels a year. The difference between an investment that pays off and one that sits on the shelf = a design operators love.

Read
Zammit
FoundersFrom MVP to Full Version

Digitizing a Factory One Configurator at a Time

Founders ask how you digitize a custom manufacturing business without boiling the ocean. With Zammit you don't ship 40 configurators at once. You prove one model — engineers, architects and contractors ordering complex made-to-order parts with no salesperson — then expand across categories toward the full catalog and the flows around it: quote, account, OTP, checkout, tracking. Two things kept the path from MVP to full version honest: the DriveWorks engine's constraints, and the fact that I visited the factory. You can't promise a configuration the shop floor can't make. Let the real manufacturing rules define 'full version' — not your roadmap optimism.

Read
Zammit
Product ManagersTypography & Visual Hierarchy

Typography Was How We Made Complex Configuration Readable

Self-serve B2B configuration lives or dies on what the user looks at first. On Zammit, a shelving configurator asks for dimensions, shelf count, edge profiles, per-shelf depth, placement. Flat, that's an abandoned form. Sequenced with type scale, weight, and hierarchy, it's a guided decision. For PMs: visual hierarchy is conversion and support deflection wearing a typography costume.

Read
Zammit
CEOsSpecific Feature ROI

Where the Configurator Pays Back: ROI in the Retail Shelving Planner

The ROI question I'd ask any designer about a flagship feature isn't 'is it polished?' It's 'which manual step did you delete?' On Zammit's Retail Shelving Planner, the answer was concrete: custom laser-cut orders used to need a salesperson translating intent into a fabrication spec. The spatial configurator let retail pros set dimensions, shelf count, edge profiles and placement themselves — and the order reached the factory already valid. A configurator earns its budget when it removes a human bottleneck and produces output the shop floor can trust. Beauty is table stakes. Eliminated steps are the return.

Read
Zammit
Engineering LeadersIndustry-Specific Accessibility

Accessibility for a Spatial Configurator That Isn't a Shop-Floor Tool

Accessibility in manufacturing software usually conjures gloves and ruggedized touchscreens. Zammit wasn't a shop-floor tool. Its users were engineers, architects, contractors and retail pros doing procurement on web and mobile. So the accessibility challenge was cognitive and spatial, not environmental. The flagship shelving planner asked people to configure dimensions, shelf count, edge profiles and per-shelf placement — explicitly without CAD knowledge. That means the spatial model has to be legible to someone who's never read a technical drawing, while still respecting WCAG fundamentals: contrast, focus order, input alternatives for a visual UI. Real accessibility here is refusing to gatekeep a complex purchase behind expertise the user never needed.

Read
Zammit
CEOsPersonalization & Tailored Models

One Platform, Many Buyers: Personalization Without Fragmentation

Personalization sounds expensive — until you see it's how one platform serves very different buyers without building several. Zammit sold custom laser-cut products to engineers, architects, contractors and retail pros — different vocabularies, different priorities, one self-serve system. We didn't build four products. We tailored the edges: six segment onepagers meeting each buyer in their own language, feeding the same configurators and checkout underneath. That's the trade-off CEOs should watch. Over-personalize and your build fragments. Under-personalize and the architect bounces because it reads like it was written for someone else. Personalize the framing generously. Keep the engine singular.

Read
Zammit
FoundersColor & Psychology

Color as a Trust Signal When You Remove the Salesperson

When you remove the salesperson, the interface has to carry the trust. On Zammit, buyers configure and order custom laser-cut products with no human in the loop — so color did real work: a serious, restrained palette to feel like a manufacturing partner, and functional color to guide decisions and confirm valid choices through quote and checkout. Color isn't decoration in self-serve procurement. It's the reassurance your missing salesperson used to give.

Read
Zammit
Project ManagersDocumentation & Organizational Handoff

Documenting So the System Outlives the Solo Designer

For about two years I was Zammit's only product designer — which made me a single point of failure for 40 configurators, 25 flows, and 6 onepagers. Documentation was how I refused to stay one. Screenshots survive on their own; the reasoning behind a flow evaporates. So I documented the fragile stuff: why each configurator option exists, how it maps to a real fabrication choice, where the DriveWorks engine forced a decision. For a project manager, that's the difference between a true organizational handoff and just transferring files. The best thing I left behind wasn't the configurators — it was someone else's ability to confidently grow them.

Read
Zammit
Product ManagersUser Research

Researching Buyers Who Used to Just Call Sales

When you digitize a B2B sales process, you are not just replacing a form — you are replacing a person. On Zammit, custom laser-cut orders used to flow through a salesperson who quietly translated vague intent into a real spec. My research job was to find everything that human did invisibly. Engineers think in tolerances. Retail buyers think in finished shelving. Same product, different mental models. Build for one and you lose the other. The lesson for PMs: research doesn't just validate scope — it defines it. We knew which of ~40 configurators to build because users told us which decisions they could own alone, and which still needed a guiding hand.

Read
Zammit
Engineering LeadersInternationalization (i18n)

i18n Inside a Configurator Engine's Constraints

i18n in a configurator platform isn't a translation problem. It's an architecture problem. On Zammit, much of the user-facing language and option logic lived inside the DriveWorks configurator engine — not a tidy front-end string table. That changes everything: option labels, units, edge-profile terminology, manufacturing validation messages, and the checkout/OTP/tracking flows all cross that boundary. For CTOs: decide early what is localizable vs engine-bound. Retrofitting that split is brutal. Plan for string expansion reflow on mobile. And keep domain terms consistent across the configurator and the commerce surface. Localization fails quietly when one product ends up speaking two languages.

Read
Zammit
Engineering Leaders

Industrial Planning Systems: How Do You Design a UI That Works With Complex Hardware and Harsh Spatial Constraints?

Engineering leaders of industrial systems, ruggedized touchscreens, work gloves, direct sunlight — these aren't 'edge cases' to consider. They're the environmental conditions. In the manufacturing platform project we designed with large UI components, high contrast, and an Offline Mode for network loss. Hardware + environment = part of the design, not an 'add-on.'

Read
Zammit
Studio & Agency

Industrial and Industry 4.0 Projects: Why Your Studio Needs a Product Designer Who Has Worked on the Production Floor

Studio leaders, an industrial project is an opportunity for large budgets and long-term projects. But it demands expertise in the production-floor world. My experience on the manufacturing platform lets me come in Plug & Play — talk with manufacturing engineers, understand industrial processes, and design solutions that work in reality.

Read