Priya, a graphic designer working out of a small apartment in Pune, took on a logo and branding project for a client who ran a chain of three gyms. There was no written contract, just a long WhatsApp conversation and a verbal "sounds good." Three weeks in, the client asked for a complete redesign after approving the first concept, then wanted five extra variations for social media, then went quiet for eleven days before messaging to ask why the project was "taking so long." When Priya finally sent her invoice, the client paid only sixty percent of it, arguing that the delay was her fault. She had no document to point to. Nothing said whose fault a delay was, what counted as a revision, or when payment was actually due. She ate the loss and moved on, but she also promised herself she would never start another project without a contract again.
This is a familiar story for independent consultants across India, designers, developers, content writers, chartered accountants doing outside consulting, marketing freelancers. The work itself is often not the hard part. The hard part is the absence of a shared, written understanding of what was promised and what happens when things do not go as planned. A short, plain-language agreement fixes most of this, and it does not need a lawyer to draft one for a straightforward project.
Why "we will figure it out" is not a plan
Verbal agreements and WhatsApp chats feel efficient in the moment, but they fall apart exactly when you need them most, during a dispute. A contract is not really about trust. Most clients who sign one never need to refer back to it. It exists for the small number of projects that go sideways, and for those, it is the difference between a quick resolution and weeks of back and forth with no leverage on either side.
It also changes how a client treats you before anything goes wrong. A consultant who sends a two-page agreement before starting work reads as organised and established, which matters when you are competing for projects against other freelancers on pure word of mouth. If you are weighing whether to present yourself as an informal freelancer or something closer to a proper small business, our piece on freelancer versus registered business in India is a useful companion to this one, since the two decisions tend to reinforce each other.
Scope of work: write down what you will not do
The single biggest source of freelance disputes in India is scope creep, a client asking for "just one small thing" repeatedly until the project has quietly doubled in size. The fix is to describe the deliverables specifically enough that both sides can check them off a list. Instead of "logo design," write "three initial logo concepts, two rounds of revisions on the chosen concept, final files in PNG, SVG and PDF format." Then add a line stating that anything beyond this scope will be quoted and billed separately. This single sentence has probably saved more freelance income in India than any other clause.
If you regularly send clients a breakdown of what is included, a quotation generator is worth using so every client gets a consistent, professional document rather than a different format each time.
Payment terms: be specific about money and dates
"Payment on completion" is not a payment term, it is an invitation to delay. A workable clause states the total fee, the advance required to begin work, usually somewhere between thirty and fifty percent for a new client, the milestones at which further payments are due, and the exact number of days after invoicing that payment is expected, commonly seven, fifteen, or thirty days.
Many independent consultants in India also add a late payment clause, something like one and a half to two percent of the outstanding amount per month for payments beyond the due date. This is a standard commercial practice rather than a legally mandated rate, so you are free to set whatever figure feels fair, but having a number in writing matters more than the exact figure. It gives you something concrete to point to instead of an awkward follow-up message every few days.
For consultants invoicing registered clients, keeping invoice numbers sequential and properly dated also matters for your own records and for GST purposes if you are registered. Our invoice number generator and GST invoice generator can help keep this consistent without building a system from scratch. If you are still unclear on when PAN and TAN actually matter for a consulting income, our guide on PAN and TAN for small businesses covers the basics.
Who owns the work, and when
A surprisingly large number of Indian freelance disputes come down to a single unanswered question, does the client own the final files the moment work is delivered, or only after the final payment clears. The safer default, and the one most consultants should use, is to state explicitly that ownership and usage rights transfer to the client only upon receipt of full payment. Until then, the work remains yours. This single clause gives you real leverage against a client who tries to use your deliverables while stalling on the last invoice.
For software or technical work, also be clear about what happens to source files, source code, or design files versus final exported assets, since clients sometimes assume they are entitled to raw working files when the agreement only ever promised finished output.
Cancellation and a kill fee
Projects get cancelled partway through for all sorts of reasons, a client's budget gets cut, their own plans change, priorities shift. A short cancellation clause protects the time you have already put in. A common structure is to state that if the client cancels after work has begun, they owe payment for work completed to date, plus a flat cancellation fee, often twenty to twenty five percent of the remaining contract value, to compensate for the lost opportunity to take on other work during that period.
Confidentiality and a basic liability limit
If you will see a client's business data, financial numbers, or unreleased product details, a one paragraph confidentiality clause protects both sides and signals professionalism. Pair this with a simple limitation of liability stating that your liability under the agreement will not exceed the total fees paid for the project. Without this, a consultant can technically be exposed to claims far larger than what they were ever paid for the work, which is a disproportionate risk for a freelance engagement.
Putting this where clients can actually see it
A written contract works best as part of a consultant's broader professional presence, not a document that only appears after a client has already committed. Many consultants publish a plain terms of service or working process page on their own website, alongside a portfolio and client testimonials, so that expectations are visible before anyone signs anything. It is also worth having a clear service page describing exactly what you offer as a freelancer or consultant, since a client who understands your process before reaching out is far less likely to push back on standard terms later.
None of this requires expensive legal drafting for most small consulting engagements. A one to two page agreement covering scope, payment, ownership, cancellation and confidentiality, signed over email or a simple e-signature tool, is enough protection for the vast majority of freelance work in India. The goal is not to anticipate every possible dispute. It is to make sure that when something does go wrong, as it eventually will with at least one client, you are not relying on memory and a WhatsApp scroll to make your case.