The IT services buyer of a decade ago took a cold call to learn what was possible. The one we talk to now has read the analyst reports, sat through three reference calls, and has a shortlist in a spreadsheet before any vendor knows the project exists. Opening a conversation with that buyer is a different craft, and most outreach has not caught up.
What the buyer already knows
By the time an enterprise IT services opportunity is visible from the outside, the committee has usually met more than once. They know the category, they know the incumbents, they have a view on the pricing model, and they have a rough idea of who they will invite. The vendor that calls to "introduce our capabilities" is telling them things they wrote down a month ago.
This is the single most common reason outreach into IT services buyers fails: it is pitched at the stage the buyer was at last quarter.
What still moves them
- A specific observation about their situation. Not "companies like yours", but "you announced a core banking migration in March and the integration partner you named has not done one at that scale in Europe". It has to be true, and it has to be the kind of thing they would want to know. This is research, not copywriting, and there is no shortcut to it.
- Evidence of a comparable engagement. Buyers at this stage are mostly de-risking. A conversation that offers to walk them through how a similar programme was run, including what went wrong, is one they will take. A conversation that offers a demo is not.
- Access to the person who did the work. The practice lead who ran the comparable programme is worth more on a first call than any salesperson, and buyers know it. If you can offer that person's time, say so in the first message.
- Timing against a real deadline. A regulatory date, an end-of-support date, a contract renewal. Buyers in motion respond; buyers at rest do not, however good the message.
What no longer does
- The capabilities deck. They have seen a hundred and they all have the same five pillars.
- Claims of partnership tiers and certifications. Table stakes, assumed, and not a reason to take a call.
- "We'd love to learn more about your priorities." They are not going to brief a stranger. The research should already have a view on their priorities, and the message should state it.
- Volume. Sending more of a message that does not land to more people at the same company produces an internal note that says "block this domain".
Getting onto the shortlist from outside
The honest answer is that it is hard, and it mostly happens through one of three doors. The first is the reference: someone the buyer trusts says your name, which is why the network around a buying committee is worth mapping as carefully as the committee itself. The second is the adjacent problem: a smaller engagement on something the committee has not yet scoped, which earns the right to be in the room when the bigger one is. The third is the second opinion: an offer to review the plan they already have, which buyers accept more often than vendors expect, because committees are nervous and a free sanity check is cheap.
All three require knowing the account well before the first message. None of them is improved by sending the message sooner.
The buyer is not waiting to be educated. They are waiting to be surprised by someone who did the reading.
What this changes about the programme
For IT services clients we weight the first half of an engagement heavily towards research: committee maps, trigger events, the incumbent landscape and, where it exists, the public record of the buyer's own words. The outreach that follows is lower volume and more specific, and it is aimed at the stage the buyer is actually at. Fewer messages, more replies, and meetings that the practice lead is glad to take. We have written more about how we work in this market on the IT services page.
