Five calls in our last batch ended in a no, and none of the objections were about price. Each call ran 13 to 20 minutes, 82 minutes in total, so these were real conversations. The prospects told us exactly what would have to be true for a yes.
Building in-house came up most often. An AI infrastructure lead at a connected-security company said his team had already built internal tools for AI proxying, key management, and usage monitoring. He declined a meeting under a “build over buy” mandate with deadlines already set. A VP of Engineering at a large software company runs a bespoke internal gateway for AI token management and governance. He said no because of a release cycle and asked us to come back in January. An AVP in data engineering at a large asset manager would not book until he understood how the product fit his internal architecture. His team was building its own gateway, and he had already heard that Snowflake offered something similar.
Financial stability and liability came up with a different kind of buyer. A founder of an investment firm that uses CT Corp for entity management pressed hard on the liability coverage and financial stability of a newer provider compared with legacy ones. The call was long and friendly, but we never reached a meeting, and the record is marked do not call.
Across the batch, lawyer-led processes were judged too risky to automate, and strict external-vendor policies ended conversations early. You cannot talk your way past these on the call.
So this is what we now do before the pitch.
First, we send an architecture one-pager before the call. It shows where the product sits relative to their gateway, what data passes through it, and what we store and for how long. The AVP’s question was about architectural fit, and it should have been answered in writing before he had to ask.
Second, we build the build-versus-buy case for them. An in-house gateway carries an annual cost in engineering hours, plus key rotation, monitoring, and governance that someone must own after the original builders move on. We put that in a number they can check. A “build over buy” mandate can change once the cost is on the table.
Third, we have the risk pack ready: certificate of insurance, financial standing, and completed security questionnaire answers. We mention it early when a legal or security team is likely to be involved, not as a PDF after the call.
Fourth, for lawyer-led work we propose a scoped pilot with a human approval step and a full audit log. Risk teams agree to controlled scope far more readily than to automating an entire process.
Fifth, we check the vendor policy in the first minute. Can an external vendor be onboarded, and what does that take? Learning the answer after 15 minutes is the most expensive way to hear no.
Risk objections are predictable. Name the three that your buyer’s security, legal, and engineering teams will raise, and answer them before they ask. The pitch comes second.