Getting your first 10 US customers before anyone is on the ground

The short version. You get the first 10 US customers from India by behaving local before you hire local. I would narrow the wedge until the buyer can name the pain in a sentence, build proof that survives a forwarded email, set a buyer-safe commercial path, and sell around US hours with founder control. The ground team comes after repeatability. Distance is a tax.

Before you start:

• Pick a US wedge small enough that every account can be researched by hand.
• Use founder-led sales until objections, proof, pricing, and security answers repeat.
• Make timezone, contract, payment, and trust gaps boring before the first serious call.
• Customer 10 should come from the same lane as the earlier wins, or the signal is noisy.

Step 1: Pick a painfully narrow US wedge, then write what done looks like

Start with the buyer you can picture on a Tuesday morning instead of a market map from a fundraising deck. Be brutally narrow. A remote India team wins the first 10 US customers when the account list is small enough for handmade proof, named buyers, timezone-aware follow-up, and a buyer-safe contract path to feel local. If the segment needs explaining, the wedge is still mush.

Your first ICP should be a workbench, with account names, trigger events, buying committee clues, public-page language, and job-post phrases. I use Your first ICP: how to pick who to sell to before you have data when the founder keeps drifting toward TAM math. Done means a named US account list where every row has a pain, a likely owner, a current trigger, and a reason to care now.

• Narrow vertical or workflow
• Named buyer and blocker
• Clear trigger event
• Account source URL
• Pain in buyer language

Step 2: Make distance invisible, then write what done looks like

US buyers forgive distance when the packet answers risk before procurement smells risk. Make proof portable. A forwarded email should carry the problem, demo clip, deployment shape, pricing guardrails, legal basics, and security answer without forcing the champion to translate your company for a CFO. The homepage has to say the same thing as the sales email.

Remote trust also means paperwork. For US vendor files, state the contracting entity plainly, keep Form W-8BEN-E language aligned to the IRS page, describe any SOC 2 claim with the AICPA SOC suite, keep payment method choices grounded in Stripe payment method docs, and store the signed order form in a shared deal folder. Done means the buyer never pauses because India feels administratively hard.

• Single-page buyer memo
• Demo clip with context
• Security answers
• US-friendly payment path
• Signed order form template

Step 3: Run a US selling day from India, then write what done looks like

The first US customers come from calendar discipline more than heroics. Protect the overlap. I would reserve India evenings for live buyer work and move research, CRM cleanup, pricing edits, and demo teardown into India daytime so the founder's sharpest hours touch the US buyer. A delayed reply says more than your deck.

Timezone pain becomes an asset when every touch feels intentional. Send the recap while the buyer is still near the meeting, attach the exact artifact discussed, name the owner, and put the next decision in plain English. Outbound math belongs in the same rhythm, because reply panic can wreck the evening block. Done means the overnight gap never blocks legal, finance, security, or the internal champion.

• US-hour live calls
• India-day research block
• Same-day recap
• Owner for every deal
• CRM next action

Step 4: Ask: which accounts deserve founder time, and what done looks like?

Founder time is the scarcest asset before a US hire exists. Guard it hard. A polite curious prospect who needs a new category explained can eat the week, pull the demo toward edge cases, spray opinions across the roadmap, and leave the founder chasing someone else's anxiety. I score accounts by pain visibility, budget owner access, implementation surface, reference potential, and how closely the problem matches the wedge.

Use segment choice as a filter, because enterprise logos and SMB velocity ask for different proof. If that debate is still open, Enterprise or SMB first? Picking your first segment is the useful fork. Done means every founder-led call has a written reason, a named buyer, an expected objection, and a next artifact.

• Trigger visible this month
• Buyer reachable by founder
• Use case matches wedge
• Budget path plausible
• Reference value clear

Step 5: Sell a proof path, then write what done looks like

Your first US sale should feel like a controlled lab, because remote selling punishes vague pilots. Sell the path. The offer needs a clear before-state, a buyer-owned milestone, a narrow deployment surface, success evidence, and a paid next step so the customer is buying progress instead of admiring a demo. Free exploration creates false confidence.

If you sell AI, proof has to include failure behavior. The buyer wants to know what happens when the model is unsure, what data leaves their environment, who reviews the output, and how the workflow recovers. GTM for AI startups: what actually changes and what founders get wrong matters here because demos can outrun trust. Done means the proof can be repeated by the same buyer type without a custom services cave.

• Paid proof scope
• Start state
• Success evidence
• Failure behavior
• Expansion condition

What goes wrong

The common failure is mistaking US activity for US entry. Noise feels productive. Founders collect friendly calls, advisor intros, event chats, and LinkedIn praise while the account list stays shapeless and the offer keeps changing after every meeting. That motion produces stories for investors and confusion for buyers.

The other failure is hiring too early. Wait for signal. A salesperson without a repeatable wedge inherits fog, then turns that fog into more sequences, louder demos, stale CRM notes, and new excuses while the founder loses the clean feedback needed to fix the wedge. I prefer founder-led sales until the objections rhyme; Founder-led sales: how to land your first 10 customers covers the operating cadence, while When to hire your first salesperson, and who actually works is the hiring line I would respect.

Step 6: Turn wins into a repeatable lane, then write what done looks like

Customer 10 matters only if it came from the same lane as the earlier wins. Protect the pattern. Write the close notes while the pain is fresh, including source, trigger, buyer title, objection, proof artifact, sales cycle shape, and the moment the buyer believed. The notes become the first US playbook.

The first local hire should inherit a lane, a message, a calendar rhythm, a proof path, and a clean disqualification rule. Until then, presence can be built with sharper public pages and credible mentions; Building US trust and presence remotely on a seed budget fits that phase. Done means customer 10 can be explained without mythology.

• Closed-won source
• Repeated objection
• Proof artifact reused
• Disqualification rule
• Hire-ready lane

Common questions

Can I get my first 10 US B2B customers from India without a US salesperson?

Yes, if the founder owns discovery and the wedge is painfully specific. A US salesperson helps after objections, proof artifacts, pricing shape, and disqualification rules repeat. Before that, distance can be managed with US-hour calls, portable proof, clean vendor paperwork, and crisp follow-up from India.

Should I visit the US before customer 10?

Visit when the trip can compress active deals or deepen a segment, rather than create random meetings. A flight makes sense after named accounts, live opportunities, event density, and buyer proof already exist. Before that, the same budget usually buys sharper research and more focused founder time.

What should I outsource from India?

Outsource research operations, list cleaning, data enrichment, inbox QA, and CRM hygiene. Keep discovery, qualification, pricing, objection handling, and proof design with the founder until the pattern is obvious. The dangerous handoff is the sales conversation, because the market is still teaching the company what to become.