Conversion-Led UX & Wireframes
Wireframes for home, collection, product, cart and checkout drawn from your own session recordings, site-search logs and support tickets. Not a template library.
Custom Shopify storefronts for Lombardy brands whose product is configurable, whose buyers are half Italian and half everywhere else, and whose accountant has opinions about the checkout.
Delivered remotely for brands across Milan and Italy.
The hard part of a Milan build is almost never the homepage. It is the product. A Brianza sofa comes in nine frames, forty fabrics and three depths; a Como scarf exists in a colourway that only ran for one season; a leather bag can be personalised with initials and ordered in a width the site has never had to express. Most Italian stores solve this by putting a PDF price list behind a contact form, which turns a buying decision into an email thread and hands the order back to whoever answers fastest.
The second problem is that one store is being asked to serve two completely different buyers. An Italian customer in Milan wants an Italian interface, a delivery promise measured in days, and the payment methods they already use. A German or French buyer wants a price in their own market that is not a currency conversion accident, duties made obvious before the cart, and copy that was written rather than machine-translated. We build both on one catalogue, at theme level, so navigation, filters, size guidance, cart and transactional email switch together instead of a widget translating the product title and leaving everything else in Italian.
Then there is the paperwork nobody puts in a design brief. An Italian order can need codice fiscale, partita IVA, and an SDI recipient code or PEC address, and a default theme collects none of it. Capturing those fields cleanly — only when they apply, only for the buyers who need them, without turning checkout into a tax form for a private customer buying a candle — is a build decision. Retrofitting it means emailing customers for data you should have asked for once.
Milan's year has a spike in it that most agency timelines ignore. Salone del Mobile at Rho Fiera turns April into the single biggest order-taking window for anything to do with interiors, and the Fuorisalone spills the same attention across Tortona, Brera and Isola for a week. Fashion labels get the same effect twice, in February and September. That has two consequences for a build. First, the storefront has to be live and stable well before the fair, not launched into it, because the week you get the most qualified traffic of the year is the worst possible week to be debugging a new theme. Second, the store has to have somewhere to put that traffic: a press and press-kit path, a showroom or appointment request that is not a generic contact form, and collection pages for the pieces you are actually showing. We scope Milan builds backwards from the fair date and cut over in the quiet stretch — usually late autumn or the first half of the summer, never August, when half your suppliers are closed anyway.
The same standard of work we run for every client — applied to a Milan brand’s realities.
Full service detailWireframes for home, collection, product, cart and checkout drawn from your own session recordings, site-search logs and support tickets. Not a template library.
A bespoke theme in clean, commented Liquid with modular sections your team can rearrange themselves. Zero dependency on page-builder apps.
Collection architecture, filtering, badging and cross-sell rules mapped to how your catalogue actually sells. Bestsellers surface; dead stock stops eating grid space.
Image pipeline, third-party script audit and app cleanup enforced against a hard budget: LCP under 2.5s on 4G mobile, CLS under 0.1, INP under 200ms.
Products, variants, metafields, collection copy and redirects loaded and QA'd in a dev store before cutover. You review a real store, not a Figma file.
Loom walkthroughs, a written theme guide and 30 days of post-launch fixes included. Your team owns the store from day one.
We do not work off a rate card. Every Milan engagement starts with a fixed statement of work — named deliverables, named dates, one number — written after we have looked at your store, not before. If a smaller first step would serve you better, we will say so.
Get this scopedTwo weeks inside your analytics, heatmaps, site search and support inbox. We leave with a ranked list of what is currently costing you revenue.
Sitemap, template inventory and grey-box wireframes for every page type. Signed off before a single pixel gets designed.
Figma component library, type scale and every awkward state: empty cart, sold out, pre-order, bundle, back-in-stock, subscription upsell.
Liquid development in a dev store, tested on real devices and against your live app stack. Accessibility checked to WCAG 2.1 AA.
Redirect map, tracking validation, DNS cutover on a low-traffic window. Then 30 days of monitoring against the pre-launch baseline.
Anonymised under NDA. Figures pulled from the client’s own analytics.
~$6M/yr DTC, 900+ SKUs across size and colour variants, US · Shopify Plus
Returns ran at 31% and refund cost consumed the entire paid media margin. One size chart image served 40 different fits, and 62% of add-to-carts started on a collection page that never showed variant availability. The named constraint: no new product photography budget, so every fix had to come out of the existing asset library and the review corpus.
~$11M/yr, 2,300 SKUs, configurable upholstery, US · Shopify Plus + Hydrogen storefront (Oxygen)
Fabric, leg and size options turned 2,300 SKUs into more than 40,000 variant permutations, and the Liquid theme rendered a configurable PDP in 6.9 seconds on mobile. Collection filtering ran client-side, so 40% of shoppers left before the first product painted. The named constraint: the ERP stayed. It was the single source of truth for stock and lead times and was not up for replacement.
“Full rebuild in 11 weeks, launched two days before Black Friday, which was an aggressive ask and probably a stupid one on my part. They pushed back hard on three homepage ideas I was attached to and were right about all three. AOV went from $58 to $79, mostly off the bundle builder they put on the product page.”
Thirty minutes with the strategist who would actually run your account. We screen-share your store, read your data live, and tell you the three highest-value things we can see from the outside.
Prefer to write it out? [email protected] gets a real reply the same business day, Mon-Fri, 9am-6pm MT.