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.
We build Shopify storefronts for Chicago brands that already have a warehouse, a sales rep and a distributor list — and now need the direct channel to earn its keep.
Delivered remotely for brands across Chicago and Illinois.
A lot of Chicago brands come to a storefront project sideways. The company is thirty years old, the revenue comes from grocery, hardware or specialty wholesale, and the website was built once by a cousin's agency to satisfy a retailer who asked for a URL on the packaging. Nobody designed it to sell. It shows.
That starting point changes the build. A Fulton Market snack brand needs freeze-protected shipping windows and multi-pack architecture on the product page. A Merchandise Mart housewares line needs dimensional freight logic and room-based merchandising. A Ravenswood brewery or distiller needs age gating, state shipping rules and a case-quantity cart. None of that is theme decoration. It is structure, and it has to be decided before anyone opens Figma.
We build in clean Online Store 2.0 Liquid, with the sections your merchandiser can actually rearrange, and we build the operational truth into the front end: real stock by location, honest delivery estimates from a Midwest warehouse, and pricing display that will not get you a phone call from your largest account. Then we hand it over documented, because your team is small and nobody in your building wants to file a ticket to change a homepage banner.
The typical Chicago merchant we build for is not a DTC-native brand. They are a manufacturer or distributor with real inventory sitting in Elk Grove Village, Bedford Park or out along I-55, an ERP that has been running since before Shopify existed, and a catalog whose logic was designed for a line sheet rather than a collection page. That means the design work starts with taxonomy — how a 900-SKU housewares or hardware catalog collapses into browsable collections — and with MAP rules, so the direct channel does not undercut the retailer whose reorder pays the mortgage. It also means the calendar bends around trade: the Inspired Home Show and NeoCon at theMART set the spring, the National Restaurant Association Show at McCormick Place sets May, and nobody wants a cutover the week the sales team is on the floor.
The same standard of work we run for every client — applied to a Chicago 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 Chicago 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.