Most freelancers do not skip contracts because they think contracts are pointless. They skip them because finding a template, editing it, and chasing a signature is more work than the ₹40,000 project seems to justify. So the project runs on a WhatsApp "yes, let's do it," and that is fine, right up until the scope doubles or a payment goes quiet.
The fix is not a 12-page agreement from a US template site with clauses about Delaware arbitration. It is one clear page that fits how Indian freelancers actually work. Here is a template you can copy today, plus the handful of clauses people most often leave out and regret.
The freelance contract template — copy this
Paste this into a doc, replace everything in brackets, and you have a usable freelance service agreement. It is deliberately short. A contract a client will actually read and sign beats a perfect one they never open.
Clause 1 is the one that does the most work and gets the least thought. If you want it in detail, what to put in a scope of work breaks that clause into the six parts that actually prevent an argument.
FREELANCE SERVICE AGREEMENT
Between:
Freelancer — [Your name / studio name], [city], [email], [phone]
Client — [Client name / company], [city], [email], [phone]
Date — [DD/MM/YYYY]
1. SCOPE OF WORK
[Describe exactly what you will deliver. Be specific.
Example: "Design of one primary logo, a one-page brand
guideline, and a business-card layout." List what is NOT
included so there is no assumption later.]
2. DELIVERABLES
[Final files and formats. Example: "Logo in SVG, PNG and
PDF; brand guide as a PDF." Note how many source files, if any.]
3. TIMELINE
Start: [date, or "within 2 working days of advance payment"].
Delivery: [date, or "X working days after start"].
Client feedback on each draft within [3] working days.
4. FEES
Total fee: ₹[amount] [+ 18% GST if you are registered].
Advance: ₹[50% of total], payable before work begins.
Balance: ₹[remaining], payable on delivery, before final
files are released.
5. PAYMENT TERMS
Invoices are payable within [7] days via [UPI / bank transfer].
Payments delayed beyond the due date carry interest at [1.5]%
per month on the outstanding amount.
6. REVISIONS
Fee includes [2] rounds of revisions. Further rounds are
billed at ₹[amount] per round.
7. INTELLECTUAL PROPERTY
Ownership of the final delivered work passes to the Client
only on receipt of full payment. Until then, all rights stay
with the Freelancer. The Freelancer may show the work in their
portfolio unless the Client asks otherwise in writing.
8. CANCELLATION
If the Client cancels, fees for work done up to that point
remain payable and the advance is non-refundable.
9. CONFIDENTIALITY
Both sides keep each other's business information private.
10. GOVERNING LAW
This agreement is governed by the laws of India. Any dispute
falls under the jurisdiction of the courts of [your city].
Signed —
Freelancer: __________________ Date: __________
Client: __________________ Date: __________
That is the whole thing. Ten clauses, one page, no lawyer required for a standard project. If you do design work specifically, layer the design contract template on top: it adds revision-round, source-file, and usage-rights clauses.
The clauses Indian freelancers most often skip
If you strip this down further, keep these four. They are the ones that actually save you money.
The advance, tied to "before work begins." The advance is not just cash flow, it is the line that separates a committed client from someone still shopping, and fifty percent upfront is the most common convention in India for design, development, and content work. If a client will not pay it, that is information.
IP transfers on full payment, not on delivery. This one sentence is what gives you real bargaining power. If ownership passes only when you are paid in full, an unpaid client does not legally own the logo they are already using. Most people skip this. They write "IP transfers to the client" with no condition and quietly hand away their only bargaining chip.
A stated late-payment interest rate. A number on the page changes behaviour. "1.5% per month on overdue amounts" is a normal, enforceable term, and it gives you something concrete to point at instead of an awkward reminder. If you are a registered micro or small enterprise, the MSMED Act gives additional statutory protection on delayed payments, worth reading up on separately. That statutory rate (three times the RBI bank rate, compounded monthly) is a separate mechanism from whatever rate you write into your own contract, and can be much higher.
Jurisdiction: your city. If a dispute ever goes formal, you do not want to be arguing it in a court three states away, and naming your own city is standard and costs you nothing at signing.
The real problem is not the template — it is getting it signed
Here is where most contracts die. You have the template. You fill it in. You export a PDF and email it. The client opens it on their phone, has no clean way to sign, says "I will print, sign, and scan it," and then never does. Or you both end up creating accounts on a signing tool for a single signature.
That friction is why the contract becomes the thing you meant to send. A template only helps if it actually gets signed, before the work starts, not after the regret.
Skip the print-sign-scan loop. Draft this contract on your Riffit dashboard and send your client a link to sign.Try Riffit freeThis is exactly why I built contracts into Riffit. You start from the Project template on the dashboard, fill in the same details the template above asks for, and send it by email, or on WhatsApp on Pro. Your client signs from the link, typed or drawn, verified with a one-time code. Your client gets the signed PDF; you keep the audit-trail certificate. If you want the full walk-through, see how to send a freelance contract your client will actually sign.
A fair question before you send anything electronically: how is a signature typed on a phone treated? Short version: Indian law recognises electronic signatures for ordinary agreements like this one, and what matters is the record of who signed and when. The longer version is in are electronic signatures legal in India.
And once the work is done, the document at the other end of the project is the invoice. Here is how to create a clean freelance invoice in India to close the loop.
FAQ
Yes. The clauses (scope, deliverables, timeline, fee, payment terms, revisions, and IP) apply to any freelance service work, whether that is development, writing, video, consulting, or design. Adjust the scope and deliverables lines to describe what you actually hand over. For a high-value or unusual engagement, a lawyer review is still worth it.
Yes. A service agreement between two parties is a valid contract under the Indian Contract Act, 1872, as long as there is a clear offer, acceptance, and consideration. It does not need to be on stamp paper or notarised to be enforceable for ordinary freelance work, though stamping rules can apply to certain higher-value agreements depending on your state.
Fifty percent upfront is the common norm in India for design, development, and content work, but it is not a rule. For a new client or a large project, some freelancers split into three: an advance, a milestone payment, and a balance on delivery. The important part is that some money changes hands before you start.
Because it is your leverage. If ownership of the final work passes only when you are paid in full, a client who has not paid does not legally own what they are using. If you transfer IP on delivery instead, you give away your strongest reason for them to clear the balance.
You can, and a signed agreement shared over WhatsApp is far better than nothing. The cleaner path is to send it as a proper document your client signs with a one-time code, so there is a clear record of who agreed and when. In Riffit you make it on the dashboard and your client gets it as a link, by email or, on Pro, on WhatsApp.