EDITOR’S NOTE

Hey there 👋

There’s a scene inside most large retail organizations right now that would have seemed implausible five years ago. A small team of no more than four or five people gets a brief, a deadline, and access to a few API keys. Three weeks later, they ship something that previously would have occupied a product roadmap for 18 months and required a dedicated engineering team to build.

Nike’s conversational shopping assistant is exactly that story.

Faced with a conversion problem they had diagnosed clearly but solved poorly, a cross-functional squad inside Nike’s digital product org decided to stop waiting for a “big AI transformation” and just build. They used existing infrastructure, a well-designed prompt architecture, and an orchestration layer to wire it all together. 

Let’s get into how it was done. 🚀

TL;DR 📝

  • Nike’s mobile conversion problem was a discovery problem. Mobile shoppers were bouncing because the browse experience offered no fast, intuitive way to find what they were actually looking for.

  • Working with digital product consultancy Rangle, Nike shipped a generative AI-powered shopping assistant in three weeks without training a custom model and without a lengthy engineering programme.

  • The “intelligence” was in the prompt architecture. The team’s biggest investment of time was designing the conversation flow and the system prompt.

NEWS YOU CAN USE 📰

How We Built Nike's Personalized AI Shopping Assistant in Just 3 Weeks. With thousands of product SKUs and data from over 170 million loyalty program members, Nike envisioned a hyper-personalized, conversational shopping experience. One that felt like a natural, one-on-one conversation and made customers feel understood and supported by surfacing relevant products in real time and at scale, in an intelligent, dynamic, and non-intrusive way. [Source: Rangle]

AI Mode is Google’s next ads engine, and it already knows how to monetize it. As AI Mode expands, ad formats, reporting, and control are starting to take shape, with Google playing a long game that competitors can’t match. As conversational search gains traction, the bigger question isn’t who has more users, but who can monetize them. [Source: Search Engine Land]

