Dream Big, Then Pull the Brake [83]
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.
Summary
In this episode of Leading Pre-Sales, hosts Nate and Ava discuss a common dilemma SE leaders face: when should you build custom tools versus buying existing solutions? The conversation begins with a relatable scenario where an SE leader realizes their bought POC platform has limitations, leading their team to create workarounds through spreadsheets, scripts, and makeshift solutions. One SE named Priya built a rough prototype of an improved POC workspace in an afternoon, prompting the leader to reconsider the build versus buy decision.
The core insight presented is that most leaders evaluate tool ideas by starting with constraints—security reviews, data protection, performance requirements—which kills innovation before it has a chance. Instead, the recommended approach is to reverse this process: first define the desired outcome and what customers should experience, then treat security and data protection as problems to solve once you understand what you're protecting. This fundamentally changes the design philosophy from building the minimum to pass review to building the right solution and making it safe.
However, the episode emphasizes the critical need for structural guardrails. The leader introduces Marcus, a senior SE who serves as the decision-maker. The process involves a time-boxed exploration session (1-2 hours) where innovation happens without constraints, followed by Marcus asking a single qualifying question: "Is this our biggest bottleneck right now?" The episode illustrates why this matters through a cautionary example where two senior SEs spent most of a quarter building a custom demo data generator while their region's competitive win rate declined—the build idea wasn't addressing the actual biggest problem.
To distinguish genuine platform failures from "shiny toy syndrome," the leader tracks workarounds systematically: when the same workaround appears three times in a month, it indicates a pattern. Additionally, each SE logs one line every Friday documenting features customers wanted in POCs but couldn't access. This structured logging creates evidence rather than relying on informal complaints in Slack. Priya's prototype gained traction because 12 SEs had logged the same gaps repeatedly over weeks.
The final framework presented is: give build ideas a time-boxed session with no constraints, designate one person as the decision-maker, ask if it's the biggest bottleneck, and if not, park it while continuing to log evidence. When the "couldn't do it" log grows significantly, the idea returns to the table with data backing its importance.
About this episode
Ava's team kept duct-taping workarounds onto a bought POC platform until one SE built the tool she actually wanted in an afternoon. Nate pushes back on skipping constraints, and together they work out how to pair unconstrained dreaming with a named brake so build ideas don't turn into distractions.
Key Insights
- Leaders who start tool evaluations with constraints (security, compliance, performance) tend to kill innovation prematurely, whereas starting with desired customer outcomes and treating safety as a downstream problem leads to better solutions that are then secured appropriately.
- The same workaround appearing three times within a month signals a genuine platform limitation worth investigating, as it indicates a pattern rather than isolated incidents.
- SE teams can spend significant time building tools that address appealing problems rather than their biggest actual bottleneck, exemplified by the cautionary case where a well-built demo data generator was completed while competitive win rates declined due to unaddressed handoff issues.
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
Core vs. Context: When Your SEs Should Let a Build Deal Go [92]
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.
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.