Do Indian Founders Need a US Company for US Contracts?
In this guide
Consider an illustrative SaaS company with an Indian private limited company and several US enterprise customers.
The business is growing, but every US contract is signed by the Indian entity. That may be a valid structure, yet the governing law, dispute forum, tax, transfer-pricing and collection mechanics need deliberate review.
His CA had recommended it years earlier: keep all revenue flowing into the Indian entity, avoid FEMA complexity, keep GST filing simple. On paper, it made sense.
In practice, it created a legal exposure that compounded silently until it surfaced at the worst possible moment.
What Went Wrong
Suppose one contract specifies California law and a California forum. A dispute could then require the Indian company to defend or resolve the matter in that forum even though it has no US entity or operational setup.
The Indian entity had no registered agent in California. No attorney on record. No one monitoring court filings. No one watching for legal notices.
The founder found out about the lawsuit six weeks after it was filed - from a follow-up email from the opposing lawyer. By then, the window to file a response had already closed.
The California court entered a default judgment in 47 days. Not because the founder’s position was weak. Not because the facts were against him. Because nobody showed up.
The Real Damage: Lost Future Deals
The founder’s lawyer explained that the judgment was technically unenforceable in India under Section 13 of the Code of Civil Procedure. The immediate financial exposure was containable.
But eight months later, when the founder was closing a major US enterprise deal - a healthcare technology company running standard vendor due diligence - their procurement team found the unresolved California judgment in 11 minutes using standard US legal databases.
The deal was dead in four days. No negotiation. No escalation path. Procurement policy is procurement policy.
In California, a court judgment is enforceable for 10 years and renewable for another 10. Every US enterprise sales process, every acquisition conversation, every institutional investor doing due diligence would find that judgment on record.
The Structural Problem
Each US customer contract signed by the Indian entity can create obligations under the chosen governing law and dispute forum. The risk depends on the contract and the company’s ability to perform and defend it.
A counterparty may enforce the dispute clause in the agreement. Review governing law, forum, service of process, limitation of liability and enforcement before signing.
If the entity on the other side of the contract has no presence in that jurisdiction - no registered agent, no attorney, no one watching for process servers - the legal system records it as a default.
The Fix
The solution was straightforward:
- Delaware C-Corp incorporation - $800 one-time cost
- Registered agent in Delaware - $150/year, with a physical address and monitored mailbox for all legal and government correspondence
- Contract migration plan - obtain counterparty consent before assigning or novating any active agreement
- Contracting policy - decide which entity signs based on tax, regulatory, liability and commercial advice rather than customer location alone
The next US enterprise prospect ran the same standard procurement check six months later. Clean record on the Delaware entity. Contract signed in three weeks.
The total cost of building proper US legal infrastructure was less than the legal fees from the first week of the California default proceeding.
Where ZenoLedger Comes In
This is exactly the gap ZenoLedger exists to fill.
Most formation services - Stripe Atlas, Clerky, Doola - handle the US side well. But none of them address the India side: FEMA/RBI compliance, Form ODI filing, outward remittance reporting, Annual Performance Reports, transfer pricing between your Indian and US entities.
ZenoLedger handles both sides end-to-end:
- US entity formation - Delaware C-Corp or LLC with a registered agent, EIN, and compliance calendar
- Banking and payments - Mercury bank account, Stripe gateway, US credit cards
- RBI/FEMA compliance - Form ODI with your AD bank, UIN registration, APR filing
- Ongoing compliance - US annual filings, Indian tax obligations, transfer pricing documentation
If an Indian entity signs all US customer contracts, review whether that remains the right structure as the business grows. A US entity can help in some situations, but it also adds tax, filing and FEMA obligations; the answer depends on the contracts and operating model.
The judgment does not come when you expect it. It comes in a procurement email, on a deal you needed to close.
Book a free consultation to get your US entity structure right from day one.
This article was inspired by a detailed case study shared by Sapna Sarda on X.
Discuss your circumstances
Requirements and costs depend on your company and can change. Discuss current requirements with the relevant professional before acting on general guidance.