Intro to Sales Engineering and Solutions Consulting: Creating Reusable Assets (Demo Scripts, ROI Calculators, Technical Briefs)

Creating Reusable Assets (Demo Scripts, ROI Calculators, Technical Briefs)

Creating Reusable Assets: The SE’s Force Multiplier

(Demo Scripts, ROI Calculators, Technical Briefs)

What This Is

Reusable assets are pre-built tools (demo scripts, ROI calculators, technical briefs) that let you scale your impact without reinventing the wheel for every deal. They’re critical because: - Speed: You close deals faster by reducing prep time (e.g., a pre-recorded demo snippet for a common objection).
- Consistency: Every prospect gets the same high-quality experience, even if you’re juggling 10 deals.
- Proof: Assets like ROI calculators or compliance briefs objectively prove value—especially in competitive POCs (e.g., a cybersecurity SE using a SOC 2 technical brief to outmaneuver a cheaper competitor during a compliance-focused evaluation).

Real-world scenario:
A prospect is evaluating your API security platform vs. a competitor. During the POC, they ask, “How does your solution handle zero-day threats compared to [Competitor]?” Instead of winging it, you pull up a pre-built technical brief with side-by-side comparisons, a demo script showing your zero-day response in action, and an ROI calculator proving your solution reduces breach costs by 40%. The prospect’s CISO (your Economic Buyer) signs the deal because you’ve removed doubt with reusable proof.

Key Terms & Frameworks

• Demo Script (aka "Demo Playbook"): A step-by-step guide for your demo, including talking points, transitions, and objection handling. Used to keep demos tight, repeatable, and aligned with the prospect’s pain points (e.g., a script for “reducing cloud costs” vs. “improving DevOps velocity”).
• ROI Calculator: A spreadsheet or interactive tool that quantifies the financial impact of your solution (e.g., “Our tool saves $200K/year in manual compliance audits”). Used in discovery and closing to justify price.
• Technical Brief: A 1–2 page document (or slide deck) that explains how your solution works, often with architecture diagrams, data flows, or compliance mappings (e.g., “How Our Tool Meets NIST CSF”). Used in POCs and security reviews to address technical objections.
• Battle Card: A competitor-focused asset with strengths/weaknesses, objection responses, and differentiation. Used in competitive deals to counter FUD (Fear, Uncertainty, Doubt).
• Discovery Template: A structured set of questions to uncover pain, metrics, and decision criteria (aligned with MEDDIC). Used in first calls to qualify deals.
• POC Playbook: A step-by-step guide for running a Proof of Concept, including success criteria, timelines, and stakeholder roles. Used to reduce POC failure risk (e.g., “If the prospect doesn’t engage with the tool in Week 1, they’re not serious”).
• MEDDIC: Qualification framework (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion). Used to prioritize deals and tailor assets (e.g., an ROI calculator for the Economic Buyer, a technical brief for the Champion).
• Challenger Sale: A sales methodology where you teach, tailor, and take control of the conversation. Used to frame the problem before presenting your solution (e.g., “Most companies waste 30% of cloud spend—here’s how we fix it”).
• Mutual Action Plan (MAP): A shared document outlining next steps, owners, and timelines. Used to align stakeholders and avoid “ghosting” (e.g., “By Week 2, we’ll review your compliance gaps with your security team”).
• Objection Handling Matrix: A cheat sheet of common objections (e.g., “Too expensive”) with responses and proof points. Used to prepare for pushback in demos and negotiations.
• Demo Flow: The sequence of your demo (e.g., Problem → Solution → Proof → Next Steps). Used to keep demos engaging and avoid “feature dumping.”
• Proof Points: Customer stories, case studies, or data that validate your claims (e.g., “Company X reduced downtime by 50%”). Used to build credibility in demos and ROI calculators.

Step-by-Step / Process Flow

1. Identify the Asset Type (Discovery → Qualification)

• Goal: Figure out which asset will move the deal forward.
• How:
• Use MEDDIC to diagnose the prospect’s needs:
  • Metrics: “What’s the cost of this problem?” → ROI Calculator
  • Decision Criteria: “What’s most important to you?” → Technical Brief (if technical) or Demo Script (if feature-focused)
  • Champion: “Who’s advocating for this internally?” → Battle Card (if competitive) or Mutual Action Plan (if multi-stakeholder)
