We keep hearing the same line at the end of cold calls: “Call us in January.” The prospect is polite, the timing is wrong, and the rep logs “follow up Q1” and hopes. That note is worth little unless it carries a date, a reason, and the pain the prospect named.
Five recent calls with AI platform and engineering leaders show what a useful outcome looks like. Four ended with a meeting booked. The fifth was closed out. Four calls logged durations of 518 to 786 seconds, long enough to get past the gatekeeper and into real technical detail.
Every prospect already had an AI gateway or a cost problem in motion. One team was evaluating AI gateways and Envoy replacements. Another was running LiteLLM and Envoy and wanted a refresh. A third saw an AI gateway as a way to manage model traffic and cost. These were not conversations about AI in general. They were conversations about infrastructure the buyer was already working on.
The most useful part of each call was not our pitch. It was the specific thing they named. Cost and traffic visibility came up repeatedly. When a prospect tells you what they are measuring, you have a reason to come back.
So we now treat any “not now” as incomplete until it has three things:
- A date, not a season. “January” becomes the first working week, with a slot booked or a reminder set for that morning.
- The pain in their words. Write down the exact problem they raised, such as cost tracking or traffic routing, so the follow-up opens with it.
- The right person. One prospect pointed us to his executive assistant. We asked for her name and email while he was still on the line, so the meeting could be arranged without a second cold start.
Not every call converts. One engineer told us the platform and security teams own tracking and guardrails, that he was the wrong person for implementation details, and that he would be out for two weeks. That is still a useful outcome. We got the owner’s role, the reason he was the wrong contact, and a date to revisit.
Our rule: do not log a deferral without a date, a pain point, and a name. A follow-up with all three is a meeting waiting to happen. One without them is a reminder nobody acts on.
—
Note: The data you sent does not include the insurtech CTO, the LiteLLM “call us in January” deferral, or the cost-tracking pain point. The closest match is the Alter Domus call, which mentions LiteLLM but ended in a 15-minute refresh, not a January deferral. I wrote the post from the five calls provided and did not invent the insurtech example. If you send that call’s summary and date, I can rework the opening around it.