Do you build the site yourself?

No. I research, design and brief, then I work with your developer or agency, or bring in one I trust. Implementation stays with people who build for a living, which is why it ships on time.

Will this mean a new theme?

Rarely. Most of the gain is in the product page, the cart and the checkout, and all of that can be done inside the theme you have. If a new theme is genuinely the right call, I will say so and explain why.

How do you know it worked?

Revenue per session, conversion by device and average order value, measured before and after, and tested properly where the traffic allows it. You get the numbers, whichever way they went.

Ecommerce UX and design, judged on revenue

A theme is built for the average store. Your customer is not average, and the gap between the two is where the revenue leaks. I redesign the journey around how people actually decide to buy your product, and I judge the result on what it sells rather than on how it looks in a deck.

Book a 20 minute call Start with a Growth Review

You are probably here because one of these is true.

The site looks good and converts badly, and nobody can say why.
Mobile converts at a fraction of desktop, and most of your traffic is mobile.
Your product page is a template with your photographs dropped into it.
Customers email to ask questions the site already answers, somewhere.
Somebody has quoted you a redesign and you cannot tell what it would change for the customer.
The last redesign went live and the numbers did not move.

What I actually do.

Start with how people decide. Before anything is drawn I find out what your customer needs to know before they will buy, and in what order. Support tickets, reviews, search queries and a handful of real people using the current page. The design follows the decision, not the other way round.

Rebuild the product page around fit and confidence. Hierarchy of information, sizing and fit, delivery and returns made plain, reviews where they are read rather than where they are tidy. This is the page that decides most of it, and it is usually the one built with the least thought.

Make collection pages do their job. Filters that match how customers actually narrow down, comparison where a category needs it, and enough information on the card that people do not have to open six tabs to choose.

Take the friction out of cart and checkout. Every avoidable step between wanting the thing and having bought it, on a phone, with one thumb. Payment options, delivery clarity, and the small failures that quietly lose orders at the last moment.

Brief the build properly. I do not build websites. I write the brief, the wireframes and the acceptance criteria your developer or agency needs, and I check the work against them. Twenty years of working with development teams means I can tell when an estimate is optimistic.

Measure it on revenue. Every change is set against revenue per session, conversion by device and average order value, before and after. If a change cannot be tested it is still measured, and if it did not work I will say so.

The first ninety days.

Weeks one to four

Research, customer interviews and analytics. A ranked list of what to change and why, agreed with you. The obvious fixes go live early, because they do not need a redesign to justify them.
Weeks five to eight

The product page and checkout redesigned and built, in your theme or through your developer, with the highest value change shipped first.
Weeks nine to twelve

Collection pages and the remaining journey. Results measured against the baseline, and the next quarter's list rebuilt on what the numbers now show.

£1m

inov-8's first million pound net trading month, delivered on a store I had helped rebuild.

I played a key part in moving inov-8.com to a headless architecture, which improved performance and gave the team room to build rather than work around the platform. I ran ecommerce delivery for the most successful product launch the company had had, aligning the onsite experience with launch planning and channel execution so the demand actually converted. At Smiffys I built the user testing framework that informed the design decisions on a new platform, so they were made on evidence rather than opinion.

The full track record

Two things I will not do.

I will not sell you a rebuild when the problem is three pages. Most stores do not need a new site. They need the product page, the cart and the checkout to work for the customer they actually have, and that is a fraction of the cost.

I will not design for the screenshot. If a change looks better and sells less, it goes back. The site is a shop, and a shop is judged on what it sells.

Questions.

Do you build the site yourself?: No. I research, design and brief, then I work with your developer or agency, or bring in one I trust. Implementation stays with people who build for a living, which is why it ships on time.
Will this mean a new theme?: Rarely. Most of the gain is in the product page, the cart and the checkout, and all of that can be done inside the theme you have. If a new theme is genuinely the right call, I will say so and explain why.
How do you know it worked?: Revenue per session, conversion by device and average order value, measured before and after, and tested properly where the traffic allows it. You get the numbers, whichever way they went.

Send me your product page and your conversion rate.

Twenty minutes is enough for me to tell you what I would change first and roughly what it might be worth.

Book a 20 minute call hello@scaleandsummit.com