Hiring a consultant feels informal at first — a few calls, a scope discussed over email, an invoice at the end of the month. Then a dispute shows up over unpaid fees, or the consultant claims to be a de facto employee entitled to PF and gratuity, and suddenly that informal arrangement needed to have been a proper contract all along. A consultancy agreement is what stops that scenario from playing out. LegalDev drafts and reviews these agreements so both sides know exactly what they signed up for, and so the relationship holds up if it's ever questioned.
At its core, it's a contract between a business (the client) and an independent professional or firm (the consultant) for a defined piece of work — strategy, technical implementation, compliance advice, whatever the engagement actually is. It sets the scope, the fee, how long the work runs, who owns what gets created along the way, and how either side can walk away from it.
What makes it different from an employment contract isn't just the title. It's the nature of the relationship itself: a consultant works with autonomy over how the work gets done, while an employee works under the company's direction and control. That distinction sounds academic until it isn't — Indian courts have leaned on it for decades to decide real disputes.
This is the part most businesses underestimate. The Supreme Court, in Dhrangadhra Chemical Works v. State of Saurashtra, laid down what's still the controlling test: it's not what you call someone in the contract, it's how much control the company has over the way the work gets done. An employer can tell someone what to do and how to do it. A company engaging a genuine consultant can only tell them what needs to be delivered — the "how" stays with the consultant.
Get this wrong, and it's not just a labelling problem. A consultant who is, in substance, being treated like an employee — fixed hours, company equipment, ongoing supervision, no other clients — can later claim entitlement to PF, gratuity, and other statutory employee benefits, regardless of what the contract calls them. A well-drafted consultancy agreement won't magically fix a relationship that's actually employment in disguise, but it does force clarity on the terms upfront, and it gives you something concrete to point to if the classification is ever challenged.
A generic downloaded template rarely covers everything that matters for an Indian engagement. Here's what a properly drafted one should include:
We don't start with a template that assumes every consulting engagement looks the same, because they don't — advising on a compliance audit is a different animal from a six-month product consulting stint.
It's a contract between a business and an independent consultant that sets out the scope of work, payment terms, confidentiality, intellectual property ownership, and how the engagement can be ended. It formalises what's otherwise just a verbal or email-based understanding.
An employment contract creates an employer-employee relationship where the company controls both what work gets done and how it gets done. A consultancy agreement engages an independent professional who controls the "how," works with more autonomy, invoices for their fees, and handles their own taxes.
Yes, if the actual working relationship looks like employment — fixed hours, close supervision, company equipment, no independence in how the work is carried out — regardless of what the contract is titled. Indian courts look at the substance of the relationship, not just the label, which is why the agreement's terms need to genuinely reflect an independent engagement.
Generally yes, under Section 194J of the Income Tax Act, for professional or technical services above the prescribed threshold. The exact rate and applicability should be confirmed based on the nature of services and the consultant's status.
Not necessarily — a confidentiality clause built into the consultancy agreement is usually enough. A standalone NDA is worth having only if confidential discussions happen before the main agreement is signed, or if the relationship is unusually sensitive.
For a straightforward engagement, typically two to four working days, depending on how quickly the scope of work and commercial terms are finalised between the parties.