How to run an async sales demo that moves deals

An async sales demo lets a buyer see your product on their own time, without booking a call first. It moves deals when it answers the questions a buyer has before the call and stays accurate after the product changes. It stalls when it is a one-way recording that nobody maintains and nobody can ask anything of.

Picture a founder who sends a clean async demo in cold emails and embeds it on the landing page. Then the pricing changes: three tiers become two, and the call to action gets new copy. The demo still shows the old pricing modal to every prospect who clicks through. One of them replies asking why the demo does not match the site. That is a hypothetical, but it is the kind of failure a static demo invites. You hear from the one buyer who says something, and the rest leave quietly.

We make an AI demo agent, so weigh the later sections accordingly. The early ones apply to any async demo.

What does an async sales demo have to do besides play back a recording?

It has to help a buyer research your product alone and move closer to a decision without a rep on the line. That means answering the obvious pre-call questions: what does this do, is it for me, and what happens next. A demo that only plays back screens shows the product but does not guide the buyer. The ones that work have a clear path, a visible outcome and a call to action that says what to do next.

The same asset can do three jobs if you build it for them:

• Cold outreach. Linked in the first email, it replaces "want to see a demo?" with something the prospect can act on right away.
• Landing page. Placed in the hero, it gives visitors a reason to stay past the headline.
• Post-call follow-up. Sent after discovery, it reinforces what you discussed and gives the buyer something to forward internally.

That reuse only works while the demo is accurate. One stale version breaks all three channels at once.

What should an async sales demo show?

One task the buyer needs to verify before they move forward, not everything the product does. For a B2B SaaS that is usually one of three questions: does this solve my specific problem, can I see myself using it, or is this worth a real conversation.

Build the path around that task: five to seven screens and one clear outcome. If a screen does not help the buyer answer their question, cut it. The first draft usually has too many screens and at least one section that exists because someone thought it was impressive, not because it was useful.

Also cut generic narration. "Welcome to our platform, let's get started" is drag. Name the buyer's problem in the first five seconds instead. How you build the thing depends on the format. Build a product demo covers screens, narration and sample data, and interactive demo covers the kinds of clickable demo and when each fits.

How do you keep an async sales demo current when the product changes?

Give it one owner and a short check that runs before every outbound batch. A demo built from captured screens or a recording shows the product as it was the day you captured it, so every pricing change, renamed feature or new button makes it a little more wrong, and nobody is told.

1. Spot the change. When a release ships, someone lists which screens or copy it touches.
2. Update the asset. Edit or recapture only the affected steps.
3. Verify the published version. Click through the live link and compare pricing, plan names and the call to action with the live site.
4. Then send. Run the next outbound batch only after the check.

That is four steps, not forty, but only if the demo is small. Take the pricing change from the opening. If the pricing modal shows up on three screens in a screenshot-based demo, fixing it means recapturing three screens and republishing, and re-recording narration if there is any. Keep the demo short and the number of things that can go stale low, and the check stays a ten-minute job.

How do you personalize an async demo without rebuilding it for every buyer?

Keep one core path and vary three things by role: the opening line, the proof-point screen and the call to action. A founder cares about strategic fit and return. An engineer cares about how it fits the stack and what it costs to maintain. RevOps cares about pipeline visibility and handoff.

• The opening line. Name the buyer's role or pain directly.
• The proof-point screen. Show the feature most relevant to that role.
• The call to action. Match what that buyer's next step actually is, whether that is booking a call, starting a trial or reading the docs.

Personalization earns its keep when the path through the product differs by role. It is busywork when the demo is the same and you are swapping a name in the header. In that case a personalized subject line does more than a personalized demo.

There is a cost. Every variant is another asset to keep current, which brings back the maintenance problem above. A fixed asset forces a trade between effort per buyer and relevance per buyer. Scale outbound demos goes into where that trade breaks down.

Which signals tell you the demo is moving deals forward?

Watch depth, repeat views, call-to-action clicks and reply rate. Views alone are noise, because a high view count with no replies means the demo gets watched and does not do its job.

• Watch depth. Did they finish, or drop off at screen three?
• Repeat views. A second view from the same account often means someone is sharing it internally.
• Call-to-action clicks. Did the demo produce an action, or just a view?
• Reply rate after send. The downstream signal that ties demo engagement to your sales motion.

Set up a simple alert, for example when a prospect watches past a threshold you choose or clicks the call to action, so a founder or rep follows up within the hour. The view is the buying signal and the follow-up is what converts it. If views are high and pipeline is flat, go back to the buyer task and ask whether the path is clear and the call to action says what to do next.

What can an async demo not do, and where does an AI demo agent fit?

A recording or click-through cannot hear the buyer. The pre-call questions it is supposed to answer are exactly the ones it cannot respond to when a buyer asks something the author did not plan for. A buyer who gets stuck on "how does this handle our setup?" has nobody to ask, and the thread goes quiet.

An AI demo agent keeps the part of async that works, which is that the buyer shows up on their own time, and adds a conversation. Inkly runs three stages with each visitor:

• Qualify. It asks the visitor's role, goal and use case before it shows anything.
• Guide. It drives the product on screen through the workflows that match their answers, and answers questions in context.
• Convert. It reads buying intent, offers the meeting at the right moment, and hands sales the visitor's questions, interests and engagement.

That last stage replaces the guesswork in the signals section above. Instead of inferring from watch depth what a buyer cared about, sales sees what they asked and explored. How it works goes through each stage, buyer intelligence shows what sales receives, and agentic demo defines the category.

It does not replace everything. A two-minute clip is still the better leave-behind for a colleague who only wants a quick look, and a complex deal with several stakeholders still needs a person on the call.

What does it cost, and when is it not worth it?

Every plan includes the voice and chat demo agent, and plans are priced by active visitors, where one person counts once a month. Free is $0 for 30 active visitors. Pro starts at $150 a month ($120 a month billed yearly) for 150 active visitors, and adds visitor details, tailoring and qualification. Enterprise is custom and adds a clickable clone of your product, live product streaming and the CLI. Current numbers are on the pricing page.

Skip the agent if few people reach the demo today, since the problem is then traffic or your message. Skip it if nobody has written down how the product works, because the agent starts from your product materials and key workflows, and a guided validation checks the experience before it goes live. And skip it if a founder can still reply to every inquiry within the hour.

FAQ

How do I create an async sales demo prospects can watch on their own time?

Build around one buyer task, keep it to five to seven screens and end on a clear call to action. Host it as a standalone link or embed it on your landing page. Skip the login if you can, so the buyer reaches the first screen right away.

How do I keep the demo accurate when pricing or features change?

Give it one owner, list which screens each release touches, update only those, and click through the published link before the next outbound batch. Keeping the demo short keeps that check short.

What should an async demo include so it supports conversion and not just awareness?

A clear buyer task at the start, a path that answers the obvious pre-call questions, a proof point specific to the buyer's role, and a call to action that says what to do next. Anything that serves none of those four is a feature tour.

Which metrics matter most for an async demo?

Watch depth, repeat views from the same account, call-to-action clicks and replies after send. A raw view count tells you little by itself.

Is an AI demo agent an async demo?

In one sense, yes: the buyer comes on their own time and nobody on your team has to be there. The difference is that the agent talks with the visitor, drives the product to match what they said, and tells sales what happened.

Conclusion

Pick one buyer path, publish it, and write the check you will run before every send. That check is what keeps a good demo from going stale. After a few weeks, read your replies and ask how many buyers wanted to ask something and had nobody to ask. If it is most of them, add a conversation. If it is few, the demo you have is probably enough.

For reps who spend first calls on basics, see how sales teams use Inkly.