The Ratio Most Teams Inherit

SaaS taught a generation of Sales Leaders a comfortable ratio: One Solutions Engineer for every three, four, sometimes five AEs. Demos were repeatable, the product was stable, and the SE’s job was mostly to show what already worked.

That ratio doesn’t survive contact with AI and infrastructure sales.

When the buyer is a Staff Engineer evaluating an inference platform, or a data team testing a vector database against their own workloads, the technical evaluation isn’t a step in the deal. It is the deal. Each one is bespoke. Each one runs on the customer’s data, in the customer’s environment, against the customer’s definition of success.

One SE can run two or three of those well at the same time. Not eight.

So the maths changes. At the companies that sell well into technical buyers, ratios much closer to one SE for every one or two AEs are common at this stage – and occasionally better than one to one while the product is still young.

What Under-Resourcing Actually Costs

Running lean on SEs rarely looks like a problem on a spreadsheet. AE headcount drives pipeline, and pipeline is what the board asks about.

But the cost shows up downstream, in ways that are easy to misattribute.

• POCs that drift. An SE juggling six evaluations can’t set success criteria up front on any of them. Without criteria, evaluations don’t end – they fade.
• AEs doing technical work badly. When the SE is unavailable, the AE answers the architecture question. Sometimes they get it right. The buyer notices when they don’t.
• Founders pulled back in. The technical founder becomes the overflow SE. Every hour spent on a customer’s cluster configuration is an hour not spent on the product.
• Slower learning. SEs hear the sharpest product feedback in the company. When they’re overloaded, that signal never makes it back to the roadmap.

Win rates fall, cycles lengthen, and the diagnosis is usually “we need more pipeline”. So the company hires another AE.

And the SE bottleneck gets worse.

Plan SE Capacity Like Sales Capacity

The fix is to stop treating Sales Engineering as a support function and start modelling it as capacity.

Start from the evaluation, not the AE. How many technical evaluations does the team need to run per quarter to hit the number? How long does a typical one take? How many can one SE run in parallel before quality drops? That gives you SE headcount directly – and it usually gives you a higher number than the inherited ratio would.

Then sequence accordingly. At a Developer Tooling company with a self-serve product and short evaluations, the hire after the Founding AE might well be a second AE. At an AI platform selling agentic workflows into regulated enterprises, with eight-week proofs of concept and security reviews to match, it’s almost always an SE.

The first of those hires matters most, and we’ve written about why in Your First Solutions Engineer Decides Whether the POC Closes. This is the next question: once the first SE is in seat, how fast does the function need to grow behind them?

Usually faster than the plan says.

Hiring for the Pressure, Not the Demo

Building SE capacity is also a hiring problem, because the profile has shifted.

The SaaS-era SE was strongest at the polished demo. The AI-era SE needs to be strongest when the demo breaks: debugging an integration live, scoping a POC that a sceptical engineer will accept, and saying no to the evaluation that will never convert.

What to look for:

• Builder credibility. Ideally someone who has shipped production systems, not just presented them. Technical buyers can tell within ten minutes.
• Commercial instinct. The best SEs qualify as hard as the AE does. They know which evaluations are worth running, and which are free consulting.
• Writing. Success criteria, architecture notes, POC summaries. Much of the job happens in documents the champion forwards internally to people the SE never meets.
• Range across the stack. In infrastructure especially, the problem is rarely confined to your product. It’s the five systems either side of it.

These people are scarce, and they’re courted constantly by the frontier labs and the larger platforms. Start the search earlier than feels necessary, and expect the comp conversation to look closer to engineering than to sales support.

The Principle

In technical sales, the AE opens the door. The SE decides whether anyone walks through it.

Underfund the second, and the first stops mattering.

If you’re modelling your next few GTM hires and the SE line looks thin, happy to give a second perspective.