Most freelance disputes are entirely predictable from reading the contract before signing. The problem is knowing what to look for. Kill fees that don't exist. IP clauses that capture your prior work. Net-60 payment terms buried in the fine print. Scrutr AI finds all of it.
What red flags appear in most freelance contracts?
The most common and costly clause missing from freelance contracts is a kill fee — language that requires the client to pay something if they cancel mid-project. Without it, a client can terminate your project after weeks of work and owe you nothing. Scrutr flags this automatically and gives you suggested replacement language. The second most common issue is IP ownership language. Work-for-hire clauses can be written to capture not just the work you do for the client, but your pre-existing tools, frameworks, and code libraries. Scrutr identifies overbroad IP assignment and recommends a carve-out for prior inventions.
Payment terms: what's fair and what's a trap?
Net-60 payment terms — meaning the client pays you 60 days after invoicing — are above industry standard for freelancers and a significant cash flow problem for small operators. Net-14 or Net-30 is the norm. Scrutr flags Net-60 terms and includes this in the negotiation email it drafts for you. Additionally, watch for contracts that don't specify late fees. Without a late payment penalty clause, clients have no contractual incentive to pay on time. Scrutr identifies missing late fee language as a missing protection.
Scope creep: the silent budget killer
Vague scope-of-work language is how clients justify asking for more without paying more. Contracts that describe deliverables in broad terms — 'website redesign,' 'marketing support,' 'content creation' — leave the definition of 'done' entirely to interpretation. Scrutr flags imprecise scope language and suggests you define deliverables, revision rounds, and what falls outside the agreed scope. A well-drafted scope clause is the single best protection against scope creep.
Non-competes in freelance contracts: are they enforceable?
Non-compete clauses in freelance agreements are common and often overbroad. A clause preventing you from working with any company in the same industry for 12 months is both unreasonable and, in many jurisdictions, unenforceable. Scrutr flags non-compete duration, geographic scope, and industry breadth, and explains what standard looks like. Note that enforceability varies significantly by state and country — Scrutr gives you the information to have an informed conversation, not legal advice.