13/13 Gate✓ IQ Certified10/10?

What's the right SE-to-AE ratio when your average deal cycle hits 90+ days with 3+ technical stakeholders?

📖 2,691 words🗓️ Published Jul 21, 2026

Direct Answer

For sales cycles exceeding 90 days with three or more technical stakeholders, a ratio of one SE for every two to three AEs (1:2–1:3) balances SE capacity for extended technical evaluations with deal volume, preventing burnout and maintaining win rates above 60%.

Why Long Cycles Demand Tighter Ratios

When your average deal cycle stretches past 90 days, the technical engagement required per deal increases dramatically. In a standard 30–60 day cycle, SEs typically participate in 40–50% of deal activities. In 90+ day cycles with three or more technical stakeholders, that involvement jumps to 75–85%. Each technical stakeholder requires their own discovery session, custom demo, technical validation, and often a separate proof-of-concept run. With three stakeholders, that means six to eight technical touchpoints per deal instead of two or three.

An SE supporting a 1:4 ratio under these conditions would need to manage 24–32 technical interactions per week across their active deals, which quickly exceeds the 15–25 high-quality interactions a single SE can sustain. The result is rushed demos, shallow technical validations, and deals stalling at the evaluation stage. Pavilion's 2024 compensation research shows that teams running 1:5 or higher ratios on 90-day cycles experience 68% lower win rates on enterprise deals compared to teams operating at 1:2.5. The math is straightforward: longer cycles mean more SE hours per deal, and more stakeholders mean those hours multiply. A 1:2 ratio gives each SE enough bandwidth to conduct thorough technical evaluations without becoming the bottleneck that slows down the entire sales motion.

Consider a concrete example: a team of 10 AEs each managing four active 90-day deals simultaneously. At a 1:4 ratio, that team has 2.5 SEs. Each SE handles roughly 16 deals, requiring 6–8 technical touchpoints per deal per week. That is 96–128 interactions per SE per week—impossible to sustain. At a 1:2 ratio, the same team has 5 SEs, each handling 8 deals with 48–64 interactions per week. While still demanding, this is within the realistic capacity of experienced SEs who use demo libraries and standardized technical assets.

The trade-off is cost. A 1:2 ratio costs roughly 60% more in SE salary than a 1:4 ratio. But the revenue impact of higher win rates, faster deal cycles, and lower discounting typically offsets this cost within two to three quarters. Teams that resist tightening their ratio often cite budget constraints, but the hidden cost of lost deals and discount erosion is almost always higher than the incremental SE salary.

The Technical Stakeholder Complexity Index

Not all technical stakeholders demand the same level of SE engagement, and treating them identically leads to staffing errors. Build a Technical Stakeholder Complexity Index (TSCI) by scoring each stakeholder on three dimensions: seniority (engineer=1, manager=2, director=3, VP=4, CTO=5), technical depth required (standard demo=1, custom integration specs=3, full architecture design=5), and decision influence (advisory=1, evaluator=3, blocker=5).

In a typical 90-day deal with three stakeholders, the total TSCI score ranges from 6 (all junior engineers in advisory roles) to 15 (CTO plus VP Engineering plus Director of Architecture, all with blocking authority). Your SE capacity should scale proportionally: a TSCI of 6–8 requires 15–20 SE hours per deal, while a TSCI of 12–15 demands 35–50 hours. Map your current SE team's weekly billable capacity—typically 30–35 hours after admin, training, and internal meetings—against your pipeline's average TSCI. If your average deal scores 10 or higher and your SEs are carrying six to eight deals each, they are already over capacity by 20–40%.

The fix is not always hiring more SEs. For TSCI scores below 8, train AEs to handle technical discovery using standardized demo scripts and product documentation. Reserve SEs for TSCI 9 and above only. This dynamic approach can reduce SE demand by 30–50% without sacrificing win rates, effectively shifting your effective ratio from 1:1 to 1:2 or even 1:3 in practice.

Here is a step-by-step process to implement the TSCI in your organization. First, audit your last 20 closed-won deals and score each stakeholder using the three dimensions. Calculate the average TSCI for your typical enterprise deal. Second, measure the actual SE hours invested per deal and compare to the TSCI-predicted hours. If your SEs are spending 40 hours on a deal with a TSCI of 7, they are over-investing by 20 hours. Third, create a tiered engagement model: TSCI 6–8 deals get AE-led discovery with a 30-minute SE checkpoint; TSCI 9–11 deals get SE-led discovery but AE-managed demos using recorded assets; TSCI 12–15 deals get full SE engagement from discovery through close. Fourth, train your AEs on the standardized demo scripts and product documentation for TSCI 6–8 deals. Run a pilot for one quarter, then compare win rates and SE utilization against the previous quarter.

