In 2022 we were hired to sell infrastructure to the people who would otherwise build it themselves.
The buyer here is an engineer, and engineers are the hardest audience in outbound for a reason that has nothing to do with cynicism. They can do it themselves. Every managed service is competing against a competent team's belief that a weekend and an open-source project would solve the same problem.
So the conversation is never about capability. It is about what a senior engineer's time is worth and how much of it currently disappears into keeping a database upright.
What we did
Five months in the UAE, into airlines, marketplaces, banks and the data teams behind them. 25 meetings booked, 19 confirmed held, 25 companies introduced.
Aviation and travel: Emirates, Etihad Airways, Dubai Airports. Marketplaces and commerce: noon, Dubizzle, InstaShop, Kaso, Lyve Global, GMG, Al-Futtaim. Financial services: RAKBank, Daman, Oriental Insurance, YAP, Hubpay, Thndr. Media and advertising technology: ArabyAds, Connatix, Rapp.
Talking to engineers means answering the question they have not asked yet
Two things worked with this audience and both are unusual advice for an SDR.
Be specific about the technology in the first message. A vague benefit statement to a head of data engineering reads as marketing and gets deleted; naming the actual components signals that the sender knows what the product is. Reps who were coached to be less technical did worse.
And concede the obvious point early. Yes, you could run this yourself. The meeting is about whether you should, and what the two engineers currently doing it would work on instead. A prospect who has been handed his own strongest objection stops preparing it and starts thinking.
What it shows
Technical buyers reward precision and punish polish. Let the specifics into the first sentence, concede the build-it-yourself argument before they make it, and aim the conversation at the opportunity cost rather than the feature list.