70 Sales Engineering and Presales Statistics (2026)

A sales engineer is usually shared between several sellers. In Navattic’s survey of 70+ sales engineers and presales professionals at B2B SaaS companies, taken in December 2025 and January 2026, the most common ratio was 3:1, three account executives to one engineer,¹ and most organizations had each engineer support two to five.¹ Those engineers ran an average of 7 demos a week,¹ and a standard demo took 3.6 hours of their time, prep included.¹

The figures below cover how many sellers one engineer supports, how long demos take, how much of the week goes to selling, what engineers are measured on, and how far AI has reached the work. They come from four reports published in 2025 and 2026. Three are by companies that sell demo or RFP software (Navattic, Consensus and Loopio) and one is by the North American Association of Sales Engineers (NAASE), so every figure keeps its population beside it.

Mystery Demo takes software companies’ real sales demos as a buyer and brings back what was said, shown and quoted, from the first call to the technical deep dive. It meets demos like the ones these engineers describe from the buyer’s side of the table.

Key Takeaways

One Sales Engineer Usually Supports Several Account Executives

If you run sales or enablement, the engineer your sellers bring to a demo is usually shared, so how that engineer’s hours get split is a team decision. Three surveys asked how many account executives one engineer supports, and each reported the answer in its own categories.

NAASE’s full spread shows how far apart teams sit. Of its 42 respondents, 31% supported two to three account executives, 24% supported four to six and 17% supported seven or more,³ while 17% said it varies, 7% were not sure and 5% supported just one.³

NAASE also split one answer by ratio, inside that small sample. Among engineers supporting one to three account executives, 40% named their alignment with the account executives as a leading challenge, against 17% of those supporting four or more.³ Their demos draw on the engineer’s time, so the next question is what one demo costs.

A Standard Demo Takes Hours, Prep Included

For the team booking demos, the engineer’s time on a demo includes the preparation before it, not only the call. Navattic’s respondents averaged 7 demos a week, with 3 to 5 the most common range.¹ As Navattic published them, closing a deal took an average of 3 demos, while the most common range was 4 to 5.¹

Two surveys timed the work around a single demo, and they timed different things. Consensus counted “staff hours” without saying whose.

Repeating the same demo is common. In Navattic’s survey, 94% ran repetitive demos at least sometimes,¹ 34% ran them often,¹ and 34% said their standard demo had little to no customization.¹ Consensus measured how standardized demos are: 28% of its respondents said their demos were only 0 to 25% standardized,² and 38% said 30 to 50%.²

Navattic also measured what surrounds the demo:

Many demos reach buyers who were not qualified for them:

Demos are only part of the job, and Consensus also put a number on the rest of the week.

Selling Takes Little More Than Half an Engineer’s Time

For a sales leader, the engineer borrowed for a demo is also doing other teams’ work, out of the same week. Consensus’s respondents spent 56% of their time on direct sales activities: active sales cycles, demos, discovery and proofs of concept.² The report names three parts of the other 44%: implementation or customer success support at 14%, marketing at 11% and product development collaboration at 9%.²

NAASE asked a different question, which responsibilities sit in the role at all, and also found a broad role among its 42 respondents.

Consensus also tracks burnout from year to year. Its 2026 report puts the share of engineers with no burnout symptoms at 12%, against 20% in its 2025 report.²

RFPs Are Timed in a Different Population

RFP work is measured among the people involved in responding to RFPs. Loopio’s 2025 report surveyed 1,544 of them, from proposal managers to sales engineers, and its figures describe 2024. Those teams spent 25 hours writing each RFP, down from 30 the year before.⁴

The drop was not shared by every role. Proposal teams cut their writing time per RFP from 34 hours to 24,⁴ while respondents in sales operations, enablement or presales roles went from 25 hours to 28.⁴

Engineers themselves ranked RFPs low among their troubles: 12% of NAASE’s respondents named security reviews, compliance or RFPs among their biggest challenges.³ None of these surveys says how much of a sales engineer’s own week goes to RFPs. The surveys count the hours, and what those hours do to deals is the harder question.

The Surveys Do Not Isolate What Engineers Do to Win Rates

For a revenue leader, the surveys show how engineers describe their value and how they are measured, not what their work changes. NAASE and Consensus asked about value and measurement in different ways.

Many of NAASE’s engineers listed the win rate among the places they add value, and few named it as the main factor in their reviews. The value shares add up to 185%, so respondents picked several areas, while the review shares add up to about 100%, so they picked one. In Consensus’s survey, closed revenue was the most common measure, and more respondents said their team carries a quota than said they carry their own.

The win rates that were measured do not measure what engineers contribute:

