IT services buyers are not short of vendors. They are short of reasons to spend forty-five minutes with a new one. The approaches that earn a first call establish three things before asking for anything.
One: that you understand their environment, specifically
Not their sector. Their environment - the migration they are midway through, the platform they are consolidating, the compliance date on their calendar. Sector-level relevance reads as research; environment-level relevance reads as understanding.
Two: what doing nothing costs
Every technical buyer has a backlog of things that would be good to fix. The item that gets scheduled is the one with a cost attached to leaving it alone - downtime, audit exposure, engineering hours burned on maintenance rather than delivery.
The proposal that describes the architecture competes on rate card. The one that describes the consequence competes on outcome.
Three: why this conversation, now
A first call needs a reason to happen this month rather than next quarter. Absent a trigger - a contract end, a project start, a regulatory date - the meeting will be agreed politely and rescheduled indefinitely.