Leading PreSales | The Solution Engineering Leadership Show

Leading PreSales | The Solution Engineering Leadership Show

Podcast43 episodes summarized

MurmurCast publishes AI-generated summaries of Leading PreSales | The Solution Engineering Leadership Show’s Podcast episodes — 43 summarized so far, covering Build vs. Buy Decision Framework, Core vs. Context Business Functions, SE Leadership and Team Culture, Product Feedback and Market Signals, Sales Qualification Strategy, Lightweight vs. Heavy Custom Development. Each summary distills the key insights, topics, and takeaways so you can decide what’s worth your time before pressing play.

Core vs. Context: When Your SEs Should Let a Build Deal Go [92]

5mNov 20, 2026

The episode teaches solution engineering leaders to distinguish between core and context business functions when customers consider building custom solutions versus buying software. SEs should let lightweight, context-focused builds go while fighting harder for core capabilities, and leaders must publicly validate this approach to change team culture.

DiscussionInsightfulBuild vs. Buy Decision FrameworkCore vs. Context Business FunctionsSE Leadership and Team Culture

The Iceberg Under Every Build Deal [91]

5mNov 18, 2026

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.

InsightfulDiscussionBuild vs. Buy decision frameworksTotal cost of ownership (TCO) modelingHidden costs of custom-built solutions

Leaderboards, Not Cameras [89]

6mNov 13, 2026

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.

StoryInsightfulAI adoption measurement and metricsLeaderboard design and gamification risksPeer visibility vs. surveillance in driving behavior change

Your SEs Just Inherited the Customer's Bill [88]

6mNov 11, 2026

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.

StoryDiscussionConsumption-based pricing models and SE accountabilityUsage estimation and sizing accuracy in discoveryDivision of responsibilities between SEs, AEs, and deal desk

Rebrand or Real Role? The FDE Test [86]

6mNov 6, 2026

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.

ResearchOpinionForward Deployed Engineers vs. Solution Engineers distinctionRole definition and career titling trendsCompensation structures and market positioning

No Quota, Still Commercial [85]

6mNov 4, 2026

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.

DiscussionInsightfulForward Deployed Engineer (FDE) team structure and metricsQuota vs. consumption-based performance measurementFinancial justification and cost recovery models

Engineering Is the Entry Ticket [84]

6mNov 2, 2026

Forward-deployed engineering engagements often fail due to poor discovery, scoping, and stakeholder management rather than technical deficiencies. Engineering skills are necessary to enter the room, but success depends on identifying success criteria, mapping stakeholders (especially those who lose if the project succeeds), and having leadership cover to push back on misguided requests.

DiscussionStoryForward-deployed engineering failuresDiscovery methodology and stakeholder managementSuccess criteria and scoping in pre-sales

Dream Big, Then Pull the Brake [83]

6mOct 30, 2026

The episode explores how SE leaders should approach build versus buy decisions by starting with desired outcomes rather than constraints, and using a structured decision-making process with time-boxed exploration, a designated decision-maker, and evidence-based prioritization against actual bottlenecks.

DiscussionInsightfulBuild versus buy decision-makingConstraint-first versus outcome-first design philosophyStructured innovation management with guardrails

Stop Waiting Weeks: Make Your SE Team AI-Self-Sufficient [82]

6mOct 28, 2026

AI assistants can enable solution engineers to self-serve work that previously required weeks of cross-team dependencies, such as creating landing pages and drafting case studies. The key is establishing templates and guardrails approved by other departments upstream, rather than giving SEs unrestricted access, to balance speed with governance.

DiscussionInsightfulAI-enabled self-service workflowsCross-functional dependencies and bottlenecksTemplate-based governance and guardrails

Hours Saved Is Not Money Saved [81]

6mOct 26, 2026

The episode explains why "hours saved" doesn't equal money saved in business cases, and teaches solution engineers to instead identify which actual cost lines shrink or ask buyers what they'll do with freed capacity. The hosts emphasize that finance teams need to see real financial impact, not speculative time savings.

InsightfulDiscussionBusiness case errors and financial justificationHours saved vs. actual cost reductionFreed capacity and customer commitment

The €1,000 Contradiction: Don't Promise Enablement You Haven't Funded [80]

6mOct 23, 2026

The episode critiques a job posting that promises an ambitious enablement mandate with insufficient budget (€1,000/year for training), arguing that posting mandates without adequate funding creates a contradiction that damages employer credibility. The hosts discuss how to align budget visibility with job posting promises and advocate for transparent, regional-specific benefit listings.

