Do I need a written contract for every client?

Yes, even for small projects. Verbal agreements are enforceable in most states but nearly impossible to prove. A written contract sets scope, price, and timeline in a format a judge or arbitrator can read. Even a one-page email chain that both parties confirm in writing is better than a handshake. For recurring clients, a master service agreement (MSA) plus individual statements of work is the cleanest structure.

Who owns the work I create as an independent contractor?

By default under US copyright law, the creator owns the work — meaning you, the contractor. The client does not automatically own what you built unless the contract explicitly assigns intellectual property rights to them or the work qualifies as 'work made for hire' under copyright law (a narrow category for employees and certain commissioned works). If you want to keep licensing rights, your contract should say so. If the client needs full ownership, the contract should include an IP assignment clause.

What's the difference between a proposal and a contract?

A proposal is an offer — it describes what you'll do and for what price, but it isn't binding until accepted. A contract is an agreement — both parties have accepted terms and there's mutual consideration (you do work, they pay money). The cleanest workflow: send a proposal, client approves it, you send a contract (or the proposal includes signature blocks that convert it to a contract upon signing). Never start work on a proposal alone without a signed agreement.

Can I use a contract template from the internet?

For straightforward project work, yes — with care. Verify the template is designed for your state's law (some contract provisions only work in certain jurisdictions), update all placeholders, and add any project-specific terms before sending. For high-value, complex, or ongoing engagements (retainers, equity-adjacent arrangements, white-label work), have an attorney review at least once. The one-time cost of a legal review on your template is almost always worth it.

What happens if a client doesn't pay and I have a contract?

A signed contract gives you several options: send a demand letter referencing the contract terms, send to collections, file in small claims court (most states: $10,000–$25,000 limit), or pursue civil litigation. If your contract has an attorney's fees clause (common in B2B contracts), the client may be responsible for your legal costs if you win. Without a contract, you have the same options but a much harder time proving the agreed terms.

Should my contract include a kill fee?

Yes if you're doing substantial upfront work. A kill fee (also called a cancellation fee) is a payment owed by the client if they cancel after work has begun. Common structures: 25%–50% of the remaining project fee if cancelled at >50% completion, or 100% of deposits already paid. Kill fees protect you from putting 40 hours into a rebrand and having the client walk. They're standard in creative, agency, and custom software work.

Independent Contractor Agreement: What to Include and What to Never Skip

Most contractors negotiate price and timeline carefully and then use whatever contract template Google surfaces first. This is backwards. The contract is the document that matters when things go wrong — when the client stops responding, disputes the scope, or says the work isn't what they expected. The time to think carefully about it is before the project starts, not after.

Here's what every independent contractor agreement needs, in order of how often the omissions cause problems.

The Six Core Sections

Every contract should have these six. Skip any of them and you're creating a gap someone can exploit.

1. Scope of Work

The most litigated section. The scope of work describes exactly what you will deliver, in terms specific enough that a third party could read it and know whether you delivered or not.

Weak scope: "Website redesign and development"

Strong scope: "Design and develop a 5-page marketing website (Home, About, Services, Blog, Contact) built on Shopify using a licensed premium theme. Includes up to 3 rounds of design revisions on the home page mockup before development begins. Mobile-responsive. Excludes copywriting, product photography, third-party app installation (except those specified in Appendix A), and ongoing maintenance."

Every exclusion you add to the scope is a future dispute you've prevented. "Excludes" language is as important as what you're including.

If the scope is complex, put the detailed spec in an appendix or separate Statement of Work and reference it in the main contract. The contract body stays clean; the SOW carries the technical detail.

2. Payment Terms

Specify:

Total fee (or hourly rate and estimated hours)
Payment schedule (deposit %, milestones, final payment)
Invoice timing (when invoices go out)
Due date (net-15, net-30, or upon receipt)
Late payment penalties (e.g., 1.5% per month after 30 days)
Accepted payment methods (ACH, check, card)

The late payment clause matters. Without it, you have no contractual basis for charging interest on overdue invoices — you'd need to rely on state law, which is messier. With it, you have an explicit right to charge interest and a stronger position in any dispute.

Don't leave payment milestones vague. "50% upon project completion" is ambiguous if the client disputes whether the project is complete. "50% upon delivery of all files listed in Appendix A and written client approval" ties the milestone to specific, objective events.

3. Timeline and Deadlines

List:

Your start date (often contingent on deposit receipt)
Major milestones and their target dates
The final delivery date
Revision windows (how long the client has to review and respond before the project is considered accepted)
Explicit statement that timeline extends proportionally if client delays feedback

