The sales engineer doesn't scale. A co-worker does

Go and reread the last job ad your company posted for a security presales role. Real technical depth, the poise to sit across from the owner of a twenty-person business without talking in acronyms, and enough road time to cover more than one region. If that ad is still open after a few months, the wording isn't what's wrong with it.

When security deals stall, the reflex is that ad: we need a sales engineer. The part nobody budgets for is what happens once you've actually hired one.

You can't clone a good presales person

The profile is rare by construction. It takes enough security knowledge to survive a technical question and enough commercial instinct to avoid burying a business owner in acronyms. Very few people carry both, and those people already have jobs they like.

Say you find one anyway. Search, negotiation and ramp-up eat months, and when the hire is finally productive they cover one territory. For the second territory you start over, with a weaker candidate or a bigger number, usually both.

Then there's the way the role gets used, which never makes it into the business case. Your sales engineer doesn't appear early, where they'd earn their salary helping decide which accounts are worth a call; they appear once a deal is already wobbling and somebody has asked for a technical review. That's an emergency resource dressed as a multiplier. Every proposal queued behind that calendar reaches the customer two weeks after the conversation that prompted it, by which point the urgency has cooled and the budget went somewhere else.

The arithmetic is dull and it doesn't negotiate: the conversations you can prepare in a quarter equal your presales hours divided by the time one preparation takes. Shave the second number all you want; the first one only moves when you hire.

Train every rep instead? The market won't wait

The other route is pushing security into the sales force with courses and ride-alongs. Sound in theory. In practice you're asking dozens of people who sell connectivity and phone systems to become, in the gaps between monthly targets, people who can read a security posture and defend a managed-security quote in front of a sceptical owner.

And the window is open right now. NIS2 has applied in Italy since 16 October 2024 through Legislative Decree 138/2024, with ACN as the competent authority, but the pressure doesn't stop at the entities in scope: it travels down the supply chain and reaches SMEs as questionnaires and contract clauses sent by the companies they supply. A twenty-person firm hears about it from its largest customer, not from a regulator. Whoever is on the phone at that moment owns the conversation.

A training programme that pays off next year doesn't catch this window.

What a co-worker puts in that seat

A co-worker isn't one more tool in the stack that someone has to be talked into adopting. It's a capability sitting next to the rep while the work happens, and there are two of them.

The lead generation co-worker knows who to call and why. It reads the signals on every SME in your base (exposed assets, credentials surfacing in a data breach, questionnaires, posture, compliance coverage) and keeps that picture current, with nobody requesting a scan or opening a ticket. When an account gets worse, you hear about it while it happens rather than at renewal.

The sales co-worker knows what to say and what to propose. It builds the four-phase brief (Prepare, Discovery, Objections, Close), keeps objection answers ready that are built on that customer's own data, and lands on a service from your catalogue, at your price, inside a white-label report the customer keeps.

Underneath sit two layers worth keeping apart in your head. The signals say what is true about the account. The sales framework decides how it's said: vocabulary, discovery questions, scripts, closes, tone, quality rules. The framework governs form, never substance, and it can't make a fact true that the signals never saw. It reads like an architecture footnote, and it's the reason a rep can trust the page in front of them before dialling.

There's also a practical difference against hiring. This capability switches on across the whole sales force with no infrastructure to build and nothing to integrate, because it sits on top of the systems you already run.

What a co-worker won't do

The refusals matter as much as the features, since refusals are usually where trust breaks.

• It won't invent numbers. Where there's no figure that holds up, it says so instead of filling the gap: nothing it can't stand behind ends up on a slide. A human presales under pressure rounds up; this one stops.
• It won't sell for your rep. The relationship and the negotiation stay exactly where they've always been, because the co-worker prepares and your people close.
• It isn't a security product you resell to the SME. What the customer buys is yours, priced from your list and delivered under your brand.
• It won't certify anyone's compliance. It gets the work towards NIS2 or ISO 27001 in order and puts gaps and priorities in sequence, but the declaration belongs to the customer and whoever advises them.

None of those four lines is a gap waiting for a future release. They're product decisions, and they're the reason the brief a rep reads over the phone holds together when the customer pushes back.

So what happens to the sales engineer?

Nothing disappears. On tenders and complicated architectures, that's still the person you want in the room, and no software replaces them. What changes is everything else: they stop being the mandatory stop on every single conversation in your SME base, because preparing a call no longer depends on their calendar. You're not replacing the expert. You're just not making everyone else wait for one.