Selling software to operations buyers

Vertical SaaS companies often aim outbound at the most senior technical title they can find. It feels like the safe choice. For a lot of products it is the wrong one, and the reason is simply how much cold email each inbox already receives.

The inbox arithmetic

A CTO or VP of Engineering at a growing software company is one of the most heavily prospected people in business. Their inbox has trained them to delete anything that pattern-matches to outreach within about a second, and they are right to.

A head of operations at a 300-person construction contractor, a logistics firm running four depots, or a field-service business with ninety engineers is not in that position. They receive far less, and what they do receive tends to be worse — generic, obviously merged, clearly untargeted.

The same quality of message produces a materially different outcome, for no reason other than the level of competition in the inbox.

They also feel the problem directly

This is the more important half. Operational buyers live inside the problem your software solves, every day, in a way an executive sponsor usually does not.

The person doing schedule reconciliation across four sites in a spreadsheet does not need to be convinced the problem exists. They need to believe you can fix it and that implementing you will not become their third job. That is a much shorter conversation than persuading someone abstractly interested in efficiency.

Triggers, not firmographics

Filtering on industry, headcount and region describes a company that could plausibly buy. It says nothing about timing, and timing is most of what determines whether a message gets a reply.

What actually changes someone from indifferent to interested is a change in their circumstances. The ones worth searching for:

• A new operations hire, 30 to 90 days in. New leaders arrive wanting a visible early win and have unusual licence to change things. This is the single strongest trigger we know of.
• A second site, depot or region. Processes that worked at one location break at two. This is often the exact moment spreadsheet workflows stop being viable.
• Hiring for a role that exists to patch a process. A posting for a "scheduling coordinator" or "data reconciliation analyst" is a company paying salary to work around a missing system.
• A system migration. An ERP or finance change orphans adjacent workflows, and someone is currently rebuilding them by hand.
• A compliance deadline with a date. Regulatory dates create budget and urgency that no salesperson can manufacture.
• Rapid headcount growth in the operating function. Field teams growing faster than the systems supporting them.

All of these leave public traces — job postings, press releases, LinkedIn updates, planning applications, tender notices. That is what makes them searchable, and it is why research is most of the work.

What a first message looks like

The difference between a 1% and a 5% reply rate is rarely the subject line. It is whether the first sentence proves a person looked at this specific company before writing.

"I saw you're in field service" is a merge field wearing a disguise. "You posted for a second dispatch coordinator in Leeds three weeks ago" is evidence, and evidence buys the next fifteen seconds.

After that, keep it structurally simple: name the trigger, name the problem it usually creates in their words not yours, say in one line what you do about it, and make a small ask. Not thirty minutes to explore synergies. Something proportionate to a cold email from a stranger.

The vocabulary test

Operational buyers are quick to spot someone who has never done the work. If you write "streamline your workflows" you sound like software marketing. If you write about the Thursday afternoon reconciliation, the double-entry between the depot system and the finance system, the driver who calls in because the schedule changed after they left — you sound like someone who has been in the building.

Write in the vocabulary of the job, not the vocabulary of the category.

This is also a real constraint on who should run outbound for you. Someone who cannot describe the buyer's Tuesday cannot write a first line worth reading.

Where this does not apply

If your product is genuinely technical and the buyer is genuinely an engineering leader, target them — just accept the inbox competition and compensate with far sharper research. And if your ACV is a few thousand dollars a year, the maths does not support a human-researched motion at all; that is a self-serve and product-led problem wearing an outbound costume.