Windsor Harlow Start a conversation

Services / Commerce & Product Design

Storefronts that convert, and design that arrives build-ready.

The interface that gets designed is the interface that gets shipped.

Typical first engagement
5–12 weeks, fixed scope
Starts with
Performance and conversion baseline
Ends with
Live storefront, design tokens and editor documentation

The problem

What this practice is actually for.

Design handed over as flat mockups gets rebuilt by whoever is available, in whatever the theme already does. That gap is where conversion goes to die.

We keep design and engineering in one engagement: components specified with states and tokens, a performance budget agreed before the first screen, a conversion baseline taken at the start.

  • Design delivered as coded components and tokens, not static files
  • Core Web Vitals treated as a launch requirement, not post-launch cleanup
  • Checkout and funnel instrumentation in place before the redesign ships
  • Content editable by your merchandising team without a developer

Capabilities

Commerce & Product Design — the full stack.

4 capability groups

Shopify
Custom storefronts, theme development, headless builds (Hydrogen and custom front ends), platform migrations, app and API integration
UI/UX design
Product design delivered as build-ready components, design tokens, states and breakpoints; design-system documentation
Front of funnel
Performance budgets, Core Web Vitals, image and font strategy, checkout and conversion instrumentation
Migration
Catalogue, customer and order migration with reconciliation, plus redirect mapping to protect search rankings

Typical engagements

How this work usually starts.

Indicative scope and duration

Fixed scope

Custom Shopify storefront

Design and build on a defined scope, with a theme your merchandising team can operate and a measured performance budget at launch.

6–10 weeks · design + build

Fixed scope

Headless commerce build

Shopify as commerce engine with a custom front end where content, personalisation or performance demands justify the additional complexity.

8–12 weeks · headless

Fixed scope

Platform migration

Move to Shopify with catalogue, customer and order data reconciled, redirects mapped, and search visibility protected through cutover.

5–9 weeks · reconciled migration

What you get

Deliverables, every time.

01

Design system

Components, states, tokens and breakpoints, documented and implemented in code — one source of truth for design and build.

02

Performance budget

Agreed Core Web Vitals targets, verified at launch, with the specific costs of any exception written down.

03

Editor documentation

How your team changes content, merchandising and page structure without a developer in the loop.

04

Conversion baseline

Funnel instrumentation and a before/after measurement, so the redesign can be judged on results rather than taste.

Questions

What clients ask before they commit.

A well-built theme covers most stores and costs materially less to run and maintain. Headless earns its keep with complex content needs, multiple storefronts or personalisation that themes cannot express. We will price both and tell you which one we would choose with our own money.

Yes, and preferably together. Design arrives as build-ready components with tokens and states rather than flat mockups, which removes the interpretation gap that usually degrades a design between approval and launch.

Not if migration is treated as an engineering task. Redirect mapping, structured data, URL preservation and Core Web Vitals are part of the scope, with a pre-launch crawl comparison so regressions are caught before cutover rather than in next month's traffic report.

Have a Commerce problem worth a senior pair of eyes?

Tell us the system, the constraint, and what happens if it is not solved. A senior engineer replies within one business day.

Scope an engagement