Chapters

The Power of Chapters

Chapters are one of the most underused tools in Supademo, and also one of the most powerful.

They're not required, but they are strongly recommended because they give structure to a demo. Chapters help viewers understand where they are, what their options are, and what they can do next. They add clarity without adding complexity.

Chapters often act like bookends. At the beginning of a demo, they help set expectations and invite engagement. At the end, they create a clear next step. Visually, chapters are usually styled through workspace themes, which helps teams stay consistent while still allowing flexibility within individual demos.

Chapters can be added anywhere in a demo, and they can be duplicated, deleted, or rearranged just like steps. This makes them especially useful for branching, segmentation, gating, and calls to action, without relying on complex hotspot logic.

In practice, chapters give viewers a cleaner mental model of the demo, and they give teams cleaner analytics than relying on hotspots alone.

Four Core Chapter Types

There are four core chapter types, and each one serves a different purpose.

Default Chapters

Default chapters are the most commonly used and the most flexible. They work well as intro slides, decision points, or transitions. Default chapters support up to four buttons, and each button can route a viewer to a specific step in the demo, another demo, or an external URL.

A common use case is feature branching, such as Add, Edit, or Delete workflows for a single feature. Another is persona-based branching, like end user versus admin or executive views.

In sales demos, default chapters are often used to let viewers self-select what matters to them. One button might lead to a product overview, another to a feature deep dive, and another to pricing. Every choice a viewer makes is trackable, which helps teams understand interest, intent, and priorities.

Form Chapters

Form chapters are often associated with lead capture, but at their core, they are about access control.

They allow teams to collect information using customizable fields and can sync directly with tools like Salesforce or HubSpot. Forms can be configured with options like skip buttons, business-email-only requirements, domain allowlists or blocklists, notification routing, and automatic CRM sync.

Common use cases include lead capture on marketing pages, controlled sharing in sales workflows, and domain-gated access, such as limiting a demo to users from a specific company. Forms are also used in onboarding to confirm readiness, gather feedback, or validate progress before moving forward.

Forms are not just for lead generation. They are powerful control points and should always be designed to collect only what's necessary.

Embed Chapters

Embed chapters allow viewers to take action without leaving the demo.

They let teams embed third-party tools directly into the demo experience, avoiding context switching. Common examples include Calendly or Cal for booking meetings, HubSpot forms, Typeform, Google Forms, and other supported tools.

Embed chapters work best when momentum is high. When a viewer finishes a demo and is ready to take the next step, embedding that action directly into the demo makes it easy to follow through. This is why embed chapters are often one of the most effective ways to turn demos into conversion points.

Password Chapters

Password chapters add an extra layer of protection on top of URL-based sharing.

They require viewers to enter a password before continuing and are used for sensitive content. Common scenarios include customer-specific workflows recorded in live environments, pricing demos, healthcare or finance use cases, and internal-only content.

Even if a demo link is shared more widely than intended, password protection keeps the content secure.

Dynamic Variables

Chapters become even more powerful when paired with dynamic variables.

Dynamic variables allow placeholders for things like names, company names, logos, and other customer-specific details. This increases personalization without requiring separate demos for each audience.

When used alongside chapters, dynamic variables make it possible to keep a single demo structure while still delivering a personalized experience. The flow stays the same, but key details adapt based on who is viewing the demo.

Dynamic variables aren't limited to chapters. They can also be used in hotspot text, and in HTML demos, they can be inserted directly into any text element. This makes it easy to personalize guidance and context throughout the demo without duplicating steps.

Common use cases include adding a viewer's name, company, industry, or location so the demo feels relevant. Variables can be filled in manually for one-to-one sharing, or populated automatically through CRM integrations for one-to-many campaigns.

This is especially valuable for sales and marketing teams. The same chapter-based demo can be reused across dozens or hundreds of prospects while still feeling tailored to each viewer.

Maintainability

The main benefit here is maintainability. Instead of duplicating demos to personalize them, teams keep a small set of standardized demos and personalize them dynamically. Updates are easier, structure stays consistent, and personalization doesn't create long-term overhead.

Default End-of-Demo CTAs

One final note on chapters. By default, Supademo adds a closing CTA chapter at the end of demos. These are usually configured at the workspace theme level and often include actions like booking a meeting, contacting sales, upgrading, or continuing onboarding. Teams can standardize these CTAs or adjust them for specific use cases.

Decision Design

Chapters are ultimately about decision design.

They should be used intentionally, not decoratively. If a chapter doesn't help a viewer decide what to do next, it probably doesn't need to be there. In many cases, chapters are a better choice than hotspots for branching because they reduce cognitive load, clearly communicate options, and make analytics easier to interpret.

But chapters aren't the only way to guide viewers through a demo. Once a viewer has chosen a path, the moment-to-moment guidance still matters. That's where hotspots come in. In the next lesson, we'll look at how hotspots work, how they differ from chapters, and how to use them together to create demos that feel clear, intentional, and easy to follow from start to finish.