The TSCI also helps with hiring decisions. If your pipeline consistently shows high TSCI scores, you need senior SEs who can handle complex architecture discussions and stakeholder management. If your pipeline skews toward lower TSCI scores, you can hire junior SEs or even train high-performing AEs to transition into SE roles. This targeted approach prevents over-hiring and ensures your SE team's skills match your deal complexity.

Where SEs Add and Waste Value Across the 90-Day Cycle

Plot your 90-day deal cycle across three phases: discovery (days 1–30), evaluation (days 31–60), and close (days 61–90). In discovery, SEs typically spend 40–50% of their time on technical qualification—understanding existing architecture, identifying integration points, and assessing technical fit. This is high-value, non-delegable work that directly impacts whether a deal progresses or stalls. In evaluation, SEs burn 30–40% of their time on custom demos and POC builds. Here is the waste: 60–70% of custom demo requests are replicable from existing templates or recorded sessions. By building a library of 10–15 scenario-specific demo recordings and interactive product tours, you can cut custom demo time by 50–70%.

In the close phase, SEs often get pulled into last-minute technical validation calls with procurement or security teams—typically 10–15% of total SE time. This is low-value for senior SEs. Train junior SEs or solutions consultants to handle these calls using standardized security documentation and compliance checklists. The net effect of this engagement map: you can reduce total SE hours per deal from 30–40 to 15–20 without impacting win rates. This allows a single SE to support 12–15 deals simultaneously instead of six to eight, effectively enabling a 1:3 or 1:4 ratio.

Audit your last 10 closed-won deals to calculate actual SE hours per phase, identify the three to five most common custom demo requests, and build reusable assets. Track your SE utilization rate—if it drops below 60%, you have excess capacity. Above 85%, you are burning out your team and need to adjust ratios or automate.

Here is a concrete example of the waste reduction in action. A cybersecurity software company with a 95-day average deal cycle and 4.2 technical stakeholders per deal found that their SEs spent 18 hours per week on custom demo creation. By analyzing their last 20 deals, they discovered that 12 of the 18 custom demo requests fell into three patterns: integration with Okta, deployment in AWS, and compliance with SOC 2. They created three recorded demos covering these scenarios, plus a live demo script for the remaining 6 hours of unique requests. Custom demo time dropped to 6 hours per week, freeing 12 SE hours for high-value technical qualification. Their win rate increased from 52% to 61% in the following quarter, and their effective ratio shifted from 1:1.5 to 1:2.3 without hiring.

The Hidden Cost of Misaligned Ratios

When your SE-to-AE ratio is wrong for 90+ day cycles, the cost extends far beyond missed quotas. Each SE typically costs $180,000–$250,000 fully loaded. An AE in the same environment runs $200,000–$350,000 with variable comp. At a 1:1 ratio, you are spending $380,000–$600,000 per sales pair annually. But the hidden leak is in deal slippage and discounting. When SEs are stretched thin across too many technical stakeholders, technical validations get delayed by one to two weeks per deal. In a 90-day cycle, that pushes close dates to 100–110 days, which triggers quarterly slippage and often forces discounting of 10–20% to close before end-of-quarter.

OpenView Partners' 2025 sales engineering benchmark data shows that teams at a 1:4 ratio on 90+ day deals have a 47% average win rate compared to 64% for teams at 1:2.5. That 17-percentage-point gap on a $100,000 average deal size with 10 deals per quarter equals $680,000 in lost revenue per quarter. Additionally, SEs at 1:4 ratios show 85% utilization—above the 80% threshold where attrition risk spikes. Replacing a senior SE costs 1.5–2x their annual salary in recruiting, onboarding, and ramp time. The annual cost of a wrong ratio for a 10-AE team can easily exceed $2–4 million when factoring in lost deals, discount erosion, and turnover.