Navattic does not say how many deals or customers its CRM data covers or how long the deals were observed, and a link between demos sent and deals won is a correlation, not a measure of what engineers do. NAASE cites a 2015 McKinsey article that associates strong presales capabilities with higher win rates, an association rather than an isolated effect. The surveys do show how engineers are changing their own work, starting with AI.

AI Use Is Common, and Most Reported Gains Are Modest

For an enablement team, AI is already part of most engineers’ work, and in the largest survey most respondents called the gain slight or moderate. Three surveys measured AI in different populations.

Of Consensus’s respondents, nearly 73% called their gains slight or moderate² and 15% significant or transformational.² NAASE reads its own numbers as use moving faster than company rules: 45% said their AI guidelines exist but are still evolving,³ 26% called them unclear or inconsistent,³ and 22% said their company provides approved or private AI tools.³

Regular use differed by industry, in two small groups within NAASE’s 42: 75% among software and IT engineers and 50% elsewhere.³ Among Loopio’s RFP teams in 2024, 70% of those using AI used it at least weekly.⁴

Consensus, which sells demo automation, suggests AI is often layered onto manual workflows rather than built into how demos are delivered.² It found that 64% of teams did not use what it calls intelligent demo automation.² None of the survey questions asks what AI demo tools do to win rates or to the hours a demo takes, and the vendor figures that come near it describe the vendors’ own customers.

Chief Mystery Officer

Mystery Demo

These surveys are practitioners describing their own week, and they are useful for exactly that. What none of them shows is the other side of the table: which integration a rival’s engineer demonstrates live and which one they promise for next quarter, which question they move to a follow-up, how long they let the buyer talk before the screen share starts. Those choices are made one buyer at a time, and they are the demo your buyer compares with yours. The only way to see them is to be the buyer they are made for.

What a Rival’s Sales Engineer Shows Your Buyer

The figures above are survey shares and averages, most of them practitioners reporting on their own work. None of them says what one rival’s engineer shows a buyer in the technical deep dive, what they promise is coming, or which question they take offline. That happens on a call, with a buyer in the room.

Mystery Demo reaches that call the way a serious prospect would:

Below is that scorecard on our public example board, where the client and all five competitors are invented. Every real board is built from the calls with that client’s own competitors.

Each row is a rival and each column a step the buyer went through: how fast they answered, how good the demo was, how transparent they were, and how they followed up. The notes in the demo column say who ran each demo and how, which is the part no survey of engineers reports about a rival.

Pick the rival whose engineer your buyers meet most often. After a short intro call to plan that buyer, we take the rival’s demo and deep dive as the buyer, and the recordings come back with that rival’s row of the scorecard filled in, for a flat €499 per competitor.

Frequently Asked Questions

What Is the Typical Sales Engineer to Account Executive Ratio?

3:1 was the most common ratio in Navattic’s survey of 70+ presales professionals, with most organizations at two to five account executives per engineer.¹ Roughly 40% of Consensus’s 423 presales professionals worked at 3:1 to 5:1,² and NAASE’s most common answer was two to three account executives, at 31%.³

How Many Demos Does a Sales Engineer Run per Week?

7 demos a week on average in Navattic’s survey, with 3 to 5 the most common range.¹

How Long Does It Take to Prepare and Deliver a Sales Demo?

3.6 hours for a standard demo including prep, and 7 hours for a custom one, in Navattic’s survey.¹ In Consensus’s survey, 28% spent six or more staff hours preparing and following up on a single demo.²

How Much of a Sales Engineer’s Time Goes to Selling?

56% of their time went to direct sales activities, in Consensus’s survey of 423 presales professionals.²

How Long Does It Take to Write an RFP?

25 hours of writing per RFP in Loopio’s 2025 report, which describes 2024, down from 30,⁴ and 28 hours for respondents in sales operations, enablement or presales roles.⁴

Do Sales Engineers Use AI?

59% of the 42 engineers in NAASE’s survey used AI tools regularly.³ In Consensus’s survey, 88% reported some productivity gain from AI, and nearly 73% of all respondents called their gains slight or moderate.²

How Are Sales Engineers Measured?

78% of Consensus’s respondents named closed revenue or ARR as a measure of presales performance, the most common one.² Among NAASE’s 42 respondents, half said their reviews or pay turned on a mix of metrics.³

References

1. Navattic: State of Demo Automation 2026
2. Consensus: 2026 Sales Engineering Compensation & Workload Report
3. North American Association of Sales Engineers: Sales Engineering Signals 2025 (2026)
4. Loopio: 2025 RFP Response Trends & Benchmarks Report