5 Documents Your First Employees Must Sign & Why Most Startups Get Them Wrong

Your first few hires usually join on a one-page offer letter and a handshake. It feels right for the stage - informal, fast-moving, high-trust. It is also exactly how startups end up with no legal claim to code an early engineer wrote or no record of what an early hire was actually promised in equity.

1. An offer letter that actually assigns IP to the company

"You will build our product" is not the same as a clause stating that everything the employee creates in the course of their work belongs to the company, not to them personally. Without it, ownership of early product work can be genuinely contestable.

Your offer letter or employment agreement should:

• Clearly state that IP created in the course of employment belongs to the company.
• Cover code, designs, documentation, processes and related work product.
• Include a cooperation clause for signing any further documents needed to perfect that ownership.

Real pattern: In diligence, investors ask for employment agreements and IP assignments. "We didn't sign anything, but everyone knows the code is ours" is not a satisfactory answer.

2. A confidentiality agreement signed before access, not after

Your first employees typically have access to everything- the cap table, the roadmap, investor conversations. An NDA signed on day one is worth far more than one signed after someone's already seen everything and is walking out the door.

Ensure your confidentiality terms:

• Define what is confidential (broadly, but sensibly).
• Cover current and former employees.
• Survive termination of employment.
• Sit alongside your IP and non-solicitation clauses.

3. Written ESOP terms, not a verbal percentage mentioned in the interview

"You will get around 1%" is not a grant. Without a board-approved ESOP scheme and a formal grant letter, an early employee's equity promise has no legal standing and disputes over informal equity promises are one of the most common flashpoints in early startups.

At a minimum:

• Have a board-approved ESOP scheme in place before promising equity.
• Issue a grant letter specifying number of options, vesting schedule, exercise price and key terms.
• Avoid vague verbal promises, if you must discuss ranges early, make it clear they are indicative and subject to formal approval.

Real pattern: We often see early employees who were "told 1%" but have no documentation. When the company grows, those conversations become disputes- Was it 1%? Of what? On what vesting? Subject to what conditions?

4. A POSH policy, the moment you cross 10 employees, not before you think you need one

Once your establishment has 10 or more employees, the POSH Act requires an Internal Committee and a documented policy. This is not optional past a headcount threshold and it is not a "later" problem.

Even before you hit 10, it is wise to:

• Have a basic anti-harassment policy in place.
• Communicate a clear reporting channel for concerns.
• Treat culture and conduct as a priority from the first hire.

But once you cross 10, the legal obligations kick in fully and you must comply.

5. Start thinking about DPDP from your first user, not your hundredth

The moment your product touches user data, even in beta, you are stepping into the world of the Digital Personal Data Protection Act (DPDP). You do not need a 50-page privacy policy on day one, but you do need to know- what data you collect, why, where it is stored, who can access it, and how you will handle user requests or a breach.

Your first employees and consultants will have access to this data. Their confidentiality and access controls should reflect that.

Treat data as a core asset and a core risk from the start, not as a compliance afterthought you will fix "when you are bigger."

6. Consultant agreements that do not accidentally create an employee

Many early hires are structured as consultants for tax and flexibility reasons. If the actual working relationship looks like employment - fixed hours, direct control, ongoing exclusivity - a consultant can later be reclassified as an employee, with retrospective consequences for benefits and compliance.

Your consultant agreements should:

• Reflect a genuine contractor relationship (scope, deliverables, independence).
• Avoid language that implies employment (e.g., "working hours," "reporting to," "full-time").
• Address IP, confidentiality and termination clearly.

Real pattern: Labour and tax authorities look at substance over form. A "consultant" who functions like an employee can create exposure for unpaid benefits, taxes and compliance.

The fear worth having

None of this looks urgent while the team is five people who all get along. It becomes urgent the day someone leaves unhappy, a dispute over equity surfaces or an investor's diligence team asks to see employment documentation that was never created.

Next in this series: Your team and your governance are in place. Now the clock actually starts because incorporation triggers a set of deadlines most founders do not hear about until they have already missed one.

Next: The First 180 Days: A Founder's Compliance Countdown

::