# December 27th, 2025

As the year winds down, inboxes quiet a bit, and everyone starts thinking about what to double down on next - we shipped a couple of updates focused on **clarity and confidence**.

Less guessing. More signal. Both updates below are about helping your demos work better *without* adding more work for you.

Here’s what’s new 👇

### A/B Testing

{% hint style="info" %}
Available from the Growth plan.
{% endhint %}

Stop guessing what converts. Start proving it.

You can now **A/B test your demos** in Storylane and see which version actually performs better - using real buyer behavior.

{% @storylane/embed subdomain="app" linkValue="xos6sibfdhof" url="<https://app.storylane.io/share/xos6sibfdhof>" %}

#### What you can test

* Lead form vs no lead form (Gated vs ungated experience)
* Short vs long demo
* CTA early vs CTA at the end
* Use-case intro vs feature-first walkthrough

#### How it works

1. Create an A/B test and select Variant B (Variant A is auto-selected)
   1. (Recommended) duplicate your original demo, make changes, and use it as variant B.
2. Determine the traffic split. It will automatically split using your existing demo link
3. Track performance and conversions in one place
4. Roll out the winning version with confidence

These experiments help answer the big question every GTM team asks:

**Are we delivering a&#x20;*****buyer-first*****&#x20;experience for each key persona?**

No opinions. No endless debates.

***

### Storylane Windows app improvement

We’ve improved the **Storylane Windows app** with two upgrades:

* Capture in full-screen mode
* Record video

***

Thanks for trusting us.\
If you have any questions, feel free to reach out at <support@storylane.io>.<br>


---

# 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/changelog/december-2025/december-27th-2025.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.