US market entry for Indian SaaS: a 90-day outbound plan

Most Indian SaaS founders plan the US the way they planned India: hire a rep, give them a list, wait. In the US that costs $96,000 a year for one SDR who takes five months to ramp and knows nothing about your product. There is a cheaper sequence of steps, and it front-loads the things that decide whether outbound works at all. Here is the plan we run, week by week.

Weeks 1 to 2: infrastructure before anyone writes an email

Buy two or three lookalike domains. Host the mailboxes with a US provider. Set SPF, DKIM and DMARC on every one. Start warming against real inboxes. Nothing goes to a prospect for three weeks, and that is the point: the domains need history before they carry your name.

At the same time, write down the ICP in one paragraph a stranger could act on. Company size, the title that feels the pain, the trigger event that makes them look. If you cannot name the trigger, you are not ready to source a list.

Set up the CRM the way you want the data to arrive. Every held meeting gets logged with the signal that produced it, so by day 90 you know which triggers convert.

Weeks 2 to 3: five conversations by hand

Before any automation, book five US meetings yourself. Warm intros, a founder-to-founder LinkedIn note, an old customer who moved. Take the calls yourself. You are not selling yet. You are listening for the first objection, the phrase they use for the problem, and what made them take the meeting.

Those five calls write the sequence. Skip this step and you will automate a message that has never been tested on the buyer you are targeting.

Weeks 3 to 4: source the first list off signals

Now build the list, and build it from events rather than titles. Companies in your segment that hired a sales leader in the last 30 days, raised a round, posted for the role your product replaces, or opened a US office. Two contacts per company, three at most. Aim for 300 accounts, not 3,000. A small list you can personalise beats a large one you cannot.

Write the sequence. Five steps over three weeks. Step one names the signal in the first line. Step three adds a LinkedIn touch for anyone who opened twice. Every email under 80 words, first person, one ask, founder's signature.

Weeks 4 to 8: run it on US time, answer replies in US hours

Domains are warm. Sequences fire between 7:30am and 9:30am in the prospect's own timezone. Someone on your side answers positive replies within two hours of US business hours, which in practice means a founder or a first hire working 6pm to midnight IST for the first month. Book meetings into US-friendly slots and take them.

Track three numbers every week: reply rate by signal type, reply-to-meeting rate, and show rate. If reply rate is under 3% after two full sequences, the copy or the signal is wrong. Change one thing at a time.

Weeks 8 to 12: cut what did not work, widen what did

By now you have data. Drop the triggers that produced replies but no meetings. Double the list on the trigger that produced held meetings. Rewrite step one for the segment that responded. Add a second sending domain set if volume is climbing past 6,000 a month.

If you are holding eight or more meetings a month by week 12, the motion works and the question becomes capacity. That is when a US hire makes sense: they walk into a machine that already books, instead of building one from a blank list.

What the plan costs if you do it yourself

Domains and mailboxes, a sequencer, a data source with signals, an enrichment tool, and someone's evenings for three months. Call it $400 to $800 a month in tools and most of a founder's time. It is doable. Most founders do the infrastructure half well and run out of patience before the signal half is right.

What it costs if we build it

A Sprint is $3,000 one-time and ships the engine in 14 days, into your accounts. The US market entry pack adds $750 for the US-hosted domains, timezone scheduling and a copy review. The Intent Watcher finds the signals, the Sequence Composer writes off them, the Reply Triager sorts the inbox and the CRM Auto-Pilot logs the meetings. You still take the calls. You also keep the code.

Either way, the order of operations is the same. Infrastructure, five manual conversations, a signal-led list, US-timed sending, replies answered fast. The founders who skip a step are the ones who conclude the US is hard.