Build a guided Demo with your AI assistant (Walnut MCP)

Ask your AI assistant for a Demo in plain words, and it builds a guided Demo with you in the chat. It uses the screens in your Screens Library and shapes the Demo around how you'll use it and who it's for. You check the outline and a visual plan before anything is built. You end up with a new Template and a published Demo link to share.

This works in any assistant connected to the Walnut MCP: Claude, ChatGPT, Codex, or Microsoft Copilot Studio.

Before you start

• Connect the Walnut MCP with Full access. Building creates a Template and publishes a Demo, so Read-only access isn't enough. See Connect Walnut to Claude, ChatGPT, Codex, or Copilot.
• Fill your Screens Library and label it. New Demos are built only from Screens Library screens, and each screen needs a Product and a Feature label so your assistant can find it. See Fill the library and label it.
• Optional: connect your CRM, call recorder, or calendar to the same assistant (for example Salesforce, HubSpot, Gong, or Google Calendar). Your assistant then looks up the prospect and suggests answers for you.

Build a guided Demo

1. Ask for a Demo

Say what you need, as specifically as you like:

Build a Demo for Acme's VP of Sales to watch after yesterday's call.

I need a website embed Demo that shows marketing leaders how our campaign builder works.

If you name a prospect and a CRM, call recorder, or calendar is connected, your assistant looks them up first. It tells you in a few lines what it found, such as when you last met and their main pain. It never pastes transcripts, deal amounts, or contact details into the chat.

2. Answer two questions

Your assistant asks two multiple-choice questions, one at a time, and skips any your request already answered:

1. How will the Demo be used? Pre/post-call or leave-behind, Live call demo, New feature announcement, or Website embed. You can also describe another use.
2. Who is it for? Pick one of the suggested roles, or describe the audience in your own words.

When your assistant has something to go on, it marks a suggested answer and says why, for example "Live call demo: you meet them on Thursday."

:::info Guided or live Every use except Live call demo gets a guided Demo: a walkthrough of guide steps that viewers move through with Next and Back. A Live call demo gets no guides, because nothing should pop up while you present. You click through its linked screens yourself. :::

3. Reuse what you have, or build new

Before building anything, your assistant checks your library for up to three existing Demos and Templates that already fit. For each one, you can:

• Share as is: get the existing Demo's link.
• New link from its Template: publish a fresh Demo from that Template, personalized for this prospect.
• Build new: carry on and build a new Demo.

4. Approve the outline

To build new, your assistant drafts a short outline from the screens in your Screens Library, with one step per feature and up to 20 steps. Approve it, or ask for changes such as "Drop the admin settings step and add reporting." Each change produces a new outline to approve.

If your library has no screen for a step, your assistant leaves that step out and tells you. It never fills the gap with a placeholder or with screens from another Template.

5. Review the plan

Once you approve the outline, Walnut prepares a Demo plan and your assistant gives you its link. The page fills in as the plan is made, and shows the Demo the way a viewer will experience it:

• Guided view: every guide step in order, as cards you read from left to right. It ends with the button the last step shows, such as Book a meeting.
• Non-guided view: a map of where viewers can go, from the start screen through each link, plus the screens in the navigation bar. Click a screen for a larger preview, the screens it leads to, and a link to open it in Walnut.

A plan for a live call demo shows only the Non-guided view. Only signed-in members of your company can open the plan page.

The page has no buttons. Ask for changes in the chat, using the screen numbers from the plan:

• Reword a guide step, change where a link goes, or remove a link. These changes apply right away.
• Add, remove, or swap a screen. Walnut re-plans that section in the background. Your assistant gives you the page link again, and you can check back when it's ready.

You can change a plan as many times as you like. A plan stays open for 24 hours. After that, ask your assistant to plan again.

6. Build it

Tell your assistant the plan looks good. Walnut builds the Template from exactly the plan you approved, then publishes a Demo from it. Your assistant follows the build and tells you when it's done, without you having to ask.

You get:

• The Template link, to open and edit it in Walnut
• The Demo share link, ready to send
• Anything worth checking before you share, such as a link that didn't save. For a live call demo, it also lists any screen with no way forward, since you need to click through every screen while presenting.

What a guided Demo includes

• Guides. If the library screens you build from already have guides, those guides come along. Otherwise, Walnut writes a new walkthrough:
  • A welcome step on the first screen, which names the prospect's company when you gave one
  • One step for each step of the outline
  • A closing step on the last screen, with a call-to-action button (or Done)
• Tooltips and modals. A step about a specific element on the screen points at it as a tooltip. Other steps, including the welcome and closing steps, are modals. The background is dimmed behind each step.
• Sections that follow the steps of your outline.
• Linked screens. Screens are linked so viewers can also click through, and a navigation bar is shared across screens when the plan includes one.

Personalize and share it

After the build, you can keep going in the same chat:

• Publish another link for a different prospect. Your assistant asks for each variable on the Template, such as the company name, or a link like a meeting-booking URL. You can keep the default for any of them.
• Add a variable if the Template has none where you need one. Name the text to replace, for example "Demo Inc".
• Change the Demo's settings, such as who can open it or when it expires.
• Translate the Template into another language, then republish the Demo.

See What you can do with the Walnut MCP for details.

If your Screens Library can't cover the Demo

• The library is empty. Your assistant walks you through filling it: go to Resource Hub → Screens, then use Promote from template to reuse screens from a Template you already have, or Capture screens with the Chrome extension. Then label each screen with a Product and a Feature.
• Screens are still processing. Newly added screens take a moment before they can be used. Your assistant tells you how many are still processing, so you can try again shortly.
• Nothing in the library fits this Demo. Your assistant explains how to add the screens you need. If an existing Template fits, it also offers to publish a new link from it instead.
• Some content is "not available". Screens that exist but can't be built from yet are reported as not available, and your assistant offers the closest screens it can use.

More prompts to try

Build a guided Demo of our analytics dashboard for a CFO, to send after the call.

I'm presenting to Globex on Thursday. Build a live call demo for their Head of IT.

Build a new feature announcement Demo for the new approval workflow, for existing customers.

In the plan, reword step 3 so it talks about saving time, and remove the link from screen 5.

For more ideas, see the MCP prompt library.