Sales demo guide
What to say when you don't know the answer during a sales demo
Say this: “That is a good question. I do not want to guess and give you the wrong information. Let me confirm it with our team and send you a precise answer by tomorrow. Before I do, can I check what you need this capability to do?”
The short answer
- Do not bluff. A confident wrong answer creates more risk than a calm admission that you need to verify a detail.
- Acknowledge the question, clarify why it matters, share only what you know, and promise a specific follow-up time.
- Write down the exact question and context during the call. Your follow-up should answer the question, name any limitations, and reconnect the answer to the buyer's goal.
Use the CLEAR framework
Not knowing one answer does not ruin a sales demo. Guessing, becoming defensive, or letting the question derail the conversation can. Use this five-part response to stay credible and keep the demo moving.
- Confirm the question. Repeat the important part so everyone agrees on what is being asked.
- Learn why it matters. Ask one short question about the prospect's workflow, risk, or requirement.
- Explain what you know. Give verified, relevant context without stretching it into an answer you cannot support.
- Arrange the follow-up. Name who will verify the answer and when the buyer will receive it.
- Record the commitment. Capture the wording, owner, and deadline before returning to the demo.
The clarification step is especially valuable. “Does it integrate with our ERP?” could mean a native integration, an API, scheduled file imports, real-time synchronization, or a security review. You may not know the answer to the broad question, but one follow-up question can reveal the answer the buyer actually needs.
Exact phrases for common sales demo questions
Choose a response that matches the kind of uncertainty. Keep it short enough that it sounds natural, then return to the buyer's priority.
| Situation | What to say |
|---|---|
| You need to verify a technical detail | “I do not want to guess on the technical detail. Let me confirm it with our solutions team and send you a precise answer by tomorrow. Which part of the workflow depends on it?” |
| You know part of the answer | “What I can confirm is that we support [known capability]. I need to verify whether that also covers [unknown detail] in your setup.” |
| The question is too broad | “When you say integration, do you mean transferring data, triggering an action, or giving users single sign-on access?” |
| The prospect asks about security or compliance | “That deserves an exact answer rather than a general one. I will verify the requirement with our security team. Is this a procurement requirement or a technical control your team needs?” |
| The prospect asks for an exact price | “I can explain how pricing is structured, but I need to confirm the exact figure for that configuration. Let me capture the number of users and expected usage so the quote is accurate.” |
| The feature may not exist | “I cannot confirm that capability today. Let me verify whether there is a supported alternative. How essential is it to your decision?” |
| You need a moment to think | “Let me take a moment to make sure I answer the question you are actually asking.” |
| Someone else on the call may know | “I want to check before I answer. Priya, is that something you can confirm now, or should we follow up after the call?” |
How to answer without losing momentum
A difficult question often signals buying intent. The prospect may be testing whether the product fits a real workflow, whether a stakeholder will approve it, or whether a known risk can be removed. Treat the question as discovery, not an interruption.
After you set the follow-up, bridge back to the demo with a sentence such as: “I have captured that. Since the outcome you want is faster approval, let me show you the workflow that leads up to that point.” This acknowledges the open item without allowing one edge case to consume the rest of the meeting.
If the unanswered question could disqualify the product, do not minimize it. Pause the planned demo and learn more. A direct conversation about a real limitation is more useful than finishing a polished presentation for a solution that may not fit.
What not to say when you do not know
- “I think it should work.” The buyer may hear this as a promise.
- “Nobody has ever asked that.” This makes a reasonable requirement sound like the prospect's problem.
- “It is probably on the roadmap.” A roadmap is not a commitment unless you have verified it.
- “That is a question for support.” You can involve another team without pushing ownership onto the buyer.
- “I will get back to you.” This is incomplete without an owner and a time.
- A long improvised answer. More words do not make an uncertain answer safer.
The best response sounds accountable, not apologetic: “I need to verify that” is stronger than repeatedly saying sorry or filling the silence with possibilities.
Prepare for the questions most likely to stop a demo
Before the call, list the questions that would be hardest to answer live: security requirements, uncommon integrations, migration constraints, pricing exceptions, implementation timelines, performance limits, and roadmap requests. Add a short approved answer or a named expert for each.
Keep product documentation, a security brief, pricing rules, and prospect-specific discovery notes available during the meeting. The goal is not to memorize every detail. It is to make the verified answer easy to retrieve and to know which questions still require an expert.
For a repeatable system, use this guide to prepare for technical questions during a sales demo, including security, integrations, implementation, pricing, and product limits.
How a real-time AI sales assistant can help during the demo
A live meeting assistant is most useful when the answer already exists in your product material but is difficult to retrieve while you are presenting. It should shorten the search for context, not turn an uncertain suggestion into a product promise.
Imagine a prospect asks: “Can we require SSO for contractors while employees continue using their existing login?” A generic AI answer may describe how SSO usually works. A useful answer needs the prospect's exact question plus your own authentication and plan documentation.
| Stage | How SleekAssist fits | What the salesperson still owns |
|---|---|---|
| Before the demo | Add the relevant product brief, security document, or technical reference and set the session context. | Use current, approved source material and remove outdated documents. |
| When the question lands | SleekAssist detects questions from the live transcript and can use uploaded documents and optional on-screen context to surface a suggested response in the browser. | Read the suggestion for meaning, not as a script. Check that it answers the buyer's actual requirement. |
| When the source is incomplete | The transcript and surrounding conversation help preserve the exact question instead of reducing it to “check SSO.” | Use the CLEAR response, identify the missing detail, and promise a verified answer by a specific time. |
| After the session | When transcript saving is enabled, the transcript and suggested answers remain available in SleekAssist history. | Confirm the final answer with the appropriate product, security, legal, or pricing owner before sending it. |
This is the practical boundary: SleekAssist can help retrieve and structure an answer during a sales call, but it cannot make an unverified claim safe. If the source does not support the answer, saying “I need to confirm that” remains the correct response.
When SleekNote is the better mode
Some demos are less about handling difficult questions live and more about remembering a dense conversation afterward. For those meetings, SleekNote records the transcript and produces structured notes, decisions, action items, follow-up questions, and an email draft when the session ends.
SleekAssist and SleekNote are separate session modes. Choose SleekAssist when live guidance is the main risk; choose SleekNote when an accurate recap and follow-up are the bigger workload. That distinction also prevents an AI meeting tool from doing more than the job you selected it to do.
Turn the unknown answer into a strong follow-up
A good response during the demo only protects trust if the promised answer arrives. Before ending the call, read back every open question, confirm who owns it, and state when the prospect should expect a response.
Your follow-up should include:
- The prospect's original question in their language.
- A direct answer in the first sentence.
- Any conditions, limitations, or required configuration.
- A link or document that supports the answer.
- The next step, especially if the answer requires a technical session.
Whether you work from handwritten notes, a saved SleekAssist transcript, or a SleekNote follow-up draft, compare the email with the original question before sending it. The final message should answer what the buyer asked—not a broader, easier version of the question.
A follow-up email template
Subject: Answer to your question about [topic]
Hi [Name],
During today's demo, you asked whether [repeat the question]. I confirmed with [team or source] that [direct answer].
The important condition is [limitation or setup requirement]. Based on your goal to [buyer's goal], the next best step is [action]. I have included [documentation or example] here: [link].
I also captured [other action items]. We will [next step] by [date].
Best,
[Your name]
Frequently asked questions
Is it okay to say “I don't know” during a sales demo?
Yes. Say it briefly, explain that you want to verify the answer, clarify what the prospect needs, and give a specific follow-up time. Honesty protects credibility; an unsupported guess can damage it.
What if the prospect keeps pressing for an answer?
Hold the boundary: “I understand this is important, which is why I do not want to speculate. I will confirm it with the right owner and reply by [time].” Then ask whether the requirement is a deal-breaker so you can prioritize the follow-up correctly.
How quickly should I follow up after the demo?
Follow the deadline you gave on the call. For a straightforward question, the same business day is ideal. If research will take longer, send a short progress update before the original deadline rather than going silent.
Can AI answer questions for me during a sales call?
A real-time AI meeting assistant can use the conversation and your reference documents to suggest an answer. It is most useful for recall, structure, and finding relevant context. You should still verify claims involving security, compliance, pricing, contracts, product limits, or roadmap commitments.
Choose the meeting workflow by the problem you need to solve: SleekAssist for contextual help with live questions, or SleekNote for structured notes and a follow-up draft after the call.
Compare the workflows