Freelance Contracts in India: Send One Your Client Will Actually Sign

Ask ten Indian freelancers if they use contracts and nine will say some version of "I should, but." I should, but it feels too formal for a ₹40,000 project. I should, but the client is a friend of a friend. I should, but I do not have a template and writing one feels like a lawyer's job. I should, but by the time I find a Word file and fill it in, the project has already started.

So most projects run on a WhatsApp "yes, let's do it." And most of the time that is fine — until it is not. The scope quietly doubles. A payment slips past two months. A client reuses your work on three other pages you were never paid for. Every one of those is a conversation that a one-page contract would have settled before it started.

The problem was never that freelancers do not value contracts. It is that sending one has always been a hassle. That is the part we fixed.

Why "I'll send a contract" rarely happens

Walk through what sending a contract actually used to involve. Find a template you half-trust. Edit it in Word or Google Docs. Export a PDF. Email it. Wait. The client opens it on their phone, has no easy way to sign, says "I'll print and sign and send it back," and then never does. Or you both create DocuSign accounts for a single signature.

Five steps, two apps, and a follow-up — for a document the project cannot start without. So the contract becomes the thing you mean to do and never quite do. The friction wins.

Contracts now live inside Riffit

Riffit started as invoicing. Contracts are the natural other half — the document at the start of a project, the way invoices are the document at the end. Here is the whole flow now:

• Draft from a template built for India. Pick a project type, fill in the client, scope, amount, and timeline. Karnataka jurisdiction by default, IP assignment baked in, GST optional, and an MSMED-friendly late-fee clause — so it reads like a contract written for an Indian freelancer, not a US SaaS form.
• Send it on WhatsApp or email. The client gets a link. No app to install, no account to create.
• Your client signs from the chat. Typed or drawn signature, verified with an OTP — so the signature is actually tied to them, not just a name in a box.
• Both of you get the signed copy. A clean signed PDF, plus a separate audit-trail certificate, delivered to both parties automatically.

Two minutes, one chat, done. The same place you already send invoices.

The audit trail is the part that matters

A signature is only as good as your ability to prove it later. Every contract signed through Riffit comes with an audit-trail certificate — who signed, when, from where, and verified by OTP — structured to address the §65B (Indian Evidence Act) / §63 (BSA) requirements. That is the difference between "I have a signed PDF somewhere" and "I have a record I can point to if anyone ever asks."

And if the client wants changes before they sign, you hit Revise & resend. The new version supersedes the old one, and the audit trail keeps the lineage — so there is never a question about which version is the real one.

What it costs

Contracts are on the free plan too — every Riffit account gets 3 contracts free, for life. That is enough to cover your next few projects and see whether signing-on-WhatsApp actually changes how often clients sign (it does). On Pro, contracts are unlimited, and you get AI-assisted drafting that turns a one-line brief into a sign-ready agreement.

You do not need a lawyer to send a clean, enforceable project contract. You need a template that fits how you work and a way to get it signed before the project drifts. That is the whole point.

FAQ