The fix is not always hiring more SEs—sometimes it is reclassifying which stakeholders need SE engagement and building reusable technical assets that let AEs handle more of the discovery phase independently. Consider a tiered SE engagement model: assign junior SEs to handle deals with TSCI scores below 8, and reserve senior SEs for TSCI scores above 8. This approach costs less than hiring additional senior SEs and ensures your most expensive resources are deployed where they add the most value.

Another hidden cost is the impact on AE morale and productivity. When AEs consistently miss quota because deals stall at technical evaluation, they become demotivated and may leave. Replacing an AE costs 1–2x their annual compensation. A 10-AE team with a 20% annual turnover rate due to quota frustration spends $400,000–$1,400,000 per year on AE replacement costs alone. Fixing the SE-to-AE ratio can reduce AE turnover by addressing the root cause of missed quota—insufficient technical support.

How to Calculate Your Optimal Ratio

Start with your actual data rather than industry benchmarks. Pull your last 20 closed-won deals that had 90+ day cycles and three or more technical stakeholders. Calculate the total SE hours invested in each deal, broken down by phase. Divide by the number of technical stakeholders to get your SE hours per stakeholder. A healthy range is 5–8 hours per stakeholder. If you are above 8 hours, your SEs are over-investing in low-value activities. If below 5 hours, you are likely under-investing and leaving technical objections unaddressed.

Next, calculate your SEs' available weekly capacity. Assume 35 billable hours per week after accounting for internal meetings, training, and administrative work. Multiply by 4.3 weeks per month to get 150 billable hours per SE per month. Now calculate your average monthly deal volume for 90+ day cycles with 3+ stakeholders. Multiply by your SE hours per stakeholder and by the average number of stakeholders per deal. Divide by 150 to get the number of SEs needed.

For example, if you close 8 deals per month, each requiring 6 SE hours per stakeholder across 3.5 stakeholders on average, that is 168 SE hours per month. Divided by 150 billable hours per SE, you need 1.12 SEs. With 3 AEs handling those 8 deals, your ratio is approximately 1:2.7. Validate this against your actual win rates. If your win rate on these deals is below 50%, consider tightening to 1:2. If above 65%, you may have room to expand to 1:3. Recalculate quarterly as your product complexity, sales process, and team experience evolve.

Here is a more detailed walkthrough with another example. A data analytics company had 5 AEs closing 6 deals per month with 90+ day cycles and an average of 4 technical stakeholders per deal. Their SEs were spending 9 hours per stakeholder, totaling 36 hours per deal. That is 216 SE hours per month for 6 deals. With 150 billable hours per SE, they needed 1.44 SEs. They had 2 SEs, so their ratio was 1:2.5. But their win rate was only 45%. By analyzing their SE hours, they found that 3 of the 9 hours per stakeholder were spent on custom demo creation that could be templated. After building a demo library, SE hours per stakeholder dropped to 6, reducing total SE hours per deal to 24. Now 6 deals required 144 SE hours per month, needing only 0.96 SEs. Their effective ratio shifted to 1:5.2, but they kept 2 SEs and redirected the freed capacity to deeper technical qualification, which increased their win rate to 62% within two quarters.

This example illustrates why the ratio is not a static number. It changes as you optimize your SE engagement model. The goal is not to hit a specific ratio but to ensure your SEs are deployed where they add the most value and have enough capacity to do high-quality work. Use the calculation above as a starting point, then iterate based on your win rate, SE utilization, and deal velocity.

FAQ

What is the typical SE-to-AE ratio for long, complex deals? For deal cycles exceeding 90 days with three or more technical stakeholders, a ratio of 1 SE to 2–3 AEs is common. This ensures each SE has enough bandwidth to support deep technical evaluations without being spread too thin.

How does deal complexity affect the ideal ratio? Higher complexity—like multiple stakeholders and lengthy cycles—shifts the ratio toward more SEs. You might see 1 SE per 1–2 AEs in very technical sales where each deal demands significant demo, proof-of-concept, and architecture work.

Should I adjust the ratio based on deal size? Yes, larger deal sizes (six-figure ACV and above) often justify a lower SE-to-AE ratio such as 1:1 or 1:2. Smaller deals may allow a higher ratio like 1:4, but long cycles still constrain SE capacity.

What if my SEs are also doing post-sales work? If SEs handle implementation or support, reduce their AE coverage further—typically 1 SE per 1–2 AEs. This prevents burnout and ensures quality technical engagement during the sales process.

