The buyer who cannot add another initiative
A revenue leader agrees reps may not be ready for a launch, but the launch comes first.
This is relevant, but the launch comes first. I cannot ask managers to add meetings or build a new program this quarter.
Skill testedTreating workload as a design constraint, not an objection
Two briefs. Hand each sheet to one person only.
The buyer who cannot add another initiativequotain.com/scenarios/launch-first-discovery-call
Rep brief
Everything the seller may know before the call.
- You sell
- You sell a sales coaching and practice product to sales and enablement leaders.
- Situation
- A revenue leader agrees that reps may not be ready for an upcoming product launch. The readiness problem is real, but reviewing and rolling out a new program would compete with the launch work already consuming frontline managers.
The buyer who cannot add another initiativequotain.com/scenarios/launch-first-discovery-call
Buyer brief Private
For the person playing the buyer. Keep the difficulty at guarded for the first attempt and the retry.
- Open with
- “This is relevant, but the launch comes first. I cannot ask managers to add meetings or build a new program this quarter.”
- Hidden facts
- In an early design-partner call, two experienced reps failed to uncover the new buyer's approval process and gave the wrong demo. The CRO now wants every rep certified before launch.
- Pressure
- Product marketing and frontline managers disagree on what readiness means. Any test must use launch work already underway and produce a shared standard without adding manager meetings.
- Reveal rules
- Share the failed call only if the rep asks what made readiness urgent. Reveal the disagreement only if the rep asks how reps will be certified, who defines success, or what work managers are already doing.
- How to react
- If the rep makes a generic time-saving claim, challenge it.
- If the rep manufactures urgency, say the launch already supplies enough urgency and begin closing the call.
- If the rep asks about the launch workflow, describe the design-partner call and the disagreement over readiness.
The buyer who cannot add another initiativequotain.com/scenarios/launch-first-discovery-call
Score the attempt. One row per pass criterion.
| Pass criterion | Met | Partly | Missed | Evidence (quote or timestamp) |
|---|---|---|---|---|
| Learns what changed for reps and what failure has already occurred. | Met | Partly | Missed | Evidence |
| Identifies the stakeholders who must agree on readiness. | Met | Partly | Missed | Evidence |
| Defines the constraints of a small test, including what it must reuse and what overhead it must avoid. | Met | Partly | Missed | Evidence |
Debrief
- Did the rep treat the launch workload as a design constraint or an objection to defeat?
- What constraint should shape the proposed test?
- Was there enough evidence to act now?
Retry
One retry goal
Live call to check it on
Next scenarios. Same skill area, a different buyer.
From the guide Discovery Call Roleplay: 7 Scenarios to Practice Before a Live Call, which covers how to run, score and retry these scenarios.
Practice this buyer with AI.
Quotain plays the buyer from this brief, holds the difficulty and scores every retry.