Every freelance developer has lived through at least one of these nightmares:
- A client messages you on WhatsApp at 11 PM: "Hey, can we also add dark mode and rework the dashboard layout? Should be a quick tweak!"
- You finish the project, send the invoice, and realize the contract says Net-90 payment subject to client satisfaction.
- An agency subcontract says Pay-When-Paid—meaning if their end client ghosts them, you work for free.
As an independent developer and the founder of ClauseRadar ([https://clauseradar.online]
I built an AI contract risk scanner, Scope Guard, and Payment Chaser specifically for freelancers, indie agencies, creators, and job seekers after seeing how often builders get burned by legal fine print.
Here are the 5 most dangerous clauses you should never sign without a counter-clause—along with copy-paste fixes you can use today.
- The "Work Made For Hire" IP Transfer Before Payment The Trap: "All work, drafts, code, and pre-existing tools used in the project belong to the Client from the moment of creation, whether or not paid." Why it's dangerous: First, if IP transfers on creation instead of on full payment, a shady client can legally use your code in production while refusing to pay your final invoice. Second, including "pre-existing tools" means they technically own your reusable UI components, auth wrappers, and boilerplate! The Safer Counter-Clause: "Ownership of deliverables transfers to the Client only on receipt of full payment. Contractor retains all rights in pre-existing tools, libraries, and know-how, granting the Client a non-exclusive license to use them within the deliverables." Full guide & email script: IP Transfer Only After Full Payment (https://clauseradar.online/guide/ip-transfer-on-full-payment-clause)) & Protecting Your Prior Tools (https://clauseradar.online/guide/work-for-hire-clause-freelancer-prior-tools)
- "Unlimited Revisions" & WhatsApp Scope Creep The Trap: "Contractor will provide revisions until the Client is fully satisfied and perform any additional tasks reasonably requested without extra pay." Why it's dangerous: "Reasonably requested" and "until satisfied" have no ceiling. Your fixed-price ₹50,000 / $1,000 project slowly turns into 4 months of unpaid labor. The Safer Counter-Clause: "The fee includes two (2) rounds of consolidated revisions within the agreed scope. Additional revisions or out-of-scope requests require a written change order billed at [RATE]/hour." How to reply on WhatsApp/Slack when a client asks for a "free tweak": "Hi [Client], happy to help with this! Since this falls outside the 2 revision rounds in our agreement, I'll put together a quick change-order estimate (approx [X] hours / [Amount]). Once you approve it in writing, I'll jump right on it!" (Pro tip: You can paste any client Slack/WhatsApp message into ClauseRadar's Scope Guard [https://clauseradar.online/scope-guard], and it checks your contract terms to generate a polite change-order quote automatically).
- Uncapped Indemnification & Liability The Trap: "Contractor shall indemnify Client against all claims, damages, data loss, third-party API outages, and legal fees of any kind, with no cap." Why it's dangerous: If you build a ₹40,000 web app and AWS goes down, or the client gets sued over content they provided, an uncapped indemnity clause means you could be liable for millions. The Safer Counter-Clause: "Contractor's total aggregate liability, including any indemnity, shall not exceed the total fees actually paid to Contractor under this Agreement in the preceding 12 months. Neither party is liable for indirect or consequential damages or third-party service outages." Full guide: Uncapped Indemnity Clause Meaning and How to Cap It (https://clauseradar.online/guide/uncapped-indemnity-clause-meaning-and-cap)
- Net-90 Payment Traps & The MSMED 45-Day Rule (For Indian Devs) The Trap: "Payment will be made within 90 days of invoice approval at the Client's sole discretion." Why it's dangerous: You are not a bank; you shouldn't finance your client for 3 months.
- Global Fix: Push for 30% upfront deposit, Net-14 payments, and deemed acceptance after 5 business days (so a client can't ghost your delivery to stall the invoice clock).
- Indian Devs Bonus (MSMED Act 2006): If you have a free Udyam registration as a micro/small enterprise, Section 15 of the MSMED Act requires buyers to pay within the agreed period—which cannot exceed 45 days from acceptance—and Section 16 mandates compound interest at 3x the RBI bank rate on late payments!
Demand Notice Format: MSMED Act 45-Day Payment Rule & Demand Notice (https://clauseradar.online/guide/msmed-45-day-payment-demand-notice-format)
- Pay-When-Paid in Agency Subcontracts The Trap: "Agency will pay Subcontractor within 15 days after Agency receives payment from the end client." Why it's dangerous: You have zero control over whether the agency's end client pays on time. Always require a hard backstop date: "within 15 days of client payment, and in no event later than 30 days from invoice date." Full guide: Pay-When-Paid vs Pay-If-Paid in Subcontractor Agreements (https://clauseradar.online/guide/pay-when-paid-vs-pay-if-paid-subcontractor-agreement) Try ClauseRadar on Your Next Contract (Free Scan) I built ClauseRadar (https://clauseradar.online) using Svelte, Vite (statically pre-rendered across 100+ guides for speed), and Supabase so developers, creators, and job seekers can audit contracts in 30 seconds.
- Contract Scanner (https://clauseradar.online/dashboard): Upload a PDF/DOCX or paste text across 4 modes (Freelance, BrandDeal Shield for Creators, Job Offer & Bond, Agency White-Label).
- Scope Guard (https://clauseradar.online/scope-guard): Paste a client's "quick tweak" message to see if it's in scope or billable, complete with a change-order quote.
- Payment Chaser (https://clauseradar.online/chaser): Track overdue invoices with a 3-level escalation sequence.
- 100+ Free Contract Guides (https://clauseradar.online/guides): Browse plain-English guides and copy-paste clauses from our Clause Library (https://clauseradar.online/vault). Give the Sample Audit Report (https://clauseradar.online/sample) a spin and let me know what you think in the comments! Written by Pintu Ray, Founder of ClauseRadar (https://clauseradar.online).
Top comments (3)
The 11 PM "quick tweak" message should be printed on the first page of every freelance contract guide. The counter clause for revisions is exactly right, and I would underline one thing about it: a cap only protects you if it was settled while everyone was still friendly, before the work started. Mid project, the same sentence reads like an argument. That is the whole reason the tool I am building, worXwap, makes both sides settle one short agreement card first, with the deliverable, the deadline and the revision count on it, before anyone writes a line of code. Your clause says what the limit is. The card is just a place where both sides have already agreed to it, so you are pointing at a page instead of defending a position.
Spot on! Pre-alignment before writing a single line of code is the ultimate fix for scope creep. You hit the nail on the head—pointing to a pre-agreed document beats arguing mid-project every single time. Checked out worXwap too, love what you're building! Keep it up 🚀
Thank you for actually going and looking at worXwap, that means more than the kind words on their own. And yes, pointing at what was agreed beats arguing in the middle of the work, every time. The hard part I keep meeting is getting that agreement written while it still feels friendly, before anyone thinks they need protection from the other person. Once it is written early, it just reads as being clear about the job. Glad the pre alignment point landed with you.