The 5 contract clauses that quietly wreck freelancers (and the exact words to push back)

Ricardo — Mon, 13 Jul 2026 10:21:26 +0000

Most freelancers lose money not on the work, but on a single sentence they skimmed in a contract. Here are the five clauses I've learned to catch before signing, why each one is dangerous, and the exact language I use to push back. Steal all of it.

1. Unlimited revisions

The clause: "Contractor shall provide revisions until the Client is fully satisfied."

Why it wrecks you: There is no cap on rounds and no definition of "satisfied." A $2,000 project can become a three-month unpaid marathon because "satisfied" is entirely the client's opinion.

Push back with: "I include up to 2 rounds of revisions per deliverable. Additional rounds are billed at my hourly rate of $X. This keeps us both focused on getting it right in the first two passes."

2. IP transfers on signature, not on payment

The clause: "All intellectual property created shall be the property of the Client upon creation."

Why it wrecks you: If ownership transfers on creation (or on signing), you've handed over the work before you've been paid. If they ghost you, they legally own it and you have no leverage.

Push back with: "Ownership of all deliverables transfers to the Client upon receipt of final payment. Until then, the work remains my property."

3. Kill fee missing entirely

The clause: ...there isn't one. The contract is silent on what happens if the client cancels halfway.

Why it wrecks you: They cancel after you've done 70% of the work, and with no kill fee, you're owed nothing for it.

Push back with: "If the project is cancelled after work has begun, completed milestones are billed in full and the current in-progress milestone is billed at 50%."

4. Net-60 (or worse) payment terms

The clause: "Invoices are payable within 60 days of receipt."

Why it wrecks you: You're financing the client's business for two months, interest-free. For a solo operator, Net-60 is a cash-flow killer.

Push back with: "My standard terms are Net-15, with a 50% deposit before work begins. This lets me commit fully to your timeline."

5. Non-compete that's absurdly broad

The clause: "Contractor shall not provide similar services to any company in the Client's industry for 24 months."

Why it wrecks you: If you're a freelance designer and the client is in "e-commerce," this clause tries to ban you from working with the entire e-commerce industry for two years. That's your whole livelihood.

Push back with: "I'm happy to agree not to work with your named direct competitors [list 2-3] for 6 months. A blanket industry ban isn't something I can sign, since it would prevent me from working at all."

The pattern behind all five: contracts are written to protect the party who wrote them. Reading yours slowly, out loud, is the highest-ROI 20 minutes in freelancing.

I got tired of doing this scan manually on every SOW, so I turned it into a Claude Code skill (/redline) that flags these clauses in plain English and drafts the pushback. It's part of a small pack of freelance-admin skills I put together; the invoice-generator one is free if you want to try the format: https://agentia11.gumroad.com/l/qclmyx

But honestly, even if you never touch the tool, save these five. The next contract you sign will probably have at least one of them.

7 Claude Code skills that kill freelance admin work (invoices, proposals, contract redlines)

Ricardo — Mon, 13 Jul 2026 07:37:11 +0000

I bill clients as a freelancer, and I noticed I was rewriting the same Claude Code prompts every week: draft an invoice, write a proposal from a job post, turn messy meeting notes into a summary + action items, check a contract for risky clauses before signing.

So I packaged them as reusable Claude Code skills — plain-text files you drop into your skills folder, no API keys, no subscriptions:

/invoice — describe the work in plain English, get a polished invoice back (HTML + Markdown) in seconds
/proposal — paste a job post or call notes, get a tight, client-ready proposal
/meeting — paste messy notes or a transcript, get a summary + action-item table + a follow-up email draft
/redline — paste a contract or SOW, get the risky clauses flagged in plain English before you sign
/outreach — a personalized 3-touch cold email/LinkedIn sequence for a prospect
/scopecheck — paste a new client ask against your original scope, get a verdict and a ready-to-send response
/setrate — turn a target income into an hourly rate or project price, with the math shown

Example of what /redline actually outputs on a real (anonymized) contract clause:

Flagged: Unlimited revisions clause (Section 4.2)
"Contractor shall provide unlimited revisions until Client is fully satisfied" has no cap on rounds or timeline — this is the single most common freelance scope-creep trap. Suggested response: "Happy to include up to 2 rounds of revisions per deliverable; additional rounds billed at the hourly rate."

That's the kind of thing that's obvious once you see it, but easy to miss when you're reading a contract for the third time at 11pm.

I made /invoice free to try on its own. The full 7-skill pack is $27 (one-time, not a subscription) — Claude Code Freelancer Pack.

If you're a freelancer/consultant using Claude Code for actual client work: what's the admin task you'd want automated that isn't on this list? Genuinely collecting ideas for what to build next.