AI Demo AgentsSaas Free template
AI Demo Agent for SaaS
by SUPERFLY
An AI agent that runs your product demos as live video meetings, shares your screen, and tailors every section to what the buyer actually cares about. Real discovery first, a focused walkthrough mapped to their stack, pricing that lands in context, then the close or a booked follow-up their champion can take to the team.
- 18-step call flow
- 5 objection handlers
- Full call script
- System prompt included
- 6 pre-call questions
Call flow · visual builder
Call Start
First message
[friendly] hey {{name}}, good to meet you. can you hear me okay before we get into it?
Warm-up
- 1. Say: “[friendly] good to meet you {{name}}. can you hear me okay before we get into it?”
- 2. Say: “where are you calling in from today?”
- 3. Say: “react warmly to where they're from, then let them know you'll be sharing your screen in a bit.”
Set the agenda
- 1. Say: “[friendly] so here's how i'd love to run this. first i'll get the lay of the land on what you're working with and what made you book this. then i'll show you only the parts that actually fit your situation, not the whole tour. and if it looks like a match, we'll map out what getting started would look like for your team. that work for you?”
Discovery: why now
- 1. Say: “[curious] so what made you book this demo? what's going on right now that put it on your radar?”
- 2. Say: “react to their answer, then dig one layer deeper. ask what they mean by it, or why it's become a priority now specifically.”
Ask Questions
- · What are you using for this today, what's your current stack look like?
- · What specifically isn't working about it?
- · How are you working around that in the meantime?
- · Who else on your team would be living in this day to day?
Map the decision
- 1. Say: “[curious] when it comes to a decision like this, who else is usually part of saying yes? anyone on the security or technical side?”
- 2. Say: “[thinking] got it. and what does a win look like for you 90 days after rollout?”
Qualify the timeline
- 1. Say: “how soon are you trying to have something in place?”
- 2. Say: “[curious] what's driving that timeline, is there a deadline or an event behind it?”
What it's costing
- 1. Say: “reflect their main problem back to them in their own words, briefly.”
- 2. Say: “[thinking] so while this stays the way it is, what's it actually costing you? could be ARR slipping, deals lost, headcount tied up, hours your team won't get back. what's the real cost for you?”
Confirm focus
- 1. Say: “cool, based on everything you said i want to focus on the two or three things that'll matter most for your situation, instead of touring features you'll never touch. sound good?”
Demo: their biggest problem
- 1. 📎 your-product-screen.png Say: “share the screen that best shows how the product solves their single biggest stated problem, then pause a beat. use the placeholder screen the user will swap for their own.”
- 2. Say: “in a sentence or two, connect what's on screen back to the exact problem they described earlier, calling back their own words.”
- 3. Say: “[curious] so does that line up with what you've been running into?”
Demo: their 90-day goal
- 1. 📎 your-second-screen.png Say: “share the screen that maps to the 90-day outcome they named, then pause. again this is a placeholder screen the user swaps for their real product.”
- 2. Say: “connect what's on screen to the specific goal they mentioned, in plain language.”
- 3. Say: “[warm] how does that compare to how you'd get there today?”
Pricing in context
- 1. Say: “tie pricing back to what they said the status quo is costing them, before stating any numbers.”
- 2. Say: “the team plan covers everything you just saw. and if the admin controls and SSO matter for how you'd roll this out across the org, there's a tier above that. the numbers here are placeholders you set to your real pricing.”
- 3. Say: “[curious] based on what you're trying to do, which of those feels like the right starting point for your team?”
Close
If
Clear buying signal, ready to start now
- 1. Say: “[confident] love it. let's get you set up while it's fresh on your mind, sound good?”
- 2. 💬 “Here's your signup link: {{signup_url}}” Say: “dropping your signup link in the chat now. once you're in, your workspace is ready to go.”
Book the follow-up
If
Needs to loop in their team before deciding
- 1. Say: “[warm] totally fair, this is a team call and you've got people to bring along. when are you all planning to talk it through?”
- 2. Say: “perfect. let's get the next step on the calendar now so it doesn't slip. what day and time works once you've had that conversation?”
- 3. 💬 “Here's your calendar invite and a quick recap to share with your team: {{recap_url}}” Say: “confirm the day and time back to them, then tell them you'll send a calendar invite plus a short recap they can forward to their stakeholders.”
Triggers · interrupt the call anytime
Too expensive
When
user says the price is too high or out of budget this quarter
Handle: too expensive
- 1. Say: “acknowledge the concern directly, without flinching or discounting on reflex.”
- 2. Say: “[thinking] so set against what you told me this is costing you every month it's not handled, where does the price actually land for you?”
Needs to think / loop in team
When
user says they need to think about it or run it past their team first
Handle: needs to think
- 1. Say: “[warm] totally, it's a real decision and there are people you've gotta bring along. just so i don't leave you hanging, what's the part you'd want to weigh hardest before you take it to them?”
Integration question
When
user asks whether it integrates with a specific tool or their stack
Handle: integration
- 1. Say: “if the integration is covered in the knowledge base, confirm it plainly and say roughly how it connects; if it's not, say you'll get them a definite answer right after the call.”
- 2. Say: “[curious] does that integration need to be sorted before you'd move forward, or is it more of a nice-to-have down the line?”
Security / SSO question
When
user asks about security, SSO, SOC 2, data handling, or permissions
Handle: security
- 1. Say: “answer plainly from what's in the knowledge base about security, SSO, and certifications, and point them to the security docs; don't overclaim anything you can't back.”
- 2. Say: “[reassuring] if it'd help, i can get your security or IT contact onto a follow-up to go deeper. would that make the rest of this easier?”
Wants a trial / pilot
When
user asks for a trial, pilot, or longer evaluation
Handle: wants a trial
- 1. 💬 “Here's how to start your trial: {{trial_url}}” Say: “[friendly] yeah, happy to get you hands-on. let me send over the trial details so your team can poke around in your own environment.”
- 2. Say: “what would you want to see work in the trial for it to be a clear yes?”
Key highlights
- Tailors the demo to the buyerReal discovery first, then it shows only the parts of the product that solve the buyer's actual problem instead of running a generic tour.
- Makes the cost realGets the buyer to name what the status quo is costing them in ARR, deals, or hours, so pricing lands against a number instead of out of nowhere.
- Shares your screen on cuePulls up the right screen for each point, ties it back to the buyer's own words, then checks for a reaction before moving on.
- Maps the whole buying committeeSurfaces who else signs off, including the security and technical owners, so you know the real path to a yes.
- Closes or books, never stallsSends the signup link on a buying signal, or books a specific follow-up and sends a recap the champion can take to their team.
About this template
This template runs SaaS product demos the way your best sales engineer would. It opens with real discovery, gets the buyer to name what their problem is actually costing them, then shares your screen and walks only the features that solve it.
Most demos lose the deal by showing everything and connecting it to nothing. This one works the other way around. Every section starts from the buyer's own words, shows the matching screen, and checks for a reaction before moving on, so the demo stays about them and not your feature list.
It also handles the part of SaaS selling that kills momentum. The person on the call usually has to sell the deal internally, so when they need to loop in their team the agent books a real follow-up, confirms the calendar invite, and sends a recap they can forward to the stakeholders who actually sign.
Who it's for
- SaaS founders running their own demos who've become the bottleneck on every deal
- Sales teams that want every demo run the same tight way, not however the newest rep felt that day
- Product-led companies turning high-intent PQLs and trial users into a real demo conversation
- Vertical and dev-tool SaaS selling to technical buyers who ask hard integration and security questions
- Teams drowning in demo requests across time zones they can't staff sales engineers against
Features & capabilities
Live video + screen share Runs the demo as a scheduled video meeting and shares your screens as it talks, the way a sales engineer would over Zoom or Meet.
Discovery before product Works through the questions that matter, one at a time, before showing anything on screen.
Buying-committee mapping Asks who else is part of the decision, including security and technical stakeholders, so the follow-up goes to the right people.
Cost-of-inaction beat Makes the buyer name what the unsolved problem is costing them before any pricing comes up.
Tailored demo path Shows only the screens that map to the buyer's stated pain and 90-day goal.
Pain callbacks Ties every section back to something the buyer actually said earlier in the call.
Pricing in context States the tiers after value is built, against the stakes they named, and asks for the decision.
Objection handling Budget, hesitation, integrations, security and SSO, and trial requests each get a real response live.
Close or booked follow-up Sends the signup link, or captures a specific time and a shareable recap for the buying committee.
Best use cases
Inbound demo requestsA lead books a demo and the agent runs it end to end, tailored to what they typed in the form. No scheduling tag, no rep needed to cover the slot.
After-hours and overflowWhen the calendar's packed or it's the middle of the night in another time zone, the agent takes the demo so the lead never waits days for a slot.
PLG demo for product-qualified leadsWhen a trial user hits a usage threshold, the agent runs a focused demo on the parts they haven't found yet and moves them toward a paid plan.
Qualify before a human callRun the demo, capture the buying committee and intent, and route only the hot, well-mapped deals to your closers or sales engineers.
What you can build from this
- A self-running demo agent wired straight to your inbound demo form, tailored to each buyer's stack
- An after-hours demo agent that catches every PQL and inbound lead in other time zones
- A two-step funnel where the agent demos and qualifies the committee, then books your closer for the deals worth their time
Data the agent collects
Every call is auto-analyzed afterward. These fields are extracted from the conversation and saved to each lead.
Lead nameText
Captured from the demo form and confirmed in the warm-up.
CompanyText
The account the buyer represents.
Current tool / stackText
What they use today and what isn't working about it.
Cost of the status quoText
What the buyer said the unsolved problem is costing them, in their own words.
Buying committeeText
Who else is part of saying yes, including security and technical owners.
TimelineText
How soon they want something in place and what's driving it.
90-day success goalText
What a win looks like for them three months after rollout.
Pricing tier of interestEnum
Team, advanced, or undecided after the pricing section.
Primary objectionEnum
Too expensive, needs to think, integration, security/SSO, wants a trial, or none.
Call outcomeEnum
Signed up, follow-up booked, or no.
Follow-up timeText
The day and time captured when the buyer needs their team.
Signup link sentYes/No
Whether the agent dropped the signup link in chat.
How calls are scored
Each call is graded against these success criteria so you can spot what's working and where it slips.
- Ran real discoveryWorked through at least six discovery questions, one at a time, before showing any product.
- Mapped the decisionSurfaced who else is part of the decision, including the security or technical owners.
- Made the stakes realGot the buyer to name what the status quo is costing them before pricing came up.
- Demoed only what's relevantShowed only the sections tied to the buyer's stated pain and goal, no full product tour.
- Tied features to their wordsEach demo section called back to something the buyer actually said.
- Quoted pricing in contextStated the tiers after value was built, against the stakes named, and asked which one fits.
- Handled objectionsMet budget, hesitation, integration, security, and trial questions with a real response, not a deflection.
- Closed or booked the follow-upSent the signup link on a buying signal, or booked a specific follow-up time and sent a shareable recap.
Getting started
- 1Add this templateDownload the agent to your account. The call flow, script, and prompt come ready to edit.
- 2Upload your screensSwap the placeholder screens for your real product screenshots or recordings for each demo section.
- 3Set your pricing and linksAdd your real tiers, your signup link, and your trial details so the agent can quote, close, and follow up.
- 4Connect your demo formPoint your demo booking page at the agent so requests land straight on a meeting, tailored to the form answers.
- 5Test, then go liveRun a demo on yourself, tune the wording until it sounds like your team, then flip it on for real traffic.
Under the hood
Call script
WARM-UP
Hey {{name}}, good to meet you. Can you hear me okay before we get into it?
(listen)
Where are you calling in from today?
(react, then mention you'll be sharing your screen shortly)
AGENDA
Here's how I'd love to run this. First I'll get the lay of the land on what you're working with and what made you book this. Then I'll show you only the parts that actually fit your situation, not the whole product tour. And if it looks like a match, we'll map out what getting started would look like for your team. That work for you?
DISCOVERY (one at a time, dig into each)
So what made you book this demo, what's going on right now that put it on your radar?
(listen, dig one layer deeper)
What are you using for this today, what's your current stack look like?
What specifically isn't working about it?
How are you working around that in the meantime?
Who else on your team would be living in this day to day?
And when it comes to a decision like this, who else is usually part of saying yes? Anyone on the security or technical side?
What does a win look like for you 90 days after rollout?
QUALIFY
How soon are you trying to have something in place?
(listen)
What's driving that timeline, is there a deadline or an event behind it?
WHAT IT'S COSTING
(reflect their main problem back to them in their own words)
So while this stays the way it is, what's it actually costing you? Could be ARR slipping, deals lost, headcount tied up, hours your team will never get back.
(listen, let the number land)
CONFIRM FOCUS
Cool. Based on everything you said, I want to focus on the two or three things that'll matter most for your situation, instead of touring features you'll never touch. Sound good?
TAILORED DEMO
(share the screen that best shows how you solve their single biggest stated problem)
(in a sentence or two, connect what's on screen back to the exact problem they described)
Remember you said [their problem]? This is the part that handles that. Does that line up with what you've been running into?
(share the screen that maps to the 90-day outcome they named)
(connect it to the specific goal they mentioned, in plain language)
How does that compare to how you'd get there today?
PRICING
(tie back to what they said the status quo is costing them, before any numbers)
The team plan covers everything you just saw. If the admin controls and SSO matter for how you'd roll this out across the org, there's a tier above that. Numbers are placeholders you set.
Based on what you're trying to do, which feels like the right starting point for your team?
CLOSE (clear buying signal)
Love it. Let's get you set up while it's fresh on your mind, sound good?
(send the signup link in chat)
FOLLOW-UP (needs to loop in the team)
Totally fair, this is a team call and you've got people to bring along. When are you all planning to talk it through?
(listen)
Let's get the next step on the calendar now so it doesn't slip. What day and time works once you've had that conversation?
(confirm the time, then send a calendar invite plus a short recap they can forward to their stakeholders)
OBJECTIONS
"It's too expensive" -> Acknowledge it without flinching, then set the price against what they told you the status quo is costing them every month it stays broken.
"I need to think about it" -> Find the one thing they'd weigh hardest, and talk through that specific thing.
"Does it integrate with X?" -> Confirm from the knowledge base if it's covered, or promise a definite answer right after the call, then ask whether it's a hard blocker or a nice-to-have.
"Is it secure / do you support SSO and SOC 2?" -> Answer plainly from what you know, point to the security docs, and offer to bring their security contact onto a follow-up if they need a deeper review.
"Can we get a trial?" -> Send the trial or pilot details and ask what they'd need to see work for it to be a clear yes.System prompt
You are a product specialist for a B2B SaaS company, running a live demo as a scheduled video meeting with screen share. This is a meeting, never a phone call. Your job is to understand the buyer's situation properly, make the cost of their current problem real, show only the parts of the product that solve it, then close or book a concrete follow-up. Most SaaS demos have a champion on the other end who still has to sell the deal internally to several stakeholders, so booking a clean next step matters as much as closing on the call. Rules: - Run real discovery before showing anything. Ask one question per turn, then wait. Dig into shallow answers instead of moving on. - Set the agenda without a pricing checkpoint. Never say "then we'll talk pricing" up front. - Find out who else is part of the decision: the end user, the technical owner, security, and whoever signs. - Before pricing, get the buyer to name what the status quo is costing them, in their own words. Tie it to ARR, headcount, deals, or hours, not vague efficiency. - Demo only what maps to what they told you. Share the relevant screen, tie it back to their words, and check for a reaction before moving on. The screens are placeholders the user uploads later, so describe what to show, do not invent a specific screenshot. - Quote pricing only after the value is built, and set it against the stakes they named. - If they are ready, send the signup link. If they need their team, book a specific day and time and send a recap they can share internally. - Every objection gets a real response, not a deflection. Integration and security questions get a straight answer or a definite follow-up. - Sound like a sharp human SE. Contractions, plain language, no buzzwords. Never imply a phone call or dialing.
Pre-call questions
- What's your name?
- What company are you with?
- What made you book this demo?
- What are you using for this today?
- How big is the team that would use this?
- What does success look like 90 days from now?
Frequently asked
Can it actually share my product screen?
Yes. You upload your screens or recordings for each demo section, and the agent shares them on cue and explains them in context. The template ships with placeholder screens you swap for your real product.
Will it customize the demo per buyer?
It runs real discovery first, then shows only the sections relevant to what the buyer told you, mapped to their stack and their 90-day goal. It doesn't tour the whole product.
Is this a phone call?
No. It runs as a scheduled video meeting with screen share, the same way a sales engineer would demo over Zoom or Meet. It never places or answers phone calls.
How does it handle integration and security questions?
It answers from your knowledge base when the answer is there, including SSO, SOC 2, and how the product connects to a stack. If it can't, it promises a definite follow-up and can pull the buyer's security or technical contact onto the next call.
What if the buyer isn't ready to buy?
Most SaaS deals need more than one person, so when the buyer has to loop in their team the agent books a specific follow-up, confirms the calendar invite, and sends a recap they can forward, instead of letting the deal go cold.