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.
Summary
Tim from SE Rockstars introduces a podcast episode featuring hosts Nate and Ava discussing a common SE leadership challenge: requesting headcount. The episode is framed around a real coaching situation where an SE leader attempted to justify a request for three additional SEs by presenting slides and quotes from tired engineers, only to have the CRO challenge whether the existing 12 SEs were being deployed on the right deals. Rather than accepting defeat, the leader built a simple capacity model using one CRM field to track effort per opportunity across six weeks, categorized into four effort buckets (under 5 hours, up to 15, up to 40, more than 40). This straightforward spreadsheet pivot table revealed a critical inefficiency: one AE was consuming 38% of total pre-sales capacity despite having the third-lowest closed ACV, and three SEs had already sensed this problem without data to back it up. The leader implemented this tracking method specifically as an opportunity-level post-engagement assessment rather than a timesheet, which proved crucial for adoption and data quality. The conversation then shifts to qualification gates, with discussion of whether a 25% win probability threshold is appropriate. The leader notes that while such a gate makes sense for general pipeline deals, strategic named accounts require different treatment with deliberate upfront capacity allocation decisions. This distinction eliminates the false narrative of a universal SE-to-AE ratio, recognizing instead that ratios vary dramatically (1:1 for high-value strategic accounts versus 1:20 for volume business with brief demos). Once the capacity model was in place, the leader identified efficiency gains: 15% reduction in custom prep for first demos and enabled two AEs to run standard first calls independently (with the caveat that AEs running custom demos can damage technical credibility later in the cycle). When presenting this data to the CRO showing consumption per rep against ACV per rep, the executive reallocated resources without being asked, resulting in one additional hire instead of the requested three, while covering more deals overall. The episode concludes with actionable recommendations: implement a capacity tracking system for a full quarter before sharing results with leadership, present reallocation proposals rather than complaints, and ensure sufficient data collection before drawing conclusions.
About this episode
Ava asked her CRO for three more SEs and got one question back: prove the twelve you have are on the right deals. She rebuilt the ask as a capacity model — and found one AE eating 38% of her team's hours.
Key Insights
- The speaker discovered that one AE was consuming 38% of pre-sales capacity while having below-average deal value, a problem three SEs had sensed for months but couldn't quantify without data.
- The leader argues that implementing a simple opportunity-level effort tracking system (not a timesheet) with four broad effort buckets can identify efficiency problems within a single quarter without requiring expensive tooling or dashboard builds.
- The speaker contends that universal SE-to-AE ratios are misleading; strategic named accounts warrant 1:1 ratios with deliberate upfront capacity allocation, while volume business with standard demos may run 1:20 or higher ratios, and qualification gates should reflect these different deal types.
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
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.
Engineering Is the Entry Ticket [84]
Forward-deployed engineering engagements often fail due to poor discovery, scoping, and stakeholder management rather than technical deficiencies. Engineering skills are necessary to enter the room, but success depends on identifying success criteria, mapping stakeholders (especially those who lose if the project succeeds), and having leadership cover to push back on misguided requests.