The Midnight Repository Problem: Getting IP Ownership Right Before Your Pune Team Writes a Line of Code

It's 2 a.m. in San Francisco, which means it's early afternoon in Pune. Your distributed engineering team is pushing commits to the repository that holds — as far as your investors are concerned — your company's most valuable asset. But here's the uncomfortable question every US founder with an Indian team should be able to answer without hesitation: if a dispute arose tomorrow, could you actually prove you own that code?

For many seed and Series A companies, the honest answer is no. Not because they were careless, but because they copied an IP assignment template drafted for California employees and applied it to contractors in Maharashtra. The two situations are governed by different legal regimes, and the differences matter.

Why US Boilerplate Fails Quietly in India

American employment agreements typically rely on the doctrine of "work made for hire" under US copyright law, supplemented by broad assignment language. India's Copyright Act of 1957 has its own work-for-hire framework, but its application to software developed by independent contractors is narrower than most founders assume. An assignment clause that works for a W-2 engineer in Austin may leave gaps when the counterparty is an independent contractor in Kharadi.

The result is rarely a dramatic lawsuit. More often, the problem surfaces during diligence: an acquirer's counsel flags that a handful of Pune contractors signed agreements with assignment language that doesn't clearly cover future works, or that moral rights waivers are missing. Suddenly your closing timeline stretches by weeks while you scramble for corrective assignments — sometimes from people who have moved on and aren't easy to reach.

The Four Documents That Need to Exist on Day One

When core product work happens in Pune, four instruments should be executed before the first commit:

1. A written IP assignment deed, not just a contract clause. Under Indian law, assignment of copyright in future works requires the assignment to be in writing and to take effect only when the work comes into existence. A standalone assignment deed — signed by each contributor, referencing the engagement — closes the gap that a single clause inside a services agreement can leave open.

2. An NDA drafted with Indian enforcement in mind. Indian courts do enforce confidentiality obligations, but injunctive relief can be harder to obtain than in US courts, and damages awards tend to be modest. That makes prevention the strategy: define confidential information precisely, restrict repository access by role, and ensure the agreement specifies Indian jurisdiction deliberately rather than by default. Many US founders insist on California or Delaware law; that choice is enforceable in many cases, but understand that actually litigating it means navigating enforcement of a foreign judgment in India. Arbitration seated in a neutral venue is often the more practical route.

3. Explicit moral rights provisions. Indian law treats certain author's rights as non-waivable in broad terms, but the practical scope for software — where Section 52 exceptions and the nature of computer programs limit their application — is more workable than founders fear. Still, address attribution and modification rights explicitly in your agreements so no ambiguity survives.

4. Contractor classification documentation. If your Pune contributors are engaged as contractors, the agreement should reflect genuine independence — or you should engage them through an employer-of-record or a properly structured entity. Misclassification is a compliance problem in its own right, and it complicates IP enforcement because the relationship's legal character affects which statutory protections and obligations attach.

The Clauses That Don't Travel Well

Beyond the documents themselves, several standard American provisions deserve re-drafting rather than recycling:

• Non-compete covenants. Post-employment non-competes that are routine in parts of the US are generally unenforceable in India as restraints on trade under Section 27 of the Indian Contract Act. Non-solicitation and confidentiality restrictions have far better prospects. If your template leans on a non-compete for protection, it's protecting nothing.

• Garden leave and restrictive notice provisions. These need to be structured around Indian notice-period norms, which are actually longer than US norms — many Indian employment contracts run 60 to 90 days. Use that to your advantage rather than importing a two-week US framework.

• Automatic assignment of "all work product." Overly broad language can create interpretive problems. Indian courts favor specificity: define whether the assignment covers work created using your equipment, during working hours, related to your business, or all of the above.

A Practical Diligence Self-Audit

If you raised money or sold the company next quarter, would your data room survive scrutiny? Run this quick audit:

• Does every Pune contributor — employee, contractor, or agency — have a signed assignment deed covering the specific code they touched?
• Are agency engagements backed by flow-down IP terms binding the individual engineers?
• Can you produce signed agreements for every contributor, including early team members who may have started informally?
• Is your source code repository access controlled and logged, so authorship and timing can be established independently?

That last point matters more than founders realize. In any ownership dispute, contemporaneous evidence of who wrote what, and under what engagement, is often more decisive than the elegance of the contract language.

Build the Paper Before You Need It

None of this requires an Indian law degree or a prohibitive legal budget. It requires recognizing, early, that the legal infrastructure for a distributed team is not identical to the infrastructure for a co-located one. A few hours with counsel familiar with both US and Indian practice — at the point you make your first Pune hire, not your first Pune acquisition offer — is among the highest-ROI legal spend an early-stage founder can make.

The code your Pune team writes at 2 a.m. their time is your most valuable asset. Own it on paper as completely as you own it in your heart.