Keep the platform. Rebuild the experience.

Yes, and it is often the safer route. Homepage, collection, and product templates can be released in sequence so change is observable and reversible. We agree the order during planning based on where the current experience is weakest.

Not if it is inventoried first. We catalogue existing sections, metafields, custom logic, and app dependencies before development, then plan how each is carried across, replaced, or deliberately retired.

Either. We can develop from your brand system or designs, or take design direction as part of the engagement. If you have a brand guideline but no storefront design, we work from the guideline and resolve the commerce-specific patterns it does not cover.

A redesign can remove friction we can identify and explain, and we prioritize work on that basis. We do not promise a conversion increase — too much depends on traffic, pricing, product, and seasonality — but we do document what changed so you can evaluate it.

Each app is reviewed for what it contributes, what it costs in storefront weight, and whether the redesign still needs it. Some are re-integrated, some are replaced by native functionality, and some are removed — with your agreement in every case.