Freelance Contract Builder
Most freelancers work without a contract or with a generic template that misses the clauses that actually cost money — IP ownership, scope creep, kill fees, late payment. The Freelance Contract Builder takes the deal terms and produces an engagement-specific agreement with the protections that match the real risks of this particular project.
What this skill does
Generic contract templates miss the clauses that actually matter — IP, scope, kill fees, late payment — because those are the clauses that depend on the specifics of the engagement. A web developer's contract needs different protections than a copywriter's. A retainer needs different language than a fixed-price project. This skill produces situation-specific contracts, not a download with your name in the header.
The process starts with the deal terms. Parties, jurisdiction, deliverables (and what's explicitly excluded), timeline, fee structure, payment schedule, kill fee, expense handling, IP ownership, pre-existing materials. Retainers get an extra layer — what's included in the monthly fee, how overages are billed, minimum commitment term, notice period to end. Each engagement is then run through a risk profile across five factors: scope clarity, client type, payment size, IP sensitivity, and timeline pressure. High-risk areas get strengthened clauses.
Every contract follows the same ten-section structure: parties, scope, timeline, compensation, IP, confidentiality, warranties and liability cap, termination, general provisions (including substitution rights and no-mutuality-of-obligation for UK IR35 posture), and signatures. Plain English throughout — legalese the parties can't understand defeats the purpose. The defaults lean slightly more protective of the freelancer because they have less bargaining power and more downside, but the contract still has to work for both sides or it gets rejected.
The draft gets stress-tested against the scenarios that actually break freelance projects: client ghosts after delivery, scope creeps past the original brief, unlimited-revisions request lands, project cancelled at 60% completion, client delays feedback for weeks, dispute arises and you need a resolution path before litigation. If a scenario isn't covered, the clause gets tightened.
The output includes a Risk Assessment (the specific risks of this engagement and how the contract handles them), the full contract text, and Clause Notes explaining which clauses are "do not remove" (IP, payment, liability cap) and which are safely adjustable in negotiation (revision rounds, timeline flexibility). If a client has already sent their own contract, the skill reviews it against the structure and drafts amendment clauses the freelancer can propose — you don't have to reject the client's contract, you can strengthen it.
This produces a drafted contract, not legal advice. Contracts are legally binding and the small print really does matter — especially around IP assignment, liability caps, and termination clauses where a single word can shift who bears the risk. Have a qualified solicitor review the draft before signing. The skill is a starting point for professional review, not a substitute for one.
When this triggers
- ·You're about to start a project and the client expects a contract by Monday
- ·You've been using a downloaded template and a recent project showed it had holes
- ·The client sent their own contract and you need to know what to push back on
- ·You're moving from one-off projects to retainers and the old contract doesn't cover it
- ·An IP-sensitive build is starting and the standard template doesn't carve out your pre-existing tools
Example
Trigger
User: 'Six-week web build, £8K, fixed price. Two-thirds upfront / one-third on launch. UK client, sole trader on my side. They're using a stock CMS but I'm writing custom plugins.'
Output
Risk Assessment · Fixed-price + custom code = scope-creep risk is high. Strong change-order clause needed. · Custom plugins are your IP until paid in full — assignment tied to final payment, not handover. · You're bringing pre-existing utility code into the plugins. Pre-existing IP carve-out needed or you lose reusability. · UK sole trader engaging UK client — IR35 less relevant commercially but substitution + no-mutuality clauses still worth including for HMRC posture. · Late payment penalty needed — "due on receipt" is unenforceable without a specified consequence. The Contract (10 sections, plain English): 1. Parties — full names, addresses, sole-trader status 2. Scope — 6 numbered deliverables, 3 explicit exclusions (copywriting, photography, ongoing support beyond launch) 3. Timeline — milestones with client-feedback deadlines (delays caused by client extend the timeline pro-rata) 4. Compensation — £8K split 66/33, late penalty 8% + Bank of England base rate (statutory), kill fee 50% of remaining work 5. IP — full assignment on final payment, pre-existing IP schedule attached, perpetual licence-back for portfolio 6. Confidentiality, 7. Warranties, 8. Termination, 9. General (governing law, mediation first), 10. Signatures. Clause Notes: which 4 clauses are "do not remove" vs the 6 that are safely negotiable.
Get this skill + 6 more
Included in the The Freelancer Stack — win clients, deliver work, get paid. Save $100+ vs buying individually.
Get The Freelancer Stack — $99What you get
- 153-line SKILL.md, ready to drop into ~/.claude/skills/
- Tested through 3 Karpathy-loop iterations (versions v1.0.0 → v1.3.0)
- Triggers automatically when relevant — no command to remember
- Lifetime updates as the skill is refined further
More from Legal & Compliance
Produces letters that are firm enough to be taken seriously, specific enough to be legally meaningful, and professional enough that they don't escalate the situation unnecessarily
Produces the actual words to say or write — not generic advice like "stay calm and be professional. Takes the specific conflict, identify the underlying interests, and draft a communication strategy…
Doesn't produce a generic 50-point checklist — it assesses what a specific business does with data, identify the gaps, prioritise them by risk, and give concrete steps to close each gap
Handles the part of business relationships that causes the most expensive disputes: who owns what was created
Doesn't produce a generic wall of text — it produces a policy that accurately describes what THIS business does with data, which laws apply, and what rights users have
Produces T&Cs that protect the business from real risks — not a generic template that covers everything and protects nothing
Browse the full library
297 skills across 31 categories. One purchase, lifetime updates.
See all bundles