Sample scorecard
Objection handling with Maya Chen
Fictional session, real rubric
Objection handling counts double in this score, because it’s the skill being practiced.
Clarity
Each turn made one point, and the pitch fit in a single sentence.
Our planner rebuilds the day's routes in minutes when someone is out
Value & relevance
Tied the product to the sick-day scramble Maya described, not to features.
so dispatch stops firefighting
Structure
A strong opening question, but the pitch came before the cost of the problem was clear.
Thanks for making time, Maya. Before I pitch anything
Discovery questions
One good open question. A follow-up on how often routes break would have shown the impact.
how are your dispatchers planning routes today?
Objection handling
Counts doubleAcknowledged the bad past experience, then answered it with a low-risk pilot.
That's fair, and I'd be skeptical too.
Confidence & language
Calm and concise throughout, with no filler or apologies.
and you only continue if your dispatchers actually use it
Call to action
Offered a pilot, but without a start date or a next meeting.
What if we started with one depot for a month
Strengths
- Asked how routes are planned today before pitching anything.
- Linked the product to the problem Maya described in her own words.
- Agreed with the objection before answering it, which kept the conversation open.
Improvements
- Ask how often routes break and what that costs before you pitch.
- Put a date on the pilot: propose a start week and a review call.
- Back the pilot with one concrete result you could measure together.
Stronger version
You said
What if we started with one depot for a month, and you only continue if your dispatchers actually use it?
Try
Could we start one depot on a 30-day pilot next Monday, and book 20 minutes at the end of the month to review usage with your dispatch lead?