Founders Agreements for Indian Startups
Every successful company begins with two or more people who agree on the rules of their partnership. The founders who skip this step are building on sand.
The One Agreement That Determines Whether a Startup Survives
Two people with a great idea decide to build something together. They complement each other. One brings the technical capability. The other brings the market understanding. They start building.
Six months later, one founder is working eighteen hour days. The other has taken on a consulting engagement "temporarily" and contributes two hours a week. Both still own 50% of the company. Twelve months later, the relationship has deteriorated, the product launch is delayed, and neither founder can move forward without the other\'s consent. The startup dies not because the market rejected the product, but because the founders never agreed on the rules of their partnership.
This is not a hypothetical. It is the most common cause of startup failure in India that has nothing to do with product market fit.
A founders agreement prevents this by answering seven questions before they become disputes: Who owns what? Who does what? What happens if someone stops contributing? Who makes which decisions? Who owns the IP? What are the non compete boundaries? How do we resolve disagreements?
The conversation these questions force is uncomfortable. That discomfort is precisely why most founders skip it. And that is precisely why most co-founder relationships fail.
Equity Split and Vesting: The Mathematics of Commitment
Equity split is the single most consequential decision founders make. Get it wrong and it poisons every subsequent decision — fundraising, hiring, pivots, exits.
Equal Split (50/50 or 33/33/33) — Simple but dangerous. Equal split assumes equal contribution over the entire life of the company. This assumption is almost never valid. One founder will inevitably contribute more time, capital, IP, or relationships. Equal split with no vesting creates the worst possible outcome: a non-contributing founder with an equal stake and no mechanism to adjust.
Contribution Based Split — Factor in capital contribution, IP contribution, full time versus part time commitment, domain expertise, and network value. Weight each factor and arrive at percentages that reflect current and expected contribution. This is harder to agree on but produces a more defensible and sustainable equity structure.
Vesting Schedule — The safety mechanism. Standard in India is four years with a one year cliff. Vesting means equity is earned over time, not granted on day one. If a founder leaves before the cliff, they forfeit their entire stake. After the cliff, equity vests monthly or quarterly. This ensures that equity tracks actual contribution. Without vesting, a co-founder who contributes three months of work and then disengages walks away with their full stake — permanently diluting the founders who stayed and built the company.
Acceleration Clauses — Single trigger acceleration (all unvested equity vests upon a change of control event like acquisition) and double trigger acceleration (vesting accelerates only if the founder is also terminated post acquisition). Double trigger is standard. Single trigger can discourage acquirers because it locks in all founder equity regardless of continued contribution.
IP Assignment: The Clause That Protects the Company's Core
In India, intellectual property created by an individual belongs to that individual unless there is a written assignment to the company. This is the default position under the Copyright Act 1957, Patents Act 1970, and Designs Act 2000.
If a founder writes the core algorithm, builds the initial codebase, designs the product architecture, or creates the brand identity before incorporation — all of that IP belongs to the individual, not the company. If that founder leaves, the IP leaves with them. The remaining founders and the company have no rights to use, modify, or license that IP.
The founders agreement must contain an IP assignment clause that transfers:
• Background IP — Pre-existing intellectual property that each founder brings to the venture, to the extent relevant to the company\'s business.
• Foreground IP — All intellectual property created during the founder\'s association with the company in connection with the company\'s business.
• Moral Rights Waiver — Under the Copyright Act, authors retain moral rights even after assignment. A waiver (to the extent permitted by law) prevents a departing founder from objecting to modifications of their original work.
The IP assignment must be documented separately for each type of IP — copyright, patents, designs, trade secrets, trademarks — because each is governed by a different statute with different formalities for valid transfer.
Roles, Decision Making, and Deadlock Resolution
The most frequent source of co-founder conflict is not equity. It is authority. Who has the final word on product decisions? Who approves the marketing budget? Who hires the CTO?
A well structured founders agreement creates three tiers of decision making:
Individual Authority — Each founder has unilateral decision making power within their defined domain. The CEO handles external relations, fundraising, and strategic partnerships. The CTO handles product architecture, engineering hires, and technology stack. Decisions within a founder\'s domain do not require co-founder approval. This prevents decision paralysis on day-to-day operations.
Majority Consent — Decisions that cross domains or involve significant financial commitments require majority founder consent. Hiring above a certain salary threshold, entering vendor contracts above a specified value, and opening new offices typically fall here.
Unanimous Consent (Reserved Matters) — Decisions that fundamentally alter the company require all founders to agree. Issuing new equity, raising capital, changing the business model, entering new geographies, approving budgets above a threshold, and appointing or removing key management. Without unanimous consent on reserved matters, a majority founder can unilaterally reshape the company against the interests of the minority founder.
Deadlock Resolution — When founders cannot agree on a reserved matter, the agreement must provide a resolution mechanism. Options include casting vote rights for one founder (typically the CEO), referral to an independent advisor or mentor, a cooling off period followed by re-vote, or ultimately, a buyout mechanism where one founder offers to buy the other\'s stake.
Founder Exit: Good Leaver, Bad Leaver, and Everything Between
Every founders agreement must contemplate the possibility that a co-founder leaves. The circumstances of departure determine the consequences.
Good Leaver — Departure due to death, disability, serious illness, or termination without cause. The departing founder retains all vested equity. The company or remaining founders may have a right to purchase vested shares at fair market value, typically determined by an independent valuation. Unvested equity is forfeited and returns to the ESOP pool or is redistributed.
Bad Leaver — Voluntary resignation, termination for cause (fraud, breach of fiduciary duty, material breach of the founders agreement, conviction for a criminal offence), or breach of non-compete or confidentiality obligations. All unvested equity is forfeited. Vested equity may be subject to a buyback at a discount to fair market value — typically the lower of cost or fair market value. In extreme cases (fraud, IP theft), some agreements provide for forfeiture of all equity including vested shares.
Drag Along and Tag Along — If a majority founder receives a buyout offer, drag along rights compel minority founders to sell on the same terms. This enables the acquirer to obtain 100% ownership. Conversely, tag along rights protect minority founders by ensuring they can participate in any sale on the same terms as the majority founder. Both rights should be specified in the founders agreement before they appear in the Shareholders Agreement.
Non Compete Post Exit — The departing founder should be restricted from competing for a reasonable period (typically 1-2 years) and within a defined geographic scope. Indian courts scrutinise non-compete clauses under Section 27 of the Indian Contract Act, but post-sale non-compete provisions have been upheld where the restriction is reasonable in scope and duration.
Regulatory Compliance: Companies Act, DPIIT, and FEMA
The founders agreement does not exist in a regulatory vacuum. It must align with multiple statutory frameworks.
Companies Act 2013 — The founders agreement must not conflict with the company\'s Articles of Association. The V.B. Rangaraj v. V.B. Gopalakrishnan judgment established that where there is a conflict between a shareholders agreement and the Articles, the Articles prevail. The founders agreement should include a clause requiring the Articles to be amended if they conflict with the agreed founder terms.
DPIIT Startup Recognition — For startups seeking DPIIT recognition (and the associated tax benefits under Section 80-IAC, angel tax exemptions, and government procurement relaxations), the founders agreement should reference the startup\'s innovation focus and the founders\' commitment to scalability. Recognition requires the entity to be incorporated as a Private Limited Company, Partnership Firm, or LLP, and not be formed by splitting or restructuring an existing business.
FEMA Compliance — If any founder is a Non Resident Indian or the company plans to raise capital from foreign investors, FEMA rules apply from day one. Foreign founders may hold equity in Indian companies under the automatic route for most sectors, but sectoral caps, pricing guidelines (based on valuation by a qualified valuator), and FC-GPR filing within 30 days of share allotment must be accounted for in the founders agreement. Non-compliance penalties under FEMA can reach three times the amount involved.
DPDPA 2023 — If the startup processes personal data, the founders agreement should designate data governance responsibilities among co-founders from inception. Who is responsible for consent architecture? Who ensures breach notification compliance? Which founder oversees the vendor data processing framework? Building this into the founders agreement prevents the common pattern where no one takes ownership of data compliance until a breach forces the issue.
What You Need to Know
Building Something Together?
The conversation about equity, roles, and exit is difficult. Having it now, with the right framework, is significantly less painful than having it in front of an arbitrator two years from now.
[email protected]