How Many Sales Engineers per Account Executive?
By Steve LePatner
Sales leaders at AI and SaaS companies ask me this question all the time: how many sales engineers do we need for every account executive? It usually comes up when deals start slipping because technical work is piling up, or when the board asks why the solutions team is growing faster than the quota carrying team.
I have been recruiting sales and technical sales talent since 1997 and founded Howard Lee & Associates in 2002. The honest answer is that there is no universal ratio. The right number depends on what your sales engineers actually do in a deal and how many deals they can support well at once. The good news is that you can work it out for your own business.
Why there is no standard ratio
Two companies with the same headcount can need very different solutions teams. A few factors drive most of the difference:
- Product complexity. An AI platform that has to connect to a customer's data, security review and existing systems needs far more technical involvement than a simple self-serve tool.
- Deal size and length. Larger enterprise deals often involve proofs of concept, custom demos and long technical evaluations. Smaller, faster deals may need only a standard demo.
- Who the buyer is. If you sell to engineering, data or security teams, they will want to talk to someone who can go deep. If you sell to business users, the account executive can often carry more of the conversation.
- What the AE can handle alone. Some account executives are highly technical and can run early demos themselves. Others need a sales engineer on almost every call.
- What else the SE owns. In many companies, sales engineers also support renewals, onboarding handoffs, RFPs, partner enablement and product feedback. That work takes time away from new deals.
Copying a ratio from another company without looking at these factors is one of the fastest ways to end up over or under staffed.
How to calculate the ratio for your team
Instead of starting with a ratio, start with capacity. Here is the approach I suggest to sales leaders:
- Map the technical work in a typical deal. List each stage where a sales engineer is involved, such as discovery, demo, technical deep dive, proof of concept, security review and handoff.
- Estimate the hours per stage. Ask your current sales engineers. Their estimates will be more accurate than a guess from the top.
- Add up the hours per deal. Do this separately for each segment if your enterprise and mid market deals look very different.
- Estimate how many active deals each AE carries. Look at your pipeline, not your hopes for the pipeline.
- Account for non deal work. Subtract the time sales engineers spend on renewals, RFPs, internal meetings and enablement from their available hours.
- Compare demand to capacity. Total technical hours needed across all AEs, divided by the productive hours one sales engineer has, gives you a working headcount.
Here is a simple example, using made up numbers for illustration only. If each AE has six active deals that each need about ten hours of SE time a month, one AE creates about sixty hours of technical work a month. If a sales engineer has about one hundred productive deal hours a month after other duties, one SE could support a little under two AEs at that pace. Change any of those inputs and the answer changes, which is exactly why you should run the math with your own data.
Signs your ratio is off
Even without perfect data, the warning signs are usually visible.
You have too few sales engineers when:
- Demos and proofs of concept are booked weeks out.
- Account executives run technical calls they are not equipped for, and deals stall after the first technical meeting.
- Sales engineers are working nights and weekends and talking about burnout.
- Win rates drop on deals with heavy technical evaluations.
You may have too many when:
- Sales engineers join calls that do not need them, just to stay busy.
- AEs lean on SEs for work they should own, like basic demos or follow up emails.
- The solutions team has time for projects but pipeline is thin.
If you are seeing the first list, our solutions engineering recruiting page explains how we help companies add strong sales engineers quickly.
Pooled or dedicated sales engineers
How you deploy sales engineers matters as much as how many you have.
- Dedicated pairing assigns one sales engineer to a small group of account executives. It builds trust and deep account knowledge, and it works well for complex enterprise deals.
- Pooled support lets account executives request a sales engineer from a shared team. It is more flexible and helps cover uneven demand, but it can weaken relationships and accountability.
- Hybrid models pair sales engineers with enterprise AEs while a smaller pool covers mid market and inbound deals.
Many growing companies start pooled and move toward dedicated pairing as enterprise deals become a bigger share of revenue.
Hiring for the ratio you will need
Sales engineers often take longer to hire than account executives, especially for AI products where the role requires real technical depth plus the ability to present to executives. If your hiring plan adds AEs this quarter and sales engineers next quarter, your technical capacity will lag behind your pipeline.
I recommend planning sales engineer hires alongside AE hires, not after them. Before you open the role, be clear about which segment the hire will support, which stages of the deal they will own and how you will measure success. If you are also hiring the sellers they will support, our account executive recruiting page covers how we approach those searches.
FAQ
Is there an industry standard ratio of sales engineers to AEs?
Not one that holds across companies. The right number depends on product complexity, deal size, buyer type and what else your sales engineers own. Calculating capacity from your own deal data is more reliable than copying another company.
Should sales engineers report to sales or to a separate solutions leader?
Both models work. Many companies have sales engineers report to a head of solutions engineering who partners with sales leadership, which helps protect technical standards and career paths.
When should a startup hire its first sales engineer?
Usually when technical questions start slowing deals down and founders or engineers can no longer cover every demo. We wrote more about this in our post on when to hire your first sales engineer.
Can strong technical AEs reduce the need for sales engineers?
Yes, to a point. Technical AEs can handle early demos and discovery, which frees sales engineers for deep evaluations and proofs of concept.
Talk it through
If you are trying to figure out the right sales engineering coverage for your team, I am happy to talk it through. You can book a 15 minute call with me, and you can see how we work on our services page.
Hiring for a sales or technical role?
Book a 15 minute call with Steve to talk through your search.
Book a 15 Minute Call