Sales engineers spend about forty percent of their time on deals that genuinely close, and not one engineer measured has reported being above eighty percent.
Taking the midpoint of each band, the field average is just under forty percent. Fifty seven percent of engineers put themselves at forty percent or below. One in ten puts themselves at twenty percent or less.
The ceiling is the part leaders tend to sit with longest. Nobody measured has reported spending more than eighty percent of their time on deals that genuinely close. Not one person. Whatever the best case looks like in this profession, nobody has reached it yet.
A sixty percent misallocation across a team of forty engineers is roughly twenty four engineers' worth of effort going to deals that will not close. Priced at a loaded cost per engineer, that is a number a revenue leader can put in a plan. It is also the number nobody has, because no system in the stack records which deals an engineer worked and which of those were real.
This is the measure that turns a qualification problem into a capacity problem, and capacity is the version that gets funded.
The strongest organisation measured is more than double the weakest. All of them are selling technical products to enterprise buyers with broadly similar sales cycles.
Getting into deals early does not protect the week on its own. Nothing in the field so far shows allocation improving simply because access improved.
Six fixed questions, put to a whole team at once inside a meeting they already hold. Fifteen minutes. Everyone answers at the same time from their phone, anonymously, and the distribution appears in front of the room as it fills.
The wording never changes between organisations, because changing it would destroy the comparison. Nothing is attributed to a person and nothing is attributed to a company. Leaders see their own team’s results before anyone sees anything.
This is a small number of organisations measured in depth rather than a large survey. It is not a representative sample of the profession and it is not presented as one. What it is: the same six questions, asked the same way, of teams who answered without a manager watching.
Most teams have never seen this figure for themselves. That is the first problem, because an allocation nobody measures cannot be defended in a staffing conversation or challenged in a forecast review.
Ask the question on a cadence. One question, asked of the team each quarter, anonymously: what share of the last fortnight went to deals that will genuinely close. It costs nothing and it produces a trend line, which is worth more than any single reading.
Then connect it to a decision. The number on its own changes nothing. Attached to a specific question, such as which deals an engineer should decline this quarter, it becomes the argument for declining them.
The harder problem underneath is that engineers often cannot decline, because the request arrives as a commitment somebody else already made. That is a routing problem rather than a time management one.
According to the Deal Flow Benchmark, sales engineers spend about forty percent of their time on deals that genuinely close. Fifty seven percent of engineers report forty percent or less, and none of the engineers measured reported more than eighty percent.
It is both, but capacity is the version leadership can act on. A sixty percent misallocation across forty engineers is roughly twenty four engineers’ worth of effort spent on deals that will not close, which converts directly into a cost figure using a loaded cost per engineer.
The benchmark is free and it stays free. Six questions, fifteen minutes, answered anonymously inside a meeting your team already has. You get a written read on your own numbers and where they sit against the field. There is nothing to install and nothing to buy.