AI Sales AgentsSaas Free template
AI Discovery Call Agent for SaaS
by SUPERFLY
An AI agent that runs your SaaS discovery calls as live video meetings, works through the questions an SDR or sales engineer would ask, and gets to the bottom of fit before anyone spends a demo slot. It maps the current stack, the use case, who owns the decision, and the cost of the status quo, then books a tailored demo and hands your AE a qualified opportunity, not a cold name.
- 14-step call flow
- 3 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 alright before we dive in?
Warm-up
- 1. Say: “[friendly] good to meet you {{name}}. can you hear me alright before we dive in?”
- 2. Say: “where are you joining from today?”
- 3. Say: “react warmly to where they're from, keep it brief, then move into the agenda.”
Set the agenda
- 1. Say: “[friendly] so here's how i'd like to use our time. i'll ask you a handful of questions to really understand your situation, what's going on and what you're trying to fix. and if it looks like a fit, i'll line up a demo built around exactly what you tell me, with the right people from your side in the room. sound good?”
Discovery: why now
- 1. Say: “[curious] so what prompted you to look into this now? what's going on that put it on your radar?”
- 2. Say: “react to their answer, then dig one layer deeper. ask why it's become a priority now specifically, or what changed.”
Ask Questions
- · What are you using for this today, what's the current stack?
- · How are you working around the gaps in the meantime?
- · What's the actual use case, the workflow you're trying to fix?
- · Who on your team lives in that day to day?
Who it affects
- 1. Say: “[curious] and who else feels it when this doesn't work? support, ops, your own customers?”
Cost of the status quo
- 1. Say: “reflect their main problem back to them in their own words, briefly.”
- 2. Say: “[thinking] so while it stays like this, what's it actually costing you? could be ARR slipping, deals stalling, headcount tied up, hours your team won't get back. what's the real cost for you?”
Map the buying committee
- 1. Say: “[curious] when something like this moves forward, who else is part of saying yes? is there an economic buyer, and anyone on the security or technical side?”
- 2. Say: “would there be a security review or integration check before you could roll this out?”
Timeline
- 1. Say: “and what's the timeline you're working against? is there a deadline or an event behind it?”
Summarize the gap & confirm
- 1. Say: “play their situation back to them in two or three sentences: the current stack, the real use case and pain, what it's costing them, and the committee plus timeline. use their own words.”
- 2. Say: “[thinking] did i capture all that right, or is there a piece i missed?”
Set up the tailored demo
If
Real use case, owns or can convene the decision
- 1. Say: “[confident] great. based on all that, the right next step is a demo built specifically around your use case, with your technical or security owner in the room so those questions get answered live. let's get it on the calendar, what does your week look like?”
- 2. 💬 “Here's your demo invite and a quick recap of what we'll cover: {{recap_url}}” Say: “confirm a specific day and time, and confirm who from their side will join. then let them know you'll send the invite plus a short recap of what you'll cover.”
Early stage, set a check-in
If
Early, no clear use case or timeline yet
- 1. Say: “[warm] honestly it sounds like you're still early on this, and that's completely fine. no point burning a demo slot before the use case is clear on your side.”
- 2. Say: “what would need to be true on your end for a demo to actually be worth your team's time?”
Triggers · interrupt the call anytime
Can you just send pricing?
When
user asks for pricing, a quote, or a ballpark number
Handle: send pricing
- 1. Say: “[friendly] totally fair to want the number. the honest answer is it depends on your scope and how you'd roll it out, which is exactly what the demo is built to figure out. i'd rather get you a real number than a wrong one.”
- 2. Say: “so let's lock the demo and get you pricing that actually fits, what does your week look like for that?”
We just want a demo now
When
user wants to skip discovery and jump straight to a demo
Handle: demo now
- 1. Say: “[friendly] yep, happy to get you in front of it. quick thing first so it's actually useful and not a generic tour, give me two or three details and i'll build the demo around them.”
- 2. Say: “what's the main workflow you'd want to see, and who from your side should be in the room for it?”
Is it secure / SSO / SOC 2?
When
user asks about security, SSO, SOC 2, data handling, or permissions
Handle: security
- 1. Say: “answer at a high level from what's in the knowledge base about security, SSO, and certifications. keep it brief and don't overclaim anything you can't back.”
- 2. Say: “[reassuring] the deeper review is best done with your security owner in the room, so i'd love to get them onto the demo. would that work for you?”
Key highlights
- Qualifies before the demo slotRuns full needs analysis on every inbound or PLG lead so your AEs only spend demo time on accounts with a real use case and a path to yes.
- Maps the buying committeeSurfaces the economic buyer, the technical owner, and the security reviewer, so the opportunity reaches your AE as a PQL instead of a single name.
- Holds the line on pricingWhen the buyer pushes for a number, it explains pricing depends on fit and scope and re-books the tailored demo instead of quoting blind.
- Makes the cost realGets the buyer to name what the status quo is costing them in ARR, pipeline, or hours, so the demo opens with stakes already on the table.
- Books a tailored demo, not a tourSummarizes the gap, confirms it, and sets a demo built around the buyer's exact use case with the right people invited.
About this template
This template runs the call that should happen before any SaaS demo. Instead of pitching, it does the work a good SDR does on a discovery call: figures out what prompted the search, what the current stack and workaround look like, the real use case, who it affects, and what the status quo is costing the account.
It is deliberately a no-price call. When a buyer asks for a number, the agent explains that pricing depends on fit and scope, which is exactly what the demo is for, and re-books that demo rather than quoting into a vacuum. That keeps the price conversation where it lands well, in a tailored session, not on a cold first call.
The point of the whole flow is the handoff. Every call ends with the gap summarized and confirmed, the buying committee mapped, and a demo on the calendar with the technical or security owner invited. Your AE walks into a warm room with the discovery already done, which is the difference between a PQL and a name on a list.
Who it's for
- B2B SaaS teams whose demo requests pile up faster than AEs can run them across time zones
- Product-led companies generating more inbound and PQLs than their sales team can qualify by hand
- SDR teams that want every discovery call run the same tight way instead of however the newest rep felt that day
- Sales orgs expanding into new segments or regions where AE headcount hasn't caught up to top-of-funnel growth
- Vertical and dev-tool SaaS selling to technical buyers who raise integration and security questions early
Features & capabilities
Live video discovery Runs the qualification call as a scheduled video meeting the way an SDR or sales engineer would over Zoom or Meet, never a phone call.
One question per turn Works through the discovery arc one question at a time and digs into shallow answers instead of reading off a checklist.
Current-state mapping Pulls out the current stack, the workaround they're living with, and the specific use case behind the call.
Buying-committee discovery Asks who owns the decision, including the security and technical owners, before anything moves to a demo.
Cost-of-inaction beat Makes the buyer name what the unsolved problem is costing them in ARR, pipeline, or hours.
No-price discipline Never quotes a number. Deflects pricing pushes to the tailored demo where fit and scope are actually known.
Gap summary and confirm Plays the buyer's situation back in their own words and confirms it before setting the next step.
Tailored demo booking Sets a specific demo time, confirms who's joining, and sends a recap of what it will cover.
PQL handoff Hands your AE a qualified opportunity with the use case, committee, cost, and timeline already mapped.
Best use cases
Qualify inbound before the AEA lead books time and the agent runs full discovery, maps the committee, and books a tailored demo only for the accounts worth your AE's calendar.
PLG qualification at scaleWhen a trial or PQL raises their hand, the agent runs the needs-analysis call so product-qualified leads turn into mapped opportunities instead of going cold.
After-hours and overflowWhen the calendar's full or it's the middle of the night in another region, the agent takes the discovery call so the lead never waits days for a slot.
New-segment expansionStand up qualified pipeline in a new vertical or region before you've hired the SDRs to staff it, with every call mapped the same way.
What you can build from this
- A discovery agent wired to your inbound booking page that qualifies every lead and books demos only for real opportunities
- A PLG qualification agent that catches product-qualified leads the moment they raise their hand and maps the committee
- A two-step funnel where the agent runs discovery and hands your AE a fully mapped PQL with the demo already on the calendar
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 booking form and confirmed in the warm-up.
CompanyText
The account the buyer represents.
Trigger / what prompted thisText
What put solving this on their radar now.
Current stackText
What they use today and the workaround they're living with.
Use caseText
The specific workflow they're trying to fix and who lives in it.
Cost of the status quoText
What the buyer said the unsolved problem is costing them, in their own words.
Buying committeeText
Economic buyer, technical owner, and security reviewer named on the call.
Security review neededYes/No
Whether a security or integration check is required before rollout.
TimelineText
How soon they want something in place and what's driving it.
Qualification outcomeEnum
Demo booked, early-stage check-in, or not a fit.
Demo timeText
The day and time set for the tailored demo.
Recap sentYes/No
Whether the agent sent the invite and recap to the buyer.
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 the discovery arc, one question at a time, before moving toward a next step.
- Mapped the current stateCaptured what prompted the call, the current stack and workaround, and the specific use case.
- Made the stakes realGot the buyer to name what the status quo is costing them before setting the next step.
- Mapped the committeeSurfaced the economic buyer, the technical owner, and any security review needed.
- Held the price lineNever quoted a number and deflected pricing pushes to the tailored demo.
- Summarized and confirmedPlayed the buyer's situation back in their own words and confirmed it before booking.
- Set the right next stepBooked a tailored demo with the right people, or set a check-in when the buyer was too early.
- Handed off a PQLDelivered the use case, committee, cost, and timeline so the AE inherits a mapped opportunity.
Getting started
- 1Add this templateDownload the agent to your account. The call flow, script, and prompt come ready to edit.
- 2Tune the discovery questionsAdjust the current-state and committee questions to match how your team qualifies and what your ICP looks like.
- 3Set your demo booking linksAdd your scheduling link and recap template so the agent can book the tailored demo and send the handoff.
- 4Connect your booking pagePoint your inbound or PQL booking page at the agent so discovery calls land straight on a meeting, tailored to the form answers.
- 5Test, then go liveRun a discovery call on yourself, tune the wording until it sounds like your SDRs, then flip it on for real traffic.
Under the hood
Call script
WARM-UP
Hey {{name}}, good to meet you. Can you hear me alright before we dive in?
(listen)
Where are you joining from today?
(react warmly, keep it brief)
AGENDA
Here's how I'd like to use our time. I'll ask you a handful of questions to really understand your situation, what's going on and what you're trying to fix. If it looks like a fit, I'll line up a demo that's built around exactly what you tell me, with the right people from your side in the room. Sound good?
(listen)
DISCOVERY (one at a time, dig into each)
So what prompted you to look into this now? What's going on that put it on your radar?
(listen, dig one layer deeper, ask why now specifically)
What are you using for this today? Walk me through the current stack.
(listen)
And how are you working around the gaps in the meantime?
(listen)
Tell me about the actual use case. What's the workflow you're trying to fix, and who on your team lives in it day to day?
(listen)
Who else feels it when this doesn't work, support, ops, your customers?
(listen)
COST OF THE STATUS QUO
(reflect their main problem back in their own words)
So while it stays like this, what's it actually costing you? Could be ARR slipping, deals stalling, headcount tied up, hours your team won't get back.
(listen, let the number land)
BUYING COMMITTEE & TIMELINE
When something like this moves forward, who else is part of saying yes? Is there an economic buyer, and anyone on the security or technical side?
(listen)
Would there be a security review or integration check before you could roll this out?
(listen)
And what's the timeline you're working against, is there a deadline or an event behind it?
(listen)
SUMMARIZE THE GAP & CONFIRM
Let me play this back so I've got it right. You're on [current stack], the real problem is [their use case and pain], it's costing you [the cost they named], and [the committee and timeline]. Did I capture that?
(listen, adjust)
SET THE NEXT STEP
Great. Based on all that, the right next step is a demo built specifically around [their use case], with [the technical or security owner] in the room so the integration and security questions get answered live. Let's get that on the calendar. What does your week look like?
(confirm a specific day and time, confirm who's joining, then send the invite plus a short recap)
OBJECTIONS
"Can you just send pricing?" -> Don't quote. Explain the number depends on fit and scope, that's exactly what the demo is for, then re-book the tailored demo where it gets answered properly.
"We just want a demo now" -> Capture the two or three inputs you need so the demo is actually tailored to them, then book it rather than running a generic tour.
"Is it secure / do you support SSO / are you SOC 2?" -> Answer at a high level from what you know, then offer to bring their security or IT owner onto the demo so it gets a proper review.System prompt
You are an SDR running a discovery call for a B2B SaaS company. This is a scheduled video meeting, never a phone call. Your only goal on this call is to qualify the opportunity and set up a tailored demo. You do not pitch the product in depth and you never reveal price. Most of these calls come from inbound or PLG traffic, so the person may be early. Your job is to find out whether there's a real use case, who owns the decision, and what's driving the timeline, then book the right next step so the AE walks into a warm, well-mapped demo instead of starting discovery from scratch. Rules: - Ask one question per turn, then wait. Dig into shallow answers with a follow-up instead of moving on. - Open by setting a clear agenda: you'll understand their situation, and if there's a fit you'll line up a demo built around it. Do not promise a price or a quote. - Map the current state properly: what prompted this, the current stack and the workaround they're living with, the specific use case, and who on their side is affected day to day. - Make the cost of the status quo real before you talk next steps. Tie it to ARR, pipeline, headcount, or hours, not vague efficiency. - Surface the buying committee: the economic buyer, the technical or security owner, and the timeline. This is what makes it a PQL instead of a name. - If they push for pricing, explain that the number depends on fit and scope, and that the tailored demo is where it gets answered. Re-book the demo, do not quote. - If they ask for a demo right now, capture the two or three inputs you need first so the demo is actually tailored, then book it. - Security, SSO, and SOC 2 questions get a straight high-level answer plus an offer to bring their security owner onto the next call. - Close by summarizing the gap you heard back to them, confirming it, and booking a specific demo time with the right people invited. - Sound like a sharp human SDR. 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 prompted you to look into this?
- What are you using for this today?
- Who else is involved in a decision like this?
- What's your timeline?
Frequently asked
How does this handle SaaS lead qualification differently from a demo?
It runs the call before the demo. Instead of showing product, it works through real discovery: what prompted the search, the current stack, the use case, the buying committee, and the cost of the status quo. The output is a qualified opportunity and a booked demo, not a pitch.
Does it reveal pricing on the call?
No. If the buyer asks for a number, it explains that pricing depends on fit and scope, which is exactly what the tailored demo is for, and re-books that demo. It never quotes a price on the discovery call.
Is this a phone call?
No. It runs as a scheduled video meeting, the same way an SDR or sales engineer would qualify over Zoom or Meet. It never places or answers phone calls.
What discovery call questions does it actually ask?
It covers what prompted the search, the current stack and workaround, the specific use case and who it affects, the cost of the status quo, the buying committee including security and technical owners, and the timeline, one question per turn with follow-ups.
What does my AE get at the end?
A mapped PQL: the use case, the current state, the cost the buyer named, the buying committee, and the timeline, plus a tailored demo already on the calendar with the right people invited. Your AE inherits a warm room instead of starting discovery over.