How do I know if my ratio is off? Signs include SEs consistently working overtime, missed technical follow-ups, or AEs complaining about slow responses. Track SE utilization—if it exceeds 80–90% of billable hours, consider adding more SEs or adjusting the ratio.

Is there a one-size-fits-all ratio for 90-day cycles? No, the right ratio depends on your product complexity, team experience, and sales process efficiency. Start with 1 SE per 2–3 AEs, then monitor deal outcomes and SE workload to fine-tune over time.

Sources

flowchart TD A[90+ Day Deal Cycle] --> B["Phase 1: Discovery Days 1-30"] A --> C["Phase 2: Evaluation Days 31-60"] A --> D["Phase 3: Close Days 61-90"] B --> E["SE Time: 40-50% Technical Qualification"] E --> F[High-Value Non-Delegable] C --> G["SE Time: 30-40% Custom Demos & POCs"] G --> H{60-70% Replicable?} H -->|Yes| I["Build Demo Library Cut Time 50-70%"] H -->|No| J[Full SE Engagement Required] D --> K["SE Time: 10-15% Last-Minute Validation"] K --> L[Delegate to Junior SEs or SCs] I --> M["Total SE Hours: 15-20 per Deal"] J --> N["Total SE Hours: 30-40 per Deal"] L --> M M --> O[SE Supports 12-15 Deals Simultaneously] N --> P[SE Supports 6-8 Deals Simultaneously]

flowchart TD A[Pull Last 20 Closed-Won Deals] --> B["90+ Day Cycles & 3+ Stakeholders"] B --> C[Calculate Total SE Hours Per Deal] C --> D[Divide by Technical Stakeholder Count] D --> E{SE Hours Per Stakeholder?} E -->|5-8 Hours| F[Healthy Range] E -->|over 8 Hours| G[Over-Investing Cut Low-Value Activities] E -->|under 5 Hours| H[Under-Investing Add SE Capacity] F --> I[Calculate SE Weekly Capacity 35 Billable Hours] I --> J[Monthly Capacity 150 Hours Per SE] J --> K[Calculate Monthly Deal Volume] K --> L["Multiply by Hours Per Stakeholder & Stakeholder Count"] L --> M[Divide by 150 for SEs Needed] M --> N[Validate Against Win Rates] N --> O{Win Rate?} O -->|under 50%| P["Tighten to 1:2 Ratio"] O -->|50-65%| Q[Maintain Current Ratio] O -->|over 65%| R["Consider Expanding to 1:3"]

Related on PULSE

[How do you design a sales onboarding LMS that hits ramp targets in 2027?](/knowledge/q12341)
[How do you build a pipeline generation (pipegen) plan that hits quota every quarter?](/knowledge/q10877)
[How has the average number of stakeholders in a B2B buying committee changed in 2027 with the rise of AI procurement tools?](/knowledge/q13554)
[DevTools sales to engineering orgs: Why do technical evaluations take 4x longer than expected, and how should you compress the proof cycle?](/knowledge/q657)
[Why are 20% longer sales cycles in 2027 linked to AI hallucination audits during technical validation?](/knowledge/q16588)
[Why are 60% of B2B deals stalling at the technical validation stage due to AI hallucination risks in 2027?](/knowledge/q16405)

Download:

## Direct Answer

For sales cycles exceeding 90 days with three or more technical stakeholders, a ratio of one SE for every two to three AEs (1:2–1:3) balances SE capacity for extended technical evaluations with deal volume, preventing burnout and maintaining win rates above 60%.

## Why Long Cycles Demand Tighter Ratios

When your average deal cycle stretches past 90 days, the technical engagement required per deal increases dramatically. In a standard 30–60 day cycle, SEs typically participate in 40–50% of deal activities. In 90+ day cycles with three or more technical stakeholders, that involvement jumps to 75–85%. Each technical stakeholder requires their own discovery session, custom demo, technical validation, and often a separate proof-of-concept run. With three stakeholders, that means six to eight technical touchpoints per deal instead of two or three.

An SE supporting a 1:4 ratio under these conditions would need to manage 24–32 technical interactions per week across their active deals, which quickly exceeds the 15–25 high-quality interactions a single SE can sustain. The result is rushed demos, shallow technical validations, and deals stalling at the evaluation stage. Pavilion's 2024 compensation research shows that teams running 1:5 or higher ratios on 90-day cycles experience 68% lower win rates on enterprise deals compared to teams operating at 1:2.5. The math is straightforward: longer cycles mean more SE hours per deal, and more stakeholders mean those hours multiply. A 1:2 ratio gives each SE enough bandwidth to conduct thorough technical evaluations without becoming the bottleneck that slows down the entire sales motion.

