Why India-Resident Delaware C-Corp Founders Should Set Up a Wholly-Owned Indian Subsidiary

You incorporated in Delaware because that's what US investors wanted. You live and work in Bangalore. And because it's simpler, and because the tax looks great, you pay yourself as a contractor to your own company: a 1099 line, a W-8BEN on file, an invoice every month. It works. Right up until the day it very much doesn't.

What you've actually done is turn yourself into a foreign vendor to your own startup. It's a comfortable arrangement in month three and a structural liability by month eighteen. Almost every India-resident founder we work with arrives at the same question somewhere between incorporating and their first institutional round: do I really need an Indian subsidiary? The honest answer is almost always yes, and almost always sooner than they hoped.

The short version

If you're an India-resident founder of a Delaware C-Corp, set up a wholly-owned Indian subsidiary and move onto its payroll as a full-time employee.

Do it before your first Indian hire, your first enterprise customer, or your first Indian investor, not after. The structure is cheap to build early and painful to retrofit under pressure.

Reason one: The contractor shortcut is a trap

A founder billing their own company can be taxed on a presumptive 50% of receipts, up to ₹75 lakh of receipts, provided they come almost entirely through banking channels. That can shave something like ten to eleven lakh off the annual bill. It's a genuine saving, and it's exactly why so many founders start here.

A few numbers worth knowing:

• ₹50 cr: turnover below which India's POEM guidelines don't apply (CBDT Circular 8 of 2017)
• ₹75 L: Section 44ADA receipts cap, where at least 95% of receipts come through banking channels
• ~₹10 L: the yearly saving that tempts founders into contractor status

But here's the tempting mistake: paying yourself as a contractor optimizes one line of your tax return and quietly worsens everything else. Your equity, your labour-law exposure, your Permanent Establishment story, and your visa clock.

Tax authorities everywhere are hostile to a founder being paid as a contractor by their own corporation. The IRS openly disfavours promoter-contractors of closely-held C-Corps and will recharacterise the arrangement as wages. India layers its own regime on top: provident fund, gratuity, ESI, and state labour codes attach to long-running de-facto employment regardless of the label on the invoice, and authorities can reclassify a contractor as an employee and assess back-dated liabilities.

Reason two: Running the company from India creates risks the US parent can't see

The bigger exposure isn't personal, it's structural. If the real work of the business happens in India, Indian tax law can reach the US parent in two ways. The first is Permanent Establishment: your activity here can create a taxable presence for the Delaware company, so a slice of its profit becomes taxable in India. The second, and the one that keeps advisers up at night, is Place of Effective Management. If the mind and management of the parent sit in India, POEM can treat the entire US company as an Indian tax resident on its worldwide income.

Early on you're usually under the threshold. That's not a reason to relax. It's the window in which the fix is cheap.

There's real breathing room here: the POEM guidelines don't apply below INR 50 crore in turnover, so most companies sit outside them for years. But the ceiling is real, and the structural fixes, a genuine non-India centre of governance, an approval matrix that's actually followed, and the founder employed by the Indian subsidiary rather than contracting across the border, are far easier to put in place before you cross it than after. An Employer of Record or a well-drafted transfer-pricing agreement helps at the margins, and Indian courts have accepted that arm's-length remuneration limits attribution, but neither cures a company whose de-facto headquarters is a founder's apartment in Koramangala.

Reason three: The subsidiary unlocks the things you actually need

Set the risk aside for a moment, because the subsidiary isn't only defence. It's the thing that makes the rest of your India life possible.

ESOPs for your team. Equity in the US parent can't flow cleanly to Indian contractors for RBI and FEMA reasons. If your best engineers are contractors, they forfeit the single largest upside of joining a startup, and you lose your sharpest retention tool. Employees of an Indian subsidiary can be granted equity properly.

Invoices customers will accept. Almost nothing of substance happens in India without GST registration and a PAN, which the subsidiary gets at incorporation and the foreign parent effectively can't. The first time a real enterprise customer asks for a GST invoice, the absence of an entity becomes a live deal-blocker. And Indian payment gateways like Razorpay and Cashfree onboard Indian companies far more readily than foreign ones.

Indian capital. SEBI-registered VCs, Indian angels, corporates, family offices, and government grants are largely unable or unwilling to invest into a US parent, and standard SAFEs aren't available to Indian residents for FEMA reasons. The subsidiary opens the now-standard tripartite put-option route through which Indian domestic money reaches US-topco / India-sub startups.

Your own US visa. An Indian entity that genuinely employs you builds the overseas employment history the L1 intra-company transfer depends on, and supports O1, EB1, and business-visa petitions down the line. Contractor arrangements simply don't create that record.

The timing: So when do you actually pull the trigger?

Almost every reason above goes live within the first twelve to eighteen months, and most founders hit several at once. In practice, four triggers force the decision. If any already applies, or will within the next year, you should already be on the subsidiary's payroll, or moving onto it.

