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.
Summary
The episode addresses a common frustration: sales leadership rolling out qualification frameworks without including SE leaders in the planning process. Rather than treating this as a governance complaint, the hosts reframe it as an opportunity. When a company invests in teaching a shared vocabulary (like MEDDICC elements: metrics, economic buyer, champion, etc.), it creates alignment potential—but only if SEs are involved to ensure consistent meaning across the organization. The discussion reveals that shared vocabulary often fails because only half the organization attends training, leading to different interpretations of key terms like 'champion.' The hosts argue that SE leaders should not try to own all framework elements, but instead strategically claim 2-3 letters where they provide unique value. The recommended approach is claiming metrics and identify pain, with co-ownership of decision criteria (particularly the technical side) and champion. The practical payoff comes from using these properly-filled fields as an engagement gate: SEs should refuse to engage with deals that lack clear metrics or pain indicators, signaling deal readiness through the shared framework rather than making subjective judgments. For larger organizations with SE directors, the key is ensuring those directors know which letters to claim before training sessions occur, with a simple one-sentence directive focused on volunteering for specific roles rather than requesting broader governance.
About this episode
Ava keeps meeting PreSales leaders whose sales org rolled out MEDDICC and never invited them. She and Nate work out which letters SEs actually own — and how to claim a seat at that table without turning it into a turf war.
Key Insights
- The hosts argue that when only half an organization attends qualification training, the same words get shared but their meanings diverge—one team's 'champion' meant someone who likes the company while another's meant someone willing to spend political capital, and this gap widens with partial adoption.
- Nate claims that SEs own the technical criteria side of decision criteria because they reshape customer requirements lists from competitor websites into actual needs on the second call, while AEs primarily own the commercial and budget cycle components.
- The hosts contend that a champion often trusts the SE more than the AE specifically because the SE isn't the one asking for the purchase order, giving SEs unique leverage in champion relationships that wouldn't be obvious without explicit discussion.
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
The Iceberg Under Every Build Deal [91]
Solution engineering leaders need a standardized five-year cost model to evaluate Build vs. Buy decisions in the AI era, grounded in hidden maintenance costs and opportunity expenses rather than vendor pitches. The key is creating an 'iceberg checklist' of often-overlooked costs and having customers co-create the financial analysis rather than presenting a pre-built case.
Leaderboards, Not Cameras [89]
The episode examines why AI adoption dashboards and leaderboards often fail to drive behavior change, and proposes an alternative approach: publicly sharing AI workflows that actually shipped on real deals, ranked by peer reuse rather than usage metrics.
Your SEs Just Inherited the Customer's Bill [88]
Solution engineers must own usage estimation and sizing in consumption-based pricing models, even though they don't set prices. When SEs fail to accurately estimate how often workflows trigger, customers face billing surprises that damage relationships and renewals.
Rebrand or Real Role? The FDE Test [86]
The episode examines whether Forward Deployed Engineers (FDEs) represent a genuinely different role from Solution Engineers or merely a rebranding strategy. Through analysis of real job postings and market trends, the hosts present a three-question test to distinguish authentic FDE positions from SE roles with inflated titles.
No Quota, Still Commercial [85]
Forward Deployed Engineers (FDEs) should be measured on time-to-first-value and usage ramp rather than traditional sales quotas, with compensation tied to commercial outcomes that directly correlate to revenue under consumption pricing models. Success requires a disciplined 10x cost-recovery model, a defined pilot-to-contract path, and mandatory product feedback loops to prevent FDE teams from becoming expensive consulting operations.