How to Structure Founder Employment Agreements in India

A founder who owns 40% of a company can still create expensive confusion if their job, pay, authority, IP obligations, and exit terms exist only in WhatsApp messages and a cap table. A founder employment agreement India founders can work with should turn the operating relationship into a written system before a fundraise, co-founder dispute, or departure forces the issue. It is not paperwork for paperwork’s sake. It is the document that states what the company expects from a founder who is also an employee, director, shareholder, or all three.

Separate ownership from employment

Founder equity answers one question: what does this person own? Employment answers another: what work will this person do for the company, under what terms, and what happens if that work stops? Early-stage teams often collapse these questions into one verbal understanding. That approach becomes unstable as soon as salaries begin, investors ask for documents, or one founder reduces their involvement.

Your founder employment agreement should sit alongside, rather than replace, your incorporation documents, shareholder arrangements, equity documentation, and board records. Each document should have a defined job. Do not use an employment agreement to quietly rewrite ownership rights, vesting mechanics, or investor consent matters that belong elsewhere.

Document area	Question it should answer
Founder employment agreement	What role, duties, pay, IP duties, and exit obligations apply?
Equity documents	What does the founder own, and under what vesting or transfer terms?
Board records	Who approved compensation, authority, and major changes?
Shareholder arrangements	What rights and obligations apply between owners?

Write the agreement in the company’s voice. The company is the employer. The founder is the employee. That framing may feel formal when there are only two people in a room, but it prevents the document from becoming a personal promise between co-founders. It also makes later hiring, diligence, and governance cleaner.

At Nebula, we treat this as part of building the operating layer around the product. Our venture-building process moves from validation to scale with the expectation that roles, decision rights, and ownership do not remain vague as the company grows.

Define the role and time commitment

Start with the founder’s actual job, not an inflated designation. “Founder and CEO” is a title. The agreement needs the work behind it: product direction, hiring, sales, fundraising preparation, customer delivery, finance oversight, or technology leadership. A founder employment agreement India teams can rely on should make the expected contribution clear enough for the board and the founder to assess performance.

State whether the role is full-time, part-time, transitional, or subject to a defined milestone. If a founder is studying, consulting, employed elsewhere, or building another venture, record that reality. Hidden time constraints become visible during execution failures, then get recast as commitment disputes.

• Set the title, reporting line, and start date.
• List three to six core responsibilities tied to the current stage.
• State the expected time commitment and any approved outside work.
• Define who can change the role, compensation, or authority.
• Record spending, hiring, bank, contracting, and customer-signing limits.

Avoid job descriptions that promise every function to one person. “Responsible for all company matters” creates no useful standard. It also hides the real gaps in the founding team. If the founder is responsible for revenue but does not control pricing, hiring, or product priorities, document where their authority begins and ends.

Use an annual or milestone-based review clause rather than pretending a first draft will fit the company forever. The role of a pre-revenue founder and the role of a founder managing a growing team should not look identical. The agreement should permit a deliberate update, with the right approval, when the company changes phase.

Set compensation without creating surprises

Compensation clauses should be precise even when the amount is modest. State the monthly salary, payment timing, reimbursement process, benefits if any, and the approval required for changes. If salary starts later because the company has limited cash, say so directly. Do not leave it as an informal understanding that one founder is “taking less for now.”

Separate salary from equity. Salary pays for current work. Equity reflects ownership and risk. When teams blur the two, a founder can later argue that unpaid or reduced salary should automatically result in more shares. That may be a commercial discussion, but it should not emerge by accident.

Include a process for expenses. Founders often pay for software, travel, prototype work, customer meetings, or legal filings from personal accounts. The agreement should state what counts as a company expense, what proof is required, and who approves reimbursement. A company cannot manage cash if founder spending sits outside its records.

Be equally careful with bonuses, commissions, retention payments, and any change in compensation after funding. Define the trigger, amount or calculation method, approval path, and payment timing. “Bonus after raise” is not a clause. Does the trigger mean a signed term sheet, funds received, or a board decision after closing? Write the answer.

Before signing, have Indian counsel and your finance adviser review the payment structure, deductions, records, and any director-related requirements that apply to your company. The agreement should match the way money will actually move, not the way the founders hope it will move.

Protect IP and manage conflicts

Every founder employment agreement should address intellectual property created for the company. This is especially urgent when a founder began building before incorporation, used personal devices, worked with contractors, or reused code, designs, research, content, or customer relationships from an earlier role. Do not assume the company owns work merely because the founder intended to build a company around it.

Ask each founder to identify pre-existing materials before signing. Then separate what remains personally owned from what is being assigned, licensed, excluded, or replaced. A short schedule is better than a future dispute over an undefined “existing codebase.”

• Define company-related work product and materials.
• List pre-existing IP, if any, in a separate schedule.
• Require prompt disclosure of relevant inventions and creations.
• Set confidentiality duties for company information and customer data.
• Require disclosure of outside roles, investments, and commercial interests.

Conflicts need the same discipline. A founder may advise another company, hold an investment, retain a consulting client, or have a family connection to a vendor. The agreement should require disclosure and set the approval route. The aim is not to ban every outside interest. The aim is to ensure the company knows when a founder’s personal incentives may affect a company decision.

Keep legal representation clear too. A 2026 JD Supra report on litigation involving Cooley describes allegations that a firm advised an individual founder on personal interests while also representing the company in negotiations affecting IP, equity, and employment terms. That is a useful warning: ask counsel to state who they represent when founder and company interests may differ. Read the report.