When 'Show Nothing Extra' Becomes Handcuffs [54]
The episode examines why the directive "show nothing they didn't ask for" is problematic leadership advice for solution engineers. Instead of imposing restrictive rules that eliminate judgment, leaders should move discovery decisions upstream and have SEs explicitly state their scope choices to customers.
Summary
Tim introduces a coaching situation where an SE director issued a regional instruction to keep demos minimal, show nothing extra, avoid roadmaps, and focus on closing deals. While this directive appears to address real problems—bloated 40-minute demos where customers nod politely without understanding what problem was solved—Tim explains that over-correcting with rules is ineffective leadership.
The core argument is that imposed focus through rules is different from actual focus. Rules replace judgment rather than creating it, and they prevent SEs from hearing customer needs they're not permitted to address. Tim illustrates this with an example of selling compensation management software where a customer mentioned complex product quoting needs, which seemed like upselling but was actually a legitimate related problem.
The solution involves moving scope decisions upstream into discovery rather than banning symptoms. Before building any demo, SEs should document two things: what the customer thinks they need and what the team actually heard they need. This wider discovery supports a narrower, more focused demo because good discovery questions help customers understand their own problems better, not because they add modules.
Tim also identifies hidden structural problems: compensation targets and cross-sell bonuses can drive SEs to push unwanted modules, making it a system design issue rather than a demo coaching problem. Regarding the "no roadmap" directive, Tim challenges the assumption that decision makers won't be in rooms—many founders and managing directors participate directly in evaluations.
The recommended practice is to replace the rule with one line in the demo prep template: what the team heard beyond today's scope and what they're consciously leaving out. The SE writes it, the manager reviews it (but doesn't write it), and crucially, the SE must state this scope decision aloud to the customer in the first three minutes. If the team cannot articulate the decision verbally, it wasn't a decision—it was just following a rule.
About this episode
Nate brings a coaching note that told a whole region to show nothing the customer didn't ask for, and argues that imposed focus isn't focus at all. He and Ava rebuild it as a scope decision made in discovery, out loud, with the customer in the room.
Key Insights
- Imposed focus through rules replaces judgment rather than creating it, causing SEs to stop hearing customer needs they aren't allowed to act on.
- When SEs push unwanted modules, the problem is often upstream in compensation design and target agreements, not in demo coaching.
- Wider discovery conversations lead to narrower, more focused demos because good discovery questions help customers understand their own problems better, allowing the team to consciously choose scope rather than hide it.
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.