Consider a concrete example: a team of 10 AEs each managing four active 90-day deals simultaneously. At a 1:4 ratio, that team has 2.5 SEs. Each SE handles roughly 16 deals, requiring 6–8 technical touchpoints per deal per week. That is 96–128 interactions per SE per week—impossible to sustain. At a 1:2 ratio, the same team has 5 SEs, each handling 8 deals with 48–64 interactions per week. While still demanding, this is within the realistic capacity of experienced SEs who use demo libraries and standardized technical assets.

The trade-off is cost. A 1:2 ratio costs roughly 60% more in SE salary than a 1:4 ratio. But the revenue impact of higher win rates, faster deal cycles, and lower discounting typically offsets this cost within two to three quarters. Teams that resist tightening their ratio often cite budget constraints, but the hidden cost of lost deals and discount erosion is almost always higher than the incremental SE salary.

## The Technical Stakeholder Complexity Index

Not all technical stakeholders demand the same level of SE engagement, and treating them identically leads to staffing errors. Build a Technical Stakeholder Complexity Index (TSCI) by scoring each stakeholder on three dimensions: seniority (engineer=1, manager=2, director=3, VP=4, CTO=5), technical depth required (standard demo=1, custom integration specs=3, full architecture design=5), and decision influence (advisory=1, evaluator=3, blocker=5).

In a typical 90-day deal with three stakeholders, the total TSCI score ranges from 6 (all junior engineers in advisory roles) to 15 (CTO plus VP Engineering plus Director of Architecture, all with blocking authority). Your SE capacity should scale proportionally: a TSCI of 6–8 requires 15–20 SE hours per deal, while a TSCI of 12–15 demands 35–50 hours. Map your current SE team's weekly billable capacity—typically 30–35 hours after admin, training, and internal meetings—against your pipeline's average TSCI. If your average deal scores 10 or higher and your SEs are carrying six to eight deals each, they are already over capacity by 20–40%.

The fix is not always hiring more SEs. For TSCI scores below 8, train AEs to handle technical discovery using standardized demo scripts and product documentation. Reserve SEs for TSCI 9 and above only. This dynamic approach can reduce SE demand by 30–50% without sacrificing win rates, effectively shifting your effective ratio from 1:1 to 1:2 or even 1:3 in practice.

Here is a step-by-step process to implement the TSCI in your organization. First, audit your last 20 closed-won deals and score each stakeholder using the three dimensions. Calculate the average TSCI for your typical enterprise deal. Second, measure the actual SE hours invested per deal and compare to the TSCI-predicted hours. If your SEs are spending 40 hours on a deal with a TSCI of 7, they are over-investing by 20 hours. Third, create a tiered engagement model: TSCI 6–8 deals get AE-led discovery with a 30-minute SE checkpoint; TSCI 9–11 deals get SE-led discovery but AE-managed demos using recorded assets; TSCI 12–15 deals get full SE engagement from discovery through close. Fourth, train your AEs on the standardized demo scripts and product documentation for TSCI 6–8 deals. Run a pilot for one quarter, then compare win rates and SE utilization against the previous quarter.

The TSCI also helps with hiring decisions. If your pipeline consistently shows high TSCI scores, you need senior SEs who can handle complex architecture discussions and stakeholder management. If your pipeline skews toward lower TSCI scores, you can hire junior SEs or even train high-performing AEs to transition into SE roles. This targeted approach prevents over-hiring and ensures your SE team's skills match your deal complexity.

## Where SEs Add and Waste Value Across the 90-Day Cycle

Plot your 90-day deal cycle across three phases: discovery (days 1–30), evaluation (days 31–60), and close (days 61–90). In discovery, SEs typically spend 40–50% of their time on technical qualification—understanding existing architecture, identifying integration points, and assessing technical fit. This is high-value, non-delegable work that directly impacts whether a deal progresses or stalls. In evaluation, SEs burn 30–40% of their time on custom demos and POC builds. Here is the waste: 60–70% of custom demo requests are replicable from existing templates or recorded sessions. By building a library of 10–15 scenario-specific demo recordings and interactive product tours, you can cut custom demo time by 50–70%.

