Hours Saved Is Not Money Saved [81]
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.
Summary
Tim introduces the Leading Pre-Sales podcast, which uses real coaching situations to provide actionable insights for SE leaders. The episode features hosts Nate and Ava discussing a common mistake in sales business cases: calculating savings by multiplying hours saved by an hourly rate, which produces a meaningless number if those employees remain on payroll after go-live.
The core problem is that freed capacity isn't money unless something concrete happens with that time. The hosts outline several approaches: First, SEs should ask the buyer what the person will do with reclaimed hours—if a sales ops person saves 18 hours per week, those hours could be spent building territory plans for reps, which connects to pipeline and revenue. Critically, the buyer must provide this answer, not the SE, so it becomes the customer's commitment and financial assumption, not the vendor's speculation.
The only scenario where hours truly equal money is with contractors: if freed capacity means temps aren't renewed, an actual cost line disappears. The hosts identify three valid financial arguments: (1) error cost—fixing existing mistakes that have quantifiable financial impact, (2) avoided hiring—only credible when the customer is growing and has approved headcount in their budget cycle, and (3) removing an approved cost line from their existing plan. The episode warns against partial or misleading data, such as personnel costs that don't account for contractors booked on separate budget lines.
The recommended practice is to audit all business cases for the question: "Which cost line shrinks?" If none does, rewrite it as freed capacity and require the buyer to articulate the downstream use. Leaders should embed this standard into deal reviews so SEs can't move forward without answering it.
About this episode
Ava's SE brought a business case built on hours saved times an hourly rate, but the people were still on the payroll after go-live. Nate and Ava work out how to coach SEs to turn freed capacity into revenue, error cost, or avoided hiring that finance will actually believe.
Key Insights
- The hosts argue that multiplying hours saved by hourly rate produces a financially meaningless number because if employees remain on payroll post-implementation, no cost line actually shrinks.
- The speakers claim that freed capacity only has financial value when the buyer explicitly states what activity those freed hours will be redirected toward, making it the customer's commitment rather than vendor speculation.
- The hosts assert that hours saved genuinely equals money saved only in contractor scenarios where non-renewal is possible, or when the calculation addresses quantifiable error costs or approved headcount in the buyer's budget cycle.
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.