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.
Summary
The episode opens with a cautionary tale about a customer who built an internal contract review tool using AI, which failed when the underlying API model was deprecated after exactly one year. This story illustrates the hidden costs of building solutions internally. The hosts explain that most Build vs. Buy analyses fail because they focus on initial development costs, which are rarely the expensive part. The real expense lies in ongoing maintenance, security reviews, performance monitoring, interface and API changes, on-call support, compliance updates, and critically, organizational knowledge when the original builder leaves.
The speakers introduce an 'iceberg checklist' framework that captures everything below the waterline: maintenance, new use cases, security reviews, performance and uptime, interface and API changes, on-call support costs, compliance and regulatory changes, and succession planning risks. A major insight is that most SEs lead with security concerns when discussing build vs. buy because it 'sounds scary,' but the real financial leverage with CFOs is opportunity cost—the billable or productive work time spent building and maintaining the solution instead of doing the actual job.
The core solution presented is a standardized five-year cost model template comparing Build, Buy, and hybrid approaches side-by-side across years one through five. Rather than having SEs present a finished, vendor-favorable spreadsheet, the recommendation is to provide customers with just the rows and questions, allowing the customer's own finance lead to populate the data. This approach proved effective in a long procurement cycle where the customer's maintenance cost estimates actually exceeded the vendor's estimates, as they understood their own operational pain points better. Crucially, the template must include numbers and evidence that cut against the vendor's position, presented plainly in the same document, to maintain credibility when customers inevitably discover contradictory information.
The hosts also reference research showing that roughly one-third of companies skip buying SaaS solutions believing they can build with AI instead, and that SaaS price increases are rising at approximately 12-14% annually compared to 3-4% general inflation, which mathematically shifts the economics toward build solutions. Additionally, a small study showed developers perceived themselves as 20% faster with AI tools while actually being 20% slower, another uncomfortable truth that should be included in the analysis.
About this episode
Writing the first version of software was never the expensive part; running it is. Nate makes the case for a standard five-year TCO template and an iceberg checklist, and Ava pushes him to let customers fill it in themselves.
Key Insights
- The hosts argue that initial development cost is rarely the expensive part of build solutions; the actual financial burden comes from maintenance, security reviews, API deprecation handling, on-call support, and organizational knowledge loss when builders leave the company.
- A customer's own finance lead typically provides more accurate maintenance cost estimates than vendors because they understand their unique operational pain points, and these estimates often exceed vendor predictions, which can paradoxically strengthen rather than weaken the vendor's credibility when presented transparently.
- SaaS price increases averaging 12-14% annually versus 3-4% general inflation mathematically shifts the economic calculus toward building solutions with AI, explaining why roughly one-third of companies now skip software purchases in favor of internal development.
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.
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.