• Sample questions:
  • “What’s the biggest risk if you don’t solve this problem?” (Uncovers Metrics for ROI calculator)
  • “Who else is involved in the decision?” (Identifies Economic Buyer for a tailored demo)
  • “What’s your current process for [problem]?” (Reveals gaps for a Technical Brief)

2. Build the Asset (Template → Customize)

• Goal: Create a reusable template, then tailor it to the deal.
• How:
• Start with a template (e.g., a generic ROI calculator for “cloud cost savings”).
• Customize with prospect-specific data (e.g., plug in their AWS spend, team size, or compliance requirements).
• Example:
  • ROI Calculator: Generic template → Add prospect’s “current cost of downtime” (from discovery) → Show “savings with our tool.”
  • Demo Script: Generic “security demo” → Add their specific compliance pain (e.g., “You mentioned SOC 2 is a priority—here’s how we automate evidence collection”).
• Pro tip: Store assets in a shared drive (e.g., Notion, Google Drive) with tags like #compliance, #cost-savings, #competitor-X.

3. Validate the Asset (Internal Review → Prospect Feedback)

• Goal: Ensure the asset is accurate, relevant, and persuasive.
• How:
• Internal review: Have a peer or manager check for:
  • Technical accuracy (e.g., “Does this ROI calculator use realistic assumptions?”)
  • Messaging alignment (e.g., “Does this demo script match our value prop?”)
• Prospect feedback: Share a draft with your Champion and ask:
  • “Does this address your concerns?”
  • “What’s missing?”
  • “Would this help you sell this internally?”
• Example:
  • You send a Technical Brief on “How We Meet GDPR” to your Champion. They say, “This is great, but our legal team cares more about data residency—can you add a section on that?” → Update the brief.

4. Deploy the Asset (Demo → POC → Close)

• Goal: Use the asset at the right time to advance the deal.
• How:
• Demo: Use a Demo Script to guide the conversation. Example:
  > “You mentioned downtime costs you $10K/hour. Let me show you how our tool reduces that by 70%—here’s the ROI calculator with your numbers plugged in.”
• POC: Use a POC Playbook to set expectations. Example:
  > “For this POC, we’ll focus on your top 3 compliance gaps. Here’s the success criteria—does this align with your goals?”
• Close: Use an ROI Calculator or Technical Brief to justify price. Example:
  > “Based on your $500K/year in manual audits, our $100K solution pays for itself in 3 months. Here’s the breakdown.”
• Competitive deal: Use a Battle Card to counter objections. Example:
  > “I know [Competitor] is cheaper, but they don’t support real-time threat detection—here’s a side-by-side comparison.”

5. Iterate & Reuse (Post-Deal Review → Template Update)

• Goal: Improve assets based on what worked (or didn’t).
• How:
• Post-mortem: After the deal closes (or is lost), ask:
  • “Which assets were most effective?” (e.g., “The ROI calculator sealed the deal”)
  • “What was missing?” (e.g., “We needed a case study for the CFO”)
• Update templates: Add new objections, metrics, or use cases to your assets.
• Example:
  • You lose a deal to a competitor. Your Battle Card didn’t address their “easier integration” claim. Update the card with:
  • Objection: “[Competitor] integrates with our SIEM in 1 click.”
  • Response: “Our API-first approach lets you integrate in 2 hours with 90% less custom code—here’s a customer example.”

Common Mistakes

Mistake 1: Building Assets in a Silo

• What happens: You create a demo script or ROI calculator without input from sales, product, or customers.
• Why it’s bad: The asset may be technically accurate but irrelevant to prospects (e.g., an ROI calculator that doesn’t align with their Metrics).
• Correction:
• Collaborate early: Run drafts by:
  • Sales: “Does this resonate with prospects?”
  • Product: “Are these features still accurate?”
  • Customers: “Would this have helped you make a decision?”
• Example: A cybersecurity SE builds a Technical Brief on “Zero Trust” but forgets to include a section on “legacy system compatibility.” A prospect’s Champion flags this as a deal-breaker.

Mistake 2: Over-Customizing (The “Snowflake Trap”)

• What happens: You spend hours tweaking an asset for one deal, making it unusable for others.
• Why it’s bad: You waste time and lose the “reusable” benefit.
• Correction:
• 80/20 rule: Build 80% generic, 20% customizable assets.
  • Example: An ROI Calculator with:
  • Generic tabs: “Cost of downtime,” “Labor savings”
  • Customizable fields: Prospect’s specific numbers (e.g., “Your team spends 20 hours/week on manual audits”)
