Write two or three sentences here that go further than the summary above. What the work actually involves.

What usually brings people here

The situation rather than the solution. Show you have met this problem before.

What I do

The actual work. Three or four short points rather than a list of capabilities.

How it runs

The shape of the engagement, roughly how long it takes, and what you need from them.

Write two or three sentences here that go further than the summary above. What the work actually involves.

What usually brings people here

The situation rather than the solution. Show you have met this problem before.

What I do

The actual work. Three or four short points rather than a list of capabilities.

How it runs

The shape of the engagement, roughly how long it takes, and what you need from them.

Write two or three sentences here that go further than the summary above. What the work actually involves.

What usually brings people here

The situation rather than the solution. Show you have met this problem before.

What I do

The actual work. Three or four short points rather than a list of capabilities.

How it runs

The shape of the engagement, roughly how long it takes, and what you need from them.

Two decades of running and fixing online sales, from single market shops to operations across the Nordics, the Benelux countries, Germany and the United Kingdom. Trading, merchandising, the journey itself, and the gap between what a business believes customers experience and what they actually do.

What usually brings people here

Traffic is fine and revenue is not. The platform was replaced and performance never came back. Or the team is busy, the dashboards are green, and nobody can say which lever moved last quarter.

The gap where the money is

There is a distance in every business between what the organisation believes the customer experience is and what the customer meets. Nobody is lying. The belief is assembled from a journey map drawn two years ago and a dashboard measuring the happy path. After six months inside a business you cannot use its product like a stranger, so the friction becomes invisible to exactly the people who could remove it.

What I do

I buy something, properly, with my own money, on a phone. Then I break it. I read the last two hundred support tickets as text rather than as categories. I find the two or three points where money is leaking, fix those first, and put a weekly trading rhythm in place so the team can see cause and effect inside a week rather than inside a quarter.

Where I go looking

The right product in front of the right person at the right moment, which is an internal structure problem more often than a technology one. Pricing and where value is captured, usually the fastest lever nobody is pulling. Payment and delivery, which are conversion features that end up owned by operations. And customer service, which is the only team speaking to customers every day and is managed as a cost line.

How it runs

A short diagnostic first, because the brief is often not the problem. Then the work, with one owner and a weekly decision.

Write two or three sentences here that go further than the summary above. What the work actually involves.

What usually brings people here

The situation rather than the solution. Show you have met this problem before.

What I do

The actual work. Three or four short points rather than a list of capabilities.

How it runs

The shape of the engagement, roughly how long it takes, and what you need from them.

Write two or three sentences here that go further than the summary above. What the work actually involves.

What usually brings people here

The situation rather than the solution. Show you have met this problem before.

What I do

The actual work. Three or four short points rather than a list of capabilities.

How it runs

The shape of the engagement, roughly how long it takes, and what you need from them.

Write two or three sentences here that go further than the summary above. What the work actually involves.

What usually brings people here

The situation rather than the solution. Show you have met this problem before.

What I do

The actual work. Three or four short points rather than a list of capabilities.

How it runs

The shape of the engagement, roughly how long it takes, and what you need from them.

It deliberately refuses to produce a summary. Summaries are the least useful thing a model can give you about trading data.

That loop is the thing that makes a team good. Strategy sets direction, which matters, but direction alone does not teach anyone anything. A team that decides on Monday and sees the consequence by Friday builds judgement at a rate that no planning cycle can match.

What a trading rhythm actually is

A short standing meeting, the same day each week, with the same handful of numbers, and a decision at the end of it. Not a status update. Not a dashboard review. A decision, taken by the people in the room, with a name attached.

• The same five or six measures every week, in the same order.
• Last week's decision revisited first, before anything new is discussed.
• One person who owns the call when the room disagrees.
• Forty five minutes, and it ends on time even when it is interesting.

The second point is where most attempts fail. If last week's decision is not revisited, the meeting becomes a place where decisions are made and then quietly abandoned, and people learn that the meeting does not matter.

A team that decides on Monday and sees the consequence by Friday builds judgement faster than any planning cycle.

Why documents lose

A quarterly plan operates at a timescale where cause and effect are almost impossible to attribute. By the time the quarter closes, twenty things have changed, and the plan is assessed on whether it was delivered rather than whether it was right.

Worse, planning cycles reward comprehensiveness. Every stakeholder gets a line, nothing is dropped, and the team arrives at the quarter with more initiatives than capacity. Then the rhythm that would have caught this does not exist, so the discovery happens in month three.

You need both, but build this one first

I am not arguing against strategy. A team with rhythm and no direction optimises its way into a corner. But if you can only build one thing this quarter, build the rhythm, because the strategy will be better written by a team that has spent twelve weeks learning what actually moves.

It is also the cheaper of the two to start. A rhythm needs a calendar invite and someone willing to hold the standard. That is genuinely most of it.

The support inbox is the most under used research asset in most companies. It contains a prioritised list of your problems, written by customers, free of charge.