# Welcome to Storylane

* [What's Storylane?](#whats-storylane)
* [Our product lines](#our-product-lines)
* [Who's Storylane for?](#whos-storylane-for)

### 👉 What's Storylane?

Storylane is the [#1 rated demo automation software](https://www.g2.com/categories/demo-automation?tab=highest_rated) for GTM teams to build and share interactive demo experiences. We work with 5000+ B2B companies to simplify buying and selling for marketers, sales folk, and prospects.

### 👉 Our product lines

Storylane supports four product lines, each designed to improve the buying experience:

1. **Guided Demos:** step-by-step product walkthroughs, complete with hotspots, tooltips, presenter videos and voiceovers — perfect for self-guided demo experiences.
2. **Buyer Hub:** deal rooms to host demos, videos, PDFs, forms, all in one place — perfect to enable stakeholders and push middle of the funnel deals across the line.
3. **Sandbox Demos:** hands-on HTML/CSS demo environments — complete with responsive buttons, animations, and scrolls — perfect for light-weight product simulations.
4. **RepX:** conversational sales agents trained on your demos, sales calls, and knowledge base to engage with website visitors and qualify them.

### 👉 Who's Storylane for?

We work marketing, sales, customer success, and product management teams from SME, mid-market, and enterprise software companies. Here are a few of our most common use cases:

<details>

<summary>Storylane for Marketing</summary>

* **Website demos:** embed guided demos on your website to drive product education and qualified conversions
* **Lily AI (Sales agent):** generate qualified leads for Sales by training Lily to automate early-stage product discovery for website visitors
* **Email campaigns:** attach demo links as part of your outreach efforts, newsletters, feature releases, etc.
* **Blogs and LPs:** embed demos to SEO and sponsored pages to drive on-page engagement and conversions
* **Events and conferences:** display demos at booths and devices (iPads, etc) to draw in foot traffic and leads
* **Marketplaces:** embed demos to your G2 product profile and other marketplaces to support prospect research

</details>

<details>

<summary>Storylane for Sales</summary>

* **Pre-call demos**: share guided demos and Buyer Hubs prior to live demo calls to provide basic product context, encourage advanced conversations, and accelerate sales cycles
* **Live demo calls:** avoid the risks associated with unpredictable production environments. Instead, present reliable, pre-curated sandbox demo environments during live calls
* **Leave behinds**: share personalized demos and Buyer Hubs after sales conversations to enable champions and the larger buying committee&#x20;

</details>

<details>

<summary>Storylane for Customer Success</summary>

* **Onboarding**: help customers onboard faster with instructional demos and demo playlists
* **Knowledge bases**: embed Storylane demos across your documentation for immersive product walkthroughs (Like we've done in the next few pages)

</details>

<details>

<summary>Storylane for Product Teams</summary>

* **Product change logs**: share quick interactive demos of your latest product/feature releases to drive awareness and adoption
* **Customer feedback**: Embed Storylane across Notion, Zendesk, Readme, Gitbook, Jira / Confluence, Webflow, etc to gather user feedback

</details>

{% hint style="info" %}
If you need help or have any questions, feel free to contact us at <support@storylane.io>.
{% endhint %}


---

# 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/welcome-to-storylane.md?ask=<question>
```

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.