> For the complete documentation index, see [llms.txt](https://docs.storylane.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storylane.io/storylane-playbooks/decision-stage/live-demos.md).
# Live Demos
Engage prospects effectively during sales calls by creating personalized and insightful demos. Showcase your product in a compelling manner, tailored to each prospect's needs.
### The Goal
Create a captivating demo experience during sales calls that resonates with the prospects' needs and interests, showcasing the value and capabilities of your product, all while making it interactive.
## Implementation Guide
### **1. Quick Customization**:
* Use the [Demo Editor](https://docs.storylane.io/storylane-knowledge-base/demo-editor/editing-html-screens) to change text, images, copyright, and even add custom HTML to tailor the demo to each prospect.
* Show demos of varying data sets to cater to diverse stakeholders, ensuring every viewer finds value.
* Employ [Storylane Token variables](https://docs.storylane.io/storylane-knowledge-base/demo-editor/personalization) for a personalized demo experience. We suggest adjusting the date/time in your demo to keep the content fresh, and to share a unique link for each prospect without having to replicate demos, ensuring a personalized experience.
### **2. Multiple Personas - Multiple Flows:**
* If selling to multiple personas, create [specific flows](https://docs.storylane.io/storylane-knowledge-base/demo-editor/guides-and-flows/flows-and-product-tour) for different personas, allowing prospects to pick their own personalized adventure based on their needs.
* If not, utilize Flows & Product Tours to showcase different features of your product in a single demo, making it easier for prospects to grasp the value proposition.
### **3. Navigation and Linking:**
* Design intuitive navigation within the demo: have no more than 10 steps in each flow.
* Use the prospects' language when describing content. Avoid buzz or technical terms.
* Seamlessly navigate between screens using [linking and auto-linking features](https://docs.storylane.io/storylane-knowledge-base/demo-editor/live-clickable-demo#how-to-build-live-demos). Once you have recorded various screens needed for your demo, then you can build links between captured screens to simulate a live demo experience.
{% hint style="info" %}
Practice makes perfect. Know the demo inside out for a smooth presentation and check that all links work and interactive elements function correctly.
{% endhint %}
## Customer Examples
We have plenty of customers using Storylane in the consideration and decision stages, for pre-sales, email campaigns, live sales, and sales-leave behinds... However, due to privacy concerns, we are unable to share specific demos here.
Feel free to explore some of the success stories on our [customer page](https://www.storylane.io/customer-stories), or [contact us](mailto:support@storylane.io) if you want to learn more about a specific customer use case.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.storylane.io/storylane-playbooks/decision-stage/live-demos.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