• Pro tip: Use merge tags (e.g., [Prospect_Company]) in documents to personalize quickly.

Mistake 3: Ignoring the “So What?” Test

• What happens: Your asset is technically detailed but doesn’t connect to the prospect’s pain or metrics.
• Why it’s bad: Prospects tune out if they don’t see the relevance (e.g., a Technical Brief on “How Our Algorithm Works” vs. “How We Reduce False Positives by 90%”).
• Correction:
• Lead with impact: For every asset, ask:
  • “So what? Why should the prospect care?”
  • “Does this tie to their Metrics or Decision Criteria?”
• Example:
  • ❌ Bad: “Our tool uses machine learning to analyze logs.”
  • ✅ Good: “Our tool reduces false positives by 90%, saving your team 10 hours/week—here’s the ROI calculator with your numbers.”

Mistake 4: Not Testing Assets in Real Deals

• What happens: You assume an asset works because it looks good, but it flops in a live demo or POC.
• Why it’s bad: You lose credibility (e.g., an ROI Calculator with unrealistic assumptions).
• Correction:
• Pilot assets: Test them in low-stakes deals first.
• Gather feedback: After using an asset, ask:
  • “Did this help you make a decision?”
  • “What would make it more useful?”
• Example: You use a Demo Script for the first time and realize the prospect’s eyes glaze over during the “architecture deep dive.” You shorten it and add more proof points.

Mistake 5: Forgetting the “Next Step”

• What happens: You share an asset (e.g., an ROI Calculator) but don’t tie it to a clear next action.
• Why it’s bad: The deal stalls because the prospect doesn’t know what to do next.
• Correction:
• Always include a CTA: End every asset with:
  • “Next, let’s schedule a call with your CFO to review these numbers.”
  • “Here’s the POC timeline—does this work for your team?”
• Example:
  • ❌ Bad: You email an ROI Calculator with no follow-up.
  • ✅ Good: You email the calculator and say, “Based on these numbers, our solution pays for itself in 3 months. Let’s review this with your CFO—when’s a good time next week?”

SE Interview / Practical Insights

1. “Walk Me Through How You’d Build a Demo Script for [Product].”

• What they’re testing: Can you structure a demo that aligns with pain points and decision criteria?
• How to answer:
• Start with discovery questions to uncover pain:
  > “Before building the demo, I’d ask: ‘What’s the biggest challenge you’re facing with [problem]? How does this impact your team’s goals?’”
• Map the demo flow to the prospect’s Metrics and Decision Criteria:
  > “If they care about ‘reducing downtime,’ I’d start with a real-world scenario showing how our tool prevents outages, then tie it to their specific cost of downtime.”
• Include objection handling and proof points:
  > “I’d prepare for objections like ‘This seems complex’ by showing a customer case study where we reduced implementation time by 50%.”
• End with a CTA:
  > “The demo would end with a clear next step, like scheduling a POC or a call with their technical team.”

2. “A Prospect Says, ‘Your Competitor Does X for Half the Price.’ How Do You Respond?”

• What they’re testing: Can you differentiate and justify value without badmouthing competitors?
• How to answer:
• Acknowledge the objection (builds trust):
  > “I hear that a lot—price is always a consideration.”
• Reframe the conversation around total cost of ownership (TCO):
  > “Our solution might have a higher upfront cost, but let’s look at the long-term savings. For example, [Competitor]’s tool requires 2 FTEs to manage, while ours is fully automated—here’s the ROI calculator with your numbers.”
• Use a Battle Card to highlight differentiation:
  > “One thing our customers love is [unique feature]—[Competitor] doesn’t offer that. Here’s a side-by-side comparison.”
• Ask a question to uncover real concerns:
  > “Is price the only concern, or are there other factors we should address?”

3. “During a Demo, the Prospect Asks a Question You Don’t Know the Answer To. What Do You Do?”

• What they’re testing: Can you handle uncertainty without losing credibility?
• How to answer:
• Never guess or BS. Instead:
  • Acknowledge the question (shows confidence):

    “That’s a great question—I want to make sure I give you the right answer.”

    
    

  • Offer to follow up (buys time):

    “I don’t have that detail off the top of my head, but I’ll check with our product team and get back to you by EOD.”

    
    

  • Redirect to what you do know (keeps the demo moving):

    “While I look into that, let me show you how we solve [related problem]—this is something our customers love.”

    
    

  • Follow up fast (builds trust):

    “As promised, here’s the answer to your question about [topic]. Let me know if you’d like to dive deeper.”

    
    

