Intro to Sales Engineering and Solutions Consulting: Demo Structuring (Tell‑Show‑Tell, Flow, Personalization)

Demo Structuring (Tell‑Show‑Tell, Flow, Personalization)

Demo Structuring (Tell-Show-Tell, Flow, Personalization) – The SE’s Playbook for Winning Technical Deals

What This Is

Demo structuring is the art of turning a technical presentation into a compelling, personalized story that aligns with the prospect’s pain points, decision criteria, and business outcomes. It’s not about showing features—it’s about proving value in a way that makes the prospect feel the cost of not buying. Real-world scenario: A cybersecurity SE is in a competitive POC for a SOC 2 compliance tool. The prospect’s CISO cares about audit failures, not firewall rules. The SE structures the demo to first show a failed audit report (Tell), then demo how their tool auto-remediates gaps (Show), and finally tie it to the CISO’s bonus (Tell). The competitor’s demo? A generic feature walkthrough. Guess who wins.

Key Terms & Frameworks

• Tell-Show-Tell (TST):
  A demo framework where you explain the problem/opportunity (Tell), demonstrate the solution (Show), and reinforce the business impact (Tell). Used in every demo to keep the prospect engaged and aligned.

• Demo Flow:
  The sequence of topics in your demo, designed to build logical momentum (e.g., "Problem → Solution → ROI"). Think of it like a movie plot—no spoilers, just escalating stakes.

• Personalization:
  Tailoring the demo to the prospect’s specific pain points, industry, and role (e.g., a CFO sees cost savings, a CTO sees scalability). Requires discovery before the demo.

• Discovery:
  The pre-demo call where you ask questions to uncover pain, process, and decision criteria (e.g., "What’s the cost of downtime for your team?"). Without this, your demo is a guessing game.

• MEDDIC:
  Qualification framework (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion). Used to prioritize deals and structure demos around what actually matters to the buyer.

• POC (Proof of Concept):
  A time-bound technical evaluation where the prospect tests your solution in their environment. Not a demo—it’s a mini-implementation with clear success criteria.

• Success Criteria:
  The measurable outcomes a prospect needs to see in a POC/demo to move forward (e.g., "Reduce false positives by 30%"). Always agree on these upfront.

• Objection Handling:
  Addressing pushback (e.g., "Your product is too expensive") by reframing it as a question (e.g., "What’s the cost of not solving this problem?"). Never argue—align.

• Demo Trap:
  A common mistake that kills demos (e.g., showing every feature, ignoring the prospect’s body language, or failing to tie back to their pain). Avoid at all costs.

• Champion:
  The internal advocate who wants you to win and will sell for you when you’re not in the room. Identify them early and arm them with stories from your demo.

• Economic Buyer:
  The person who controls the budget (e.g., CFO, VP). Your demo must speak their language (ROI, cost savings, risk reduction).

• Decision Criteria:
  The specific requirements the prospect uses to evaluate solutions (e.g., "Must integrate with Salesforce"). Map your demo to these explicitly.

Step-by-Step / Process Flow

1. Pre-Demo: Discovery & Qualification (MEDDIC)

Goal: Uncover pain, process, and decision criteria before the demo.
How:
- Schedule a discovery call (30–60 mins) with the prospect and key stakeholders.
- Ask open-ended questions to uncover: - Pain: "What’s the biggest challenge your team faces with [problem]?" - Impact: "What happens if this isn’t fixed in 6 months?" (Tie to Metrics in MEDDIC.) - Decision Process: "Who else needs to sign off on this?" (Identify Economic Buyer and Champion.) - Success Criteria: "What would make this demo a success for you?" (Align with Decision Criteria.) - Example dialogue:

SE: "You mentioned downtime is a major issue. Can you walk me through the last time this happened—what was the impact on revenue or customer trust?" Prospect: "We lost $50K in SLA penalties and had 3 customers churn." SE: "Got it. So if we could show you how our solution reduces downtime by 40%, would that be valuable to your team?" (This becomes your demo anchor.)

Output: A 1-page demo script with: - The prospect’s top 3 pains (ranked by impact).
- Their success criteria (e.g., "Must reduce false positives by 30%").
- Who’s attending (roles, influence, and what they care about).

2. Structure the Demo: Tell-Show-Tell (TST) Framework

