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.
Summary
Tim introduces a real scenario where an SE director proposed a six-person forward deployed team without a sales quota, triggering immediate pushback from finance. The conversation explores why FDEs shouldn't carry traditional quotas despite their commercial impact. Nate and Ava discuss how under consumption pricing models, adoption and usage directly translate to revenue—making time-to-first-value and usage ramp the two core metrics that matter. Rather than arbitrary quota numbers, these metrics appear on customer bills and reflect genuine commercial value. The debate surfaces whether FDEs should have compensation tied to usage ramp or team new business, with the trade-off being that pay-for-performance on expansion can shift engineer incentives toward sales behaviors that erode customer trust. The conversation establishes a financial test: each fully-loaded FDE (costing $220,000-$400,000 annually) must land one to two seven-figure contracts annually to justify the investment—a 10x return threshold. This creates a sharp focus: FDEs work with one to two customers at depth, not spread across ten accounts. A critical risk emerges when custom builds for one customer never feed back into the product, turning the team into an expensive services operation. The solution is a third scorecard metric: every custom build must generate a product ticket within two weeks, either for product to absorb or to formally document why it remains bespoke. This requires naming a product partner per pod to prevent tickets from disappearing into backlogs. The episode concludes with a pre-hire checklist: write a one-page cost justification, validate the 10x path before hiring, establish the product feedback loop on day one, and score only on time-to-first-value and usage ramp.
About this episode
Nate's finance team asked a new forward deployed team the obvious question: what's their quota? He and Ava work out how to score these engineers on time-to-first-value and usage ramp, set a pilot-to-contract test that covers their cost, and make sure field work feeds back into the product.
Key Insights
- Under consumption pricing models, time-to-first-value and usage ramp are commercial metrics because adoption directly correlates to when billing starts—making them quota-equivalent measures without being traditional sales targets.
- FDEs with pay-for-performance tied to expansion revenue begin demonstrating sales-like behaviors that erode customer trust, whereas measuring them on adoption and product feedback preserves the engineering relationship dynamic.
- An FDE team that generates custom builds without routing them back to product development functions as an internal consulting operation; preventing this requires mandatory product ticket creation within two weeks and a named product partner per team pod, or the feedback loop collapses into organizational debt.
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.