DiscussionOpinionJob posting authenticity and budget alignmentEnablement mandate vs. resource allocation mismatchEU Pay Transparency Directive implications

Head of SE or Jack-of-All-Trades? Scope-Test the Role Before You Sign [79]

5mOct 21, 2026

In this episode of Leading Pre-Sales, hosts Nate and Ava analyze a job posting for a second-line solution engineering head role with 15 reports and two existing team leads. They reveal how job descriptions often conflate multiple functions and offer a practical framework: split responsibilities into a concrete 12-month operating year and a 3-year vision, identifying the peer owner for each item to prevent scope creep.

DiscussionInsightfulJob description scope and realistic role definitionSecond-line SE leadership responsibilitiesFunction ownership and avoiding scope creep

Your Job Ad Is a Sieve With No Holes [78]

6mOct 19, 2026

Job ads function as filters to self-select candidates, not marketing brochures. The episode analyzes what a real job posting does well (specific compensation bands and active skill tasks) and poorly (vague adjectives like "AI curiosity" and missing success metrics), providing concrete rewrites to improve candidate quality.

InsightfulDiscussionJob ad design as a filtering mechanismCompensation transparency in job postingsActive skill demonstration tasks in recruitment

The 18-Month Goodbye: Why Your Best SE Leaves a Team They Love [77]

6mOct 16, 2026

This episode explores why high-performing solution engineers leave teams they genuinely enjoy, using the real case of Priya who departed after 18 months because she couldn't see a clear path to leadership. The hosts argue that vague growth promises and informal mentoring without real authority create a false waiting room, and that honest conversations about actual timelines and available seats are essential to retention.

StoryInsightfulSE retention and career progressionThe myth of informal leadership as a proving groundHonest communication about advancement timelines

Hire the Slope, Not the Checklist [76]

6mOct 14, 2026

The episode explores how to evaluate candidate gaps during hiring by distinguishing between closable skill gaps (language, product knowledge, demo ability) and non-closable character gaps (curiosity, initiative). The key principle is that hiring managers should standardize gap remediation into offer packages with clear ownership, budget, timeline, and accountability rather than hoping gaps resolve organically.

DiscussionStoryHiring and candidate evaluationClosable vs. non-closable skill gapsStandardized vs. flexible interview formats

The Long Leash: Why Great SEs Drown After Promotion [75]

5mOct 12, 2026

Promoting high-performing solution engineers to management roles without structured onboarding and coaching creates hidden risks, as confident new managers mask their gaps and struggle silently. The episode outlines a practical framework including 90-day phase plans with named milestones, explicit commercial training, and mentorship from status-indifferent advisors to prevent newly promoted managers from becoming overwhelmed and ineffective.

DiscussionStoryPromotion without ramp creates hidden riskWhy high performers mask their leadership gaps90-day phase plans with milestones

Your Best SE Won't Leave Over Money — They'll Leave Over the Ceiling [74]

5mOct 9, 2026

Top SEs leave due to unmet career ambitions and unclear ceilings, not primarily over compensation. Leaders must have honest conversations twice yearly about what employees are optimizing for and whether that opportunity genuinely exists in the organization within 18 months.

DiscussionInsightfulEmployee retention in solution engineeringCareer ambition and growth ceilingsHonest leadership communication

The Training That Made Me Quit [73]

6mOct 7, 2026

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.

StoryInsightfulEnablement program design and effectivenessBusiness model transformation and sales strategyOrganizational systems alignment

Hire the Second Version, Not the First [72]

5mOct 5, 2026

The episode discusses redesigning SE hiring to evaluate coachability rather than polish by introducing a two-stage interview process: an initial coaching session with one manager, followed by a panel evaluation one week later, scoring the gap between versions rather than absolute performance.

DiscussionStorySE hiring process redesignCoachability assessment over polishTwo-stage interview loop (dry run plus panel)

Retire The Technical Win Trophy [71]

6mOct 2, 2026

The episode critiques celebrating technical wins too early in the sales cycle, arguing that a technical checkpoint means nothing if the deal ultimately fails. The hosts propose redefining technical wins as validation that you're still in contention (one of 2-3 vendors) and establishing specific post-POC activities rather than retiring the metric entirely.

DiscussionInsightfulMisaligned incentive structures in sales organizationsRedefining technical wins as checkpoints, not endpointsSE engagement during later sales cycle stages
Page 1 of 3Next

Get AI summaries like this delivered to your inbox daily