4. “How Would You Use an ROI Calculator in a Deal Where the Prospect Doesn’t Have Clear Metrics?”

• What they’re testing: Can you uncover pain and create urgency even when the prospect isn’t data-driven?
• How to answer:
• Start with qualitative pain (e.g., “What’s the biggest frustration with your current process?”).
• Translate pain into metrics (even if rough):
  > “You mentioned your team spends a lot of time on manual audits. On average, how many hours per week would you say that takes?”
• Use industry benchmarks if they don’t have data:
  > “Based on similar companies, we’ve seen teams spend 15–20 hours/week on this. Does that sound right for you?”
• Build the ROI calculator together (engages the prospect):
  > “Let’s plug in some conservative numbers—if we assume 10 hours/week at $50/hour, that’s $26K/year. Our tool automates 80% of that. Does that resonate?”

Quick Check Questions

1. A Prospect Says, “We’re Happy with Our Current Vendor—Why Should We Switch?”

• How to respond:
• Acknowledge their satisfaction (avoids defensiveness):
  > “I’m glad your current solution is working for you—that’s great to hear.”
• Ask about gaps (uncovers pain):
  > “What’s one thing you wish your current vendor did better?”
• Share a proof point (social proof):
  > “A lot of our customers felt the same way until they realized they were missing [X]. For example, [Customer] switched because [reason]—here’s their story.”
• Offer a low-commitment next step (reduces friction):
  > “Would it make sense to run a quick side-by-side comparison to see if there’s a gap?”

2. During a POC, the Prospect’s Team Doesn’t Engage. What Do You Do?

• How to respond:
• Diagnose the issue (is it lack of interest, competing priorities, or misalignment?):
  > “I noticed the team hasn’t logged into the POC portal much—is there something we’re missing that would make this more valuable for you?”
• Realign on goals (remind them of the Metrics and Decision Criteria):
  > “At the start, we agreed the POC would focus on [X]. Is that still the priority, or has something changed?”
• Escalate to the Champion (if engagement is low):
  > “I want to make sure we’re delivering value. Can we loop in [Champion] to realign on next steps?”
• Offer a “POC Reset” (if needed):
  > “Would it help to restart the POC with a clearer timeline and success criteria?”

3. The Economic Buyer Says, “Your Price Is Too High—Cut It by 20% or We Walk.”

• How to respond:
• Avoid immediate discounting (protects margin):
  > “I appreciate you being upfront about budget. Before we talk price, let’s make sure we’re aligned on value—what’s the ROI you’re expecting from this investment?”
• Revisit the ROI calculator (justify price):
  > “Based on the numbers we discussed, our solution delivers [X] in savings. If we adjust the scope to hit your budget, what features would you prioritize?”
• Offer alternatives (e.g., phased rollout, smaller scope):
  > “One option is to start with a pilot for [specific use case]—that would reduce the upfront cost by 30%.”
• Ask for concessions (if you must discount):
  > “If we can adjust the price, would you be open to [longer contract, case study, reference call]?”

Last-Minute Cram Sheet

1. MEDDIC: Qualify deals by asking about Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion.
2. Demo Flow: Problem → Solution → Proof → Next Steps. ⚠️ Never start with features—lead with pain.
3. ROI Calculator: Always tie to the prospect’s Metrics (e.g., “Your downtime costs $X—here’s how we save you $Y”).
4. Technical Brief: Use in POCs to address Decision Criteria (e.g., “How we meet SOC 2”).
5. Battle Card: Prepare for competitive objections (e.g., “[Competitor] is cheaper” → “Here’s the TCO comparison”).
6. POC Playbook: Set success criteria upfront to avoid “zombie POCs.” ⚠️ If the prospect isn’t engaged in Week 1, they’re not serious.
7. Objection Handling: Acknowledge → Reframe → Prove → Ask (e.g., “I hear you—here’s a customer who felt the same way”).
8. Demo Traps:
9. ⚠️ Never live-demo without a backup video (glitches kill trust).
10. ⚠️ Don’t “feature dump”—focus on 1–2 key pain points.
11. ⚠️ Avoid jargon—explain in the prospect’s language (e.g., “reduces downtime” vs. “improves SLA compliance”).
12. Closing: Always end with a CTA (e.g., “Let’s schedule a call with your CFO to review the ROI”).
13. Reusable Assets: Build once, customize lightly, and iterate based on feedback. Store in a shared drive with tags (e.g., #compliance, #cost-savings).