SE-to-AE Ratio: Benchmarks, Coverage Models and How to Find Yours

The SE-to-AE ratio is the number of account executives each sales engineer supports. In the most recent public survey of sales engineering practitioners, a majority supported between two and six AEs at a time. The right ratio for your team depends on deal complexity, how often deals need a proof of concept and how much non-presales work your engineers carry.

Ask ten presales leaders for the right SE-to-AE ratio and you will hear ten different numbers. Most of them are rules of thumb. Here is what the published data says, the coverage models teams use and a method to find the ratio that fits your motion.

What is the SE-to-AE ratio?

The SE-to-AE ratio, also written as the AE:SE ratio, compares presales headcount with quota-carrying sales headcount. A 1:4 SE-to-AE ratio means one sales engineer supports four account executives.

It is the most common way companies budget presales headcount. It is also one of the bluntest, because it counts people instead of work.

SE-to-AE ratio benchmarks: what the data says

Published data is thin. The most recent public source is the North American Association of Sales Engineers’ Sales Engineering Signals 2025 survey, collected between December 2025 and January 2026. Asked how many AEs each sales engineer supports at the same time, respondents answered:

AEs supported per sales engineer	Share of respondents
1	5%
2 to 3	31%
4 to 6	24%
7 or more	17%
It varies	17%

Source: NAASE 2025 report, 42 respondents. The listed answers total 94%. NAASE describes the results as directional and self-selected, so read them as a signal of how teams operate today.

Three findings stand out:

• The spread is wide. Coverage runs from one-to-one to seven or more AEs per engineer. No single number describes the market.
• One in six teams has no fixed ratio. They assign engineers deal by deal.
• Sales engineers carry far more than presales. In the same survey, 76% of respondents handle sales enablement, 71% feed product and roadmap decisions, and 67% support post-sale work. Half named workload and time pressure as a challenge.

That last finding is why ratio comparisons mislead. A 1:4 team whose engineers also run enablement and renewals can have less presales time per deal than a 1:5 team that does nothing but presales.

Six factors that set the right ratio

The ratio should move with the work. Six factors matter most:

1. Deal complexity. Multi-product, integration-heavy and regulated deals need more engineer hours per opportunity.
2. Deal size. Larger contracts justify deeper presales investment per deal.
3. POC frequency. A motion where most deals require a proof of concept consumes far more engineering time than one that closes on a demo.
4. Technical buyer involvement. When IT, security and architects join every evaluation, someone has to meet them on their terms.
5. Sales motion. Product-led and transactional motions run lean. Enterprise field sales runs rich.
6. Non-presales load. Enablement, renewals, post-sale escalations and product feedback all draw from the same calendar.

Presales coverage models

How you deploy engineers matters as much as how many you have.

• Dedicated (aligned or pod). Each engineer supports a fixed set of AEs. Strong relationships and deep account knowledge, with uneven load when one AE’s pipeline spikes.
• Pooled. Engineers are assigned from a shared queue, deal by deal. Flexible and efficient, with weaker AE relationships and more context lost at handoffs.
• Hybrid. Engineers align to AEs for core deals and pull in a pool of specialists for deep areas like security, integrations or AI.
• Tiered by segment. Enterprise gets dedicated coverage, mid-market shares a pool and smaller deals run on recorded demos, content and office hours.

Many AI companies now add forward deployed engineers after the sale, embedded with the customer. That raises the bar on what presales hands off. More on that in the forward deployed engineer boom and its presales problem.

How to find your ratio

Start from demand, then convert it to headcount.

1. Count the work. For the last two quarters, count the opportunities presales touched, the demos delivered, the POCs run and the RFPs answered.
2. Estimate hours per unit. Use calendar data wherever possible. Discovery calls, demo prep, POC builds and follow-up all count.
3. Add the non-presales load. Enablement, renewals, post-sale escalations and internal meetings.
4. Be honest about available hours. No engineer has 40 selling hours a week. Subtract internal time before you do the math.
5. Translate it to a ratio. Divide your AE headcount by the number of engineers the work requires. That is your ratio for your motion today, and it will change when the motion does.

Signs your ratio is off

Too thin:

• AEs run technical demos alone because no engineer is free.
• Engineers join deals late, after discovery has already framed the evaluation.
• POCs queue up waiting for an owner.
• Engineers spend their weeks reacting instead of preparing. NAASE respondents named workload and weak AE discovery and qualification as major drivers of reactive work.

Too rich, or misallocated:

• Engineers sit in calls with no technical agenda.
• Presales time goes to deals that were never qualified.
• Deals with presales involvement win at about the same rate as deals without it.

How to make the case for more headcount

Finance funds results. Bring three numbers to the budget conversation:

1. Win rate with and without presales. If deals with an engineer close at a materially higher rate, every uncovered deal carries a measurable cost.
2. Deal size and cycle time with and without presales. Coverage can show up in bigger or faster deals even when win rate barely moves.
3. Where engineer time goes today. Hours lost to manual logging, internal meetings and deals that never close are hours you can win back before you hire.

Start with that third number. At its default inputs for a 20-person presales team, the PresalesIQ ROI calculator estimates $637,000 a year lost to manual admin. Winning that time back is the cheapest headcount you will ever add. For more on where that time goes, read why presales management still relies on manual logging.

Where PresalesIQ fits

PresalesIQ is purpose-built to give presales leaders hard evidence for coverage decisions. It captures presales activity from calendars, the CRM and Gong call transcripts, matches meetings to the right engagement and shows how deals with presales involvement perform against deals without it.

When you walk into a headcount conversation, the numbers come from the work itself, live, instead of a survey of your own team.

See it with your data.

Frequently asked questions

What is a good SE-to-AE ratio? There is no single right ratio. In NAASE’s 2025 practitioner survey, the most common answer was one sales engineer for two to three AEs (31% of respondents), followed by four to six AEs (24%). Complex, POC-heavy enterprise motions sit at the richer end, and transactional motions run leaner.

How many sales engineers do I need per account executive? Start from the work. Count presales-supported opportunities, demos and POCs, estimate the hours each takes and add the non-presales work your engineers carry. Divide the total hours by realistic selling hours per engineer, then compare the result with your AE headcount.

Is the SE-to-AE ratio the same as the AE:SE ratio? Yes. Both describe how many account executives each sales engineer supports. A 1:4 SE-to-AE ratio and a 4:1 AE:SE ratio describe the same coverage.

What is pooled presales coverage? Pooled coverage assigns engineers to deals from a shared queue instead of aligning each engineer to specific AEs. It balances workload across uneven pipelines, at the cost of weaker AE relationships and more handoffs. In NAASE’s 2025 survey, 17% of respondents said their ratio varies from deal to deal.

When should a sales engineer join a deal? As soon as technical requirements start shaping the buying decision, which in complex sales usually means discovery. Engineers who join late inherit a deal framed without them and spend the evaluation correcting it.

Does a better ratio improve win rates? Only if the added coverage reaches the right deals. Compare win rate, deal size and cycle time for deals with and without presales involvement. If the gap is large, more coverage has a clear business case. If there is no gap, fix how engineers are assigned before adding headcount.