For established online shops that should be working harder

Your store is probably not missing one big idea. It is leaking value through dozens of small decisions nobody owns.

I find the friction making an active eCommerce store harder to buy from, decide what is genuinely worth fixing and build the improvements properly.

At first, it looks like a traffic problem.

The store is live. Orders arrive. Campaigns run. The product is good enough that people clearly want it.

But growth feels more expensive than it should.

More visitors arrive without a matching rise in orders. Mobile conversion makes everybody uncomfortable. Customers ask questions the product page was meant to answer. A promotion works, but nobody is quite sure why. The team has a list of improvements that gets discussed more often than it gets finished.

No single problem looks catastrophic.

That is what makes the situation so easy to tolerate.

A customer hesitates at the navigation. They reach a collection and cannot narrow it sensibly. The product page leaves one important doubt unresolved. An app delays the moment anything useful appears. The cart introduces a surprise that should have been explained earlier.

Each moment loses only a few people.

Together, they quietly decide what every pound spent on traffic is actually worth.

So you try the obvious fixes.

You install an app because its demo solves the visible symptom. Now the store has another script, another subscription and another interface the team must remember.

You commission a redesign because a larger project feels proportionate to a stubborn problem. The new store looks fresher, but many of the old assumptions survive underneath it.

You work through a conversion checklist. Badges move, buttons change colour and another pop-up appears. The page becomes busier without becoming more convincing.

You ask for an agency proposal. It arrives with a confident total, a long feature list and just enough ambiguity to make signing it feel like an act of faith.

None of these choices is automatically wrong.

They fail when they begin with a solution before anybody has properly diagnosed the store.

If you already have a store worth improving, let me show you where the useful work is hiding.

Get a free outside view No automatic rebuild recommendation. If I cannot genuinely help, I’ll tell you.

The root problem is not a shortage of ideas. It is a shortage of ownership.

The paid-media team owns the click. The designer owns the mock-up. The developer owns the ticket. The app owns one feature. The agency owns whatever sits inside the agreed scope.

The customer experiences none of those boundaries.

They experience one store.

When responsibility is divided by discipline, the awkward spaces between those disciplines become nobody’s job. Commercial context gets lost on the way to development. Technical constraints arrive after design. Small customer frustrations survive because each one belongs partly to several people and entirely to none.

This is why adding more specialists does not always create a better buying journey.

What is missing is somebody who can follow the problem across the boundaries: from what the business needs, through what the customer experiences, into what the technology is actually doing.

The useful work happens in a deliberate order.

  1. Find the real friction Review the journey as a customer experiences it—navigation, search, collections, products, cart, performance and the moments between them.
  2. Understand what is causing it Separate the visible symptom from the theme decision, app conflict, content gap, integration or process sitting underneath it.
  3. Rank the work honestly Balance customer impact, commercial value, evidence, effort and risk so the backlog becomes a useful order rather than a collection of opinions.
  4. Build the smallest valuable answer Improve the existing store where that is sensible. Use custom development only where it earns its keep. Rebuild only when the evidence really points there.
  5. Ship, learn and continue Test the work properly, release it calmly and use what happens next to choose the following improvement.

This order sounds obvious.

In practice, most wasted eCommerce spend comes from skipping one of its steps.

A feature gets built before the problem is understood. A rebuild begins before the current store is examined. A tool gets selected before the team agrees what success would look like. Work is delivered but nobody checks whether the original friction has gone.

The answer is not more process for its own sake. It is enough clear thinking to prevent expensive activity from masquerading as progress.

You should not have to choose between advice and somebody who can implement it.

I’m Luke Michael, a UK eCommerce Consultant & Developer with over twenty years spent in-house, agency-side and freelance.

I work across Shopify, Shopify Plus, BigCommerce and WooCommerce, with the deepest roots in Shopify and Shopify Plus.

The useful part is not recognising the platform logo. It is knowing how commercial intentions turn into design decisions, how those decisions survive implementation and where established stores tend to accumulate friction over time.

Sometimes the right starting point is consultancy: reviewing a proposal, challenging a platform decision, joining a supplier call or giving you a straight second opinion before money is committed.

Sometimes it is focused development: improving a product or collection template, fixing mobile behaviour, removing performance drag, integrating a tool, building a campaign page or replacing a manual workaround.

Often it is both.

That continuity matters. The person helping decide what should be done remains responsible for making sure the finished work still solves the same problem.

The proof should come from your store, not my adjectives.

I could fill this page with vague promises about growth. They would tell you very little about what will happen on your website.

A better starting point is the evidence you already have: customer questions, search terms, support conversations, analytics, recordings, returns, device performance, team workarounds and the jobs that keep being deferred.

That evidence gives us a specific problem and a sensible way to judge whether the change improved it.

It also keeps the work proportionate.

A navigation issue may need a modest theme change, not a redesign. A slow product page may need fewer third-party scripts, not a new platform. An agency proposal may be sound but need three assumptions made explicit before you sign.

Good optimisation is not the art of making every task larger.

It is the discipline of finding the smallest piece of work that creates a meaningful improvement.

You may be wondering…

“Do we need to rebuild?”

Usually not as a first step. A rebuild is the most expensive answer to a question that has not yet been diagnosed. If the current foundation genuinely cannot support what the business needs, I will explain why.

“Can you work with our existing agency or team?”

Yes. I can provide an independent view, own a clearly bounded piece of delivery or help the people already involved make a better-informed decision.

“Is this only for large projects?”

No. One focused, finite problem is often the best way to start. It gives you something useful and lets both sides understand whether working together feels straightforward.

“Do you only advise, or do you write the code too?”

Both. Consultancy prevents the wrong work being built; development turns the right decision into something customers and the team can actually use.

“What if we are not sure what the problem is?”

That is a perfectly good reason to get in touch. Describe what feels wrong, what customers mention or where the team keeps getting stuck. The diagnosis is part of the work.

There are three sensible ways to begin.

Start with a free fit call if you have a store and a problem but are not sure what kind of help it needs.

Book paid advisory time when a specific decision, proposal or technical question needs focused independent input.

Request pricing when the work is already reasonably clear and you want to understand how I would approach delivery.

You do not need a polished brief. The useful version of the problem is usually better than the presentable one.

The choice is not “rebuild or do nothing”.

Keep accepting the friction

The backlog grows, apps continue to accumulate and every new campaign sends more people through the same unresolved journey.

Improve the store you already earned

Find the most valuable source of friction, solve it cleanly and let the evidence choose what deserves attention next.

You already did the difficult part. You built a real business with products, customers, traffic and a store worth improving.

You do not need another grand promise.

You need a clear next move and somebody capable of making it real.

Best,

Luke Michael

eCommerce Consultant & Developer

start with the thing that bothers you most

Show me where the store is making customers—or your team—work too hard.

I’ll look at the website before we speak and give you a straight view of what appears worth fixing first.

Start with a free call No obligation afterwards. No mailing list. Just a direct reply from me.

P.S. If the right next step is something your current supplier can handle perfectly well, I will tell you that too. The point is to improve the decision, not manufacture a project.

Get a free outside view