Objection handlingHard3–5 min
“Your product is missing a requirement”
In a technical review, the buyer asks about a control or integration the rep cannot confirm.
Your product is missing a requirement we need.
Skill testedProtecting accuracy when you do not know the answer
Two briefs. Hand each sheet to one person only.
Rep brief
Everything the seller may know before the call.
- Account context
- During a technical review, the buyer asks about a security control or integration you cannot confirm.
- What you know
- The approved product documentation and the name of the technical owner, but not the answer.
- What you need to learn
- Whether the requirement is mandatory, when it is needed, and what evidence the buyer expects.
Buyer brief Private
For the person playing the buyer. Keep the difficulty at hard for the first attempt and the retry.
- Open with
- “Your product is missing a requirement we need.”
- What you may mean
- Choose one before the call: a hard procurement requirement, a preference, a future need, or a technical concern that another owner can answer.
- How to react
- If the rep guesses or promises a roadmap item, ask for it in writing.
- If the rep states the limit and asks whether it is mandatory, explain when you need it.
Score the attempt. One row per pass criterion.
| Pass criterion | Met | Partly | Missed | Evidence (quote or timestamp) |
|---|---|---|---|---|
| Protects accuracy. | Met | Partly | Missed | Evidence |
| Agrees on the correct technical follow-up. | Met | Partly | Missed | Evidence |
Also counts as a pass
- State the limit
- Capture the exact question
- Identify the right owner
- Agree on a response time
- Disqualify if the requirement is mandatory and unavailable
Listen for
- Guessing.
- Promising a roadmap item.
- Changing the buyer's wording.
- Hiding the gap.
Debrief
- Was the requirement mandatory, and how did the rep find out?
- Did the follow-up go to the right owner with a date?
Retry
One retry goal
Live call to check it on
Next scenarios. Same skill area, a different buyer.
From the guide Objection Handling Roleplay: 7 Scenarios and a Scorecard, which covers how to run, score and retry these scenarios.
- Objection handlingGuarded
“This is too expensive”
A sales leader agrees the problem is real but has not tied it to a cost. Price comes up first.
Sales leader with budget this quarter3–5 min - Objection handlingGuarded
“Send me some information”
An outbound prospect wants to end the call without conflict and asks for material.
Outbound prospect with no stated problem3–5 min - Objection handlingGuarded
“We already use another solution”
The buyer has an incumbent tool and no replacement project. The rep has no approved battlecard.
Buyer with an incumbent tool and uneven adoption3–5 min
Practice this buyer with AI.
Quotain plays the buyer from this brief, holds the difficulty and scores every retry.