You need to sign in or sign up before continuing.
Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 7: Hiring — Contractor vs Employee, ESOP, Payroll #

I want to be upfront about something. This module is probably theoretical for you right now. You are a one-person OPC. You are not about to hire an employee. You may hire a contractor or two over the next 18 months — a designer for a product, a content writer, possibly a junior dev — but a full-time employee with PF, ESI, gratuity, and TDS-on-salary is unlikely until the studio is generating consistent revenue beyond what one person can deliver, which is probably 18-36 months out depending on how product traction goes. So why read this module now? Because the most useful insight in it is not "how to hire," it is "how to think about the contractor-vs-employee distinction from both sides at once — including from the side you are currently on."

Here is the move that justifies reading this module immediately. You are probably a contractor yourself, for your primary client. You have a contractor agreement with them. The classification — contractor vs employee — has tax implications, benefit implications, and labor-law implications. Most engineers in your position have never read their own classification clause closely. They signed the contract, the money started flowing, the question of whether the relationship is correctly classified under Indian law never got asked. In most cases the classification is fine, because the engagement structure (multiple clients possible, work-from-anywhere, no fixed hours, you provide your own tools, project-based deliverables) actually maps to contractor under both Indian and US tests. But the test is structural, not titular. A contract that says "Contractor" while structurally treating you as an employee (fixed reporting hours, exclusivity, embedded in their team, no other clients) creates exposure for both sides. Reading this module from your own perspective first — as the contractor who wants to know whether his classification is solid — is the cheap way in.

A truth the formal curriculum cannot say plainly: most Indian one-person OPCs that hire someone full-time misclassify them as a contractor for about 18 months and then quietly correct it (or get caught). The misclassification is rarely malicious — it is almost always operational laziness combined with information asymmetry. The OPC founder doesn't want to deal with PF/ESI/gratuity/TDS-on-salary, so they sign the new hire as a contractor on a monthly retainer. The new hire is happy because the take-home is higher (no PF deduction, no ESI). For 18 months everything works. Then something happens — the hire complains, an audit triggers, a competitor gets hired by a larger company who flags the gap — and the OPC owes back-PF, back-ESI, gratuity (potentially), interest, and penalty. The right move is get the classification right from day one, even if it costs more upfront. If the role is structurally an employee role (fixed hours, exclusive, embedded), set up payroll properly. The cost is real but bounded; the cost of misclassification accumulates silently.

ESOPs deserve a specific honesty pass too. Most Indian one-person OPC founders read about ESOPs from a US-context source (YC blog, Holloway Guide), assume the structure transfers cleanly, and propose an ESOP to their first employee that is structurally invalid under Indian law (because OPC structure has restrictions on share issuance, or because the vesting language doesn't match Companies Act requirements, or because the FMV documentation isn't there). The first ESOP an Indian OPC founder issues is usually wrong, and the wrongness only surfaces during an exit, by which point fixing it is expensive. If you ever issue ESOPs as an OPC, do it with an Indian-context lawyer, not a US-context blog post. This is one place where DIY is actively dangerous. The ICAI ESOP accounting guidelines plus a competent Indian startup lawyer are the right resources, not the YC blog (which is excellent for US C-Corps and unhelpful for OPCs).

About OPCs and ESOPs specifically — there is a structural fact worth knowing now even though it doesn't apply to you yet. An OPC by definition has only one member. Issuing ESOPs to employees while remaining an OPC is awkward — the employees become shareholders, but the OPC structure assumes single-member. In practice, most OPCs that want to issue meaningful ESOPs convert to a Pvt Ltd first (which requires triggering the conversion process — paid-up capital ≥ ₹50 lakh or turnover ≥ ₹2 crore is the automatic trigger, but voluntary conversion is also possible). The conversion is non-trivial but well-documented. Don't issue your first ESOP from inside the OPC structure unless you have specifically confirmed the path with a lawyer. The default move is "convert to Pvt Ltd, then issue ESOPs." Plan for it.

There is one specific thing I want you to do this week even though the rest of the module is theoretical. Pull out your own contractor agreement with your primary client. Read the classification language and the IP language. Identify whether the structural test (multiple clients allowed, no fixed hours, own equipment, project-based) is met by the actual day-to-day reality. In most well-structured remote consulting engagements it is. But the exercise of reading the classification language while knowing what it means is the value. You are a better contractor for having done it, and a better hirer-of-contractors when the time comes.

About the first-hire-as-contractor problem more concretely: when you do hire your first non-trivial helper (most likely a designer or a content writer), the engagement will probably be a contractor engagement structurally — they will have other clients, they will work their own hours, they will use their own equipment. Good. But the agreement still matters. The contractor agreement (Module 5 template) needs explicit language stating: (1) the engagement is on a project / deliverable basis, not retainer, (2) the contractor controls hours and methods, (3) IP transfers on payment for work-product specific to your studio, with a carve-out for the contractor's pre-existing tools and templates, (4) no exclusivity, (5) TDS will be deducted under section 194J at 10% (or 2% if the contractor is registered under specific schemes — verify with your CA). Each clause is structural protection that the engagement is genuinely a contractor relationship, not an employment relationship in disguise.

A specific thing about Indian labor law worth knowing even if currently inapplicable: the Code on Wages, the Industrial Relations Code, the Code on Social Security, and the Occupational Safety, Health and Working Conditions Code together replace 29 older labor laws. They are slowly being notified by states. By the time you hire your first employee (probably 18-36 months from now), the regime might look slightly different from what current resources describe. Re-verify the labor law status when you hire, do not rely on this module's snapshot of 2026 conditions. This is one of the few places where the material will date faster than the rest of it.

Conclusion #

Hiring is dependency injection with tax implications. A contractor is an external service; an employee is an in-process module with lifecycle hooks. ESOPs are vesting schedules, except the vested instances are humans. The module is theoretical for most one-person studios, but the contractor-vs-employee distinction matters immediately because you are probably a contractor and reading the structure from both sides clarifies your own classification. Don't issue ESOPs from inside an OPC without legal review — the structure has gotchas. When you do hire your first employee (probably 18-36 months out), set up the classification correctly from day one rather than retrofitting later.

Predictions #

  • You will read this module faster than estimated because most of it is currently theoretical. Don't speed through the contractor-vs-employee structural test — that part is operational now.
  • Reading your own contractor agreement with this module's lens will produce one small noticing — probably a clause about exclusivity or IP that you didn't fully process before. The noticing is the win.
  • The first contractor you hire (probably a designer) will trigger TDS deduction obligations that you will forget about. Set up Zoho Books with TDS configured at the chart-of-accounts level (Module 6) so it cannot be forgotten.
  • You will be tempted, when you eventually hire someone full-time, to classify them as a contractor for the first six months "to keep things simple." Resist. The simplicity is illusory.
  • Your first ESOP conversation, if it happens, will be at the wrong structural level (probably treating an OPC like a Pvt Ltd). Stop the conversation, convert the entity first, then resume.
  • The Holloway Guide to Equity Compensation is excellent for vocabulary and US-context. It is misleading for Indian implementation. Read it for vocabulary; ignore it for tactics.
  • 24 months from now, this module will go from theoretical to operational suddenly. The "I read this once already" memory will save you a week of re-learning at exactly the wrong moment.