Whether you can build on the side is decided by your employment agreement, not by Indian law. The four clauses to read, what Section 27 actually means for non-competes, and when to stop reading articles and call a lawyer.
Most people building something on the side ask this question quietly, late, and of the wrong person. It deserves a straight answer early, because the cost of getting it wrong is not a warning email. It is losing ownership of the thing you built.
This is a practical guide to what to check. It is not legal advice, and the last section explains exactly when to stop reading articles and pay a lawyer.
In general, nothing in Indian law prevents you from incorporating a company or holding shares while you are employed somewhere else. People do it constantly. A person can be a shareholder in one company and an employee of another.
The constraint is almost never the law. It is the contract you signed on your first day and have not read since.
Find your offer letter, your employment agreement, and any policy handbook you acknowledged. Four clauses matter.
Intellectual property assignment. This is the dangerous one. Many Indian employment agreements assign to the employer any IP you create during the employment period. The broad ones do not limit this to work done on company time or company equipment. If your agreement reads that way, code you write on a Sunday on your own laptop can arguably belong to your employer.
Look for language that narrows it: inventions made using company resources, or relating to the company's actual business, or during working hours. Narrow clauses are common and reasonable. Broad ones are the problem.
Exclusivity and moonlighting. Many agreements say you will devote your full working time to the employer, or will not engage in any other business without written consent. Note the difference between full working time, which is about your hours, and any other business, which is about your existence outside those hours. The second is far more restrictive.
Non-compete. Here Indian law is genuinely on your side after you leave. Section 27 of the Indian Contract Act, 1872 treats agreements in restraint of trade as void, and Indian courts have repeatedly declined to enforce post-employment non-competes. Restrictions that apply while you are still employed are treated differently and are far more likely to hold.
The practical reading: a clause stopping you competing after you resign is weak. A clause stopping you competing while you are still on payroll is not.
Non-solicitation. Usually about not poaching colleagues or customers. Often enforceable and easy to breach accidentally when your first instinct is to sell to people you already know. Your former employer's client list is the single worst place to look for your first customer.
Strip away the drafting and one distinction does most of the work: is your startup in the same line of business as your employer?
If it is not, you are in ordinary territory. Read your clauses, keep clean boundaries, proceed.
If it is, treat that as a serious problem to solve before you build, not a risk to discover after your first invoice. Same-industry side ventures are where disputes actually happen, because that is where an employer has both a motive and a plausible claim.
None of this is exotic. It is mostly about being able to show a clean line.
There is no universally right answer, and anyone who gives you one has not thought about it.
Disclosure buys certainty. A written consent, even a short email approval, largely closes the question. It also tells a manager you have one foot out, which affects how you are treated well before you are ready to leave.
Staying quiet preserves normality and carries the risk that a clause you never renegotiated is read against you later.
What tilts it: the broader your IP clause, the more disclosure is worth. If your agreement plausibly claims everything you create, silence is not protection, it is deferral.
Two separate questions people conflate.
Holding shares in a private limited company while employed is ordinarily unremarkable.
Being a director carries statutory duties and is publicly visible on MCA filings. If your agreement requires consent for outside directorships, and many do, a public filing is not a subtle thing. Some founders keep a co-founder or family member as the second director early on. Understand why you are doing that before you do it, because it has its own consequences for control.
Stop reading articles and pay for an hour of advice if any of these are true:
An hour with a competent lawyer costs less than most founders spend on tools in a month. Investor diligence on IP ownership is not a formality, and a founder who cannot cleanly prove they own their own product is a founder who does not get funded.
Open your employment agreement and read the IP clause. Not the whole document. One clause. Most people building on the side have never read it, and it is the single provision that decides whether the thing you are making is yours.
This article is general information, not legal advice, and employment agreements vary enormously. Get advice on your specific contract before making decisions that depend on it.
Working through this properly, alongside incorporation and founder agreements, is part of the first phase of LVL1 Startup School, before anyone writes a line of production code.
Your co-founders will determine your startup's success more than your idea, funding, or market. Here's how to choose the right people and structure your founding team.
Being a startup CEO is unlike any other job. Learn the essential skills, responsibilities, and mindset needed to lead your company through the challenges of early-stage growth.
Most startups fail not because they build the wrong solution, but because they solve the wrong problem. Learn how to identify and validate problems that are truly worth solving.