Coach the Chain: From Symptom to a Number [51]
The episode teaches solution engineers to properly qualify deals by coaching the chain from symptom to quantified business impact. Instead of stopping at customer symptoms like 'reporting is slow,' SEs must dig deeper to uncover consequences, classify the impact as cost/revenue/risk, and attach a concrete number—which should inform go/no-go decisions rather than be argued away.
Summary
Tim introduces the episode as part of 'qualification week' in the Leading Pre-Sales podcast, which distills real coaching scenarios from SE Rockstars' work with 350+ solution engineers. The core problem presented is that SEs accept customer symptoms as pain points without qualification. The hosts, Nate and Ava, propose that commercial value only exists in two MEDIC fields: Identify Pain (the qualitative 'why change') and Metrics (the quantitative 'how much'). Value itself reduces to three categories: cost reduction, revenue increase, or risk improvement. The central coaching framework is a four-step chain: (1) identify the symptom, (2) determine what it costs today, (3) classify whether that cost is revenue, cost, or risk, (4) quantify it with a number. Using the 'slow reporting' example, the hosts demonstrate how jumping straight from symptom to invented numbers creates false business cases. Instead, when regional managers make pricing decisions on 9-day-old data, the true pain is a margin/risk question around how many decisions per month and average deal size. A real example is shared where an SE director had teams write the cost of inaction next to software price; in one million-euro deal, the cost of inaction was only 500,000 euros, prompting the team to walk away—a judgment enabled by proper metrics capture. The hosts emphasize that metrics fields aren't just CRM reporting fields but decision gates. They address practical objections, such as limited CRM fields, by suggesting SEs add consequence and number fields if needed. The distinction between qualification (subset of discovery) and discovery itself is clarified as fluid, with discovery outputs feeding qualification fields. The final actionable move is to pick one live deal per SE and coach the chain aloud, refusing to accept incomplete fields and—crucially—believing the number when it reveals the deal isn't worth pursuing. The hosts note that most teams argue with unfavorable numbers rather than accepting them as the system working correctly.
About this episode
Ava argues that value isn't a separate framework: it hides inside Identify Pain and Metrics. She and Nate break down the exact escalation from customer symptom to a euro figure — and why that number decides whether you should even stay in the deal.
Key Insights
- Customers naturally name symptoms rather than pains, and SEs typically accept and document these symptoms as if qualification has occurred, creating false business cases without understanding root consequences.
- The hosts argue that commercial value exists only in three forms—cost reduction, revenue increase, or risk improvement—and that all other framings are decoration that obscures true deal merit.
- Most SE teams capture numbers showing deals are not worth pursuing but then argue against those numbers rather than treating unfavorable metrics as evidence the system is working correctly and the deal should be abandoned.
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 SE 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
Your CRO No Longer Wants a PreSales Department [67]
A CRO's desire to eliminate the presales department stems from revenue growth being concentrated in renewals and expansion, not new logos. The solution isn't renaming teams or restructuring, but strategically deploying SE skills to high-impact moments in the customer lifecycle with proper compensation alignment and narrow pilots before full organizational change.
Return on Token: Who Owns the Hours AI Gives Back [66]
This episode discusses the concept of "Return on Token" — ensuring that time saved by AI tools is intentionally allocated to specific business outcomes rather than absorbed into unmeasured activities. Leaders must decide what freed capacity will be used for before purchasing tools and track outcomes through managers rather than individual audits.
Your AI Policy Is a Competitive Disadvantage [65]
This episode explores why AI policies in revenue organizations are often competitive disadvantages, arguing that centralized corporate AI strategies neglect go-to-market needs and that most bans are outdated decisions rather than informed risk assessments. The hosts advocate for department-specific AI governance owned by RevOps, with explicit review dates that force legal to re-evaluate restrictions.
ROI on Token: Stop Rewarding AI Usage [64]
AI usage metrics are vanity metrics that mask whether AI tools actually produce business value. Leaders must shift focus from measuring token consumption to defining specific outcomes and explicitly allocating reclaimed time, or efficiency gains will disappear into building more tools.
Your First 30 Days of AI: The Activation Playbook [63]
Leading Pre-Sales episode on AI adoption in solution engineering teams within the first 30 days. The hosts present four critical decisions leaders must make: selecting one standard environment, prioritizing data access (email, calendar, CRM), conducting a mixed bootcamp with AEs and SEs, and establishing a bi-weekly rhythm with named ownership to prevent tool sprawl and ensure sustainable, reusable implementations.