Leading PreSales | The Solution Engineering Leadership Show

SE managers and sales managers are structurally wired to conflict due to different optimization pressures and incentives, but this can be designed out through pre-deal alignment meetings, shared CRM records, joint qualification vetoes, and explicit acknowledgment of their different accountability timelines.

The episode discusses three diagnostic signals to identify managers who are individual contributors rather than developing leaders: closed-door one-on-ones only, rhetorical patterns of blame or over-ownership, and escalation emails with excessive CC'd recipients. The hosts emphasize that these behavioral patterns appear months before performance numbers decline, allowing early intervention.

SE Rockstars hosts in-person leadership events across European cities featuring keynotes, breakout sessions voted on by attendees, and networking dinners. The community uses a member portal with recordings, directories, and event management tools to connect 250+ solutions engineering leaders who face similar challenges.

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 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.

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.

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.

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.

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.

AI can effectively coach demo performance, but only when leaders provide rich context about their ICP, personas, and standards. Generic AI advice fails because it lacks situational awareness; the solution is building a shared, context-loaded assistant that scores demo transcripts against company-specific criteria rather than generic best practices.

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.

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.

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.

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.

SE leaders should prioritize building peer relationships by first understanding what stakeholders need before introducing processes or solutions. The key is deferring your perspective until you've earned credibility through genuine listening, then using that foundation to address inefficiencies and drive alignment.