The Metric No SE Leader Can Quote: Cost Per Won Deal [52]
SE leaders often debate deal strategy (focused entry vs. full bundles) without quantifying the actual cost per deal in SE effort and hours. By reconstructing 5 closed deals per archetype to calculate SE days invested against new ARR, leaders can make data-driven decisions while accounting for adoption rates and procurement cycles.
Summary
The episode opens with a real scenario where six SE managers spent 40 minutes debating whether to pursue focused entry deals or full bundles without referencing a single metric. When asked what one deal costs in SE hours, none could answer—a gap that prompted the core investigation. The hosts outline a practical methodology: identify a typical deal archetype (e.g., $100k ARR), count actual touchpoints (discovery meetings, demos, deep dives), and factor in hidden hours (prep, environment building, infrastructure costs). A director's reconstruction found focused deals required approximately 8 SE days each, while bundles consumed 22 days but generated nearly triple the ARR. However, the analysis revealed a critical blind spot: neither approach accounted for customer adoption or expansion likelihood. One team discovered that half their entry-level customers never adopted module 2, making the cheap deal economically meaningless when expansion failed. The model must therefore include two inputs—SE effort per deal and the probability that follow-on sales materialize. An additional complexity emerges for consumption-priced models, where contract value is unreliable; instead, actual ramped usage at month 9 better reflects true acquisition cost than the signature number. The recommended framework is to reconstruct 5 closed deals of each major deal shape, calculate net new ARR divided by SE days invested, and bring this single metric to pipeline reviews alongside adoption factors. A crucial caveat warns against converting this into a quota or scorecard, as that invites gaming behavior like skipping discovery.
About this episode
Nate's managers spent forty minutes arguing focused entry deals versus full bundles — and nobody could say what one won deal costs in SE effort. He and Ava build the cost model live, then Ava pokes the hole in it: land-and-expand only pays if the first module actually gets used.
Key Insights
- Six SE managers leading 200 solution engineers collectively could not quantify the cost of a single closed deal in SE hours, revealing that most deal strategy debates occur without foundational financial data.
- When a director reconstructed actual deals, focused entry deals consumed 8 SE days for $100k ARR while bundles consumed 22 days but generated $300k ARR, showing that raw effort per deal doesn't determine optimal strategy without considering contract value and adoption rates.
- Half of the company's land-and-expand customers never adopted the second module six months in, doubling the real cost per expansion deal and demonstrating that cheap initial deals are economically hollow if expansion never occurs.
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 as 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
Retire The Technical Win Trophy [71]
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.
Never Lie, Never Answer Reflexively [70]
Solution engineers often answer questions reflexively without understanding their context, which can damage deals even when the answer is technically honest. The key principle is distinguishing between genuine honesty and unfiltered explaining, and training SEs to ask clarifying questions before responding.
Stop Begging For Headcount [69]
An SE leader shares how building a capacity model instead of requesting headcount revealed that one AE was consuming 38% of pre-sales resources with below-average deal value, leading to better resource allocation and CRO buy-in without hiring three additional engineers.
When the ICP Moves, PreSales Pays the Bill [68]
When companies shift their Ideal Customer Profile (ICP), pre-sales teams bear the heaviest operational cost despite decisions being made at the executive level. Building a named second ICP with dedicated SEs before crisis hits—rather than after—enables survival when market conditions force a pivot.
Your CRO No Longer Wants a PreSales Department [67]
A CRO's desire to eliminate the presales department stems from revenue growth being concentrated in renewals and expansion, not new logos. The solution isn't renaming teams or restructuring, but strategically deploying SE skills to high-impact moments in the customer lifecycle with proper compensation alignment and narrow pilots before full organizational change.