Shopify CRO audit. Find out where your store is losing the sale.

Free. One leak, named, on your store. No call, nothing to pay. The full ranked list is the paid step — $500, credited if we build.

Seven steps. Step four is the ranking — that’s what the $500 buys.

It goes in two steps, and the first one is free.

  1. Step one

    The free read

    Nothing

    Send your store URL and roughly how many sessions you get a month. I’ll come back with the biggest leak I can see and why it’s costing you. One thing, named, with the reason. No call required and nothing to pay.

    What step one isn’t: the full list. I’m not going through your whole funnel for free, and anyone who says they will is either not doing it properly or charging you for it somewhere else.

  2. Step two

    The prioritised plan

    $500

    The whole path, from the ad click to the thank-you page. Everything I find, ranked by what it’s worth against what it takes to fix — so you get the three things that matter rather than forty that don’t. You can hand it to any developer. If you’d rather I built it, the $500 comes off the quote, as long as we start within thirty days.

  3. Step three

    The build

    Priced after I’ve seen the store and we’ve agreed the scope. Never before.

What the free audit includes — and what it doesn’t.

A free audit that hands over the whole prioritised plan isn’t generous — it’s a vendor giving away the only part of the work the buyer can actually judge, then asking to be paid for the part they can’t.

So the free read names one leak and stops. That’s enough for you to tell whether I can see your store properly, which is the only question the free step needs to answer.

The ranking is work. It’s step four of seven and it’s where the judgement is. That one’s paid.

I’m not going to guarantee you a number.

Anyone who does is either not measuring properly or is about to blame the season. Conversion moves for a dozen reasons at once and a vendor who promises a figure is telling you they’ve stopped looking at the other eleven.

Here’s what you get instead.

  1. You see the leak before you pay.

    Step one is free. If I can’t find anything worth showing you, you’ve lost nothing and you know something.

  2. The plan comes off the build.

    If the $500 plan convinces you, it’s credited. If it doesn’t, you keep the plan and we stop.

  3. The work is measured against the number it started from.

    I record where you are before I touch anything, and I check again after. If it moved, you’ll see by how much. If it didn’t move, that’s a finding and we use it — that’s step seven, and I’d be doing it whether or not it suited me.

The six questions people actually hesitate over.

Why would I pay you to fix the site when I could put that money into ads?

Because more traffic to a page that isn't converting buys you more of the same loss.

If your store converts at 1.2%, every hundred visitors you buy produces about one order. Spend twice as much and you get twice as many visitors and roughly twice as many orders — and you've doubled your cost to get there. Move the conversion rate instead and every visitor you were already paying for is worth more, including all the ones you buy next month.

It isn't either/or forever. It's a question of which one is cheaper right now, and at a low conversion rate it's usually the site. Run your own numbers through the calculator and see whether that's true for you — the arithmetic doesn't need me.

How do I know your changes will actually make me more money?

You don't, before the work. What you can know is whether I measured it honestly afterwards.

I record your baseline before I change anything — conversion rate, revenue per session, add-to-cart, by device. I make the changes. Then I check the same numbers against the same window and tell you what moved.

Sometimes it doesn't move, or it moves for a reason that has nothing to do with me — a seasonal shift, a traffic-mix change, something else that shipped the same week. I'd rather tell you that than take the credit. That's step seven of how I work and it's the step most people skip, because it's the only one that can make you look wrong.

Is this going to turn into a full redesign?

No. Almost never, and I'll say so in the free read if a redesign genuinely is the answer.

Most stores I look at need three or four specific changes, not a rebuild. A rebuild is expensive, slow and risky — you lose everything that was already working along with everything that wasn’t.

The prioritised plan exists precisely to stop this. It ranks what I find by what it's worth against what it takes, so the top of the list is usually small and high-value. If the honest answer is that your theme can't do what you need, that's a different conversation and a different quote, and I'd tell you before you paid me anything.

What do I actually get for the $500?

The whole funnel gone through once, properly, and everything I find ranked.

That means the path from the ad click to the thank-you page: the landing or product page, the cart, the checkout, mobile separately from desktop, with your funnel data next to what I'm seeing on the pages.

What you get back is a list where every row names a page, an element, the change, what I think it’s worth and what it takes to do. Usually ten to fifteen rows. You can hand it to any developer — it isn’t written to need me. If you’d rather I built it, the $500 comes off the quote.

Do you run the ads as well?

No. I don't create ad creative, run campaigns or manage media budgets.

I work on the store — the product page, the theme, the cart, the checkout, the speed, the mobile experience. The page the ad points at, not the ad.

This is the most common reason someone and I turn out not to be a fit, so it's worth saying plainly up front. If your problem is targeting or creative, I'm the wrong person, and I'd tell you that in the free read rather than taking the project and hoping.

What happens after you’ve found the problem?

I fix it. Same person, no handoff.

This is the part that tends to go wrong elsewhere: a consultant hands over recommendations and you're left finding a developer to build them, who wasn't in the room for the diagnosis and is working from a document.

I do both. I have three specialists who help with build load when there's a lot of it — but the person who found the problem is the person who implements it, and then measures it. There's no point in the diagnosis where it becomes someone else's document.