Contractor vs First Employee in India (Legal, Tax, and Total Cost Math)

When an Indian solo founder makes a first hire, they face a choice they usually do not realise is a choice. They either default to “let me hire an employee” because that is what real businesses do, or they default to “let me get a freelancer” because that feels lighter. Both defaults are wrong roughly half the time. The right answer depends on the work, the timeline, the cost tolerance, and the founder’s appetite for legal risk, in that order.

This piece walks through the legal distinction the income tax department actually applies, the real cost difference between the two paths, the situations where each is the right call, and the mistakes that get founders into trouble with the labour department or the assessing officer. If you have already decided to hire and are just optimising the structure, skip to the cost comparison table. If you are still deciding, the legal section matters more than you think.

The legal distinction (and why it is not a choice you make)

A common misconception is that you can call someone a contractor on paper and they become a contractor. This is not how Indian tax and labour law work. The classification is determined by the actual working relationship, not by what the contract says. If you call someone a contractor but treat them like an employee (fixed hours, your office, your equipment, your supervision, exclusive engagement), the income tax department and the labour department can both reclassify the relationship retroactively, which usually results in penalties, back-payment of statutory dues, and back-payment of TDS at the higher employee rate.

The Supreme Court of India has used a few tests over the years, but the consistent thread is the “control and supervision” test. The more control you exert over how, when, and where the person works, the more they look like an employee. The more independent their work output is from your day-to-day direction, the more they look like a contractor.

Practical examples that almost always make someone an employee in the eyes of the law:

• Fixed daily hours (9 AM to 6 PM, working days mandatory)
• Use of your office, equipment, or systems as their primary working tools
• Exclusive engagement (they cannot take on other clients)
• Salary-style monthly payment regardless of deliverables
• Performance reviews, KPIs, or other employment-style management
• Paid leave, sick leave, or any benefit that resembles employee benefits

Practical examples that usually make someone a contractor:

• Project-based or output-based payment (not monthly retainer of identical amount)
• Their own equipment, systems, and workspace
• They take on other clients in the same window
• You specify the OUTPUT (a deliverable, a report, a piece of code) but not the PROCESS
• No paid leave, no statutory benefits, no fixed hours
• A clearly defined scope and end date for the engagement

The trap most solo founders fall into is hiring “a contractor” who works exclusively for them, in their office, on a monthly retainer, with fixed hours, and calling it a contractor relationship. In a tax audit or a labour dispute, that person will be reclassified as an employee, and you will owe the statutory contributions retroactively. This has happened to small businesses in India often enough that it should be treated as a real risk, not a theoretical one.

The tax difference (TDS, GST, statutory contributions)

For a contractor engagement, the tax mechanics are simple:

• You deduct TDS at the rate specified for the service category. For most professional services (consulting, design, development, writing), this is 10 percent under section 194J. For some other services, 1 to 2 percent under section 194C.
• The contractor invoices you. If they are GST-registered (mandatory above Rs.20 lakh annual turnover, optional below), they charge GST on the invoice. You can claim input credit if you are also GST-registered.
• The contractor handles their own income tax filing and pays their own GST.
• You have no statutory contribution obligations (PF, ESI, gratuity, bonus).
• You have no obligations under labour law (notice period, severance, paid leave, working hours).

For an employee engagement, the mechanics are heavier:

• You deduct TDS on salary at the slab-rate applicable to the employee’s total income (sections 192 and 192A). This requires you to estimate their full-year income, including any other declarations they make.
• You contribute to Provident Fund (PF), 12 percent of basic salary, matched by an equal employee contribution. Mandatory if you have 20+ employees, but voluntary registration is common at smaller sizes.
• You contribute to ESI (Employees State Insurance) at 3.25 percent of gross salary for employees earning under Rs.21,000 per month. Mandatory if you have 10+ employees, voluntary below.
• You accrue gratuity at 4.81 percent of basic salary annually, payable on resignation or termination after 5 years of service.
• You provide paid leave under your state’s Shops and Establishments Act (usually 12 to 21 days a year, varies by state).
• You issue Form 16 annually summarising salary and TDS for the employee’s tax filing.

The cost gap between the two structures, for the same monthly take-home pay to the worker, is meaningful. A walkthrough is below.

The total cost comparison

Take a worker who will produce work worth roughly Rs.50,000 a month to your business.

As a contractor:

• Monthly invoice: Rs.50,000
• TDS at 10% (you deduct, contractor claims credit when they file): Rs.5,000
• GST at 18% if they are GST-registered (you can claim input credit if you are): Rs.9,000
• Net cash outflow to contractor: Rs.45,000 (after TDS, before GST refund)
• Total cost to you: Rs.50,000 + Rs.9,000 GST = Rs.59,000 monthly. The Rs.9,000 GST is recoverable as input credit, so the real cost is Rs.50,000.
• Real monthly cost: Rs.50,000

As an employee earning Rs.50,000 gross per month:

