Learn

Turn product demos into step by step guides

Generate a written step by step guide from any recording. Edit it like a document, publish it at its own URL, and give the people who would rather read the same walkthrough your demo shows.

Guide steps

1

Open the workspace

2

Connect your data

3

Invite your team

4

Set permissions

5

Publish the workflow

Set up your first workspace

Published

Generated from a five step recording. Each heading links back to that point in the demo.

1. Open the workspace

Go to app.nvariant.ai and select the workspace you want to configure.

2. Connect your data

Choose Connect data, pick a source, and confirm the fields you want to sync.

One recording produces a clickable demo and a written guide at the same time.

What is an AI generated product guide?

A product guide is written, step by step documentation for a workflow: a title, a short introduction, and a numbered instruction for each action with a screenshot. nVariant generates one from any recorded demo, using the steps you already captured, so documentation stops being a separate writing project.

Guides open in a rich text editor for review, then publish to a public URL. Because a guide is text on a web page, it can be searched, skimmed, copied, translated in the browser, and read by AI assistants, which an interactive demo on its own does not allow.

Guides at a glance

Source

Any recorded nVariant demo

Structure

Title, introduction, numbered steps with screens

Editing

Rich text with headings, lists, links, and code blocks

Publishing

Public URL that needs no login to read

Updates

Regenerate from an updated recording

Documentation that writes itself from the recording

A guide is generated from the steps you captured, then stays fully editable.

Written from your steps

Headings and instructions follow the flow you recorded, so the guide matches the product instead of a blank template.

Written from your steps

Headings and instructions follow the flow you recorded, so the guide matches the product instead of a blank template.

Rich text editing

Headings, bold, lists, quotes, code blocks, and links. Rewrite any block by hand before you publish it.

Rich text editing

Headings, bold, lists, quotes, code blocks, and links. Rewrite any block by hand before you publish it.

Screens kept per step

Each step keeps the screen it came from, so a reader sees the same interface the demo walks through.

Screens kept per step

Each step keeps the screen it came from, so a reader sees the same interface the demo walks through.

Its own shareable URL

Every published guide gets a public link for a help centre, a ticket reply, or an onboarding email.

Its own shareable URL

Every published guide gets a public link for a help centre, a ticket reply, or an onboarding email.

Regenerate after changes

When the product moves on, regenerate from the updated recording instead of rewriting the page by hand.

Regenerate after changes

When the product moves on, regenerate from the updated recording instead of rewriting the page by hand.

Visible generation status

Generation reports its state as it runs: pending, generating, completed, or failed, with no silent failures.

Visible generation status

Generation reports its state as it runs: pending, generating, completed, or failed, with no silent failures.

Readers get the same answer as clickers

Some people want to click through a product. Others want to scan a page and copy a step. A guide covers the second group without writing documentation twice, because both come from one recording.

A heading and an instruction for every step

The captured screen shown next to the text

A public URL that works without a login

Create and share a guide

Published

Generated from an 8 step recording. Every heading links back to the matching step in the demo.

1

Open the application

Start at app.nvariant.ai/demo/onboarding

2

Invite your team

Click Invite and add the people who run this workflow.

3

Publish the walkthrough

Press Publish, then copy the share link.

Regenerate

Edit any block by hand before publishing.

From recording to published guide

1. Record the flow

Click through the workflow once with the Chrome extension running. Each click becomes a step with the screen it happened on.

2. Convert it to a guide

Choose convert to guide. Every step becomes a heading and a short instruction, ready to edit in the rich text editor.

3. Publish and link it

Publish to a public URL, then link it from your help centre, an onboarding email, or a support reply.

Where teams put their guides

The same generated page fits six different jobs, and every one of them saves someone writing a document from scratch.

Help centre articles

Publish the guide next to the demo so a search for how do I set this up lands on a page that answers it, with the screens included.

Customer onboarding

Send new customers a reading path for week one. They follow the steps at their own pace, and you see which steps stall in analytics.

Internal runbooks

Record a workflow once and keep it as the written procedure for the team, instead of a document that nobody updates.

Support replies

Answer a ticket with a link to the exact step rather than a paragraph of instructions typed from memory.

Release notes

Ship a new flow with a guide that shows the new screens, so the announcement carries proof rather than a claim.

Search and AI answers

A guide is crawlable text. Search engines and AI assistants can read and quote it, which an interactive demo alone cannot offer.

Getting a generated guide ready to publish

Five minutes of review turns a draft into documentation people can find and follow.

1

Title it the way customers search

Use the words a customer would type, such as how to invite your team, rather than an internal feature name.

2

Trim the introduction

Keep the opening to two sentences that say what the reader will have done by the end.

3

Name the exact button

Readers scan for the label on screen. Put the exact button or menu name in bold in each step.

4

Link the guide and demo both ways

Add the guide link under the embedded demo, and link to the demo from the guide for people who want to click through.

Guide questions, answered

What a guide contains, how it is generated, and how much of it you control.

What is an nVariant guide?

What is an nVariant guide?

How is a guide different from the demo?

How is a guide different from the demo?

Can I edit the generated text?

Can I edit the generated text?

Where do teams publish guides?

Where do teams publish guides?

What happens when the product changes?

What happens when the product changes?

Do readers need an nVariant account?

Do readers need an nVariant account?

Can a guide be downloaded?

Can a guide be downloaded?

Are guides good for SEO?

Are guides good for SEO?

Start turning demos into real adoption

Create interactive demos in minutes and see how users actually engage.

Start turning demos into real adoption

Create interactive demos in minutes and see how users actually engage.

Start turning demos into real adoption

Create interactive demos in minutes and see how users actually engage.