Skip to main content
Scenario LabMulti-stakeholderadvanced

Multi-Stakeholder Demo: Champion vs. Skeptical Security

Practice a demo when your champion wants speed and Security challenges every integration. Balance MEDDIC stakeholder mapping with live call control.

24 min practice17 min read2 decision points

Cast

Riley Park

IT Manager (champion)

  • Replace legacy reporting before board review
  • Look competent to CFO

Hidden agenda: Undersold Security risk to get demo scheduled faster

Style: Urges you to ‘skip to the dashboard’ when challenged

Sam Ortiz

Security Architect

  • Zero new attack surface
  • Audit trail for every integration

Style: Interrupts with compliance questions; skeptical of ‘SOC 2 slide’

CFO (Jordan Wells)

Economic buyer

  • Payback under 14 months
  • No repeat of breach remediation costs

Style: Silent until ROI is threatened; then concise and final

You play Alex Rivera. Read their lines aloud or have a partner play the buyer.

Setup

Stage-2 demo after solid discovery. Champion (IT manager) promised CFO would attend; CFO joined late. Security was added last minute.

Stakes: Deal at $180K; competitor claims faster deployment. Slipping this week pushes to next quarter.

Company: Healthcare tech buyer (~600 employees). HIPAA-sensitive data; prior vendor breach 18 months ago.

Your goal

Keep the demo on business outcomes, surface Security concerns without derailing, and secure a technical deep-dive with documented requirements.

Success criteria

  • Agenda confirmed with all attendees at start
  • Security concern acknowledged and parked with owner + date
  • Champion and economic buyer speak at least once each
  • Next step names Security + IT + business owner

Script

Read through each act, then work the decision points below. Coaching notes appear after annotated lines.

Act 1 — Demo start (minutes 0–10)

Alex Rivera

Before screens — six of us, 45 minutes. I suggest five on outcomes Riley and Jordan aligned on, twenty on workflow, fifteen on questions, five on next steps. Sam, I’ll reserve time for security architecture. Fair?

Riley Park · IT Manager (champion)

Let’s just show the dashboard — we’re tight on time.

Alex Rivera

We will — after Sam’s constraints are on the board so we don’t demo features you can’t deploy.

Sam Ortiz · Security Architect

Where is PHI processed? Your slide says SOC 2 — I want data flow, not badges.

Alex Rivera

Valid. I’ll show data flow in act two. Capturing: PHI processing location and audit logging — Sam, you own verification?

Sam Ortiz · Security Architect

If API pushes PHI to your cloud without on-prem option, we’re done.

CFO (Jordan Wells) · Economic buyer

What did the breach cost us last time? I’m not doing that again.

Act 2 — Recover the room (minutes 10–20)

Alex Rivera

Jordan — remediation ran about $2M and delayed board reporting. Riley’s project targets $400K annual labor savings. Sam’s on-prem option preserves your security model. Can I show how all three connect?

Riley Park · IT Manager (champion)

Yes — show the dashboard now.

Alex Rivera

Two minutes on dashboard tied to labor savings, then Sam’s architecture deep-dive Wednesday with our security engineer — not today’s screen share.

CFO (Jordan Wells) · Economic buyer

Wednesday works if Sam signs off. Riley, you’re accountable for that meeting.

Sam Ortiz · Security Architect

Send the data-flow diagram today. I’ll come Wednesday with our checklist.

Decision points

Choose a path before reading the debrief. In pair practice, pause and discuss which option you would take.

Decision 1 of 2

Sam challenges PHI handling during the dashboard section. What do you do?

Skip to dashboard as Riley asked

Risky

Why: Bypasses Security; CFO hears breach anxiety without answers. Deal dies in technical review.

Capture concern, assign owner, schedule security session

Recommended

Why: Builds consensus; Sam feels heard; champion gets demo momentum via structured follow-up.

Argue SOC 2 compliance for ten minutes on the call

Risky

Why: Technical debate without architect loses CFO; sounds defensive not consultative.

Decision 2 of 2

CFO mentions the prior breach. Your response?

Acknowledge briefly and return to features

Risky

Why: Misses economic buyer’s frame — risk and ROI drive the deal.

Bridge breach cost, savings project, and Security path

Recommended

Why: Unifies buying group around business case while honoring Security.

Offer pricing concession to reassure CFO

Risky

Why: Price doesn’t solve security fear; signals desperation.

How to practice

Solo

  • Map each character to MEDDIC roles before reading.
  • Practice the agenda contract opening until it feels natural under 30 seconds.

Pair

  • Three roles: rep, Sam (interrupt often), Riley (impatient). Rotate.
  • Debrief: who spoke most? Target under 50% rep talk time.

Manager

  • Score: agenda (Y/N), parked concern with date (Y/N), CFO spoke (Y/N).

More scenarios

Continue practicing related situations.

Related guides

Frameworks and research cited in this scenario.