### The Goal
To curate a collection of demos that delve into specific use cases. These focused showcases educate prospects, turning them into product ambassadors eager to share the gallery.
## Implementation Guide
### 1. Setting the Foundation
* **At Least Three Demos**: A gallery should showcase variety. Start with at least three interactive demos to offer breadth to your visitors.
* **Diverse Use Cases**: Each demo should address a different pain point or showcase a distinct capability of your product.
* **Consistent Design Language**: Ensure a uniform look and feel across all demos to maintain brand consistency. Use similar colors, typography, and layout patterns.
### **2. Organizing the Gallery**
* **Categorization**: Group demos based on functionalities, industries, or challenges addressed. This makes it easier for visitors to find relevant content.
* **Inline Embed with CTA**: Leverage Storylane [embedding features](https://docs.storylane.io/storylane-knowledge-base/sharing-demos/embedding), and give a hint of the demo's content with a clear CTA on top.
### 2. Demo Structure
* **Identify Key Use Cases for Each Demo**: Prioritize the use cases you want to spotlight, based on the main problems of your target audience.
* **Steps 1-2:**
* Begin with a compelling headline that immediately communicates the value of the use case. Use phrases that resonate with the pain points or desires of your target audience.
* Then, clearly articulate a common challenge faced by users. This sets the stage for the solution you offer, emphasizing its relevance and value.
* **Steps 3-9:**
* Introduce your product as the answer to the previously stated problem. Highlight its unique selling points.
* Use Storylane's tooltips and hotspots with a backdrop to showcase the feature in action. This walkthrough should demonstrate the ease of use and effectiveness.
* Present scenarios where the feature has been applied, emphasizing tangible benefits.
* Showcase how this feature integrates or complements other tools, enhancing its value proposition.
* Show social proof to validate the feature's value. This adds credibility.
* **Steps 10-12:**
* Summarize the value delivered in this use case, reiterating its key benefits.
* End with a strong CTA that encourages sharing or trying out the solution. Use phrases like "Share with your peers!" or "Try Yourself".
{% hint style="info" %}
Leveraging Storylane, you can seamlessly integrate captures from various platforms, including different software, social media, and even incorporate videos. This eliminates the need to switch between multiple apps.
{% endhint %}
### 3. Gating Demos
* If your goal is to get more eyeballs on your product, we suggest keeping the demos in the demo gallery ungated. Reasons include:
* **Accessibility:** Allows for seamless exploration without barriers.
* **Shareability:** Encourages prospects to share the demos, increasing reach.
* **Trust Building:** Demonstrates transparency and confidence.
* If your goal is to collect and nurture warm leads, gating the demos might be your way forward. Keep in mind that gated content has significantly lower impression rates.
### 4. CTA Placement
CTAs are pivotal elements in your demo, as they guide the viewer on what to do next.
* Be short and contextual: use 2,3 words for your CTA relevant to the previous content.
* Make sure it stands out. This is usually done through contrasting colors.
{% hint style="info" %}
Pro tip: With Storylane, you can add a [secondary CTA](https://docs.storylane.io/storylane-knowledge-base/editing-demos/guides-and-flows/customizing-steps#config). People love choice. Not all viewers will be ready to take the primary desired action. A secondary CTA provides an alternative, ensuring you still guide their journey.
{% endhint %}
## Customer Examples
* [**SentinelOne Demo Gallery**](https://www.sentinelone.com/lp/tour/)
* [**Unravel Guided Tours**](https://www.unraveldata.com/self-guided-product-tour/)
---
# Agent Instructions: 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:
```
GET https://docs.storylane.io/storylane-playbooks/awareness-stage/demo-gallery.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.