Solutions engineer to AE ratio: how many SEs does your team need?

Most B2B software sales teams run somewhere between one solutions engineer to three AEs and one to five, and survey data from presales platform Consensus puts the average at roughly one SE to four AEs, with three or four AEs per SE described as the likely maximum that is sustainable. The right solutions engineer to AE ratio for your team, though, comes from your own deal volume and technical complexity, not a benchmark.

This guide explains how SE to AE ratios differ by sales motion, gives you a capacity model you can run on your own CRM data in an afternoon, and covers the signs that you need another solutions engineer (or that you have too many). It is written for founders, CROs and RevOps leaders planning presales headcount, and for SEs who want to understand how their workload is being sized.

What is a typical solutions engineer to AE ratio?

Consensus, which publishes an annual sales engineering workload and compensation survey of more than 1,000 presales professionals, reported in its 2024 edition that the average ratio of AEs to SEs had stayed steady at approximately 4:1, and suggested that 3 to 4 AEs per SE is likely the maximum sustainable ratio. Those are averages across very different businesses, so they are a sense check rather than a target.

Practitioners are consistent on one point: there is no single ideal ratio. As The Sales Engineer Guy blog puts it, the right balance depends on how much your organisation relies on SEs and how much technical support your product needs during evaluation. Many startups run close to 1:1 because winning every deal matters more than cost of sale; some highly technical products have more SEs than AEs.

The table below gives typical ranges by sales motion. These are rules of thumb from how GTM teams are commonly structured, not survey data. Use them to check whether your current set-up is in a sensible zone before you build your own model.

Why does the ratio matter so much?

Getting the SE ratio wrong costs revenue in both directions. Too few SEs creates a queue: demos are delayed, discovery is rushed, proofs of concept are cut short and AEs start running technical conversations they are not equipped for. Deals slip or are lost on technical confidence. Too many SEs and you carry expensive capacity that ends up doing marketing webinars, post-sales onboarding or internal projects, while your cost of sale climbs.

Buyer behaviour has made presales capacity more important, not less. Gartner research on the B2B buying journey reports that a typical buying group for a complex B2B solution involves six to ten decision makers, and that buyers spend only 17% of their purchase journey meeting potential suppliers. In June 2025 Gartner reported that 61% of B2B buyers prefer a rep-free buying experience overall. Put together, that means the time buyers do spend with your team is short and needs to be decisive, and much of it is technical validation: will this work in our environment, is it secure, will it integrate? That is SE time.

At the same time, AEs are stretched. Salesforce's State of Sales research, published in July 2024 from a survey of 5,500 sales professionals, found reps spend 70% of their time on non-selling tasks and 67% did not expect to meet quota that year. When AEs are short of selling time, the temptation is to hand more of the deal to SEs, which shifts load onto presales without anyone deciding it should.

How to calculate the solutions engineer to AE ratio for your team

A capacity model beats any benchmark. You need four numbers, most of which are in your CRM.

A worked example

SEs log time for a month and find an average of 14 hours per opportunity: 2 hours of technical discovery, 4 hours preparing and running a tailored demo, 5 hours on a light proof of concept for about half of deals (averaged across all deals), and 3 hours on security questionnaires and follow-up. Total demand: 120 × 14 = 1,680 SE hours per quarter.

A quarter has around 500 working hours per person. After holidays, training, internal meetings and the onboarding calls SEs still help with, each SE has about 65% of time available for live deals: roughly 325 hours. 1,680 ÷ 325 = 5.2 SEs. Add 15% buffer: about 6 SEs.

Twelve AEs supported by six SEs is a 1:2 ratio, considerably richer than the 1:4 average. That tells the company something important: either its product genuinely requires heavy presales work, or SEs are being pulled into deals that should not need them. The next step is to look at where the hours go.

The combined line is deliberately optimistic, but it makes the point. A ratio is an output of how you run presales, not an input. Before you hire the next solutions engineer, check whether the same capacity can be found in qualification, reuse and protecting SE time.

Signs you need another solutions engineer

• Demo lead time is growing: If prospects wait more than a few working days for a tailored demo, you are losing momentum and some deals.
• AEs run technical calls alone: When AEs start answering integration and security questions because no SE is free, technical win rates usually fall.
• SEs are triaging rather than engaging: SEs skip discovery and go straight to a generic demo to get through the queue.
• Proofs of concept are being cut or declined: POCs that would win deals are refused for capacity reasons.
• Quarter-end burnout: SEs consistently work evenings and weekends at quarter end, and attrition or sickness rises.
• Technical loss reasons are increasing: Win-loss analysis shows more deals lost on "did not prove fit" or "security concerns".

Signs you have too many SEs (or the wrong model)

• SEs join first calls by default: An SE on every discovery call usually means AEs are not qualifying, or are using the SE as a comfort blanket.
• SEs are filling time with non-sales work: Webinars, documentation and onboarding are worthwhile, but if they are taking most of an SE's week, capacity is not the constraint.
• Low SE engagement on lost deals: If SEs only engage once a deal is late-stage, they are not shaping it; adding more of them will not help.
• Cost of sale is rising faster than win rate: More SE capacity should show up in win rate, deal size or cycle length. If it does not, look at how SEs are used.

Aligned, pooled or hybrid: how should SEs be deployed?

Most companies move from pooled or founder-as-SE in the early days, to aligned pods as the team grows, and then to a hybrid with specialist overlays once the product portfolio broadens. Each step needs a presales leader who owns capacity planning, rules of engagement and the technical win.

When should you hire your first solutions engineer?

Earlier than most founders think, if your product is technical. The usual triggers are: the founder or CTO is spending more than a day a week on demos and technical questions; AEs are losing deals at the evaluation stage; or you are moving upmarket into buyers with security reviews and integration requirements. The first SE should be a strong generalist who can run discovery, build a demo environment, handle security questionnaires and feed product feedback back to engineering. Our solutions engineering specialism page sets out the profiles we see work at each stage.

How should SEs be paid, and does it affect the ratio?

Compensation shapes behaviour, and behaviour shapes how many SEs you need. AEs typically carry a large variable component: The Bridge Group's 2024 benchmark found a median AE base to variable split of 53:47. Solutions engineers are usually paid with a heavier weighting to base salary and a smaller variable element tied to team or regional bookings, rather than individual deals. That structure encourages SEs to support the whole team, but if variable pay is tied to the number of deals touched, SEs may join calls that do not need them, and your ratio will look worse than your real need. Tie SE variable pay to team bookings and technical win rate rather than activity. For indicative pay, see our salary guide.

Hiring solutions engineers: what to look for

Whatever ratio you settle on, the quality of each SE matters more than the count. One strong SE who qualifies technical fit early and runs tight proofs of concept can support more AEs than two who demo every feature to every prospect.

• Discovery before demo: Ask candidates to run a mock discovery call before they show anything. The best SEs ask more than they tell.
• Tailored demonstration: Give them a short scenario and ask for a ten-minute demo of your product (or one they know) focused on that buyer's problem.
• POC discipline: Ask how they scope a proof of concept, define success criteria with the buyer and stop a POC that is not going to convert.
• Commercial awareness: Strong SEs understand deal stages, forecast categories and when to push back on an AE about qualification.
• Product feedback: Ask how they have fed field insight back to product and what changed as a result.

If you are building or scaling a presales team, send us the brief. If you are an SE looking for your next role, register your CV or browse current jobs.