Tailor One Demo to Three Personas on the Same Call

This template is for a live product demo where three stakeholders have different priorities and the learner has to adapt in real time. It fits mid-market or enterprise sales conversations where a champion invited the call, an end-user wants workflow clarity, and IT needs security or implementation detail. It is not a generic discovery call template. The scenario is specifically about keeping one demo relevant to multiple personas without losing control of the meeting.

Use it when the buying group is already in the room and the challenge is message control, not basic product explanation. It is especially useful after a first discovery call, when the prospect has enough context to ask pointed questions. If you only need to practice one objection or one persona, a simpler single-stakeholder demo scenario is a better fit. This template is designed for the harder case where priorities compete on the same call.

A sales manager, enablement lead, or peer coach can run it, but the template also works as a self-practice exercise. The most useful facilitator is someone who can score the learner against the rubric and push the personas to react realistically. If you are using it for team training, one person can play the personas while another scores the attempt. The key is that the facilitator keeps the call moving and does not let the learner talk only to the easiest stakeholder.

Reps should use it whenever they are preparing for a multi-stakeholder demo or after a call where they lost momentum by over-explaining to one person. It also works well as a recurring coaching drill because the skill depends on repetition and immediate feedback. The goal is not memorizing a script but learning to switch emphasis without sounding robotic. A few focused attempts usually reveal whether the rep can balance business value, usability, and technical credibility.

Yes, but only in the context of a sales demo conversation. The IT lead persona is built to ask for specific, credible detail about security, access, or implementation concerns, so the learner has to answer without derailing the demo. It is not a compliance certification or a technical architecture review. The value is in practicing how to acknowledge the concern, answer at the right level, and move the call forward.

The most common mistake is giving the same pitch to everyone and assuming one feature story will land with all three stakeholders. Another is answering the IT lead in too much depth and losing the champion and end-user. Reps also often skip the workflow proof the end-user needs or fail to connect features to business outcomes for the champion. This template surfaces whether the learner can prioritize, pivot, and keep the room engaged.

Yes. The template is meant to be cloned and adapted to your product, industry, and sales motion. You can swap in your own champion title, end-user role, security concerns, demo milestones, and objection patterns. You can also adjust the difficulty by making the IT lead more technical or the champion more impatient. Customization is the point, because the scenario works best when it mirrors your real buying committee.

Ad-hoc practice usually tests whether a rep can explain the product, but it does not reliably test stakeholder management. This template adds structure: a concrete situation, distinct personas, a learner objective, and observable rubric criteria. That makes feedback easier to score and repeat across reps. It is better when you want consistent coaching on how to run a real multi-person demo, not just a casual rehearsal.

A strong attempt shows the rep naming each stakeholder’s priority, switching examples without losing the thread, and answering objections at the right level of detail. The rep should connect features to business impact for the champion, show the workflow clearly for the end-user, and give the IT lead enough specificity to trust the answer. The best attempts also close with a concrete next step that reflects the whole room, not just the loudest person. If one persona is ignored, the attempt should be scored as incomplete.