A WhatsApp “yes, start Monday” is not a Statement of Work. When the client later asks for “just one more page,” three extra revision rounds, and payment after launch, you have no document that says what was agreed.
A Statement of Work (SOW) is the short, plain-English scope agreement that sits between your rate card / proposal and the actual build. It defines deliverables, what is out of scope, payment triggers, revision rules, and how changes get billed. For Indian freelancers billing in INR with UPI advances and chat-heavy clients, it is often the difference between a clean project and unpaid overtime.
This guide is educational — not legal advice. For high-value, retainer, or cross-border work, have a lawyer review your language. Tax and GST belong on invoices, not inside the SOW body; see Best GST Invoice Templates for Indian Freelancers (2026) (Finance Kit — GST invoices + tracker) when money moves.
What an SOW is (and is not)
| Document | Job |
|---|---|
| Rate card | What you sell and at what ₹ price (packages + add-ons) |
| Proposal | Why this client should buy a specific package now |
| SOW / scope | Exact deliverables, boundaries, milestones, change process |
| Invoice | Request for payment (GST-aware if registered) |
An SOW is not a GST invoice, tax planner, or full agency MSA. It is also not a substitute for your freelance rate card (Client Ops Kit — rate card + proposal/SOW) — the rate card prices the offer; the SOW locks the chosen offer into delivery terms.
Why Indian freelancers need one in 2026
Typical failure pattern:
- Quote agreed in voice notes
- Kickoff with “we’ll figure details later”
- Scope creep via WhatsApp groups and late-night forwards
- “Pay after launch” with no milestone triggers
- Argument about what was “obviously included”
India-specific realities that belong in the SOW:
- UPI / NEFT advances before kickoff (not “trust first”)
- INR totals and clear advance / mid / final splits (e.g. 40/30/30)
- WhatsApp as a channel — but not as the contract of record
- Revision rounds stated as numbers, not vibes
- Pause-on-nonpayment language so you are not funding the client’s experiment
Practical SOW sections to include
Use these sections whether you DIY in Docs/Notion or start from a kit template. Keep language plain; clients actually read short SOWs.
1. Parties and project title
Your legal / trade name, client name and billing contact, project title, effective date, and SOW version (v1, v2 after a Change Order).
2. Background and objectives (short)
Two to four sentences: problem, intended outcome, and measurable success criteria (e.g. “launch-ready landing page with form connected to client’s CRM”). Avoid soft promises like “world-class brand.”
3. In-scope deliverables
Bullet tangible outputs: files, pages, features, formats (Figma, repo access, PDF), platforms covered, and revision rounds included. Define a “round” as one consolidated feedback batch. If it is not on this list, it is not free work.
4. Out of scope (explicit)
List what clients often assume is free: extra pages/screens, unbought workshops, stock licences, post-handoff maintenance, meetings beyond X hours/week, rush outside timeline. Point to add-on rates or a Change Order instead of arguing later.
5. Timeline and assumptions
Start only after advance received. Note phase durations, client duties (feedback within N business days, content by date X, access), and assumptions (“copy in English by week 1”; “hosting is client-owned”). Late client inputs should push milestones — say so.
6. Fees, currency, and payment schedule
Total fee in ₹ (state if GST is extra if you are registered — confirm with your CA). Payment via UPI / NEFT (or “as on invoice”). Use triggers, not vague dates:
| Typical pattern | Use when |
|---|---|
| 50% advance / 50% on delivery | Short projects |
| 40% / 30% / 30% | Medium builds with a mid approval |
| Monthly in advance | Retainers with hour or deliverable caps |
Example: “30% on homepage design approval,” not “sometime mid-project.”
7. Revision and change control
State included rounds, how feedback arrives (one list beats 15 voice notes), what counts as a new request, extra-revision rate (₹ / round or hourly), and that a Change Order is required before out-of-scope work. That converts WhatsApp creep into a billable line.
8. Acceptance and handoff
Who signs off, acceptance window (e.g. 5 business days of silence = accepted), what “done” means for final payment, and a handoff checklist (files, access, docs).
9. Intellectual property (simple version)
Common pattern (customise with legal review): client owns final deliverables after full payment; you retain pre-existing tools/frameworks and portfolio rights unless an NDA forbids; third-party licences stay third-party. Do not invent complex IP from social posts.
10. Pause, termination, and nonpayment
Structural ideas only (not legal advice): pause if a milestone is late beyond N days; kill fee or retain advance on mid-project cancel; written notice to end with fees due for completed work.
11. Communication norms
Primary channel for decisions (email / shared doc) vs casual WhatsApp updates; IST response hours; weekly status habit. Scope changes must be written (email or Change Order), even if the chat is friendly.
12. Signatures / confirmation
Name, date, and “Agreed” from both sides. Email reply + PDF is fine for many small Indian jobs; use proper e-sign for larger deals your lawyer prefers.
DIY SOW skeleton (copy and edit)
STATEMENT OF WORK — [Project Title]
Version: 1.0 | Date: ____ | Currency: INR
1. Parties
Freelancer: ____ | Client: ____
2. Objective (1–3 sentences)
____
3. In scope
• Deliverables:
• Formats / access:
• Revisions included: __ rounds (consolidated feedback)
4. Out of scope
• ____
• Extra work via Change Order at ₹____ / hour or ₹____ / round
5. Timeline & assumptions
Start after __% advance. Client feedback within __ business days.
Assumptions: ____
6. Fees & milestones
Total: ₹______ (GST: as applicable / on invoice)
• __% — ₹______ — trigger: kickoff / advance
• __% — ₹______ — trigger: ________
• __% — ₹______ — trigger: final acceptance
Payment: UPI / NEFT as on invoice
7. Change control
Out-of-scope work starts only after written Change Order + fee agreement.
8. Acceptance
Client has __ business days to accept or list defects in writing.
9. IP (summary)
Final deliverables transfer on full payment. Portfolio use: ____
10. Pause on nonpayment
Work may pause if any milestone is unpaid > __ days.
Agreed:
Freelancer ________ Date ____
Client ________ Date ____
Fill real numbers. Revisit when packages on your rate card change.
DIY vs a ready Client Ops kit
DIY works if you have one offer, low volume, and paste the skeleton into every kickoff.
DIY breaks when several clients pile up, revision logs vanish, and milestones live in your head. Then you need SOW plus rate card, proposal, Change Order, milestone schedule, and a tracker that connect.
Soft tool recommendation: Indian Freelancer Client Ops Kit
Pranjal Vyas’s Indian Freelancer Client Ops Kit is for Indian freelancers who want proposal → SOW → kickoff → revision → milestone control without agency software.
Relevant for SOW work (per Gumroad): Markdown SOW / scope template (in/out, IP summary, pause-on-nonpayment); Change Order / extra revision template; client-facing milestone payment schedule; Excel Rate Card, Project Tracker, Milestone Schedule, Revision Log, Ops Dashboard; plain-English Client Ops Guide (India).
Price listed: launch ₹449 → list ₹599. Excel / LibreOffice / Sheets import; templates in Notion or Docs.
Positioning: not a GST invoice or tax kit. Ops decides scope and when to bill; Finance produces the invoice. For GST invoicing and payment tracking, see the Indian Freelancer Finance Kit.
Product disclaimer (paraphrased): educational / productivity only; no guaranteed clients or income; SOW/Change Order text is structural — consult a lawyer and CA for high-value or cross-border work.
Soft CTA: if kickoff is still a WhatsApp thread with no written scope, start from the Client Ops Kit SOW + Change Order templates — pranjalvyas.gumroad.com/l/oejgeh.
How the SOW connects to rate cards and invoices
- Rate card sets packages and add-on ₹ prices — see How to Build a Freelance Rate Card in India (2026 Guide) (Client Ops Kit — rate card + proposal/SOW).
- Proposal recommends a package.
- SOW locks the chosen package into deliverables and milestones.
- Invoice (Finance Kit lane) collects each milestone when due — GST invoice guide (Finance Kit — GST invoices + tracker).
| Client Ops Kit | Finance Kit |
|---|---|
| SOW, Change Order, packages | GST invoices |
| Revision log & milestone plan | Payment ledger & tax planner |
| When to pause for nonpayment | Reminder emails & compliance notes |
Buy one or both — they do not replace each other.
Common SOW mistakes
- Scope written as feelings (“modern website”) instead of deliverables
- No out-of-scope list
- Unlimited revisions
- Payment only “on completion” with no mid triggers
- Treating WhatsApp yes as the contract
- Mixing GST invoice fields into the SOW instead of a finance workflow
- Copy-pasting US legal templates that ignore INR / UPI norms
- Skipping Change Orders and then resenting free work
FAQ
Do I need a lawyer for every SOW?
For small productised jobs, a clear structural SOW often helps. For large retainers, IP-heavy products, or foreign clients, get legal review.
SOW or full contract?
Short SOW for scoped projects; longer contracts for retainers / high stakes. The SOW can sit under a master agreement if you have one.
Can I send the SOW on WhatsApp?
Yes as a PDF/link — keep emailed or signed confirmation as the record. Chat is not the contract.
Should GST appear in the SOW?
Show tax-exclusive vs inclusive. Put GST lines on invoices if registered — confirm with your CA.
Bottom line
A statement of work template for Indian freelancers in 2026 should be short, INR-clear, milestone-tied, and ruthless about out-of-scope and Change Orders. Pair it with a rate card at the front of the funnel and clean invoicing when payments are due.
If you want SOW + Change Order + milestone + revision tooling in one kit, the Indian Freelancer Client Ops Kit matches that ops problem. Verify commercial and tax rules on official sources; get legal review for high-stakes work.
Top comments (0)