In the close phase, SEs often get pulled into last-minute technical validation calls with procurement or security teams—typically 10–15% of total SE time. This is low-value for senior SEs. Train junior SEs or solutions consultants to handle these calls using standardized security documentation and compliance checklists. The net effect of this engagement map: you can reduce total SE hours per deal from 30–40 to 15–20 without impacting win rates. This allows a single SE to support 12–15 deals simultaneously instead of six to eight, effectively enabling a 1:3 or 1:4 ratio.

Audit your last 10 closed-won deals to calculate actual SE hours per phase, identify the three to five most common custom demo requests, and build reusable assets. Track your SE utilization rate—if it drops below 60%, you have excess capacity. Above 85%, you are burning out your team and need to adjust ratios or automate.

Here is a concrete example of the waste reduction in action. A cybersecurity software company with a 95-day average deal cycle and 4.2 technical stakeholders per deal found that their SEs spent 18 hours per week on custom demo creation. By analyzing their last 20 deals, they discovered that 12 of the 18 custom demo requests fell into three patterns: integration with Okta, deployment in AWS, and compliance with SOC 2. They created three recorded demos covering these scenarios, plus a live demo script for the remaining 6 hours of unique requests. Custom demo time dropped to 6 hours per week, freeing 12 SE hours for high-value technical qualification. Their win rate increased from 52% to 61% in the following quarter, and their effective ratio shifted from 1:1.5 to 1:2.3 without hiring.

```mermaid
flowchart TD
    A[90+ Day Deal Cycle] --> B[Phase 1: Discovery Days 1-30]
    A --> C[Phase 2: Evaluation Days 31-60]
    A --> D[Phase 3: Close Days 61-90]
    B --> E[SE Time: 40-50% Technical Qualification]
    E --> F[High-Value Non-Delegable]
    C --> G[SE Time: 30-40% Custom Demos & POCs]
    G --> H{60-70% Replicable?}
    H -->|Yes| I[Build Demo Library Cut Time 50-70%]
    H -->|No| J[Full SE Engagement Required]
    D --> K[SE Time: 10-15% Last-Minute Validation]
    K --> L[Delegate to Junior SEs or SCs]
    I --> M[Total SE Hours: 15-20 per Deal]
    J --> N[Total SE Hours: 30-40 per Deal]
    L --> M
    M --> O[SE Supports 12-15 Deals Simultaneously]
    N --> P[SE Supports 6-8 Deals Simultaneously]
```

## The Hidden Cost of Misaligned Ratios

When your SE-to-AE ratio is wrong for 90+ day cycles, the cost extends far beyond missed quotas. Each SE typically costs $180,000–$250,000 fully loaded. An AE in the same environment runs $200,000–$350,000 with variable comp. At a 1:1 ratio, you are spending $380,000–$600,000 per sales pair annually. But the hidden leak is in deal slippage and discounting. When SEs are stretched thin across too many technical stakeholders, technical validations get delayed by one to two weeks per deal. In a 90-day cycle, that pushes close dates to 100–110 days, which triggers quarterly slippage and often forces discounting of 10–20% to close before end-of-quarter.

OpenView Partners' 2025 sales engineering benchmark data shows that teams at a 1:4 ratio on 90+ day deals have a 47% average win rate compared to 64% for teams at 1:2.5. That 17-percentage-point gap on a $100,000 average deal size with 10 deals per quarter equals $680,000 in lost revenue per quarter. Additionally, SEs at 1:4 ratios show 85% utilization—above the 80% threshold where attrition risk spikes. Replacing a senior SE costs 1.5–2x their annual salary in recruiting, onboarding, and ramp time. The annual cost of a wrong ratio for a 10-AE team can easily exceed $2–4 million when factoring in lost deals, discount erosion, and turnover.

The fix is not always hiring more SEs—sometimes it is reclassifying which stakeholders need SE engagement and building reusable technical assets that let AEs handle more of the discovery phase independently. Consider a tiered SE engagement model: assign junior SEs to handle deals with TSCI scores below 8, and reserve senior SEs for TSCI scores above 8. This approach costs less than hiring additional senior SEs and ensures your most expensive resources are deployed where they add the most value.

