Skip to main content

Your Working Session: The Live Demo

This is the moment a client goes from "we should look into AI search" to "let's do this." Prepare it like a demo, not an improvised tour.

Step 1: Name the Current Pain Point​

Before showing anything, restate what you heard in discovery: "you told us your search box returns a list of links and most visitors give up — here's what that same question looks like with an AI answer instead." This framing matters more than the demo itself; it's what makes the demo land as a solution rather than a feature tour.

Show the deployment surface that matches the likely tier from discovery — live, using the fallback demo pattern if the client's own content isn't ingested yet. Ask a real question a visitor would actually ask, not a softball.

What to point out live: the answer is generated from real, ingested content — not a canned script. If the client's own content is loaded, use one of their real pages as the source and show it.

Step 3: Show One Action, If the Tier Supports It​

For a likely Walk or Run engagement, this is the step that separates ai12z from "just another chatbot." Ask a question that requires doing something — checking availability, finding a location, filling a form — and let ReAct call the integration live. Narrate the distinction explicitly: "that wasn't a scripted response — the assistant decided a tool call was needed, made it, and used the real result."

Step 4: Get the Room's Reaction​

Ask directly: "does this match what you pictured? What would your customers actually ask that we haven't tried yet?" Let the client type a question themselves if they're willing — nothing lands harder than watching the assistant handle a question the room made up on the spot.

Step 5: Build the Recommendation Together​

Move into the deliverable template live, informed by what just happened in Steps 1–4, not just the discovery answers from before the demo. A client's reaction to the live demo often changes the right tier recommendation — a client who came in thinking "just a search upgrade" sometimes leaves wanting the integration-driven version once they've seen it work.

Last updated on