Most cold calls end in the first thirty seconds because the prospect has no reason to care who is calling. This one went the other way, and the reason was that the prospect remembered us.
The contact is a Head of Data & AI at a fund administrator. He recalled earlier conversations with our co-founder. Our rep didn’t need to open with a pitch. The prospect already knew we were not a random caller, and he knew the tools we were discussing.
The call lasted 713 seconds, just under 12 minutes. They covered the stack he runs today: LiteLLM for model routing and Envoy for traffic. That detail mattered. When a rep can name the exact components a buyer runs, nobody has to explain why the call is happening. The conversation moves to the trade-offs between his setup and ours.
Timing was tight. He was about to walk into a client meeting, so a standard ask would have failed. A full discovery session or a demo would have meant a long commitment from someone with no spare time. Instead, the rep asked for a 15-minute refresh, and he agreed.
That is the second half of the lesson: keep the next ask small. A 15-minute refresh is easy to accept, easy to put in a diary, and easy for the prospect to justify to himself. It also gives both sides a reason to talk again without pretending the first call solved everything.
Scheduling happened in the same motion. Rather than chase a calendar later, the next step is an email to his executive assistant to lock in a time. That keeps the momentum while the intent is still fresh. A booking that depends on a follow-up three days later often never happens.
Across the five calls in this batch, four ended with a meeting booked. Five calls is not a benchmark, and we won’t claim a pattern from it. What this call does show is a sequence we can repeat: confirm the prior relationship, name the actual stack, and make the next step smaller than the prospect expected.
Three things we are taking from it.
First, check the CRM and email history before dialing. If anyone at the company has spoken with us, say so in the first minute.
Second, name the tools they actually run. Generic talk about AI infrastructure gets polite hangups. Specific talk about their routing and proxy layer gets questions.
Third, ask for the smallest meeting that still moves the deal. Fifteen minutes is often enough, and it is much harder to refuse.