The "client delay" clause saves projects regularly. Clients who don't respond to feedback requests for two weeks and then blame you for missing the deadline don't have a legal leg to stand on if your contract says: "Timeline is contingent on client review turnaround of 3 business days per deliverable. Client delays of more than 5 business days extend the project timeline proportionally."

4. Intellectual Property

Two scenarios, two very different clauses:

If the client owns the final work (the typical outcome for most custom work): Include an IP assignment clause that transfers copyright to the client upon receipt of final payment in full. Do not transfer IP until you've been paid — this gives you substantial leverage if a client goes silent.

If you retain licensing rights (common in stock work, template-based work, or when you want to show the work in your portfolio): Be explicit. "Contractor grants Client a perpetual, non-exclusive, worldwide license to use the Deliverables for [specified purpose]. Contractor retains ownership of all underlying intellectual property."

Also address:

Third-party assets: who's responsible for licensing stock photos, fonts, plugins, APIs? Usually the client, but spell it out.
Portfolio rights: "Contractor may display the completed work in Contractor's portfolio and marketing materials" — clients can and do try to prohibit this if you don't address it upfront.

5. Revision and Change Order Process

Define:

How many rounds of revisions are included
What constitutes a "revision" vs. a "new request" (scope change)
How change orders are priced and approved (in writing)
What happens to the timeline if a change order is approved

The cleanest structure: "Up to 3 rounds of revisions are included. A revision round is defined as a single set of consolidated feedback. Additional revision rounds beyond the included 3 are billed at $[rate] per hour, approved in writing before work begins."

Without this, clients assume revision is infinite. With it, you have a contractual basis for billing the work they added.

6. Termination and Kill Fee

What happens if the client cancels? What if you need to exit?

Client cancellation: Client may terminate the project at any time. Upon termination: (a) work to date is due; (b) client owes the kill fee structure described in the contract (e.g., 50% of remaining project fee if cancelled after design approval).

Contractor termination: Contractor may terminate if client fails to pay any invoice within 15 days of written notice, or materially breaches this agreement. Upon termination, contractor delivers all completed work and client owes for all work completed to date.

What happens to deliverables: Typically, the client gets what's been paid for. Work in progress that hasn't been paid for stays with the contractor until payment is made.

Clauses That Often Get Left Out (and Shouldn't)

Beyond the six core sections, these clauses prevent specific painful situations:

Governing law and jurisdiction: Which state's law applies? Where is any dispute resolved? Without this, multi-state disputes get complicated fast. Pick your state; add it to the contract.

Dispute resolution: Some contracts require mediation before litigation, which saves money. Others go straight to arbitration (binding, private, usually faster and cheaper than court). Specify this before you need it.

Independent contractor status: A brief clause confirming you're an independent contractor, not an employee — you control your methods, your schedule, and your tools. This doesn't bulletproof you against misclassification claims (the actual facts do), but it establishes mutual intent.

Non-solicitation (limited): Prevents the client from hiring your subcontractors directly. Usually 12–24 months. Relevant if you use dedicated subs whose relationships you've built.

Indemnification: Each party indemnifies the other for their own errors. Client indemnifies you for claims arising from client-provided content. You indemnify the client for claims arising from your work (if you used unlicensed assets, etc.).

Limitation of liability: Caps your liability at the total fees paid under the contract. Without this, if your work causes a client business problem, they could theoretically sue for consequential damages far exceeding your fee.

The Proposal-to-Contract Workflow

The cleanest workflow in practice:

Send a proposal with detailed scope, price, and timeline — but no signature block
Client approves the proposal verbally or via email
Send the contract incorporating the approved scope, with a signature block
Client signs and returns the contract
Client pays the deposit per payment terms
You start work only after step 5

Every contractor who starts work before deposit payment creates an unnecessary risk. "They seemed trustworthy" is not a substitute for "they paid."

For recurring clients on retainer, replace the per-project workflow with a master service agreement that covers standing terms, plus a simple statement of work each month specifying that month's deliverables and payment.

Where to Start

If you're writing your first contract, the fastest approach: use a reputable template (many states have bar association resources; freelancer organizations like Freelancers Union and AIGA publish solid templates). Edit the template to match your specific scope, payment terms, and state. Have an attorney review it once, pay $300–$500 for that review, and then use the reviewed version for the next 5 years.

The Proposal OS teardown sprint on Reise walks through the proposal-to-contract conversion in more detail, including scope definition, pricing presentation, and the follow-up sequence that gets agreements signed faster.

The contract is the foundation. Everything else — the proposal, the pricing conversation, the client relationship — sits on top of it. Get the foundation right once.