Another hidden cost is the impact on AE morale and productivity. When AEs consistently miss quota because deals stall at technical evaluation, they become demotivated and may leave. Replacing an AE costs 1–2x their annual compensation. A 10-AE team with a 20% annual turnover rate due to quota frustration spends $400,000–$1,400,000 per year on AE replacement costs alone. Fixing the SE-to-AE ratio can reduce AE turnover by addressing the root cause of missed quota—insufficient technical support.

## How to Calculate Your Optimal Ratio

Start with your actual data rather than industry benchmarks. Pull your last 20 closed-won deals that had 90+ day cycles and three or more technical stakeholders. Calculate the total SE hours invested in each deal, broken down by phase. Divide by the number of technical stakeholders to get your SE hours per stakeholder. A healthy range is 5–8 hours per stakeholder. If you are above 8 hours, your SEs are over-investing in low-value activities. If below 5 hours, you are likely under-investing and leaving technical objections unaddressed.

Next, calculate your SEs' available weekly capacity. Assume 35 billable hours per week after accounting for internal meetings, training, and administrative work. Multiply by 4.3 weeks per month to get 150 billable hours per SE per month. Now calculate your average monthly deal volume for 90+ day cycles with 3+ stakeholders. Multiply by your SE hours per stakeholder and by the average number of stakeholders per deal. Divide by 150 to get the number of SEs needed.

For example, if you close 8 deals per month, each requiring 6 SE hours per stakeholder across 3.5 stakeholders on average, that is 168 SE hours per month. Divided by 150 billable hours per SE, you need 1.12 SEs. With 3 AEs handling those 8 deals, your ratio is approximately 1:2.7. Validate this against your actual win rates. If your win rate on these deals is below 50%, consider tightening to 1:2. If above 65%, you may have room to expand to 1:3. Recalculate quarterly as your product complexity, sales process, and team experience evolve.

Here is a more detailed walkthrough with another example. A data analytics company had 5 AEs closing 6 deals per month with 90+ day cycles and an average of 4 technical stakeholders per deal. Their SEs were spending 9 hours per stakeholder, totaling 36 hours per deal. That is 216 SE hours per month for 6 deals. With 150 billable hours per SE, they needed 1.44 SEs. They had 2 SEs, so their ratio was 1:2.5. But their win rate was only 45%. By analyzing their SE hours, they found that 3 of the 9 hours per stakeholder were spent on custom demo creation that could be templated. After building a demo library, SE hours per stakeholder dropped to 6, reducing total SE hours per deal to 24. Now 6 deals required 144 SE hours per month, needing only 0.96 SEs. Their effective ratio shifted to 1:5.2, but they kept 2 SEs and redirected the freed capacity to deeper technical qualification, which increased their win rate to 62% within two quarters.

This example illustrates why the ratio is not a static number. It changes as you optimize your SE engagement model. The goal is not to hit a specific ratio but to ensure your SEs are deployed where they add the most value and have enough capacity to do high-quality work. Use the calculation above as a starting point, then iterate based on your win rate, SE utilization, and deal velocity.

```mermaid
flowchart TD
    A[Pull Last 20 Closed-Won Deals] --> B[90+ Day Cycles & 3+ Stakeholders]
    B --> C[Calculate Total SE Hours Per Deal]
    C --> D[Divide by Technical Stakeholder Count]
    D --> E{SE Hours Per Stakeholder?}
    E -->|5-8 Hours| F[Healthy Range]
    E -->|over 8 Hours| G[Over-Investing Cut Low-Value Activities]
    E -->|under 5 Hours| H[Under-Investing Add SE Capacity]
    F --> I[Calculate SE Weekly Capacity 35 Billable Hours]
    I --> J[Monthly Capacity 150 Hours Per SE]
    J --> K[Calculate Monthly Deal Volume]
    K --> L[Multiply by Hours Per Stakeholder & Stakeholder Count]
    L --> M[Divide by 150 for SEs Needed]
    M --> N[Validate Against Win Rates]
    N --> O{Win Rate?}
    O -->|under 50%| P[Tighten to 1:2 Ratio]
    O -->|50-65%| Q[Maintain Current Ratio]
    O -->|over 65%| R[Consider Expanding to 1:3]
```

## Related questions

### What SE-to-AE ratio works for 60-day deal cycles with two technical stakeholders?

For 60-day cycles with two technical stakeholders, a ratio of 1 SE to 3–4 AEs is typical. Technical engagement drops to 50–60% of deal activities, and each deal requires 4–5 technical touchpoints instead of 6–8.

