SE Capacity Planning
Definition
The process of allocating Sales Engineer hours across active deals based on deal value, win probability, technical complexity and SE skill fit. SE capacity is typically the bottleneck on enterprise-segment growth — every committed deal claims 40-120 SE hours, and there are only ~1,800 productive hours in an SE's year.
Why benchmarks do not transfer
Three variables dominate load and they vary more between companies than the published ratios do: technical intensity per deal, how much of the work repeats across deals, and how much non-deal work the engineer absorbs — enablement, escalations, answering product questions.
A calculation against your own data
- Estimate end-to-end SE hours for ten recent evaluated deals. Ten is enough to see the distribution.
- Use the shape, not the average. Technical intensity is rarely normally distributed; staffing to the mean guarantees the tail lands as overtime.
- Measure the non-deal week for two weeks rather than estimating it. The estimate is always low.
- Divide, then hold capacity back. A fully-loaded team has no slack for the large deal that arrives unannounced.
Concurrency, not throughput
Six deals across a quarter is comfortable. Six deals in the same fortnight, each expecting responsiveness, is the condition that produces both burnout and quality loss. Track concurrent deals per engineer.
Related terms
- Sales Engineer
- SE Ramp Time
- PreSales Operations
- Proof of Concept
- Knowledge Reuse Rate
- Time-to-First-Response
Further reading
- How Many Deals Can One Sales Engineer Actually Support?
- AI-Powered Sales Engineer Workforce Management
- What Actually Breaks When RFP Volume Doubles
See how this works on a real deal
WinIQ turns RFPs, competitor data and account research into deal-specific output your SEs can defend.
Request a Demo