Goal: Make the demo feel like a story, not a feature dump.
How:
- Tell (Problem/Opportunity):
- Start with their pain (from discovery).
- Use data (e.g., "You mentioned downtime costs you $50K per incident").
-
Example:
> "Last quarter, your team spent 200 hours manually triaging alerts—time that could’ve been spent on proactive security. Today, I’ll show you how our tool automates 80% of that work, so your team can focus on high-risk threats."

• Show (Solution):
• Demo only what matters to their pain/success criteria.
• Personalize (e.g., use their company name, data, or industry examples).
• Keep it interactive (e.g., "Which of these alerts would you prioritize?").

• Example:
  > "Here’s how our tool ingests your existing SIEM data. Watch as it auto-classifies this alert as a false positive—no manual review needed. Now, let’s look at a high-risk alert, like the one that caused your last breach."

• Tell (Impact/ROI):

• Reinforce the business outcome (e.g., "This saves 160 hours/month, or ~$80K/year").
• Tie to their role (e.g., CFO: cost savings; CTO: scalability).
• Example:
  > "With this automation, your team reclaims 160 hours/month—time that can be spent on threat hunting. That’s a direct impact on your SOC 2 compliance and your team’s morale. How does that align with your goals for this year?"

Pro Tip: End with a question (e.g., "Does this address your top priority of reducing false positives?"). This forces engagement and surfaces objections early.

3. Personalize the Demo

Goal: Make the prospect feel like the demo was built just for them.
How:
- Use their language: If they call it "incident response" (not "threat detection"), use their term.
- Leverage their data: If possible, ingest their logs, tickets, or metrics into the demo (e.g., "Here’s your actual false-positive rate from last month").
- Industry examples: A healthcare prospect cares about HIPAA; a fintech prospect cares about PCI DSS.
- Role-based tailoring:
- CFO: Show cost savings (e.g., "This reduces your audit costs by 30%").
- CTO: Show scalability (e.g., "This scales to 10K endpoints without performance hits").
- End User: Show ease of use (e.g., "Your analysts will love this—no training required").

Example:

"You’re in retail, so I know chargeback fraud is a major pain. Let’s look at how our tool reduces false declines by 25%—directly impacting your bottom line. Here’s a real example from [Competitor Retailer] that saw a 2% revenue lift after implementation."

4. Handle Objections in Real Time

Goal: Turn objections into opportunities to reinforce value.
How:
- Listen first: Let them finish—don’t interrupt.
- Clarify: "Just to make sure I understand, are you concerned about [X] or [Y]?" - Reframe: Tie the objection to their pain.
- Objection: "Your product is too expensive." - Response: "I get that. Let’s talk about the cost of not solving this. You mentioned downtime costs you $50K per incident. How many incidents do you have per quarter?" (Now you’re talking their numbers.) - Isolate: "If we could show you a way to reduce costs by 20%, would that address your concern?"

Example Dialogue:

Prospect: "Your competitor’s tool has a better dashboard." SE: "I hear that. Can you help me understand what specifically about their dashboard is more valuable to you? Is it the customization, the real-time data, or something else?" (Dig for Decision Criteria.) Prospect: "It’s the real-time alerts—we need to act fast on breaches." SE: "Got it. Let me show you how our tool not only provides real-time alerts but also auto-remediates 60% of them—so your team isn’t just alerted, they’re protected. Here’s how it works..." (Now you’re differentiating.)

5. Close the Demo with Next Steps

Goal: End with clear action items (not "Thanks for your time!").
How:
- Summarize: "Today, we showed how [solution] addresses [pain], saving you [X] time/money. Does that align with your goals?" - Ask for commitment: "Based on what we’ve covered, what’s the next step for you?" - Propose a path: "I’d recommend a POC where we can test this in your environment. Would that work for your team?" - Leverage the Champion: "[Champion’s Name], how do you see this fitting into your timeline?"

Example:

"We’ve covered how our tool reduces false positives by 30%, saving your team 160 hours/month. Based on what we’ve seen today, would it make sense to set up a POC to validate this in your environment? I can have a proposal to you by EOD tomorrow."

Common Mistakes

SE Interview / Practical Insights

1. Mock Demo Role-Play: "The Prospect Asks a Question You Don’t Know"

Interviewer: "How do you handle a question you can’t answer?" Bad Answer: "I’d say I don’t know and get back to them." (This kills momentum.) Good Answer:

"I’d say, ‘That’s a great question. Let me check with my team to get you the most accurate answer. In the meantime, can I share how we’ve solved this for [similar customer]?’ This keeps the demo moving while I follow up."

Why It Works:
- Shows confidence (you’re not flustered).
- Buys time to get the answer.
- Reinforces social proof (customer examples).

2. Tricky Situation: "The Prospect Says Your Competitor Does X Better"

Interviewer: "How do you respond when a prospect says your competitor is better?" Bad Answer: "Our product is actually better because..." (This starts a feature war.) Good Answer:

"I appreciate that feedback. Can you help me understand what specifically about [competitor’s X] is more valuable to you? Is it the speed, the UI, or something else? That way, I can show you how we address that need in a way that’s unique to your environment."

Why It Works:
- Digs for Decision Criteria (you might uncover a hidden requirement).
- Positions you as consultative (not defensive).
- Opens the door to differentiate (e.g., "We do X and Y, which your competitor doesn’t").

3. Demo Disaster: "The Tech Fails Mid-Demo"

Interviewer: "What do you do if the demo crashes?" Bad Answer: "I’d apologize and try to fix it." (This wastes time and kills credibility.) Good Answer:

"I’d say, ‘I want to respect your time, so let me switch to a pre-recorded video of this feature while we troubleshoot. Here’s the key takeaway: [summarize value].’ Then, I’d pivot to a discussion about their pain points or next steps."

Why It Works:
- Minimizes downtime (pre-recorded videos are your backup).
- Keeps the focus on value (not the glitch).
- Shows adaptability (you’re not flustered).

Quick Check Questions

1. Scenario: "The prospect says, ‘Your competitor does X for half the price.’ How do you respond?"

Answer:

"I understand cost is important. Can you help me understand what specifically about [competitor’s X] is most valuable to you? Is it the feature itself, or the outcome it delivers? That way, I can show you how we deliver that outcome in a way that’s tailored to your environment—and often at a lower total cost of ownership."

Why It Works:
- Avoids a price war (you’re not defending cost yet).
- Uncovers their true priority (maybe they care about support, not price).
- Opens the door to differentiate (e.g., "We include 24/7 support, which your competitor charges extra for").

2. Scenario: "The prospect’s CFO joins the demo last minute. How do you adjust?"

Answer:

"I’d start by asking the CFO, ‘What’s the most important outcome you’d like to see from this demo?’ Then, I’d pivot to show how our solution impacts revenue, cost savings, or risk reduction—using data from their industry. For example, ‘Companies like yours typically see a 15% reduction in audit costs with our tool. Here’s how that works.’"

Why It Works:
- Respects their time (they’re busy).
- Speaks their language (ROI, not features).
- Leverages social proof (industry benchmarks).

3. Scenario: "The prospect keeps interrupting with questions. How do you handle it?"

Answer:

"I’d say, ‘These are great questions—I want to make sure we cover everything. Let me address this one, and then we’ll dive deeper into [topic] so I can give you the full picture.’ This keeps the demo on track while making them feel heard."

Why It Works:
- Balances engagement with structure (you’re not ignoring them).
- Prevents derailment (you’re not letting them hijack the flow).
- Builds trust (you’re responsive, not rigid).

Last-Minute Cram Sheet (10 One-Liners)

1. Tell-Show-Tell (TST): Start with their pain, demo the solution, end with ROI.
2. Discovery > Demo: Always uncover pain, process, and success criteria before the demo.
3. Personalize or perish: Use their data, language, and industry examples.
4. MEDDIC: Qualify deals around Metrics, Economic Buyer, Decision Criteria, Decision Process, Pain, Champion.
5. Success Criteria: Agree on measurable outcomes upfront (e.g., "Reduce false positives by 30%").
6. Objection handling: Never argue—reframe (e.g., "What’s the cost of not solving this?").
7. Demo flow: Problem → Solution → ROI. No spoilers, just escalating stakes.
8. ⚠️ Demo trap: Never live-demo without a backup video. Glitches kill trust.
9. Close with next steps: End with "What’s the next step for you?"—not "Thanks for your time."
10. Champion power: Arm your champion with stories and data from the demo to sell for you.

Bonus: "If you remember nothing else, remember this: Prospects don’t buy products—they buy better versions of themselves."