Skip to content
Customer paying by card at a shop checkout

CS-05 · Retail

The pricing agent we switched off

A retailer asked for an agent to recommend weekly markdowns. It was accurate in testing and unused in practice, because the buyers did not trust a recommendation they could not trace. We switched it off and wrote down why.

An honest write-up of a deployment that did not work

Pilot length
8 wks
Buyer adoption by week eight
Low
Agent switched off
1
Lessons we now apply everywhere
3

What went wrong

Right answers nobody used.

The agent's markdown recommendations held up well against what experienced buyers later chose. But it presented a number, not a reason, and the buyers carried the margin risk personally.

We had optimised for accuracy and skipped the harder question: would the people accountable for the decision act on it? By week eight, most of them were not opening the recommendations at all.

What we changed in how we work

Lesson 1

Explain before you recommend

Every agent now shows the records and reasoning behind a suggestion, not just the suggestion.

Lesson 2

Ask who carries the risk

If the user owns the consequence, they co-design the agent from week one.

Lesson 3

Measure use, not just accuracy

Adoption is a release criterion alongside the test-set score.

It was probably right. I just couldn't defend it in the Monday meeting.

Category buyer, during the pilot review
All case studies

Want the honest version of what AI can do for you?

We'll tell you where we think it won't work, too.