Your AI Doesn't Give Bad Demo Advice — You Gave It Nothing [53]
AI can effectively coach demo performance, but only when leaders provide rich context about their ICP, personas, and standards. Generic AI advice fails because it lacks situational awareness; the solution is building a shared, context-loaded assistant that scores demo transcripts against company-specific criteria rather than generic best practices.
Summary
The episode challenges the assumption that AI cannot coach demos effectively. It opens with a real example where someone asked AI for demo tips and received generic advice (focus on decision makers, don't let end users derail you, hit economic buyer motives first). While not wrong, this advice was useless because the prompt contained zero context about audience, deal stage, or sales motion. The hosts argue this generic guidance can actually be harmful—for example, telling an SE to focus on the economic buyer when facing five admins who want a specific workflow results in a disconnected conversation.
The core argument is that the problem isn't AI's capability but rather leadership's responsibility to feed it information. Two key structural elements must be in place: first, a centralized shared assistant loaded with company-specific knowledge (ICP, personas, demo standards, methodology); second, a system for SEs to upload demo transcripts and receive feedback scored against those internal criteria rather than generic books.
Nate and Ava discuss implementation, revealing that one director built this setup in a day and a half using existing enablement materials. The coaching should operate in two separate layers: structural decisions (who's in the room, pacing) and demo craft (opening, clicking, narration). The transcript analysis is highlighted as particularly powerful—by the third session, SEs can see concrete improvements like stopping unnecessary click narration. The hosts address concerns about standardization by proposing a split: team-owned base layer (non-negotiable standards) and SE-owned personal layer (how the assistant communicates with that individual). They acknowledge different team members need different coaching approaches. Finally, they clarify this augments rather than replaces human manager feedback—humans should provide judgment about context (like knowing the CFO's boss was replaced), while AI handles pattern detection in demos.
About this episode
Nate saw a one-line prompt produce textbook-generic demo advice, and a comment section full of people saying "it needs more context" without ever building any. He and Ava work out how SE leaders turn that context into a shared enablement asset — and what it does for coaching between 1:1s.
Key Insights
- The hosts argue that generic AI advice about demos is actively harmful when it lacks context—an SE told to focus on the economic buyer when facing end users creates a disconnected room, not a successful demo.
- Nate and Ava claim that companies have already written the necessary context (in enablement decks and standards) but haven't made it machine-readable, so the real leadership job is translating existing knowledge into a shared assistant's prompt rather than creating new content.
- The hosts contend that demo transcript scoring generates behavioral change faster than traditional enablement because it provides immediate feedback and demonstrates concrete improvement over multiple sessions, unlike deck-based training that asks for attention without returning value.
Topics
Transcript
Hey there and welcome to Leading Pre-Sales, the show for solution engineering leaders who want to build teams that drive revenue and not just demos. My name is Tim and I'm the co-founder of SE Rockstars and together with Jan, we've coached over 350 solution engineers and their leaders across several dozens of companies. Every conversation you hear on this show is based on real coaching situations, real challenges, real problems that as leaders like you are dealing with right now. None of this is made up. We use AI to bring these stories to life through our two hosts, Nate and Ava, but the insights come straight from the trenches. Each episode gives you one actionable takeaway you can…
Full transcript available for MurmurCast members
Sign Up to AccessMore from Leading PreSales | The Solution Engineering Leadership Show
The Loneliest Job in the Building [59]
The episode explores the SE Rockstars Pre-Sales Leadership Community, a peer network of ~250 solution engineering leaders across Europe that addresses the isolation of SE leadership roles. The community operates through monthly online sessions with breakout discussions and an optional WhatsApp group for rapid problem-solving, with strict governance to prevent vendor infiltration.
The Seven-Figure Promotion [58]
The episode examines why promoting high-performing individual contributors into first-line manager roles without proper preparation fails, costing organizations seven figures through lost productivity, departing talent, and compromised pipeline coverage. The hosts argue that training budgets and readiness gates must precede promotions, and that candidates should understand expectations before accepting the role.
Your SEs Don't Need the Price List. They Need the Metric. [57]
Solution engineers should understand the metric behind pricing (seats, transactions, credits) rather than memorize price lists, as this enables them to design solutions aligned with customer budgets and identify expansion opportunities. The episode emphasizes teaching SEs to estimate volume math and recognize when customer questions are actually about financial impact, not just technical capacity.
One Sentence: The Pricing Guardrail Every SE Team Needs [56]
SE leaders should implement a single scripted sentence when customers ask about pricing to prevent misstated numbers from anchoring negotiations. The sentence should deflect to the AE while offering value, reference published pricing when available, and be rehearsed by the team rather than just distributed in writing.
400 Licenses Is Not a Number [55]
Solution engineers often cannot articulate the dollar value of their deals, which undermines revenue-focused incentive plans and leads to accidental time allocation decisions. The episode argues that making deal value visible and mandatory in CRM systems, combined with explicit planning conversations about priority, is essential before modifying compensation structures.