• Gross salary: Rs.50,000
• Employer PF: Rs.1,800 (12% of basic, assuming basic is Rs.15,000 with allowances making up the rest)
• ESI: Rs.0 (gross above Rs.21,000 ceiling, ESI not applicable)
• Gratuity accrual: Rs.722 (4.81% of basic Rs.15,000)
• Paid leave provision (21 days a year): Rs.2,884 monthly
• Bonus provision: Rs.4,166 monthly (one month bonus annualised)
• Equipment and setup: Rs.2,000 monthly amortised
• One-time registration and contract costs: Rs.20,000 spread over first year = Rs.1,667 monthly
• Real monthly cost: about Rs.63,239

The employee path costs about 26 percent more for the same monthly output. The gap widens at lower salaries (because ESI kicks in) and narrows at higher salaries (because PF caps and bonus stops being statutory). For a Rs.30,000 gross employee, expect closer to 40 percent overhead. For a Rs.1,50,000 gross employee, expect closer to 18 percent overhead.

When a contractor is the right choice

Despite the legal complexity, the contractor path is often the right one for a first hire. The conditions where it works:

The work is project-based or output-based, not continuous. You need a logo redesign, a website rebuild, a quarterly content batch, a tax return season. Defined start, defined end, defined output. The contractor finishes the work and you both move on.

The work requires skills you do not need every week. You need video editing twice a month, not every day. A contractor at Rs.5,000 per video is dramatically cheaper than an employee video editor who is idle 80 percent of the time.

You are not sure the work will continue past three months. A trial period before committing to an employee is rational. Hire a contractor for a defined scope, see how they perform, see how the work flow stabilises, then convert to employee if both sides want to.

The candidate is already running their own freelance practice with multiple clients. They are a contractor by structure, not just by your label. They will not become an employee under scrutiny because they genuinely work for others.

You want flexibility to scale up or down based on demand. A retainer contract with a 30-day termination clause is easier to wind down than an employment relationship with a notice period and statutory exits.

When an employee is the right choice

The work is continuous and the volume justifies a full-time person. Customer support, sales operations, account management, anything where there is a baseline of work every day forever.

The role requires deep institutional knowledge that you do not want to retrain every six months. Long tenures only happen with employment.

You need exclusivity. A senior salesperson cannot be selling for your competitor in their spare time.

You want the person to grow into a leadership role. Career growth, stock options, and long-term loyalty are easier to structure with employment.

The legal risk of misclassification is unacceptable. If the work pattern would clearly fail the control test, do not pretend it is contractor work. The penalty math is worse than the salary math.

The hybrid path (contractor to employee)

The most common smart move for a first hire is to start as a contractor for the first three to six months, then convert to employee if both sides want to continue. This is legitimate as long as the contractor period was genuinely contractor-style (defined deliverables, no fixed hours, not exclusive) for that initial period. It gives both sides an exit ramp without statutory and labour complications.

Three rules for the hybrid path to be defensible:

The contract clearly states it is a fixed-term consultancy engagement with a defined scope of work. Not a monthly retainer for “general services.”

The person genuinely takes on other work during the contractor phase (or could). If they sign an exclusivity, the contractor classification becomes legally fragile.

When you convert to employee, you start a fresh employment relationship. New contract, new offer letter, new statutory enrolments. Do not retroactively backdate “employment” to the contractor start date, because then the statutory contributions become arrears for the contractor period too.

The mistakes that cost real money

Calling someone a contractor when they fail the control test. Penalised in tax audits and labour disputes. Pay statutory dues retroactively plus interest plus penalty.

Not deducting TDS on a contractor’s invoice. Section 40(a)(ia) disallows the entire expense in your income tax, so you pay tax on income you spent. Crippling at year-end.

Paying a contractor through your personal account instead of the business account. Looks like personal expenditure to an assessing officer, gets reclassified, taxed as your income. Use the business account every time.

Not having a written contract. When there is a dispute, the labour court or civil court applies the most employee-friendly interpretation of the facts. A written contract that specifies the terms is your protection.

Treating bonus, paid leave, and statutory contributions as “optional.” They are not. The employee can file a labour complaint or a wage recovery suit and you will lose.

Promising stock options to a contractor. ESOPs are only legally clean for employees in India. A contractor with “stock options” is either misclassified or holding unenforceable promises.

The decision flowchart

Walk through these questions in order. The first “no” tells you the answer.

1. Is the work continuous and full-time (not project-based)? If no, contractor.
2. Will the engagement realistically last more than 12 months? If no, contractor.
3. Are you willing and able to pay the 25 to 40 percent statutory overhead on top of gross salary? If no, contractor.
4. Will the person work primarily from your office, on your equipment, under your supervision? If yes, you have to hire them as an employee.
5. Will they have other clients during the engagement? If yes, contractor is structurally honest.
6. Are you registered or willing to register for PF, ESI, and your state’s Shops and Establishments Act? If no, you should not hire an employee yet.

If you ended up at contractor on every relevant question, hire as a contractor. If you ended up at employee, register first, then hire.

---

The hiring decision sits inside a larger first-team framework. The pre-hire decision is covered in when to make your first hire as a solo founder. The three SOPs that should exist before either path are in the three SOPs every solo founder needs before hiring. Once the person is hired, the first hire 30/60/90 onboarding playbook covers the first three months. The 1-to-3 person tech stack you will likely need either way is in the 1-to-3 person tech stack that scales without rebuild.