CSE Pre-Sales Discovery & Requirements 5 — Questions and Answers
Question 1: A prospect refuses to share their current tech stack during discovery. Which approach is most appropriate?
- End the evaluation immediately
- Explain why the information helps you tailor the solution and offer to sign an NDA if needed (Correct answer)
- Guess the tech stack based on the company's industry
- Skip integration questions and focus only on features
Correct answer: Explain why the information helps you tailor the solution and offer to sign an NDA if needed
Explaining the business reason for the question and offering confidentiality safeguards often unlocks reluctant prospects without creating adversarial friction.
Question 2: What is the key difference between a 'use case' and a 'user story' in requirements gathering?
- A use case is more detailed; a user story is a high-level narrative focused on user goals and value (Correct answer)
- A use case is informal; a user story is a legal specification
- Use cases are written by engineers; user stories are written by salespeople
- There is no meaningful difference between the two
Correct answer: A use case is more detailed; a user story is a high-level narrative focused on user goals and value
Use cases describe detailed system interactions and flows, while user stories are brief narratives capturing what a user wants to achieve and why.
Question 3: Which of the following is a sign that the discovery process has been insufficient before moving to a demo?
- The prospect has signed an NDA
- The Sales Engineer cannot articulate the prospect's top three business pains (Correct answer)
- The demo environment is not yet configured
- The prospect has more than five stakeholders
Correct answer: The Sales Engineer cannot articulate the prospect's top three business pains
If the SE cannot name the prospect's top business pains, the demo will be generic rather than targeted and will fail to resonate with decision-makers.
Question 4: What is the role of active listening during a discovery conversation?
- Taking verbatim notes without asking follow-up questions
- Fully concentrating on what the prospect says and asking clarifying questions to confirm understanding (Correct answer)
- Waiting for the prospect to finish speaking before presenting features
- Recording the call for later transcription
Correct answer: Fully concentrating on what the prospect says and asking clarifying questions to confirm understanding
Active listening involves full attention, paraphrasing, and probing, which builds trust and uncovers information the prospect might not otherwise volunteer.
Question 5: What is 'scope creep' in the context of a pre-sales engagement, and why is it a risk?
- Adding competitors to your pipeline tracking
- Continuously expanding the solution scope beyond initial requirements, which risks delivery promises and margins (Correct answer)
- Sharing too much technical detail during a demo
- Reducing the number of stakeholders in the buying process
Correct answer: Continuously expanding the solution scope beyond initial requirements, which risks delivery promises and margins
Scope creep during pre-sales leads to over-promising, unsustainable commitments, and implementations that exceed budget and timeline.
Question 6: In enterprise discovery, what is the significance of understanding a prospect's 'status quo'?
- It helps the SE price the deal correctly
- It reveals the cost and comfort of inaction, enabling the SE to articulate why change is necessary (Correct answer)
- It identifies which competitors the prospect currently uses
- It determines how many licenses to quote
Correct answer: It reveals the cost and comfort of inaction, enabling the SE to articulate why change is necessary
Understanding the status quo reveals hidden costs, workarounds, and inertia that must be overcome for the prospect to justify the investment in change.
Question 7: A prospect's IT team approves the solution technically, but the business unit sponsor is disengaged. What is the biggest risk?
- The deal will proceed but at a lower price
- Without business sponsor engagement, the deal may stall at budget approval or lose internal priority (Correct answer)
- The IT team will block the deal at implementation
- The prospect will issue a second RFP
Correct answer: Without business sponsor engagement, the deal may stall at budget approval or lose internal priority
Business sponsor disengagement signals weak organizational urgency; without their advocacy, deals frequently stall when competing priorities arise.
CSE Pre-Sales Discovery & Requirements 5
A prospect refuses to share their current tech stack during discovery.
Which approach is most appropriate?