Most freelance developers and indie studio founders treat client contracts like "Terms & Conditions" checkboxes—scroll to the bottom, sign, and hope for the best.
Until you get hit with an "unlimited free revisions" demand on WhatsApp, a Net-60 payment delay, or an employment bond hiding a ₹2 Lakh training penalty.
That exact headache is why I built ClauseRadar
([https://clauseradar.online].
What It Does (In 30 Seconds)
Instead of a generic chat wrapper, ClauseRadar runs three specialized workflows for independent builders, creators, and job seekers:
1.Multi-Mode Contract & Bond Scanner:Switch between Freelance/Agency, BrandDeal Shield, and Job Offer & Bond modes (with dedicated support for Indian Contract Act 1872 & MSMED Act alongside US/UK/Global standards). Upload a PDF/DOCX or paste text to get a 0–100 Risk Score, red-flag clauses highlighted,and a ready-to-send negotiation email.
2.Scope Guard:Paste a client's "Hey, can we just add dark mode and tweak the layout real quick?"Slack or WhatsApp message.It checks your revision cap and writes a polite boundary reply with a billable change-order breakdown.
3.Payment Chaser: Calculates the cost of delayed capital and generates 3 escalating reminder notices (from a friendly nudge to a formal legal notice).
The Architecture & Privacy Posture
When we shared our early launch here on DEV, a Staff SDET ran a structured QA preview on clauseradar.online and scored it 98/100 (A)—while catching a missing Zoho SPF TXT record that we patched immediately.
Zero Default Storage:Raw contract text is never stored by default and never used to train models.
Opt-In Contract Memory:
Powered by Supabase (PostgreSQL + strict Row-Level Security), storing only the structured terms you explicitly approve so Scope Guard knows your project's revision limits.
Try It Out (Feedback Welcome!)
You can run a live scan or test the pre-loaded sample contracts (Indian Freelance, Creator Brand Deal, Fresher Job Bond) without even logging in:
👉 https://clauseradar.online
Would love to hear your thoughts on the Scope Guard workflow—how do you currently handle unpaid "quick tweaks" from clients?
Top comments (2)
For the quick tweaks, I keep a simple log: date, what they asked for, estimated hours, and the cost. Before touching anything I reply in writing with something like "Happy to do that, it's about 1.5 hours and $X, want me to go ahead?" That keeps it friendly and gives the client a chance to say yes or skip it. The log also helps when a project ends and someone says there were too many extras, because you can just show the list. For tiny stuff I sometimes bundle a few tweaks into one batch so it doesn't feel like nickel-and-diming.
Spot-on approach! But instead of maintaining manual logs, if you'd like to automate this and instantly convert client messages into formal change-orders, definitely check out Scope Guard on ClauseRadar (clauseradar.online)!