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.
Summary
Tim and the Leading Pre-Sales team discuss a critical gap in SE enablement: the distinction between knowing prices versus understanding the metrics that produce those prices. The episode opens with two real scenarios illustrating costly misalignments—an SE missing that a customer's scalability question was really about invoice size, and a renewal failing when finance discovered tripled usage on an invoice without prior modeling.
The hosts identify two separate skills: (1) knowing today's prices, which is explicitly NOT the SE's job because once a number leaves an SE's mouth in front of procurement, it becomes an anchor for months of negotiation; and (2) understanding the underlying metric (seats, credits, transactions, instances), which IS the SE's job and is rarely taught in enablement.
They explain why price lists are unlearnable at scale—from mid-market spreadsheets with 50+ line items to enterprise SKU lists so large they could take a week to scroll—while the metric itself is always one sentence. However, SEs need order-of-magnitude awareness: knowing whether a midsize customer lands around $100K versus $8K versus $2M annually, because without this, solutions architectures become untethered from budget reality.
The teaching methodology proposed is a 40-minute whiteboard session per business model, repeated twice yearly and involving AEs to "catch the lies." The session answers three questions: What are we selling? Which line item does it land on? How does the number get built—what pushes it up, what pulls it down? The harder muscle to build is volume estimation: making SEs do arithmetic out loud (tickets per month × automation potential × earnings per unit) to move from metric recitation to actual forecasting ability.
The conversation extends to why this matters for modern go-to-market: signature deals are now the kickoff, not the finish line. Expansion revenue requires SEs to reframe conversations from "we automate support" to "you're at 5% adoption, here's the road to 30%," which creates coverage model tensions at scale but is worth the organizational argument. The episode concludes with an immediate action: pick one business model, run the 40-minute session, then have every SE estimate volume math on one live deal aloud in front of peers, using ranges rather than precise figures (the word "roughly" signals appropriate uncertainty while precision stays with whoever owns the quote).
About this episode
Ava's SE told a customer the product "just scales" - and missed a ten-x volume question. She and Nate split pricing knowledge into two very different skills and show which one every SE has to own.
Key Insights
- Once a price figure leaves an SE's mouth in front of procurement, it becomes an anchor that can trap the vendor into months of self-negotiation, which is why SEs should never answer specific price questions.
- SEs struggle with consumption-based pricing not because they can't recite the metric, but because they lack practice doing volume arithmetic out loud (estimating tickets per month × automation rate × earnings per unit), and silence rather than ugly estimates is the actual problem.
- The shift from signature-based to expansion-based revenue models fundamentally changes what story SEs need to tell—from 'we automate support' to 'you're at 5% adoption, here's the road to 30%'—which creates unresolved tension between the narrative requirement and traditional coverage model capacity planning.
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
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.
The Metric No SE Leader Can Quote: Cost Per Won Deal [52]
SE leaders often debate deal strategy (focused entry vs. full bundles) without quantifying the actual cost per deal in SE effort and hours. By reconstructing 5 closed deals per archetype to calculate SE days invested against new ARR, leaders can make data-driven decisions while accounting for adoption rates and procurement cycles.
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.
Sales Rolled Out MEDDICC Without You [50]
When sales teams implement qualification frameworks like MEDDICC without including solution engineering leaders, it creates an opportunity rather than a problem. SEs should strategically claim ownership of specific framework elements—particularly metrics, identify pain, decision criteria, and champion—and use these as engagement gates before assigning resources to deals.
MEDDICC Without a Quality Bar Is CRM Theater [49]
A sales leader discovered that their team's MEDDICC CRM entries were generic and indistinguishable across different customers, revealing that the problem wasn't the framework itself but rather the absence of a defined quality standard. The solution involves creating segment-specific one-page standards that show both strong and weak examples, then reinforcing them through existing meetings rather than formal training programs.