New York takes the order. Milan makes it.
Sasa Milano is a bespoke menswear house in New York City, where every garment is hand-made by tailors in Italy. The counter in Manhattan takes the order; the atelier in Italy quotes it, and — once approved — makes it. We built the order management systemthat runs that entire journey: an iPad app the sales assistant operates in front of the customer, with a built-in POS at one end and the Italian tailors at the other.
A bespoke process across an ocean.
Bespoke is a conversation, not a checkout. A customer in the New York store chooses cloth and cut; tailors an ocean away in Italy price the work, agree it, and make it by hand. Coordinating that across two countries — fabric codes, design choices, measurements, quotes, approvals, deposits, delivery dates — is a lot of moving parts, and most of it had lived in messages, spreadsheets and memory.
Worse, none of it was something the customer could see. The most exciting part of a bespoke purchase — watching your garment take shape as you choose — was happening on paper behind the counter. Sasa wanted that whole process to play out, beautifully, right in front of the client.
One flow, counter to atelier.
We mapped the whole lifecycle of an order and built it as a single, guided flow — so a sales assistant on the floor can carry a customer from first fabric to a locked shipping date without leaving the app.
- Order taken on iPadThe sales assistant builds the order on an iPad on the shop floor, with a built-in POS — and saves it.
- Shared with the tailorsThe moment it’s saved, the order is sent instantly to the customer’s preferred Italian tailors.
- Tailor reviews & quotesNotified of a new order, the tailor reviews the spec and responds with a quote.
- Admin reviews the quoteAn admin checks the quote and either approves it — or opens a chat to negotiate.
- Locked with a ship dateOnce agreed, the order is locked against a firm shipping date everyone can see.
- Customer confirmedThe customer receives an email with the full order details — what they chose, and when it lands.
A configurator the customer watches.
Because the system runs in front of the customer, look and feel weren’t a nicety — they were the product. We designed the order screen as an experience the client enjoys: as the assistant selects styles together with them, an on-screen garment updates live, so they see their choices take shape before anything is committed.
— collar · sleeves · cut · buttons · colour update as selected —
The best part of buying bespoke is watching it happen. We put that on the screen.
Italy, looped in instantly.
On the other side of the order is the atelier. The system keeps the tailors in step with the floor — no waiting on an email thread, no chasing a price — so a quote can come back while the customer is still a fresh memory.
One system, both ends of it.
The whole thing is one application — a customer-facing in-store experience and a tailor-facing workflow, sharing one record so nothing falls between them. We built it on Next.jsand NestJS with MongoDB, hosted across AWS andVercel — fast and calm under the counter, dependable across the Atlantic.
This was a build, not a campaign — so we won’t hang invented metrics on it. The win is plainer than a number: a fragmented, two-country process now runs as one system the customer can watch, and the tailors are part of the same conversation rather than the end of an email chain.
Design and engineering, together.
A system meant to perform in front of customers needs design and engineering working as one — an interface worth watching, on a backend that never makes anyone wait. That’s the same single-team approach behind every project we run.
How we’d do it for you.
One custom system, one team — experience design and engineering built together. Each piece is a service in its own right.
Got a process that should be a system? Let’s build it.
Tell us how your business actually runs today — the first reply comes from a partner, not a form.