What Speaking Eight Languages Taught Me About Selling
I speak eight languages. English, Mandarin, French, Japanese, Spanish, Turkish, Persian, and Azerbaijani—and a working level of Dari. People often ask why, as if language learning is a hobby rather than a strategic choice. The honest answer is that I learned each one for the same reason: I wanted to understand how the people on the other side of a deal were actually thinking.
When you speak someone's language—their actual language, not just English with a translated slide deck— you get access to something most salespeople never reach. You understand not just what they are asking, but why they are asking it. The subtext behind a compliance question. The real anxiety underneath a “we need to evaluate alternatives.” The genuine interest hiding inside a lukewarm “we'll circle back.”
That skill—reading what is actually being communicated, not just what is being said—turned out to be the most valuable thing I brought to my years at Deutsche Bank, and eventually to building Clarm.
Financing Infrastructure Across 60 Countries
Before I moved into AI, I was a banker. I financed infrastructure projects: power plants, toll roads, port developments, hospitals. Across more than 60 countries, in partnerships that crossed languages, legal systems, cultures, and political environments.
The complexity of a project finance deal is significant. You are coordinating sponsors, lenders, contractors, regulators, and host governments, all of whom have different incentives, different risk tolerances, and different definitions of what “yes” means. A signature is not a deal. An approval is not a commitment. A “we are interested” is sometimes genuine and sometimes a polite way to exit the conversation.
Learning to read those signals accurately—in multiple languages, across multiple cultural contexts— became my most important professional skill. I made decisions worth tens of millions of dollars based on my read of whether a counterparty's stated enthusiasm matched their actual intent.
When I moved into AI at Deutsche Bank, I brought that same lens to a completely different domain. And I found something surprising: enterprise buying signals are universal.
The Universal Buying Signal Pattern
Across all those countries, all those languages, all those deal types, I kept encountering the same pattern. Enterprise buyers signal genuine interest in exactly the same way regardless of culture, language, or industry.
They ask specific questions.
Not broad, exploratory questions. Not hypothetical questions. Specific questions about their specific situation. Questions that only arise if they are mentally placing themselves inside the product.
A counterparty in a loan syndication who asked “how does this work in general” was doing due diligence. A counterparty who asked “how does this work if the host government changes the concession terms mid-project” was buying. They were already inside the scenario. They were problem-solving, not evaluating.
The same pattern holds in software. At Deutsche Bank, I watched it play out in every AI vendor evaluation. The teams that sent us generic RFPs were rarely the ones who ended up deploying. The teams that came to us with specific questions—“how do you handle our data residency requirements,” “can this run on our on-prem stack,” “what does integration with our existing workflow look like”—were the ones ready to move.
Five Enterprise Buying Signals That Don't Require a Sales Call
Based on everything I saw across banking, AI, and now SaaS, here are the five buying signals that consistently predict a real enterprise opportunity. None of them require a discovery call to detect. All of them appear in the questions prospects ask, if you are paying attention.
1. Compliance specificity
“Are you HIPAA compliant?” is a general question. “Can we configure data processing agreements for our specific PHI handling requirements?” is a buying signal. The more specific the compliance question, the more the buyer has already moved from evaluation to procurement mode.
2. Integration depth
“What integrations do you have?” is exploratory. “Can your webhook system push to our Salesforce instance with a custom field mapping?” means they are designing the implementation. They are not asking whether to buy. They are asking how to deploy.
3. Team size and volume
When someone mentions how many users, engineers, transactions, or processes they have, they are giving you the deal size in the same breath. “We have about 300 engineers across three teams” is not background information. It is the beginning of a commercial conversation.
4. Timeline language
Enterprise buyers who are genuinely evaluating use time words differently than browsers. “We would need this before Q3” is a contract timeline, not a preference. “Our current contract renews in August” is an invitation. Listen for dates.
5. Security and data questions at depth
A prospect who asks about your security certifications is doing research. A prospect who asks where their data is stored, who has access, how it is encrypted at rest and in transit, and whether an on-prem option exists—that prospect has a security team involved. Security teams only get involved when procurement is already happening.
Why This Is the Core of How Clarm Works
When I designed Clarm's intent detection layer, these were the signals I built it around. Not page views. Not session duration. Not form completions.
The conversation is the signal. The specific question is the signal. The moment a visitor shifts from “what is this product” to “how would this work for us specifically”—that moment is detectable, and it is the moment that matters.
Clarm's AI reads those conversational signals in real time. When a prospect asks a compliance question, the AI flags buying intent. When they ask about integration depth, it offers to route them to a demo or a technical conversation. When they mention team size or timeline language, that information goes into the lead profile so the founder or sales team sees it the moment they look at their pipeline.
The result is that enterprise buyers get the response they need to move forward, at the moment they need it, without requiring a human to be available 24/7. The signal does not decay. The conversation does not die overnight. The deal does not go cold while waiting for someone to check their inbox.
The Lesson I Keep Coming Back To
After everything I have seen—across languages, continents, industries, and deal types—the fundamental truth about enterprise buyers is simple.
They are busy people making consequential decisions. They ask specific questions when they are ready to move. And they make decisions based on who respects their time and their intelligence enough to actually answer those questions—specifically, accurately, immediately.
Not in a follow-up email. Not after a 30-minute intro call. Now, when they are thinking about it.
That is what Clarm is built to do. That is what 20 years of watching enterprise deals succeed and fail has convinced me matters more than almost anything else in the buying process.
Going Deeper
If you want to see how these buying signals translate into a systematic pipeline, read the buying signal pipeline for developer tools. For the compliance and security side specifically, see the HIPAA-compliant website chat guide and the on-prem inbound automation guide for finance teams.