Where are you based? Disclose your India base on the first US call
Tell US prospects you are based in India early, then frame it around overlap, support, security, and account ownership.
Tell US prospects upfront that the team is based in India, before the buyer has to ask. Proof has to sit beside the line: overlap hours, founder-led support, a security path, and named handoffs. Delay makes geography feel like a hidden risk.
Say India before the buyer turns it into risk
US buyers rarely mind India by itself; they mind doubt about late-night fixes, data care, legal handoffs, and who owns the account after the founder hangs up. You name the base. Operating model comes next; a crisp answer makes the call feel run by an adult instead of a founder hoping the hard part never arrives.
Founders from India often over-explain the base after an awkward call, then turn a normal fact into a pitch tax. Buyers read that wobble faster than they read your deck. Stripe's global country map shows cross-border software as routine, and OWASP gives technical buyers a common web-risk vocabulary.
When should it come up?
India belongs near the start, after the buyer says why the problem matters and before you ask about process, budget, security, and timing on their side. Early is cleaner. That point tells the buyer where the work happens without letting geography hijack the whole call.
Procurement asking "Are you offshore?" is the worst doorway into the topic. By then, the buyer has built a private story around risk. Founder-led calls have to set the frame before that story hardens; the basics in Founder-led sales for technical founders who have never sold matter more than a clever origin story.
Frame geography as how you work
Travel brochures for Bengaluru, Pune, Hyderabad, or Delhi miss the point. Buyers need proof that someone wakes up with their queue, their risks, their users, and their renewal in view. Plain wins. Geography should touch overlap hours, US references if they exist, response rules, data care, and how the founder stays close until the account feels safe enough to buy.
India can even sharpen the story for an AI or developer-tool founder when the buyer sees a deep bench, hard engineering taste, fast build cycles, and founder control over the account. Shyness kills that edge. Hidden bases make every later email carry extra weight, while named bases let the rest of the deal depend on pain, proof, fit, and price.
Handle the bias without feeding it
Some US buyers still hear India and picture cheap labor, slow support, accent trouble, or a vendor who vanishes after the paid pilot invoice clears inside finance. That bias exists. Strong founders win by naming the fear in buyer words and tying each fear to a concrete rule, a Slack window, a named owner, a security page, and a weekly ship note.
Founders lose the frame when they plead with the buyer to be open-minded. Buyers owe you a fair shot only after your sales motion earns it. Cold email has the same rule; weak targeting makes geography look like the culprit, while a tight point of view changes the read, as the reply patterns in Does cold outbound still work in 2026? Benchmarks and what gets replies show.
A simple line for the first call
Your line can be blunt: "We are based in India, with US-friendly overlap, founder-led support, clear handoff rules, and named coverage for early accounts while the team grows." Silence helps. Curious buyers will ask the real follow-up, and indifferent buyers will let the call return to pain.
If the buyer asks why you led with it, the answer stays short: "I prefer to remove operational unknowns early, then focus on whether the problem is real." That sentence signals taste. Founders who plan to move beyond their own calendar need the same crisp handoff in Scaling out of founder-led sales without breaking your pipeline before a rep inherits the story.