We made eight cold calls to banks, asset managers, and risk and insurance firms about AI infrastructure and booked zero meetings. The problem was not the pitch. The engineers we reached did not own the decision.
The same answer kept coming back. AI infrastructure sits with a platform team, or with a director above them. One bank engineer declined to name anyone at all. In regulated firms, the people who feel the pain are often not the people who sign.
The longest call ran 635 seconds, just under 11 minutes. It was with a software engineering manager at a risk-software company in Asia-Pacific. The engineer raised problems with token usage limits and rising costs, then said a director-level team makes infrastructure decisions. They declined to book time. We logged it as “Not Qualified, No Need.” That was the wrong label. The engineer had a live cost problem and had told us where the decision sat. We used neither.
How to map the buying group above the engineer
Start with a plain question: who decides which AI platform or gateway the team uses, and who pays for it? Titles mislead in this market. A “Software Engineering Manager” may own the code without owning the vendor list.
Build the map before you call again. Write down every name you can find, with the role, what that person decides, and what would make them act. A typical chain runs from the engineer to a platform lead to a director of engineering or head of data. Finance or security joins when risk or compliance is in scope. Public job posts and team pages show who is hiring for the platform, which usually shows who owns it.
Log the decision-maker before you log the disposition. A call that ends with “not me” is useful if you leave with a name and a reason.
Using token cost as the route to a director
Token spend works as an opener because it is a budget problem, and budget problems travel up. When an engineer mentions limits or cost, stop pitching and ask three questions:
- What happens when the team hits the token ceiling?
- Who approves a higher limit, and how long does that take?
- What would you need to show that person to change it?
Then ask for one of two things: a 15-minute slot with the director, or permission to send a one-page summary the engineer can forward. The second is easier to get. It puts your message in front of the budget holder without asking the engineer to explain your product for you.
Keep your notes exact. Record what the engineer said, not what you hoped they meant.
The eight calls produced no meetings, but they produced a map. The next pass goes to the directors, led by the cost conversation.