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 Stockholm brands whose checkout has to satisfy Swedish habits at home and read cleanly to a buyer in Hamburg.
Delivered remotely for brands across Stockholm and Sweden.
A Swedish shopper arrives at your product page already knowing how they intend to pay and where they intend to collect. Those two decisions were made before they met your brand, and a theme that treats them as afterthoughts — a wallet list in default order, a shipping line with no service-point selection — hands away conversion that the design work never gets credit for losing. We build the checkout path first and the aesthetic around it, which in practice is what produces the better-looking store as well.
The second thing a Stockholm build has to carry is two audiences in one theme. Domestic buyers read English perfectly well and still convert better in Swedish, while the export traffic you are courting in Germany, the Netherlands and the UK needs an English tree that is genuinely complete rather than a translated product title sitting on top of Swedish filter labels, Swedish size guidance and a Swedish returns page. We structure the theme with translation keys from the first section file so navigation, facets, metafields, cart and transactional email all move together instead of separately.
Then the catalogue. The categories this city actually produces each break a stock theme in a specific way. Lighting and interiors need finish and dimension variants plus freight-class shipping that does not pretend a floor lamp posts like a t-shirt. Outdoor and technical gear needs temperature ratings, materials and layering guidance on the page, because a spec-free product page quietly loses that sale to a competitor who published the numbers. Kids and baby products need standards and age information where a parent will actually see it. We design the templates around what you sell rather than asking what you sell to survive a template.
In most markets the delivery section of checkout is plumbing. In Sweden it is a conversion element, because collection at a service point or parcel locker is the default expectation rather than the budget fallback, and a buyer who cannot see which ombud their parcel lands at is being asked to accept uncertainty at the worst possible moment. That means locker and service-point selection, address handling that behaves for Swedish formats, and a wallet order that puts the methods people actually use above card entry. Swedish rules also bear on how pay-later options are presented — credit-based methods should not be pre-selected or pushed ahead of direct payment, and your counsel should confirm the specifics for your setup — so we build the payment presentation deliberately instead of accepting whatever order the integration ships with. The other build constraint is the European Accessibility Act, which since June 2025 has applied to consumer ecommerce across the EU, with exemptions for the smallest businesses. We build to accessible patterns as standard: contrast, focus states, keyboard paths through the cart, and form labelling that a screen reader can follow.
The same standard of work we run for every client — applied to a Stockholm 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 Stockholm 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.