A reskin keeps the problem.

A theme gives you a layout. It cannot know that your category is shopped on fit, or that your best product needs three objections answered before the price makes sense. We start from what your customers are deciding and build the structure that serves it. If a theme would genuinely do the job, we will tell you — and we sell six of them for $300.

The audit establishes a baseline before anything changes, so the comparison is real rather than remembered. We stage the launch, watch the numbers against that baseline, and fix what moved the wrong way. A rebuild with no measurement plan is a gamble, and we do not run those.

No. We are rebuilding the argument, not the identity. If you have brand guidelines we work inside them; if the identity itself is holding the store back we will say so and quote art direction separately rather than smuggling it in.

That is the point of shipping a design system rather than a set of pages. Sections are reorderable, settings are exposed, and merchandising changes do not need a developer. You get documentation for the parts that need it.

It can, by narrowing scope rather than compressing quality — the refresh tier exists for exactly that. What we will not do is skip the diagnosis or the mobile design, because those are the two places a fast rebuild reliably fails.

Timely access to the store and analytics, one person who can approve, and your product data. Delays in feedback move the timeline more than anything on our side.

Six phases across roughly nine weeks. Week one is the full CRO audit — a rebuild that starts without a diagnosis is decoration. Weeks two to three settle the information architecture and the order of argument before a single visual. Weeks three to four set the art direction as a system. Weeks four to six design every template, mobile on its own terms. Weeks six to nine build it in the theme, and from week nine the launch is staged and measured.

The information architecture, a design system your team can extend without breaking it, and every template — home, collection, product, cart, search, account, plus the empty and error states most redesigns discover in production. The buy box arranged in the order the decision needs, mobile designed separately, and the metafield and content structure so merchandising changes do not require a developer.

Three. A storefront refresh — four to five weeks, for when the structure holds but the presentation does not, built in your existing theme. A full rebuild — eight to ten weeks, for when the structure is the problem: information architecture rebuilt, every template and edge case, a new theme from scratch. And rebuild-and-retain — ten weeks plus ongoing, adding post-launch measurement, monthly CRO iteration and priority development time. Each is quoted per scope.

The week-one audit establishes the baseline; the launch is staged and then watched against it. The rebuild is judged on numbers rather than taste — the same before-and-after discipline as the published case studies.