Jeff Bezos reportedly wants $100 billion to buy and transform old manufacturing firms with AI. Jeff Bezos is reportedly seeking $100 billion for a new fund that will be used to buy up companies in major industrial sectors and, ultimately, modernize and automate them with AI, according to sources cited by The Wall Street Journal. [Source: TechCrunch

Generative AI improves a wireless vision system that sees through obstructions. With this new technique, a robot could more accurately detect hidden objects or understand an indoor scene using reflected Wi-Fi signals. This new technique builds a partial reconstruction of a hidden object from reflected wireless signals and fills in its missing shape using a specially trained generative AI model. [Source: MIT News

NIKE’S 3-WEEK SPRINT: BUILDING A CONVERSATIONAL SHOPPING ASSISTANT FROM SCRATCH

In a case study published by Rangle, Nike partnered with the agency to build a generative AI-powered shopping assistant designed to personalize the product discovery experience, and the entire build took three weeks. 

That speed is the real story here. Unpacking how it was possible tells us something important about where conversational commerce is going.

The problem Rangle and Nike set out to solve is one most Direct-to-Consumer (DTC) brands will recognize: mobile shoppers were landing on the footwear category page and leaving without converting.

The standard browse experience, with filters, sorting, and category pages, wasn’t giving them a fast, intuitive path to the right product, and the answer turned out to be a conversation.

The Stack 🛠️

Typical architecture for a generative AI shopping assistant of this kind draws on a short, well-established list of components, and understanding that list is useful regardless of which specific tools any given team chooses. 

An LLM API (such as GPT-4o or Claude) handles conversational understanding, context retention across a multi-turn session, and response generation. This is the engine that makes the assistant feel like a dialogue rather than a search box.

An orchestration layer (such as LangChain or LlamaIndex) manages conversation memory, routes user intent to the right downstream system, and enforces the guardrails that keep the assistant on-task. Without this layer, the assistant can’t reliably reference what the user said three turns ago.

A product search integration (such as Algolia or Elasticsearch) translates the conversational context the assistant has gathered, shoe type, use case, fit preference, and budget into structured queries against the product catalogue, returning results ranked by relevance to the conversation rather than keyword match alone.

An existing product catalogue and inventory API ensure the assistant surfaces actual in-stock options rather than ghost recommendations. The ability to plug into infrastructure that already exists is a significant part of why these builds are achievable.

All of these components are available off the shelf, but Rangel and Nike thoughtfully assembled them.

The Three-Week Timeline 📅

Week 1

The most important artefact in an early sprint like this is the conversation architecture.

This means defining the assistant’s persona, the qualifying question sequence, the decision logic for when it has enough context to make a recommendation, and the guardrails that keep it focused. Getting this right up front determines everything that follows. Infrastructure integrations can be scaffolded in parallel.

Week 2

Before any customer sees the assistant, the team needs to simulate the full range of user behaviours.

The shopper who knows exactly what they want, the one who doesn’t know where to start, the one who asks something completely off-topic. Every edge case gets a defined response built into the system prompt. The goal is to eliminate surprises before any real traffic hits the experience.

Week 3

A phased deployment that exposes a portion of real traffic to the assistant while keeping the remainder on the standard experience allows the team to observe behaviour, identify drop-off points, and iterate on the prompt architecture before any wider rollout.

This is where conversation design and engineering work together: the data tells you where the assistant loses people. The system prompt is where you fix it.

The Key Insight 🔑

Nike designed a conversation, connected it to the infrastructure they already had, and deployed it. The intelligence in this system lives in the prompt architecture, and that’s a content and strategy problem.

That matters enormously for marketers because it means the bottleneck for building something like this is the clarity of thinking about how your customers make decisions.

There’s also a broader lesson in who leads the conversation design work. The most valuable contributor in a sprint like this isn’t typically an engineer. Instead, it’s the person who understands how customers move from uncertainty to decision, and can structure a conversation that shortens that journey.

That’s a content strategy and UX skill applied to an AI context, and it’s a capability most marketing teams already have, or can develop quickly.

Stop typing prompts. Start talking.

You think 4x faster than you type. So why are you typing prompts?

Wispr Flow turns your voice into ready-to-paste text inside any AI tool. Speak naturally - include "um"s, tangents, half-finished thoughts - and Flow cleans everything up. You get polished, detailed prompts without touching a keyboard.

Developers use Flow to give coding agents the context they actually need. Researchers use it to describe experiments in full detail. Everyone uses it to stop bottlenecking their AI workflows.

89% of messages sent with zero edits. Millions of users worldwide. Available on Mac, Windows, iPhone, and now Android (free and unlimited on Android during launch).

THIS WEEK’S PROMPT 🧠

Use this prompt with your preferred LLM to design a conversational shopping assistant architecture for your own product category.

The scenario:

You are the Head of Digital Marketing for a mid-sized direct-to-consumer retail brand. Your mobile conversion rate is underperforming desktop by more than 30%; exit survey data suggests that shoppers are leaving because they can’t quickly identify the right product from your catalogue. You’ve been tasked with designing a conversational shopping assistant that can be built and deployed within four weeks, using existing API infrastructure with no custom model training or months-long engineering project.

The Prompt:

Act as a senior AI product strategist with deep experience in conversational commerce. I need your help designing the full architecture for a conversational shopping assistant for my brand. I’ll share context on our product category, customers, and current tech stack below.

Based on that, help me design the conversation flow, the system prompt structure, the recommended tooling, and the A/B test plan for a four-week build sprint. Be specific, I want something I can hand to my team as a working brief, not a set of general principles.

Current Situation

  • Our product catalogue has [X] SKUs across [Y] categories

  • Our primary mobile shoppers are [describe audience age, intent, typical session behaviour]

  • Our current tech stack includes [e.g., Shopify / Salesforce Commerce/custom], and we use [e.g., Algolia / native search] for product discovery

  • We have a [small/medium/large] engineering team and [limited / moderate/strong] AI implementation experience

  • Our biggest conversion drop-off happens at [category page/product page/cart/checkout]

QUESTIONS

  1. What are the 5–7 qualifying questions the assistant should ask to identify the right product, and in what sequence should they ask them to feel natural rather than interrogative?

  2. How should the system prompt be structured to maintain the assistant’s persona, enforce guardrails, and manage the handoff to product recommendations?

  3. Which LLMs and orchestration tools do you recommend given our stack, and what integration points should we plan for?

  4. What edge cases, unexpected user inputs, out-of-stock recommendations, and off-topic questions should we define behaviour for before we build?

  5. How should we structure the A/B test to get statistically significant conversion data within three weeks, and what should our primary and secondary metrics be?

  6. What does the first-week prompt testing process look like, and how do we simulate diverse user personas before going live?

  7. Based on the Nike case, what are the three most common mistakes teams make in the first week of a conversational commerce sprint, and how do we avoid them?

TOOLS WE USE ⚒️

These are the most popular AI tools we use at Rise Up Media. If you're not using them already, they're worth a look.

  • Claude Cowork: Claude Code but for non-devs (like us!)

  • Manus AI: General-purpose AI agent we love (and use to create this newsletter)

  • n8n: Open-source automation (if you like that sort of thing)

  • Relevance AI: No-code create-your-own AI agents platform

  • OpusClip: Auto-clips long videos into shorts (and is really good at it)

  • Buffer: Manage all your socials (with a sprinkle of AI) in one place. 

Full disclosure: some links above are affiliate links. If you sign up, we’ll earn a small commission at no extra cost to you.

HAVING FUN WITH AI

This is a real article from New York Magazine. 2026 is weird, man… 😆

WRAPPING UP 🌯

What Nike’s sprint makes clear, perhaps more than anything, is that the organizations moving fastest on AI are the ones willing to define the problem precisely and resist the temptation to solve it with a standard transformation programme.

The conversational shopping assistant isn’t a novel concept. Retailers have been trying to build it in various forms for years. What’s new is that the infrastructure required to make it work reliable LLMs, flexible orchestration, and real-time search integration is now accessible to virtually any team. The constraint today is the clarity of thinking that goes into designing the conversation itself.

Understanding how customers make decisions, knowing the questions that reduce uncertainty, and being able to write words that build trust without friction are the work that make a conversational AI experience feel like a brilliant in-store associate rather than an elaborate FAQ.

If there’s one thing to take from this issue, don’t wait for a perfect AI strategy document to emerge from a committee. Find the conversion problem you can name precisely, find the team that can own it, and give them three weeks.

Until next time, keep exploring the horizon. 🌅

Alex Lielacher

P.S. If you want your brand to show up in Google AI Mode, ChatGPT, and Perplexity, reach out to my agency, Rise Up Media. That's what we do.

Keep Reading