Demo Skill Self-Assessment Quiz

This isn't a confidence survey — it's a diagnostic across six competencies that actually separate strong demos from average ones. Answer honestly based on your last 5 real demos, not your best one.

How to take it

For each of the 24 statements, score yourself 1–5:

1 = Rarely true of my demos · 2 = Sometimes true · 3 = About half the time · 4 = Usually true · 5 = Consistently true

Total each competency's 4 items for a subtotal out of 20.

---

Competency 1 — Discovery-to-Demo Alignment

• I only show features that map directly to something the prospect told me in discovery. ___
• I can name, without checking notes, the specific business outcome this prospect said they wanted. ___
• I cut planned demo content live when I realize it doesn't serve this prospect's stated priorities. ___
• Prospects tell me the demo "felt built for them," unprompted. ___

Subtotal: ___ / 20

Competency 2 — Narrative Structuring

• My demo has a clear beginning (their problem), middle (the shift), and end (their future state) — not just a feature tour. ___
• I can explain the "why now" for this specific prospect without checking notes. ___
• I sequence the demo around their workflow, not around my product's menu structure. ___
• The demo would still make sense to someone who joined 5 minutes late. ___

Subtotal: ___ / 20

Competency 3 — Technical Fluency

• I can answer technical questions (integrations, security, data handling) without needing to "get back to you" more than rarely. ___
• I can recover smoothly on camera when something breaks or behaves unexpectedly. ___
• I know which 2–3 technical objections come up most for my product and have a ready answer for each. ___
• I can adjust technical depth up or down depending on who's in the room, in real time. ___

Subtotal: ___ / 20

Competency 4 — Stakeholder Reading

• I can tell, mid-demo, when I've lost a specific attendee and adjust before they check out. ___
• I address each named stakeholder's stated concern at least once by name during the demo. ___
• I ask who else needs to see this before assuming today's audience is the full decision unit. ___
• I read silence, camera-off, or short answers as signals to act on, not just noise. ___

Subtotal: ___ / 20

Competency 5 — Objection Navigation

• When an objection comes up mid-demo, I address it in the moment rather than deflecting to "great question, let's come back to that." ___
• I can distinguish a real blocking objection from a reflexive one, and respond differently to each. ___
• I stay curious (ask a follow-up) before I answer, rather than answering the objection I assume they mean. ___
• I don't get defensive or over-explain when a competitor or internal alternative comes up. ___

Subtotal: ___ / 20

Competency 6 — Close & Next-Step Design

• Every demo I run ends with a specific, dated next step — not "I'll follow up." ___
• The next step I propose is proportional to how ready the buyer actually is (not always "book the next call"). ___
• I confirm who else needs to be involved in the next step before the call ends. ___
• I can tell, honestly, whether a deal is stalling versus genuinely progressing — and I say so internally. ___

Subtotal: ___ / 20

---

Scoring Bands (per competency, out of 20)

What To Develop Next — the Decision Rule

Don't just pick your lowest score. Use this priority order:

1. Any competency scoring under 10 — fix this first regardless of the others; it's an active liability.
2. If none are under 10, pick the competency with the largest gap versus your role's expected level (ask your manager what "Solid" should look like at your tenure — a 2-year rep scoring 12 on Objection Navigation is behind; a new-hire scoring 12 is on track).
3. If still tied, pick the competency most repeated in recent manager demo reviews or the Post-Demo Feedback Survey open-text answers — real feedback beats self-perception.

Recommended Next Action by Band

Retake Cadence

Retake this quarterly, or immediately after any stretch of 3+ stalled deals in a row. Track your 6 subtotals over time — the goal is not a perfect score, it's a rising floor (no competency under 10) before chasing ceiling.