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
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.
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.
Return on Token: Who Owns the Hours AI Gives Back [66]
This episode discusses the concept of "Return on Token" — ensuring that time saved by AI tools is intentionally allocated to specific business outcomes rather than absorbed into unmeasured activities. Leaders must decide what freed capacity will be used for before purchasing tools and track outcomes through managers rather than individual audits.
Your AI Policy Is a Competitive Disadvantage [65]
This episode explores why AI policies in revenue organizations are often competitive disadvantages, arguing that centralized corporate AI strategies neglect go-to-market needs and that most bans are outdated decisions rather than informed risk assessments. The hosts advocate for department-specific AI governance owned by RevOps, with explicit review dates that force legal to re-evaluate restrictions.