The Training That Made Me Quit [73]
A solution engineering leader describes how excellent enablement training on value-based selling fundamentally changed his approach, but ultimately led him to quit when the organization's operating systems remained misaligned with what he'd learned. The episode explores the critical gap between training people and restructuring the systems they work within.
Summary
The episode features a conversation between hosts Nate and Ava discussing a guest's experience with transformative sales enablement training. The guest's company underwent a business model shift from selling low-margin hardware (priced in cents per unit) to enterprise software (priced at 400,000 euros). A tailored three-day training program was designed to address this specific challenge by placing the two business models side-by-side, revealing the fundamental difference in sales logic: production efficiency versus demonstrating customer ROI on high-ticket items.
The training's effectiveness came from its specificity and design. Rather than generic off-the-shelf content, the curriculum directly addressed the subsidiary's actual problem. The format was also deliberate: two blocks of 1.5 days each, spaced four weeks apart, rather than a traditional five-day bootcamp. The gap between blocks was intentional—it allowed participants to attempt new approaches in real deals, experience failures, and return with concrete problems to solve. The second block was practical, focusing on role plays and drafting real customer emails, ensuring participants left with artifacts rather than abstract concepts.
However, the story's turning point reveals a critical leadership failure. Despite being trained to sell on business value, the guest found himself working within an organization whose entire operating system still reinforced the old pricing-per-unit mentality: pricing approvals, compensation plans, and deal review processes all pointed backward. After three years of this misalignment, the guest quit to find an organization where the operating system matched the training. The guest acknowledges that this was a leadership failure, partly their own, for not recognizing that enablement cannot exist in isolation.
The episode concludes with a key recommendation for leaders: before approving any enablement program, identify one critical change required in the organization's operating system to support it, set a public date for that change, and communicate it to the team. Without visible systemic change, training fades quietly and people leave—though they leave better than they arrived.
About this episode
Nate tells the story of a value-selling programme that permanently changed how he thought about price -- and why, three years later, it was the reason he left the company. He and Ava dig into how to design enablement around a real business model shift, and what has to change around it afterwards.
Key Insights
- The guest claims that putting two business models side-by-side using the company's own financial data created a genuine insight that generic case studies never achieved—the realization that selling enterprise software requires justifying ROI rather than competing on unit cost efficiency.
- The guest argues that the effectiveness of enablement training directly depends on its specificity to an actual business problem rather than generic content, and that the format of spaced learning blocks with gaps for real-world application produces better retention than condensed bootcamp-style training.
- The guest demonstrates that even excellently designed enablement creates organizational friction when the company's operating systems—including pricing approval processes, compensation structures, and deal review mechanisms—remain misaligned with the new selling approach, ultimately driving talented people to leave.
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 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.