1. Raising from Indian or US VCs. Indian investors condition funding on founder employment with the in-country group entity, and US institutional VCs increasingly expect the same clean IP chain and founder employment, diligenced at the seed-to-Series-A boundary.
2. Drawing a regular INR salary with benefits. A payrolled salary produces Form 16, a clean TDS history, and unlocks PF, gratuity, group health, and ESIC, none of which ad-hoc cross-border wires into a personal account provide.
3. Qualifying for an Indian home loan, credit card, or mortgage. Banks underwrite against salaried documentation. Contractor founders report lower sanctioned amounts, extra collateral demands, and outright declines.
4. Preparing for a US visa petition, especially the L1. The L1 needs twelve continuous months of prior employment with a non-US group entity, and the clock only starts once you're genuinely on the subsidiary's payroll. There's no retroactive synthesis.

The exceptions: When waiting is defensible

There's a narrow set of cases for deferral, genuinely edge cases, not a path. The clearest is the pre-product solo founder: no Indian teammates, no customers, no revenue, no office, still coding alone on a laptop. No team means no ESOP problem, no business yet means PE is hard to assert, and no engaged people means no misclassification angle. But that window closes the instant the first engineer is hired or the first customer signs, usually within weeks of launch. So start the incorporation during the quiet phase and have the entity live when that day arrives.

Two other situations can justify a short delay. A founder relocating to the US within 60 to 90 days on an approved visa, with no plan to keep any Indian team, customers, or operating presence, can reasonably stay Delaware-only. And a small team held for a three-to-six-month bridge through a reputable Employer of Record can work as a stopgap. Though an EOR covers only labour-law and partial PE exposure, does nothing for ESOPs or visas, and usually won't onboard founders, so most companies that start there incorporate within a year anyway.

The takeaway: Build the body before you need it

The Indian subsidiary is easy to file under bureaucracy and defer. That framing is the mistake. It isn't overhead. It's the legal body your India operations, your team's equity, your customer contracts, your domestic fundraising, and your visa path all have to run through. Founders who wait aren't saving money. They're deferring a larger, messier bill and taking on avoidable risk in the meantime. Set it up before you need it, put yourself on its payroll, and let the rest of the structure fall into place around a clean core.

About Inkle

Cross-border tax, compliance, and structuring for US-India startups

Inkle helps startup founders incorporate and run the US-India group structure: Delaware C-Corp and Indian subsidiary, intercompany MSA and transfer pricing, founder employment and payroll, and US visa-petition support.

Talk to Inkle → 

Frequently asked questions

Does an India-resident founder of a Delaware C-Corp need an Indian subsidiary? 

In almost every case, yes, and usually earlier than founders expect. Once you have Indian teammates, Indian customers, Indian investors, or a US visa plan, a wholly-owned Indian subsidiary with the founder on its payroll is the structure that keeps ESOPs, tax exposure, labour law, and fundraising clean.

Can a Delaware C-Corp grant ESOPs to Indian contractors? 

Not cleanly. Equity in a foreign parent can't flow to Indian contractors the way it flows to employees, for RBI and FEMA reasons. Granting ESOPs to your Indian team generally requires them to be employees of an Indian entity, which means the subsidiary.

Does setting up an Indian subsidiary remove Permanent Establishment risk? 

It doesn't switch the risk off, but it's the single biggest step toward managing it. Housing India activity and the founder's employment inside a properly run Indian entity, backed by an intercompany agreement priced at arm's length, gives the US parent a defensible position rather than an exposed one.

What is the POEM turnover threshold in India?

 CBDT Circular No. 8 of 2017 provides that the Place of Effective Management guidelines don't apply to a foreign company with turnover or gross receipts of INR 50 crore or less in a financial year. Most early-stage companies sit below it for years, but the ceiling is real and growing companies eventually cross it.

Can an Employer of Record solve the problem for a founder? 

An EOR can pay a founder in India, but it doesn't resolve Permanent Establishment exposure for the US parent, it can't grant parent ESOPs to the Indian team, and it doesn't give you an Indian entity for GST, enterprise contracts, or Indian fundraising. It's a payroll patch, not a structure.

Why not just pay myself as a contractor under Section 44ADA? 

Section 44ADA's 50% presumptive scheme, capped at INR 75 lakh of receipts (and only where at least 95% of receipts come through banking channels), produces a real near-term saving. But it makes you a foreign contractor to your own company: no ESOPs, mounting labour-law and misclassification exposure, a weaker PE story, and a blocked US visa clock. The saving is narrow. The aggregate cost usually outweighs it well before an exit.

When is it acceptable to delay setting up the Indian subsidiary? 

Chiefly for a genuinely pre-product solo founder with no Indian teammates, customers, revenue, or office. Even then, start the incorporation during that quiet window so the entity is live the moment the first hire or customer lands. Two narrower cases also justify a short delay: a founder relocating to the US within 60 to 90 days on an approved visa with no retained Indian presence, and a small team on a three-to-six-month EOR bridge with a firm plan to incorporate or exit at the end of it.

How does an Indian subsidiary help with US visas like the L1? 

An Indian entity that actually employs the founder builds the qualifying overseas employment history the L1 intra-company transfer relies on, and supports B1/B2, O1, and EB1 petitions. Contractor arrangements don't create that record, so the clock only starts once real employment exists.