"Can you send me a recording?" is the most demoralizing sentence in B2B SaaS. You spent an hour building a beautiful, perfectly tailored demo. The prospect saw it once. Now they want a YouTube link to remember it by.
The recording is going to lose. The prospect will skim it at 2× speed at the airport, miss the parts that matter, and forward it to a stakeholder who has no context. By the time you're back on a call with them, the demo memory has decayed and the question now is "how does that thing you showed me actually work?"
The viewer-session feature exists because we wanted a better answer to that question.
What a viewer session is
A viewer session is a secure cloud browser, running your real product, logged into your real demo account, with your MyAISE ruleset applied in real time. You send the prospect a link. They open it in their browser. They get full interactive access — clicking, navigating, typing — to the customized product.
Behind the scenes, each viewer session runs in a private GPU task with a sandboxed Chromium browser. The proxy engine applies your ruleset inside that task. The prospect interacts with the browser through a WebRTC stream; the task and its temporary state are destroyed after use.
Why "real product" matters
It's tempting to think of viewer sessions as "a really good screen recording." They're not. The difference is that the prospect can do things.
When a prospect clicks a button you didn't plan for, the app responds the way it always responds. When they ask "can it filter by region?" they don't have to wait for you to set up another demo — they can try it right now. When they share the link with three colleagues, those colleagues get the same interactive experience you would have given them on a call.
This changes the second-meeting dynamic completely. Instead of "remind me what we saw last time", the question becomes "I noticed X when I was poking around — can you walk me through the implications?"
"Send a viewer link instead of a recap doc, and the next call starts with the prospect's feature questions — not yours."
— The second-meeting shift this is designed for
How secure is "secure"
Three layers:
- Credentials are encrypted for the assigned task. Submitted credentials are retrieved once by that task and then erased. The prospect interacts through the browser stream.
- URL blocking is enforced at the proxy. Define regex patterns for admin panels, billing pages, internal APIs — MyAISE returns a friendly "this area is hidden during the demo" page. Team owners can lock these rules so nobody on the team can accidentally disable them.
- Sessions are scoped and revocable. Each link has a short-lived token and a configurable session length. Revoke from your dashboard and the prospect's tab becomes a "session ended" splash immediately.
Editing while the prospect is exploring
You can edit the ruleset in Studio while the prospect is mid-session. Rules update over WebSocket. The next page they load reflects your edit.
This is small but turns out to matter a lot. The prospect on the airport call asks "what if the numbers were 2x bigger?" — you edit one rule, ask them to reload, and the answer is there. No second call, no follow-up deck.
Viewer sessions are available on Solo (1 concurrent) and AI SE (3 concurrent per license, shared across the team). The cloud-browser machinery is built on Selkies and runs in private GPU tasks. Session metadata, optional recordings, and enabled analytics are stored as described in our privacy policy.
Ready to try MyAISE?
Free for individuals. Mac app. 5-minute install. No account needed.