Both sides of shopping just went commodity

Share
Anubhav Pateriya — everyone rents the same AI, that choice is the moat

Over the past few weeks, two headlines crossed most consumer leaders' desks as unrelated. One was about how people shop. One about how AI gets procured. Together they retire an assumption the industry has run on for 20 years.

Demand: the journey is compressing to a single turn

Start with behavior. The shopping journey is compressing to a single turn. Rezolve's data (one vendor, but consistent with the broader zero-click shift) is stark: seven in ten purchases now follow a single search, up from six in ten a year ago. The shopper stopped behaving like a database query and started behaving like a brief.

Supply: the agent is becoming a rental

Now the supply side. Serving that shopper used to take years and a platform team. Now it ships as a configuration. Amazon packaged the engine behind its $12B Alexa business into an AWS kit any retailer can wire to its catalog, citing 3.5x the conversion of keyword search. It is not alone: Google, OpenAI with Stripe, and Shopify are racing to turn the same capability into shared rails. The agent is becoming infrastructure, not advantage.

The scarce resource flips

Here is why they connect. When demand concentrates into one high-intent turn, the whole interaction lands in a single moment: what the agent recommends, on what logic, what it refuses to do. Just as that moment becomes everything, the machinery that runs it becomes a rental. The scarce resource flips. Advantage used to come from owning the funnel: traffic, tooling, optimization muscle. The funnel is now one click long, and the tooling is bought. What stays scarce is the judgment encoded into the agent.

That breaks two things every consumer org budgets around:

  • The metrics. Click depth, dwell time, pages per session were proxies for a many-step journey. In a single-turn world they measure something that no longer happens; the dashboards and incentives built on them now optimize noise.
  • The roadmap. "Build our own assistant" assumed the build was the moat. When a competitor rents the same engine and goes live in weeks, the build is table stakes. The only durable choices left are configuration choices.

The default-config trap

Here is the trap, and it rhymes with every prior platform shift. The risk is not moving too slowly. It is moving fast and deploying the default. Two brands on the same engine, both out of the box, are interchangeable: same answers, same logic, same refusals. Adoption without a point of view does not differentiate you; it commoditizes you faster. What matters is the judgment the box cannot supply: which intent you optimize for, what you forbid the agent to do, how it weighs margin against loyalty.

I call this the Destination Problem. AI is solving the driving problem. The choices that decide who wins are destination choices, and they belong to leaders, not the machine. Execution is going abundant. Judgment is the moat.

The real question is not which agent you deploy. Everyone deploys, on the same rails. It is the destination question: when the engine is rented and the shopper arrives with a brief, what does your brand decide that the machine never can?

Explore the full thesis: the Destination Problem.

First shared on LinkedIn. Join the discussion there.