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.
Summary
Leading Pre-Sales episode 92 addresses a critical challenge: when customers choose to build custom solutions instead of buying software. The hosts use real examples—a four-month customer approval workflow that was built in three weeks, and a weekend reporting module—to illustrate costly SE effort on deals that were lost to development anyway.
The core framework presented is distinguishing between "core" and "context" functions. Core functions are those directly tied to how a customer makes money (like a bank's risk model or retailer's pricing engine), where customers rationally want control and customization. Context functions support operations but don't directly create competitive advantage (like approval workflows or expense tracking). Within context functions, the critical differentiator is weight—lightweight context needs can often be built faster and cheaper than buying a full platform.
The hosts explain that build decisions aren't typically driven by cost alone but by speed and control. Customers want custom solutions live quickly, often tailored to their specific workflows. Standard software's baked-in best practices, while valuable for adoption and consistency, become weak arguments when customers are protecting core competitive differentiators.
The episode introduces a practical workflow: before build conversations, SEs should form a hypothesis—is this about cost or core capability? If it's context and lightweight, qualifying out becomes a strategic win rather than failure, provided the loss is logged for product to understand market gaps.
Leaders play a crucial role in cultural change. One host notes that signal about build losses often dies in organizational layers, so instituting tagging systems ("lost to lightweight build") and regular product reviews creates feedback loops. Critically, leaders must publicly and repeatedly say "let it go" in team settings, as SEs won't believe it's acceptable unless leadership explicitly validates walking away from certain deals.
About this episode
Nate brings a lens his managers now use on every build-risk deal: is the capability core or context, and is the need heavy or light? Ava pushes on when best practice should win, and they agree a lost-to-build deal is often product feedback, not an SE failure.
Key Insights
- The hosts observed that customers choosing to build custom solutions are rarely driven primarily by cost; speed and control over workflow are the actual drivers, with customers often shipping lightweight builds in days or weeks after months of vendor evaluation.
- The speakers argue that best practice arguments—a standard software vendor's core pitch—lose effectiveness for core business functions where customers expect to differentiate, but remain persuasive for heavy context functions like inventory or finance that benefit from embedded expertise.
- One host discovered through organizational testing that build losses often don't surface to product teams across larger companies, requiring deliberate tagging systems and quarterly reviews with product to identify whether market gaps represent genuine product problems rather than SE execution failures.
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
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.