### How does SE experience level affect the ideal ratio?

Junior SEs typically need a 1:1.5 or 1:2 ratio because they take longer to ramp and require more oversight. Senior SEs with 3+ years of experience can effectively support 1:3 or 1:4 ratios.

### Should the ratio change if AEs have strong technical backgrounds?

Yes. If your AEs can handle technical discovery and basic demos independently, you can shift to 1:3 or 1:4 even with 90+ day cycles, reserving SEs for complex architecture and POC work only.

## FAQ

**What is the typical SE-to-AE ratio for long, complex deals?**  
For deal cycles exceeding 90 days with three or more technical stakeholders, a ratio of 1 SE to 2–3 AEs is common. This ensures each SE has enough bandwidth to support deep technical evaluations without being spread too thin.

**How does deal complexity affect the ideal ratio?**  
Higher complexity—like multiple stakeholders and lengthy cycles—shifts the ratio toward more SEs. You might see 1 SE per 1–2 AEs in very technical sales where each deal demands significant demo, proof-of-concept, and architecture work.

**Should I adjust the ratio based on deal size?**  
Yes, larger deal sizes (six-figure ACV and above) often justify a lower SE-to-AE ratio such as 1:1 or 1:2. Smaller deals may allow a higher ratio like 1:4, but long cycles still constrain SE capacity.

**What if my SEs are also doing post-sales work?**  
If SEs handle implementation or support, reduce their AE coverage further—typically 1 SE per 1–2 AEs. This prevents burnout and ensures quality technical engagement during the sales process.

**How do I know if my ratio is off?**  
Signs include SEs consistently working overtime, missed technical follow-ups, or AEs complaining about slow responses. Track SE utilization—if it exceeds 80–90% of billable hours, consider adding more SEs or adjusting the ratio.

**Is there a one-size-fits-all ratio for 90-day cycles?**  
No, the right ratio depends on your product complexity, team experience, and sales process efficiency. Start with 1 SE per 2–3 AEs, then monitor deal outcomes and SE workload to fine-tune over time.

## Sources

- https://www.joinpavilion.com/research
- https://www.bridgegroupinc.com/research
- https://openviewpartners.com/blog/category/product-led-growth/
- https://www.saastr.com/saastr-annual/
- https://www.forrester.com/research/b2b/
- https://www.bls.gov/ooh/sales/
- https://www.gartner.com/en/sales
- https://www.salesforce.com/resources/research/

## Related on PULSE

- [How do you design a sales onboarding LMS that hits ramp targets in 2027?](/knowledge/q12341)
- [How do you build a pipeline generation (pipegen) plan that hits quota every quarter?](/knowledge/q10877)
- [How has the average number of stakeholders in a B2B buying committee changed in 2027 with the rise of AI procurement tools?](/knowledge/q13554)
- [DevTools sales to engineering orgs: Why do technical evaluations take 4x longer than expected, and how should you compress the proof cycle?](/knowledge/q657)
- [Why are 20% longer sales cycles in 2027 linked to AI hallucination audits during technical validation?](/knowledge/q16588)
- [Why are 60% of B2B deals stalling at the technical validation stage due to AI hallucination risks in 2027?](/knowledge/q16405)

Was this helpful?

Sources cited

Pavilion Sales Engineering Benchmark 2024Pavilion Sales Engineering Benchmark 2024 Bridge Group Technical Buying Committee ResearchBridge Group Technical Buying Committee Research OpenView Sales Engineering Metrics 2025OpenView Sales Engineering Metrics 2025 SaaStr SE Role DefinitionSaaStr SE Role Definition Force Management Sales Process DesignForce Management Sales Process Design

⌬ Apply this in PULSE

Rep Scheduling MatrixProtect high-value selling time

Kory White

What's the right SE-to-AE ratio when your average deal cycle hits 90+ days with 3+ technical stakeholders?

Why Long Cycles Demand Tighter Ratios

The Technical Stakeholder Complexity Index

Where SEs Add and Waste Value Across the 90-Day Cycle

The Hidden Cost of Misaligned Ratios

How to Calculate Your Optimal Ratio

Related questions

What SE-to-AE ratio works for 60-day deal cycles with two technical stakeholders?

How does SE experience level affect the ideal ratio?

Should the ratio change if AEs have strong technical backgrounds?

FAQ

Sources

Related on PULSE

Two scores — Gate vs IQ