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.
Shopify storefronts for Zurich brands whose customers read in three languages and whose parcels cross a customs border on the way out.
Delivered remotely for brands across Zurich and Switzerland.
A Zurich merchant usually arrives with a better product than website. The company is profitable, family-held, forty years old in some cases, and the store was built once by an agency that treated it as a brochure with a cart attached. Nothing is broken. It simply never had to work hard, because the reputation and the wholesale channel carried the numbers. The moment direct sales matter, every soft spot shows at once: a product page that describes a movement or a cocoa origin in one paragraph, a size and fit story that stops at a PDF, a checkout that offers card only.
The build here is shaped by a small home market. Nine million people split across German, French and Italian commercial regions means the storefront has to serve several languages on one catalogue from day one, not as a phase two. We build it through Shopify Markets with translation held in the theme layer, so navigation, filters, metafield labels, cart copy and transactional email all switch together. A half-translated store reads as unfinished, and a Swiss buyer is unusually intolerant of unfinished.
Then the border. Every parcel leaving Switzerland for the EU is an export, so the product page and cart have to answer a question a domestic-only theme never asks: what will this actually cost me when it arrives. We design landed cost into the page rather than hiding it in a shipping FAQ, wire duties and import VAT into the checkout where DDP makes commercial sense, and make sure the commercial invoice and HS codes come out of the system rather than out of someone in Altstetten typing them into a courier portal.
Most Swiss stores we inherit have solved multi-language by duplicating themselves: a .ch site in German, a French site someone built later, and two inventories that stopped agreeing about eighteen months ago. Rebuilding that as one catalogue with market-level storefronts is the single highest-value structural decision in a Zurich build, and it has to be made before design starts because it changes URL structure, hreflang, price presentation and how your merchandiser works every day. Prices get set per market rather than converted live, so a German customer sees a clean euro figure instead of CHF times whatever the day's rate produced. Payment gets built around what people here actually use — TWINT, buy-on-invoice through a third-party provider, cards — which changes cart and checkout layout, not just a settings page. And delivery options are presented against Swiss Post's service levels for domestic orders and a separate, honest international promise for everything crossing out.
The same standard of work we run for every client — applied to a Zurich 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 Zurich 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.