Pre-Sales Discovery & Requirements Flashcards
7 cards from real CSE practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Pre-Sales Discovery & Requirements flashcards as text
A prospect refuses to share their current tech stack during discovery. Which approach is most appropriate?
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.
What is the key difference between a 'use case' and a 'user story' in requirements gathering?
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.
Which of the following is a sign that the discovery process has been insufficient before moving to a demo?
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.
What is the role of active listening during a discovery conversation?
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.
What is 'scope creep' in the context of a pre-sales engagement, and why is it a risk?
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.
In enterprise discovery, what is the significance of understanding a prospect's 'status quo'?
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.
A prospect's IT team approves the solution technically, but the business unit sponsor is disengaged. What is the biggest risk?
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.