There is no single correct number. The ratios quoted as standards are averages across companies with different deal sizes, products and sales motions, so they describe somebody else’s situation rather than yours. The question underneath is coverage against deals that are genuinely real, and that is a different measurement entirely.
The appeal is obvious. A ratio converts a difficult staffing argument into a single comparable figure, and a figure can go in a board deck. It also gives a presales leader something to point at when the team is drowning, which is often the real reason the question gets asked.
The trouble is that the published figures are averages taken across organisations that have almost nothing in common. A company selling a six figure platform into a twelve person buying committee and a company selling seats to one department both appear in the same average. The resulting number is arithmetically true and useless as a target.
A ratio describes how many people you have. It says nothing about what they are spending the week on.
Every ratio argument is really a coverage argument. The claim is that there is more demand for engineering time than there is engineering time, which is almost always true and does not by itself establish what to do.
What makes it actionable is asking what the demand is made of. If a third of the requests are for deals that were never going to close, the team is not short of people. It is short of a way to tell the difference early, and hiring will reproduce the problem with a larger payroll.
Sales engineers spend about forty percent of their time on deals that genuinely close. Fifty seven percent report forty percent or less, and not one engineer measured has reported more than eighty percent. Source: the Deal Flow Benchmark, an ongoing study by Dmitri Lee, Presales Navigation System. Findings current as of October 2026.
Read that against a staffing request and the arithmetic changes. Adding an engineer at the current ratio adds capacity in the same proportion it already runs, which means roughly six tenths of the new hire goes where the existing six tenths goes.
This is not an argument against headcount. There are situations where the team is well run and simply outnumbered, and refusing to hire in those conditions is how good engineers leave.
This is the number the ratio is pretending to be. It can be estimated in an afternoon from closed opportunities and calendar data, and it tends to surprise people.
Fifty nine percent join after discovery is already finished, and fourteen percent report no consistent pattern. An engineer who arrives after the requirements are set spends the deal defending somebody else’s framing.
Sixty one percent of formal warnings change nothing. If that is your number, the team is already generating the signal that would protect its own capacity and nobody is acting on it.
Take those three into the staffing conversation instead of a ratio and the discussion changes shape. It stops being a negotiation about fairness and becomes an argument about where a specific, measurable amount of capacity is going.
There is no single correct ratio, and the figures quoted as standards are averages across companies with different deal sizes, products and sales motions. The useful question is coverage against deals that are genuinely real, because a team can be short of capacity and spending most of it badly at the same time.
Sometimes, and the test is whether the existing team’s time is going to deals that close. Benchmark findings show sales engineers spend about forty percent of their time on deals that genuinely close, so hiring at the current ratio scales the other sixty percent at the same rate.
Six anonymous questions, fifteen minutes, inside a meeting your team already holds. It will tell you where the hours are going and at what point your engineers are joining deals, which is the evidence a ratio cannot give you.